[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-dev
Subject:    Sub-modules viability (was: [Vote] Considering mod_bmx for adoption by HTTP Server Project)
From:       William A Rowe Jr <wrowe () rowe-clan ! net>
Date:       2016-11-30 20:25:37
Message-ID: CACsi253oXihFs-exaLxKLfUvD0zMYkFhW9c5hPDvpMo8GAhESw () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 30, 2016 at 2:05 PM, Jim Jagielski <jim@jagunet.com> wrote:

>
> Module sub-modules NEVER get the love and attention they need
> and warrant
>

It would be interesting to see this applied to fcgid on a fast-track.
I don't know that ftp warrants it this moment. I don't know why arm4
is still one of our repositories with never-a-release.

I made the direct-to-trunk-backport-2.4 proposal based on the efforts
of Stefan who has continued to maintain a buildable external third
party module of mod_h2, while keeping it in-sync with httpd 2.4.

Maybe it is the better model. Older httpd flavors don't get the patch
attention and backport considerations they need. Independently,
Stefan can maintain a viable third party plug-in module for older flavors
of httpd, but it can move forward with httpd core. No waiting on any
backport votes, it simply happens when Stefan has cycles to do it.

Contrawise, mod_h2 plugable add-on could have become a modules
sub-project and available from the ASF. Either way, there is some level
of synchronization required. Since Stefan is doing that all, it's truly
his choice of what is simplest.

Likewise, I'm happy to ensure mod_bmx on github continues to be
a viable plug-in to httpd-2.2 or 2.4, and carry back the AL commits
to the trunk/2.4 branch efforts at httpd.

Having maintained a few sub-modules with mixed success, I'd be
happy to see us retire the model, it simply doesn't work any better
than landing on the perpetual 2.4.x release side-track. It seems like
the entire effort has slipped the rail, but more on that in a few weeks
when 2.4.24 is put to bed. In the meantime, there seems to already
be consensus to shift mod_fcgid as well to trunk/.

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Nov 30, 2016 \
at 2:05 PM, Jim Jagielski <span dir="ltr">&lt;<a href="mailto:jim@jagunet.com" \
target="_blank">jim@jagunet.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><br> Module sub-modules NEVER get the love and attention they \
need<br> and warrant<br></blockquote><div><br></div><div>It would be interesting to \
see this applied to fcgid on a fast-track.</div><div>I don&#39;t know that ftp \
warrants it this moment. I don&#39;t know why arm4</div><div>is still one of our \
repositories with never-a-release.</div><div><br></div><div>I made the \
direct-to-trunk-backport-2.4 proposal based on the efforts</div><div>of Stefan who \
has continued to maintain a buildable external third</div><div>party module of \
mod_h2, while keeping it in-sync with httpd 2.4.</div><div><br></div><div>Maybe it is \
the better model. Older httpd flavors don&#39;t get the patch</div><div>attention and \
backport considerations they need. Independently,</div><div>Stefan can maintain a \
viable third party plug-in module for older flavors</div><div>of httpd, but it can \
move forward with httpd core. No waiting on any</div><div>backport votes, it simply \
happens when Stefan has cycles to do it.</div><div><br></div><div>Contrawise, mod_h2 \
plugable add-on could have become a modules  </div><div>sub-project and available \
from the ASF. Either way, there is some level</div><div>of synchronization required. \
Since Stefan is doing that all, it&#39;s truly</div><div>his choice of what is \
simplest.</div><div><br></div><div>Likewise, I&#39;m happy to ensure mod_bmx on \
github continues to be</div><div>a viable plug-in to httpd-2.2 or 2.4, and carry back \
the AL commits</div><div>to the trunk/2.4 branch efforts at \
httpd.</div><div><br></div><div>Having maintained a few sub-modules with mixed \
success, I&#39;d be  </div><div>happy to see us retire the model, it simply \
doesn&#39;t work any better</div><div>than landing on the perpetual 2.4.x release \
side-track. It seems like<br></div><div>the entire effort has slipped the rail, but \
more on that in a few weeks</div><div>when 2.4.24 is put to bed. In the meantime, \
there seems to already</div><div>be consensus to shift mod_fcgid as well to \
trunk/.</div><div><br></div><div><br></div><div><br></div><div><br></div></div></div></div>




[prev in list] [next in list] [prev in thread] [next in thread]