Re: URL Spec WorkMode

[offlist]

I notice that you are on GitHub.  One thing I encourage you to do is to 
directly edit:

https://github.com/webspecs/url/blob/develop/docs/workmode.md

Expand the proposal, fix mistakes, correct typos -- everything is fair game.

This will result in pull requests, but pretty much anything that doesn't 
unnecessarily cause somebody to come unglued I'll take.

The same thing is true for the working draft:

https://github.com/w3ctag/url/tree/develop

Change the copyright, status, metadata at the top of url.bs.  Heck, if 
you feel so inclined, change the spec itself.

I'm making the same suggestion to Wendy.  I'd love for the end result to 
be a truly joint proposal.

- Sam Ruby

On 12/02/2014 10:28 AM, Sam Ruby wrote:
> On 12/02/2014 09:23 AM, chaals@yandex-team.ru wrote:
>> TL;DR: The administrative hold-ups are now all my fault, so I'm sorry
>> if they persist, and I will start working to remove them...
>
> Thanks in advance for helping clear administrative obstacles!
>
>> (other stuff later)
>>
>> 02.12.2014, 15:57, "Sam Ruby" <rubys@intertwingly.net>:
>>
>>> What is the hold-up for publishing a Public Working Draft?
>>
>> It has been that the chairs have been pretty busy, and we dropped the
>> ball between us. More recently, we sorted that out so the hold up is
>> now me.
>
> For discussion purposes:
>
> https://rawgit.com/w3ctag/url/develop/url.html
>
>>>   Can I ask that you respond to the following email?
>>
>> Yes. That's a very fair request. I may be able to do so tonight…
>>
>>> http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0315.html
>>>
>>> Let me know what I need to do.
>>>>   Webapps still generally works under the 2005 version of the Process -
>>>>   but we could change this document to the 2014 process. The only
>>>>   really noticeable difference will be that there is formally no "Last
>>>>   Call", and the final Patent Exclusion opportunity is instead for the
>>>>   draft published as Candidate Recommendation. (In other words, you
>>>>   need to be pretty bureaucratically-minded to notice a difference).
>>>
>>> Lets update to 2014 now.  Its only a matter of time before not updating
>>> won't be an option any more.
>>
>> Works for me. I'll start a Call for Consensus - but I imagine it will
>> be a formality.
>>
>> Cheers
>>
>> Chaals
>>
>> --
>> Charles McCathie Nevile - web standards - CTO Office, Yandex
>> chaals@yandex-team.ru - - - Find more at http://yandex.com
>
> - Sam Ruby
>

Received on Tuesday, 2 December 2014 21:38:25 UTC