Re: Relaxing mailing list requirement

--001a113ce412807198053a6d075d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I actually took Martin's comment to be about some scripts that are *used*
by github that are non-free.  But maybe I am confused.

Regardless, I am open to this change to pubrules.  Basically allow each
group to designate a tracker.  I suppose we could maintain a list of
approved ones and a process for getting new ones included.

On Fri, Aug 19, 2016 at 2:24 AM, Marcos Caceres <[email protected]> wrote:

> On August 19, 2016 at 5:07:19 PM, Martin J. D=C3=BCrst
> ([email protected]) wrote:
> > On 2016/08/19 15:30, Marcos Caceres wrote:
> > > As a community, we've increasingly shifted away from gathering
> > > spec-related feedback via mailing lists. Unfortunately, PubRules stil=
l
> > > requires us to include a link to a mailing list in the boilerplate of
> > > a spec.
> > >
> > > I'm wondering if we could relax the mailing list requirement? Instead=
,
> > > make it optional to gather feedback either through a mailing list or
> > > an issue tracker (e.g., Github issues).
> >
> > There are people (not me) who object to the use of sites such as github
> > because it forces them to use non-free JavaScript.
>
> I'm pretty sure JavaScript is free :) Also, JS is part of the Web.
> Disabling JS would be like going around looking at .java files and
> then complaining that they don't work as expected because they haven't
> been compiled.
>
> To those people: =C2=AF\_(=E3=83=84)_/=C2=AF
>
> > Also, there are people (including me) who find github highly suboptimal
> > for issue tracking, because e.g. mail notifications contain virtually n=
o
> > context.
>
> Such projects are usually lacking good collaboration practices: like,
> quoting the original person who posted. However, it's just as easy to
> make the same mistake on email - just ask anyone who has been in a WG
> with people who use Outlook or the wrath we bring on those who
> top-post.
>
> This is why I propose having options for both or either. Groups/specs
> would be free to choose - but linking to a issue trackers would better
> reflect reality.
>
> Kind regards,
> Marcos
>
>


--=20
Shane McCarron
Projects Manager, Spec-Ops

--001a113ce412807198053a6d075d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I actually took Martin&#39;s comment to be about some scri=
pts that are *used* by github that are non-free.=C2=A0 But maybe I am confu=
sed.<div><br></div><div>Regardless, I am open to this change to pubrules.=
=C2=A0 Basically allow each group to designate a tracker.=C2=A0 I suppose w=
e could maintain a list of approved ones and a process for getting new ones=
 included.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Fri, Aug 19, 2016 at 2:24 AM, 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">On August 19, 2016 =
at 5:07:19 PM, Martin J. D=C3=BCrst<br>
<span class=3D"">(<a href=3D"mailto:[email protected]">[email protected]=
a.ac.jp</a>) wrote:<br>
&gt; On 2016/08/19 15:30, Marcos Caceres wrote:<br>
&gt; &gt; As a community, we&#39;ve increasingly shifted away from gatherin=
g<br>
&gt; &gt; spec-related feedback via mailing lists. Unfortunately, PubRules =
still<br>
&gt; &gt; requires us to include a link to a mailing list in the boilerplat=
e of<br>
&gt; &gt; a spec.<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m wondering if we could relax the mailing list requirement?=
 Instead,<br>
&gt; &gt; make it optional to gather feedback either through a mailing list=
 or<br>
&gt; &gt; an issue tracker (e.g., Github issues).<br>
&gt;<br>
&gt; There are people (not me) who object to the use of sites such as githu=
b<br>
&gt; because it forces them to use non-free JavaScript.<br>
<br>
</span>I&#39;m pretty sure JavaScript is free :) Also, JS is part of the We=
b.<br>
Disabling JS would be like going around looking at .java files and<br>
then complaining that they don&#39;t work as expected because they haven&#3=
9;t<br>
been compiled.<br>
<br>
To those people:=C2=A0=C2=AF\_(=E3=83=84)_/=C2=AF<br>
<span class=3D""><br>
&gt; Also, there are people (including me) who find github highly suboptima=
l<br>
&gt; for issue tracking, because e.g. mail notifications contain virtually =
no<br>
&gt; context.<br>
<br>
</span>Such projects are usually lacking good collaboration practices: like=
,<br>
quoting the original person who posted. However, it&#39;s just as easy to<b=
r>
make the same mistake on email - just ask anyone who has been in a WG<br>
with people who use Outlook or the wrath we bring on those who<br>
top-post.<br>
<br>
This is why I propose=C2=A0having options for both or either. Groups/specs<=
br>
would be free to choose - but linking to a issue trackers would better<br>
reflect reality.<br>
<br>
Kind regards,<br>
Marcos<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv><div dir=3D"ltr">Shane McCarron<div>Projects Manager, Spec-Ops</div></di=
v></div></div></div>
</div>

--001a113ce412807198053a6d075d--