[Status] apreq-*@httpd.a.o mailing lists

--00000000000006136a056de67eff
Content-Type: text/plain; charset="UTF-8"

Seven+ years ago, apreq released our most recent distribution, and the code
was folded into httpd trunk. Since that time, contrast the apreq-dev and
apreq-cvs list activity;

https://lists.apache.org/[email protected]:lte=7y:
https://lists.apache.org/[email protected]:lte=7y:

vs discussion and commit activity indicating apreq on the dev/cvs@httpd
lists;

https://lists.apache.org/[email protected]:lte=7y:apreq
https://lists.apache.org/[email protected]:lte=7y:apreq

I've spent the last few months moderating [email protected], deleting ~5-10
emails/day, and this obviously isn't efficient. But it's also confusing
that dev@ list equally relevant to apreq-dev@. It's also concerning that
any commits on apreq-cvs@ must mirror the commit traffic to httpd trunk
(notices to cvs@ list), the two svn notification lists obscure this
oversight.

I propose we shutter the apreq -dev and -cvs lists, redirecting all further
component/subproject discussion to dev|[email protected], with a final
'see-here:' post to these  two apreq- lists, for further questions and
followup on the active list. Archives will remain available and
http://httpd.apache.org/apreq/ website updated (with a comment to indicate
apreq in the subject line of mailing list posts, and some actually working
archive links.)

If I hear no objection to that plan in the next 72 hours, I'll proceed to
ask infra to reroute all svn notices of
http://svn.apache.org/repos/asf/httpd/apreq/ to the cvs@httpd, and close
both apreq-dev/cvs to new traffic. Archives will be preserved. All
subproject business would occur on dev@httpd, and I will update the website
to make this clear, so there should be no interruption.

If there is objection, let's work through any open concerns first, on this
list.

I suspect there are still significant decisions to be made about the state
of apreq subproject, but these are best addressed by the larger community
at dev@httpd to get the maximum possible participation and consensus.

Yours,

Bill

--00000000000006136a056de67eff
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Seven+ years ago, apreq released our most recent dist=
ribution, and the code was folded into httpd trunk. Since that time, contra=
st the apreq-dev and <span style=3D"color:rgb(34,34,34);font-family:arial,s=
ans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;f=
ont-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:st=
art;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px=
;background-color:rgb(255,255,255);text-decoration-style:initial;text-decor=
ation-color:initial;float:none;display:inline">apreq-</span>cvs list activi=
ty;</div><div><br></div><div><div style=3D"color:rgb(34,34,34);font-family:=
arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:n=
ormal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-a=
lign:start;text-indent:0px;text-transform:none;white-space:normal;word-spac=
ing:0px;text-decoration-style:initial;text-decoration-color:initial"><a hre=
f=3D"https://lists.apache.org/[email protected]:lte=3D7y=
">https://lists.apache.org/[email protected]:lte=3D7y</a=
>:</div><a href=3D"https://lists.apache.org/[email protected]=
e.org:lte=3D7y">https://lists.apache.org/[email protected]=
rg:lte=3D7y</a>:</div><div><br class=3D"gmail-Apple-interchange-newline">vs=
 discussion and commit activity indicating=C2=A0<span style=3D"color:rgb(34=
,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font=
-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-s=
pacing:normal;text-align:start;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decorati=
on-style:initial;text-decoration-color:initial;float:none;display:inline">a=
preq on the dev/cvs@httpd lists;</span></div><div><br></div><div><a href=3D=
"https://lists.apache.org/[email protected]:lte=3D7y:apreq">ht=
tps://lists.apache.org/[email protected]:lte=3D7y:apreq</a><br=
></div><div><a href=3D"https://lists.apache.org/[email protected].=
org:lte=3D7y:apreq">https://lists.apache.org/[email protected]=
:lte=3D7y:apreq</a><br></div><div><br></div><div>I&#39;ve spent the last fe=
w months moderating [email protected], deleting ~5-10 emails/day, and this ob=
viously isn&#39;t efficient. But it&#39;s also confusing that dev@ list equ=
ally relevant to apreq-dev@. It&#39;s also concerning that any commits on a=
preq-cvs@ must mirror the commit traffic to httpd trunk (notices to cvs@ li=
st), the two svn notification lists obscure this oversight.<br></div><div><=
br></div><div>I propose we shutter the apreq -dev and -cvs lists, redirecti=
ng all further component/subproject discussion to dev|[email protected], with a=
 final &#39;see-here:&#39; post to these=C2=A0<span style=3D"color:rgb(34,3=
4,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-v=
ariant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spa=
cing:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration=
-style:initial;text-decoration-color:initial;float:none;display:inline"><sp=
an>=C2=A0</span>two apreq- lists,</span> for further questions and followup=
 on the active list. Archives will remain available and <a href=3D"http://h=
ttpd.apache.org/apreq/">http://httpd.apache.org/apreq/</a>=C2=A0website upd=
ated (with a comment to indicate apreq in the subject line of mailing list =
posts, and some actually working archive links.)</div><div><br></div><div>I=
f I hear no objection to that plan in the next 72 hours, I&#39;ll proceed t=
o ask infra to reroute all svn notices of <a href=3D"http://svn.apache.org/=
repos/asf/httpd/apreq/">http://svn.apache.org/repos/asf/httpd/apreq/</a> to=
 the cvs@httpd, and close both apreq-dev/cvs to new traffic. Archives will =
be preserved. All subproject business would occur on dev@httpd, and I will =
update the website to make this clear, so there should be no interruption.<=
/div><div><br></div><div>If there is objection, let&#39;s work through any =
open concerns first, on this list.</div><div><br></div><div>I suspect there=
 are still significant decisions to be made about the state of apreq subpro=
ject, but these are best addressed by the larger community at dev@httpd to =
get the maximum possible participation and consensus.</div><div><br></div><=
div>Yours,</div><div><br></div><div>Bill</div><div><br></div></div>

--00000000000006136a056de67eff--