- From: Shane McCarron <shane@spec-ops.io>
- Date: Mon, 13 Jun 2016 16:15:36 -0500
- To: Ivan Herman <ivan@w3.org>
- Cc: Robert Sanderson <azaroth42@gmail.com>, W3C Public Annotation List <public-annotation@w3.org>
- Message-ID: <CAJdbnOBPmupUwiNu1BpnceFy=ik10q8Z_weMdTKx7NN3HRSN-w@mail.gmail.com>
After much to-ing and fro-ing, I eventually decided to put the documents in the Spec-Ops repo right now, with the knowledge that the final versions will be in the Web Platform Tests repo once peer review completes. Since I have no control over that process and have no idea how long it will take... I didn't want it to be an impediment. I have updated the main README.md at [1] to briefly explain what is going on and then point to the two documents - noting that their location will migrate at some point. This indirection means we can just update the document at [1] when the documents move, and can proceed with CR review by pointing to [1], knowing that the readers can drill down from there. [1] https://github.com/w3c/web-annotation-tests/blob/master/README.md Sorry this is so complicated. We are all learning a new thing here! On Sat, Jun 11, 2016 at 7:50 AM, Ivan Herman <ivan@w3.org> wrote: > > On 11 Jun 2016, at 13:44, Shane McCarron <shane@spec-ops.io> wrote: > > I don't mind using the README.... we will need 3 of them, which is fine. > > There is a small problem. You guys set up an independent test repo outside > of Web Platform Tests. The place you really want this stuff is in the web > platform test repo [1]. But that repo does not use gh-pages :( They can > also be in the runner location (web-tests.org). That might make sense. > Again, I am going to ask the #testing people if that is appropriate. There > are very few examples of this in that location today. > > > Like for the other question: whatever is simpler, that is my only guiding > principle. If, for whatever reason, we do not use the separate test repo, > we can just scrap it, too! You guys decide. > > As for not gh-pages: I guess that is why the almighty invented rawgit:-) > > Ivan > > > > For right now I am just going to write them up... except that I have no > idea how the protocol testing is really going to work. I will make that up > as I write. Unless you want to take a shot at explaining it in WPT terms, > Benjamin? > > On Fri, Jun 10, 2016 at 11:39 PM, Ivan Herman <ivan@w3.org> wrote: > >> >> On 10 Jun 2016, at 19:31, Robert Sanderson <azaroth42@gmail.com> wrote: >> >> >> How about in https://github.com/w3c/web-annotation/tree/gh-pages/admin ? >> >> >> Not sure. I regard admin as collecting things that are really of interest >> for, well, administrative steps, essentially transitions and publication. I >> would expect this document to be of interest for a wider set of people, >> whoever wants to implement or test… >> >> I wonder whether this should not be on the top level of the test >> repository. Maybe even the README of that repo? >> >> Ivan >> >> >> R >> >> On Fri, Jun 10, 2016 at 10:27 AM, Shane McCarron <shane@spec-ops.io> >> wrote: >> >>> I considered putting it in the web-annotation-tests repo, but that is >>> only really for the data model as we have it structured currently. >>> >>> I am in the process of writing it, but if someone could recommend a home? >>> >>> -- >>> Shane McCarron >>> Projects Manager, Spec-Ops >>> >> >> >> >> -- >> Rob Sanderson >> Semantic Architect >> The Getty Trust >> Los Angeles, CA 90049 >> >> >> >> ---- >> Ivan Herman, W3C >> Digital Publishing Lead >> Home: http://www.w3.org/People/Ivan/ >> mobile: +31-641044153 >> ORCID ID: http://orcid.org/0000-0003-0782-2704 >> >> >> >> >> > > > -- > Shane McCarron > Projects Manager, Spec-Ops > > > > ---- > Ivan Herman, W3C > Digital Publishing Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 > ORCID ID: http://orcid.org/0000-0003-0782-2704 > > > > > -- Shane McCarron Projects Manager, Spec-Ops
Received on Monday, 13 June 2016 21:16:32 UTC