Repos and specs Re: [admin] Web Platform WG is the new WebApps

------------F9y71RcY9xruqGXX8DjanW
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit

On Mon, 12 Oct 2015 18:48:31 +0200, Johannes Wilm  
<[email protected]> wrote:

> Hey,
> thanks for the info.
>
> As I understand it, this has no practical impact on the editing  
> taskforce and these are more suggestions for future task forces, right?

That is how I understand it too.

> As for separate repositories: We have changed the number and names of  
> the specs we need numerous times now. If we create and delete a  
> repository every time we change the name or >the numbers and types of  
> specs, it would have turned into a complete mess.

Yes. I think the point isn't that every document written needs a new repo,  
but that mixing two different things like Web Messaging and  
ContentEditable in the same repo is a bad idea.
>
> Essentially we only have one single work item which is editing. We  
> should now now be very far away from being very clear on the names of  
> some of at least one the specs (the one >containing beforeEdit/Edit or  
> beforeInput/Input), and once that happens, I would be all for moving it  
> to it's own repository if we are clear that this these events will also  
> be added to old >contentEditable elements, text areas, input fields,  
> etc. .
> We couldn't do that hitherto because as late as late August it was  
> suggested we merge that spec with some of the other specs.

Yeah. We might work out how to split out editing into separate work items,  
but that isn't the highest priority work.

Note that we also haven't worked out properly what to do with HTML, which  
is clearly far too much stuff to have in one repo, beyond noting that "it  
is clearly too big to be a single work item"...

cheers

Chaals

>
>
>
>
> On Mon, Oct 12, 2015 at 6:23 PM, Marcos Caceres <[email protected]> wrote:
>>
>>
>>
>>
>>>> On October 12, 2015 at 8:23:25 AM, Arthur Barstow  
>>>> ([email protected]) wrote:
>>> Hi All,
>>>
>>> On October 10, the consortium formerly started the Web Platform WG
>>> [Charter] thus terminating WebApps.
>>>
>>> My expectation is this change will have little to no impact on any work
>>> started in WebApps. That said, please note the charter indicates
>>> WebApps' less developed specs (f.ex. the Editing specs) need some
>>> "incubation" before they may proceed on the Recommendation track.
>>> However, that was effectively how WebApps operated so I don't see this
>>> as a change - a spec still needs implementation commitments before
>>> advancing to the later Recommendation stages.
>>
>> For incubation, members are welcomed to bring their specs Web Incubator  
>> CG:
>> http://github.com/wicg
>>
>> The WICG can help members get specs into shape and connect them with  
>> developers and other implementers. It's a fast, IPR friendly way, to  
>> get ideas road-tested before formal >>standardization.
>>>>> The WPWG has its own Github repo [Github] and the group will not use
>>> W3C's wiki. (Only a small number of WebApps' Editors actively use W3C
>>> wiki documents (primarily IDB v2 features, Pointer Lock v2 features,
>>> Gamepad v2 features, and D3E) and I will work with those Editors to  
>>> move
>>> their relevant wiki information to their spec's repo.)
>>
>> Please please please (please!), don't use a single repository as a  
>> dumpling ground for spec - it makes it impossible for people to follow  
>> individual work items, file bugs, etc.. Please use >>separate  
>> repositories for each work item.
>>
>> I would suggest maybe making your own organization on Github, and then  
>> managing your specs through that. Again, see:
>> http://github.com/wicg
>>
>>
>>
>
>
>
> --Johannes Wilm
> Fidus Writer
> http://www.fiduswriter.org



-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
[email protected] - - - Find more at http://yandex.com
------------F9y71RcY9xruqGXX8DjanW
Content-Type: multipart/related; boundary=----------F9y71RcY9xruqGTZVpRLIo

------------F9y71RcY9xruqGTZVpRLIo
Content-Type: text/html; charset=utf-8
Content-ID: <[email protected]>
Content-Transfer-Encoding: Quoted-Printable

<!DOCTYPE html><html><head>
<style type=3D"text/css">body { font-family:'Helvetica'; font-size:12px}=
</style>
</head>
<body>On Mon, 12 Oct 2015 18:48:31 +0200, Johannes Wilm &lt;johannes@fid=
uswriter.org&gt; wrote:<br><br><blockquote style=3D"margin: 0 0 0.80ex; =
border-left: #0000FF 2px solid; padding-left: 1ex"><div dir=3D"ltr">Hey,=
<div>thanks for the info.</div><div><br></div><div>As I understand it, t=
his has no practical impact on the editing taskforce and these are more =
suggestions for future task forces, right?&nbsp;</div></div></blockquote=
><div><br></div><div>That is how I understand it too.<br></div><div><br>=
</div><blockquote style=3D"margin: 0 0 0.80ex; border-left: #0000FF 2px =
solid; padding-left: 1ex"><div dir=3D"ltr"><div>As for separate reposito=
ries: We have changed the number and names of the specs we need numerous=
 times now. If we create and delete a repository every time we change th=
e name or the numbers and types of specs, it would have turned into a co=
mplete mess.</div></div></blockquote><div><br></div><div>Yes. I think th=
e point isn't that every document written needs a new repo, but that mix=
ing two different things like Web Messaging and ContentEditable in the s=
ame repo is a bad idea.</div><blockquote style=3D"margin: 0 0 0.80ex; bo=
rder-left: #0000FF 2px solid; padding-left: 1ex"><div dir=3D"ltr"><div><=
br></div><div>Essentially we only have one single work item which is edi=
ting. We should now now be very far away from being very clear on the na=
mes of some of at least one the specs (the one containing beforeEdit/Edi=
t or beforeInput/Input), and once that happens, I would be all for movin=
g it to it's own repository if we are clear that this these events will =
also be added to old contentEditable elements, text areas, input fields,=
 etc. .&nbsp;</div><div><br></div><div>We couldn't do that hitherto beca=
use as late as late August it was suggested we merge that spec with some=
 of the other specs.</div></div></blockquote><div><br></div><div>Yeah. W=
e might work out how to split out editing into separate work items, but =
that isn't the highest priority work.</div><div><br></div><div>Note that=
 we also haven't worked out properly what to do with HTML, which is clea=
rly far too much stuff to have in one repo, beyond noting that "it is cl=
early too big to be a single work item"...</div><div><br></div><div>chee=
rs</div><div><br></div><div>Chaals</div><div><br></div><blockquote style=
=3D"margin: 0 0 0.80ex; border-left: #0000FF 2px solid; padding-left: 1e=
x"><div dir=3D"ltr"><div><br></div><div><br></div><div><br></div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Oct 12,=
 2015 at 6:23 PM, Marcos Caceres <span dir=3D"ltr">&lt;<a href=3D"mailto=
:[email protected]" target=3D"_blank">[email protected]</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
<br>
<br>
On October 12, 2015 at 8:23:25 AM, Arthur Barstow (<a href=3D"mailto:art=
[email protected]">[email protected]</a>) wrote:<br>
&gt; Hi All,<br>
&gt;<br>
&gt; On October 10, the consortium formerly started the Web Platform WG<=
br>
&gt; [Charter] thus terminating WebApps.<br>
&gt;<br>
&gt; My expectation is this change will have little to no impact on any =
work<br>
&gt; started in WebApps. That said, please note the charter indicates<br=
>
&gt; WebApps' less developed specs (f.ex. the Editing specs) need some<b=
r>
&gt; "incubation" before they may proceed on the Recommendation track.<b=
r>
&gt; However, that was effectively how WebApps operated so I don't see t=
his<br>
&gt; as a change - a spec still needs implementation commitments before<=
br>
&gt; advancing to the later Recommendation stages.<br>
<br>
</span>For incubation, members are welcomed to bring their specs Web Inc=
ubator CG:<br>
<a href=3D"http://github.com/wicg" rel=3D"noreferrer" target=3D"_blank">=
http://github.com/wicg</a><br>
<br>
The WICG can help members get specs into shape and connect them with dev=
elopers and other implementers. It's a fast, IPR friendly way, to get id=
eas road-tested before formal standardization.&nbsp;<br>
<span class=3D""><br>
&gt; The WPWG has its own Github repo [Github] and the group will not us=
e<br>
&gt; W3C's wiki. (Only a small number of WebApps' Editors actively use W=
3C<br>
&gt; wiki documents (primarily IDB v2 features, Pointer Lock v2 features=
,<br>
&gt; Gamepad v2 features, and D3E) and I will work with those Editors to=
 move<br>
&gt; their relevant wiki information to their spec's repo.)<br>
<br>
</span>Please please please (please!), don't use a single repository as =
a dumpling ground for spec - it makes it impossible for people to follow=
 individual work items, file bugs, etc.. Please use separate repositorie=
s for each work item.<br>
<br>
I would suggest maybe making your own organization on Github, and then m=
anaging your specs through that. Again, see:<br>
<a href=3D"http://github.com/wicg" rel=3D"noreferrer" target=3D"_blank">=
http://github.com/wicg</a><br>
&nbsp;<br>
<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div clas=
s=3D"gmail_signature"><div dir=3D"ltr"><div style=3D"font-size:small;fon=
t-family:arial">Johannes Wilm<br></div><div style=3D"font-size:small;fon=
t-family:arial">Fidus Writer</div><div style=3D"font-size:small;font-fam=
ily:arial"><a href=3D"http://www.fiduswriter.org/" target=3D"_blank">htt=
p://www.fiduswriter.org</a></div></div></div>
</div>
</blockquote><br><br><br><div id=3D"M2Signature"><div>-- </div><div>Char=
les McCathie Nevile - web standards - CTO Office, Yandex<br> chaals@yand=
ex-team.ru - - - Find more at <a href=3D"http://yandex.com">http://yande=
x.com</a></div></div></body></html>
------------F9y71RcY9xruqGTZVpRLIo--

------------F9y71RcY9xruqGXX8DjanW--