Re: Using Github for HTTP2

Works! Thanks.


On Sun, Feb 10, 2013 at 2:10 AM, Mark Nottingham <mnot@mnot.net> wrote:

> Try now.
>
> Cheers,
>
>
> On 10/02/2013, at 6:46 PM, William Chan (陈智昌) <willchan@chromium.org>
> wrote:
>
> > OK, I'm a newb at this stuff. Halp? :)
> >
> > willchan-macbookair:http2-spec willchan$ make -e
> draft-ietf-httpbis-http2.html
> > java -classpath ~/java/saxonb8-9-0-4j/saxon8.jar
> > net.sf.saxon.Transform -novw -l draft-ietf-httpbis-http2.xml
> > lib/myxml2rfc.xslt > draft-ietf-httpbis-http2.html
> > Error at xsl:import on line 4 of
> >
> file:/Users/willchan/src/github/willchan_chromium/http2-spec/lib/myxml2rfc.xslt:
> >  XTSE0165: java.io.FileNotFoundException:
> >
>  /Users/willchan/src/github/willchan_chromium/http2-spec/rfc2629xslt/rfc2629.xslt
> > (No such
> >  file or directory)
> > Failed to compile stylesheet. 1 error detected.
> > make: *** [draft-ietf-httpbis-http2.html] Error 2
> > willchan-macbookair:http2-spec willchan$ ls
> > Makefile README.md SUBMITTING.md draft-ietf-httpbis-http2.html
> > draft-ietf-httpbis-http2.xml lib
> > willchan-macbookair:http2-spec willchan$ ls lib
> > clean-for-DTD.xslt myxml2rfc.xslt rfc2629.xslt
> >
> > On Thu, Feb 7, 2013 at 6:15 PM, Mark Nottingham <mnot@mnot.net> wrote:
> >> For the HTTP/1.1 work, we've used the IETF's infrastructure on
> tools.ietf.org -- mostly, the SVN repository and the Trac instance for
> issue tracking.
> >>
> >> After briefly discussing it in Tokyo and conferring with the editors
> and our AD, we've moved the source for the HTTP/2 draft and related issues
> to Github.
> >>
> >> There are a couple of reasons for this. First of all, we would like to
> encourage participation from a broader audience, and more implementers have
> github accounts and are familiar with that workflow, vs. IETF tools
> accounts. Furthermore, we've had a few requests from people that want to
> fork the specification for experimentation, to be used as potential input
> to our work (as pull requests). Finally, our editors have expressed some
> preference for working with Git over SVN.
> >>
> >> As such, this isn't a problem with the IETF tools themselves (which are
> well-supported and have been very useful to date); it's more driven by the
> specific situation we're in.
> >>
> >> So, see:
> >>  https://github.com/http2/http2-spec
> >>
> >> I'm now in the process of closing the relevant Trac issues and
> adjusting our wiki to point to the relevant places.
> >>
> >> Note that this is itself an experiment; e.g., we may need to establish
> some process around issue handling, especially, if the input there gets out
> of hand.
> >>
> >> Also, note that this does NOT affect any of our work on HTTP/1.1; that
> will remain at the IETF tools site.
> >>
> >> Cheers,
> >>
> >>
> >> --
> >> Mark Nottingham   http://www.mnot.net/
> >>
> >>
> >>
> >>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>