You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mod-auth-external was originally written by Nathan Neulinger, who passed
maintenance to Tyler Allison. I've been the maintainer for nearly 15 years now.
I've pretty much completely rewritten it more than once as Apache has evolved.
It's been years since I've done any active development, beyond just keeping up
with changes in Apache, and lately I haven't done the latter very well. I don't
actually maintain any production servers these days. To test mod-auth-external,
I set up a dummy server on my desktop linux box to work as a test bed.
I moved this project into code.google.com partly in hopes of smoothing the
transition to a new maintainer when the time comes to do so. I think that the
time has come for someone else to take the job.
At a minimum, the job entails updating mod-auth-external each time Apache
modifies their API, which is really just a few times a year. I think there are
possibilities for new development - such as supporting authentication daemons -
but I don't think there is any clamor for that. I get user questions at a rate
of about ten to twelve a year, which I try to answer to the best of my ability.
So this is not a huge job.
You'd also be taking over support of mod_authz_unixgroup and probably pwauth.
Though possibly different people could maintain different parts. In fact, it
might not be a bad idea to have more than one maintainer. This google code
system certainly makes that easy.
Anyway, I'd appreciate hearing from volunteers. This is hardly the cutting edge
of open source software, but it's still useful and widely used.
Original issue reported on code.google.com by [email protected] on 12 Dec 2013 at 11:01
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 12 Dec 2013 at 11:01The text was updated successfully, but these errors were encountered: