-
Notifications
You must be signed in to change notification settings - Fork 678
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apache httpd project looking into doing its own implementation #1636
Comments
|
Hi Jim, thanks for the info ! I noted that there are concerns about the GPL2. As this module has never been part of our commercial distribution i think we can move it to a more permissive one and eventually remove it from future releases. Let me know what you think it is better. |
|
Wow! If it would be possible/feasible to "donate" the module to the ASF under the ALv2, that would be incredible. I would be most willing to help in any way. |
|
@jimjam, absolutely this is not a problem (well it would be an honour indeed ;). Is there any procedure to follow or just re-licensing the code and publicly announcing the 'donation' is enough ? |
|
For completeness, for an actual "formal" donation, there is also a small form (a software grant) that would be filed. That also helps w/ the reach of whatever marketing/PR you may want to do regarding the donation. It can also be done simply by, once relicensed, we note on this Issue that you guys are cool w/ the ASF copying the module, as permitted by the ALv2. Even though such permission is never really needed, the ASF has a long standing policy of only using code that the original copyright owners are OK with us using, even if the license would allow us to reuse it no matter what :) |
|
@jimjag the module has been relicensed |
|
That is super great news! Is it OK if I push a copy of the module to the official HTTPD repo, with all attributions intact? |
|
@jimjag yes, for sure |
|
With the relicencing complete, should this ticket now be closed? |
|
Fantastic! Thx! I will start the xfer of the source code to the ASF. Cheers! |
unbit/uwsgi#1636 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1810358 13f79535-47bb-0310-9956-ffa450edef68
|
Backported to httpd v2.4.30. |
- Remove conflict on libexec/apache24/mod_proxy_uwsgi.so - Module is part of www/apache24 as of 2.4.30 see unbit/uwsgi#1636 and https://svn.apache.org/viewvc?view=revision&revision=1810358 PR: 228391 Approved by: maintainer <schmidt ze.tum de> MFH: 2018Q2 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@470602 35697150-7ecd-e111-bb59-0022644237b5
- Remove conflict on libexec/apache24/mod_proxy_uwsgi.so - Module is part of www/apache24 as of 2.4.30 see unbit/uwsgi#1636 and https://svn.apache.org/viewvc?view=revision&revision=1810358 PR: 228391 Approved by: maintainer <schmidt ze.tum de> MFH: 2018Q2 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@470602 35697150-7ecd-e111-bb59-0022644237b5
- Remove conflict on libexec/apache24/mod_proxy_uwsgi.so - Module is part of www/apache24 as of 2.4.30 see unbit/uwsgi#1636 and https://svn.apache.org/viewvc?view=revision&revision=1810358 PR: 228391 Approved by: maintainer <schmidt ze.tum de> MFH: 2018Q2
- Remove conflict on libexec/apache24/mod_proxy_uwsgi.so - Module is part of www/apache24 as of 2.4.30 see unbit/uwsgi#1636 and https://svn.apache.org/viewvc?view=revision&revision=1810358 PR: 228391 Approved by: maintainer <schmidt ze.tum de> MFH: 2018Q2 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@470602 35697150-7ecd-e111-bb59-0022644237b5
unbit/uwsgi#1636 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1810358 13f79535-47bb-0310-9956-ffa450edef68
- Remove conflict on libexec/apache24/mod_proxy_uwsgi.so - Module is part of www/apache24 as of 2.4.30 see unbit/uwsgi#1636 and https://svn.apache.org/viewvc?view=revision&revision=1810358 PR: 228391 Approved by: maintainer <schmidt ze.tum de> MFH: 2018Q2
Just a FYI that the Apache httpd project is looking to create its own uWSGI module for the mod_proxy system (https://lists.apache.org/thread.html/df494432296a598b2213e76cb721e153c9fb36947b5fe9a1a9ac892c@%3Cdev.httpd.apache.org%3E).
Cheers!
The text was updated successfully, but these errors were encountered: