Re: possible interest in forming a community fork of akka
I agree we need a strong enough community to be able to fix the security issues in house. For the security patch release, it's hard for the forked project to keep track of all the security reports. We may only know about the security issue when Lightbend does the release. If the Lightbend employee doesn't submit the security patch PR to the forked project first, we may have some trouble to 'port' those patches to the forked project. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Sep 27, 2022 at 5:55 PM PJ Fanning wrote: > > Thanks Willem for taking the time to look into this. > > The license change means the fork project will not be able to cherry > pick future fixes from Lightbend - at least not readily. > > On a case by case basis, we could request that the PR submitter also > contribute them to the fork project. > > In some cases, the critical fix might be submitted to the fork first > and it may be easier for the Lightbend team to cherry pick those cases > than it is for the fork team to do the opposite. > > The real hope would be that the fork can attract a strong enough > community that any security issues can be fixed in house. > > The core of Akka is quite stable at this point so hopefully critical > bugs should be rare. It's possible that some of the less used non-core > code might be more susceptible to having issues. > > Links for recent security issues in Akka: > * https://doc.akka.io/docs/akka/current/security/index.html > * https://doc.akka.io/docs/akka-http/current/security.html > > > On Tue, 27 Sept 2022 at 02:30, Willem Jiang wrote: > > > > After going through the FAQ of the Akka license, it looks like we > > cannot backport the BSL codes to the Apache License branch. > > > > > If there is a newer version of the software under BSL, can I backport any > > > of the code to an older, Open Source, version of Akka? > > > > > No. In this circumstance, you would either violate Lightbend’s copyright > > > by re-releasing the code under Open Source, or you would violate the > > > earlier Akka version’s Apache license by introducing incompatible BSL > > > code (i.e., code subject to a use limitation not allowed by the Open > > > Source Apache 2.0 license). > > > > It will cause us a lot of effort to maintain the code, even if we just > > want to backport some critical bug fixes. > > > > [1]https://www.lightbend.com/akka/license-faq > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers > > wrote: > > > > > > Before going too far with this I would be interested to know: > > > 1. Who the initial committers/PMC members would be. > > > 2. How much familiarity the proposed people already have with the code > > > base. > > > 3. How diverse the community is from an employment point of view. > > > > > > In other words, I would be concerned if this is pushed by just 3 or 4 > > > people, > > > none of which have ever spent much time in the code, and who all work for > > > the same employer. > > > > > > Ralph > > > > > > > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > > > > > > > Hi everyone, > > > > > > > > Apologies if this is not the right mailing list. If it is not, please > > > > let me know and I'll switch the thread to the right list. > > > > > > > > Lighbend [1], the company that maintains the popular open source > > > > framework, Akka [2], recently announced they are moving Akka to a > > > > non-OSS commercial license [3]. > > > > > > > > There is interest in the OSS community in forking Akka under a new > > > > name and maintaining it as an ASF project [4]. > > > > > > > > It is early days yet but there is some discussion online [5]. > > > > > > > > Reading the incubator cookbook, a new podling would need to have > > > > champions and mentors from within the Incubator PMC [6]. > > > > > > > > I would like to put my name forward for such a role, as an existing > > > > ASF member [7]. > > > > > > > > If anyone else in the Incubator PMC would like to get involved, that > > > > would be great. > > > > > > > > Regards, > > > > PJ > > > > > > > > [1] https://www.lightbend.com/ > > > > [2] https://akka.io/ > > > > [3] https://www.lightbend.com/akka/license-faq > > > > [4] https://github.com/mdedetrich/akka-apache-project > > > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > > > [6] > > > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > > > > > - > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail:
Re: possible interest in forming a community fork of akka
+1 to everything Greg says, although I wouldn’t consider it to be a hostile fork just as I don’t consider the fork of Hudson to Jenkins to be a hostile fork. In my book it isn’t a hostile fork when the major contributors simply switch to the new repository and infrastructure. i.e - if the community largely is staying intact how can it possibly be a fork? You can certainly say the code forked (that happens all the time at GitHub and no one really cares) but what is more important to me is the community. Ralph > On Sep 27, 2022, at 4:23 PM, Greg Stein wrote: > > On Tue, Sep 27, 2022 at 4:55 AM PJ Fanning wrote: >> ... > >> In some cases, the critical fix might be submitted to the fork first >> and it may be easier for the Lightbend team to cherry pick those cases >> than it is for the fork team to do the opposite. >> > > Should an ALv2 fork arise *anywhere*[1], then I believe > Lightbend's community will vaporize. That community will follow the OSS > fork, and Lightbend will be relegated to picking up those ALv2-licensed > patches into their proprietary version. There will simply be no reason for > a community to hang around and contribute their work to the newly-licensed > and proprietary version of Akka. > > Cheers, > -g > > [1] whether at the ASF, or at an external hosting site. Note that, > historically, the ASF has been mostly against forks where the owner(s) > disagree with creating that fork (aka "a hostile fork"). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: possible interest in forming a community fork of akka
On Tue, Sep 27, 2022 at 4:55 AM PJ Fanning wrote: >... > In some cases, the critical fix might be submitted to the fork first > and it may be easier for the Lightbend team to cherry pick those cases > than it is for the fork team to do the opposite. > Should an ALv2 fork arise *anywhere*[1], then I believe Lightbend's community will vaporize. That community will follow the OSS fork, and Lightbend will be relegated to picking up those ALv2-licensed patches into their proprietary version. There will simply be no reason for a community to hang around and contribute their work to the newly-licensed and proprietary version of Akka. Cheers, -g [1] whether at the ASF, or at an external hosting site. Note that, historically, the ASF has been mostly against forks where the owner(s) disagree with creating that fork (aka "a hostile fork").
Re: possible interest in forming a community fork of akka
This seems needed given the state of Lightbend/licensing. Agreed with Roman's sentiment, though getting Lightbend to change at this point seems unlikely [ also, I don't have direct contacts there so am not well positioned to try to negotiate any changes ]. Glad to see people coming together around this. Notably, I imagine the Flink community will have an interest in collaborating [ 1 ]. Happy to help the effort, however I can be useful! Cheers, Austin [1] https://flink.apache.org/news/2022/09/08/akka-license-change.html On Tue, Sep 27, 2022 at 3:32 AM Claude Warren, Jr wrote: > PJ, > > Several of us working on the mdedetrich github projects [1] are preparing > to submit a proposal to the incubator, hopefully by the end of the week. > We have had contact from several individual devlopers, organizations, > projects, and companies about such a project. We identified a champion and > several mentors, we would be happy to add you to our list of mentors. > > Claude > > [1] https://github.com/mdedetrich/akka-apache-project > > On Mon, Sep 26, 2022 at 7:11 PM PJ Fanning wrote: > > > Hi everyone, > > > > Apologies if this is not the right mailing list. If it is not, please > > let me know and I'll switch the thread to the right list. > > > > Lighbend [1], the company that maintains the popular open source > > framework, Akka [2], recently announced they are moving Akka to a > > non-OSS commercial license [3]. > > > > There is interest in the OSS community in forking Akka under a new > > name and maintaining it as an ASF project [4]. > > > > It is early days yet but there is some discussion online [5]. > > > > Reading the incubator cookbook, a new podling would need to have > > champions and mentors from within the Incubator PMC [6]. > > > > I would like to put my name forward for such a role, as an existing > > ASF member [7]. > > > > If anyone else in the Incubator PMC would like to get involved, that > > would be great. > > > > Regards, > > PJ > > > > [1] https://www.lightbend.com/ > > [2] https://akka.io/ > > [3] https://www.lightbend.com/akka/license-faq > > [4] https://github.com/mdedetrich/akka-apache-project > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > [6] > > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: possible interest in forming a community fork of akka
PJ, Several of us working on the mdedetrich github projects [1] are preparing to submit a proposal to the incubator, hopefully by the end of the week. We have had contact from several individual devlopers, organizations, projects, and companies about such a project. We identified a champion and several mentors, we would be happy to add you to our list of mentors. Claude [1] https://github.com/mdedetrich/akka-apache-project On Mon, Sep 26, 2022 at 7:11 PM PJ Fanning wrote: > Hi everyone, > > Apologies if this is not the right mailing list. If it is not, please > let me know and I'll switch the thread to the right list. > > Lighbend [1], the company that maintains the popular open source > framework, Akka [2], recently announced they are moving Akka to a > non-OSS commercial license [3]. > > There is interest in the OSS community in forking Akka under a new > name and maintaining it as an ASF project [4]. > > It is early days yet but there is some discussion online [5]. > > Reading the incubator cookbook, a new podling would need to have > champions and mentors from within the Incubator PMC [6]. > > I would like to put my name forward for such a role, as an existing > ASF member [7]. > > If anyone else in the Incubator PMC would like to get involved, that > would be great. > > Regards, > PJ > > [1] https://www.lightbend.com/ > [2] https://akka.io/ > [3] https://www.lightbend.com/akka/license-faq > [4] https://github.com/mdedetrich/akka-apache-project > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > [6] > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > [7] https://whimsy.apache.org/roster/committer/fanningpj > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: possible interest in forming a community fork of akka
Thanks Willem for taking the time to look into this. The license change means the fork project will not be able to cherry pick future fixes from Lightbend - at least not readily. On a case by case basis, we could request that the PR submitter also contribute them to the fork project. In some cases, the critical fix might be submitted to the fork first and it may be easier for the Lightbend team to cherry pick those cases than it is for the fork team to do the opposite. The real hope would be that the fork can attract a strong enough community that any security issues can be fixed in house. The core of Akka is quite stable at this point so hopefully critical bugs should be rare. It's possible that some of the less used non-core code might be more susceptible to having issues. Links for recent security issues in Akka: * https://doc.akka.io/docs/akka/current/security/index.html * https://doc.akka.io/docs/akka-http/current/security.html On Tue, 27 Sept 2022 at 02:30, Willem Jiang wrote: > > After going through the FAQ of the Akka license, it looks like we > cannot backport the BSL codes to the Apache License branch. > > > If there is a newer version of the software under BSL, can I backport any > > of the code to an older, Open Source, version of Akka? > > > No. In this circumstance, you would either violate Lightbend’s copyright by > > re-releasing the code under Open Source, or you would violate the earlier > > Akka version’s Apache license by introducing incompatible BSL code (i.e., > > code subject to a use limitation not allowed by the Open Source Apache 2.0 > > license). > > It will cause us a lot of effort to maintain the code, even if we just > want to backport some critical bug fixes. > > [1]https://www.lightbend.com/akka/license-faq > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers > wrote: > > > > Before going too far with this I would be interested to know: > > 1. Who the initial committers/PMC members would be. > > 2. How much familiarity the proposed people already have with the code base. > > 3. How diverse the community is from an employment point of view. > > > > In other words, I would be concerned if this is pushed by just 3 or 4 > > people, > > none of which have ever spent much time in the code, and who all work for > > the same employer. > > > > Ralph > > > > > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > > > > > Hi everyone, > > > > > > Apologies if this is not the right mailing list. If it is not, please > > > let me know and I'll switch the thread to the right list. > > > > > > Lighbend [1], the company that maintains the popular open source > > > framework, Akka [2], recently announced they are moving Akka to a > > > non-OSS commercial license [3]. > > > > > > There is interest in the OSS community in forking Akka under a new > > > name and maintaining it as an ASF project [4]. > > > > > > It is early days yet but there is some discussion online [5]. > > > > > > Reading the incubator cookbook, a new podling would need to have > > > champions and mentors from within the Incubator PMC [6]. > > > > > > I would like to put my name forward for such a role, as an existing > > > ASF member [7]. > > > > > > If anyone else in the Incubator PMC would like to get involved, that > > > would be great. > > > > > > Regards, > > > PJ > > > > > > [1] https://www.lightbend.com/ > > > [2] https://akka.io/ > > > [3] https://www.lightbend.com/akka/license-faq > > > [4] https://github.com/mdedetrich/akka-apache-project > > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > > [6] > > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: possible interest in forming a community fork of akka
Hi PJ, Thanks for driving this discussion! As mentioned above, Lightbend switched the license from upstream and we simply _cannot_ backport code from there any longer. However, it's reasonable to me that we start a new project based on the latest APL-2.0 licensed version (forked) to save users depending on Akka open-source ecosystem to get further bugfixes and new features. Given that there're a number of volunteers for this initiative, I believe it is worth a try to revive the open-source project: 1. We need a new name here. IIUC "akka" will cause legal issues. 2. The aim of this project should be declared in the first place, especially about new features and breaking changes. TrinoDB forked from PrestoDB can be a good pioneer to learn from. > "hostile forks" The answer of the second question listed above should answer this question also. My perspective is that the initial purpose of this project is to save users depending on Akka open-source ecosystem and it's community driven. > If anyone else in the Incubator PMC would like to get involved, that > would be great. The same as Roman :) Count me in. I'd like to be involved all the way in this effort. Best, tison. PJ Fanning 于2022年9月27日周二 17:39写道： > Thanks Ralph for looking at this. > > It is early days but a number of people have expressed an interest in > joining the new community. > > https://github.com/mdedetrich/akka-apache-project/discussions/3 > > There are some former Lightbend employees and some very active > contributors. Most of the people appear to have contributed to akka or > to related projects. > > So far, it looks like quite a diverse group with no company or > interest group having too great a say. > > There are other discussions, including ones about goals and release > plans at https://github.com/mdedetrich/akka-apache-project/discussions > > On Mon, 26 Sept 2022 at 23:25, Ralph Goers > wrote: > > > > Before going too far with this I would be interested to know: > > 1. Who the initial committers/PMC members would be. > > 2. How much familiarity the proposed people already have with the code > base. > > 3. How diverse the community is from an employment point of view. > > > > In other words, I would be concerned if this is pushed by just 3 or 4 > people, > > none of which have ever spent much time in the code, and who all work for > > the same employer. > > > > Ralph > > > > > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > > > > > Hi everyone, > > > > > > Apologies if this is not the right mailing list. If it is not, please > > > let me know and I'll switch the thread to the right list. > > > > > > Lighbend [1], the company that maintains the popular open source > > > framework, Akka [2], recently announced they are moving Akka to a > > > non-OSS commercial license [3]. > > > > > > There is interest in the OSS community in forking Akka under a new > > > name and maintaining it as an ASF project [4]. > > > > > > It is early days yet but there is some discussion online [5]. > > > > > > Reading the incubator cookbook, a new podling would need to have > > > champions and mentors from within the Incubator PMC [6]. > > > > > > I would like to put my name forward for such a role, as an existing > > > ASF member [7]. > > > > > > If anyone else in the Incubator PMC would like to get involved, that > > > would be great. > > > > > > Regards, > > > PJ > > > > > > [1] https://www.lightbend.com/ > > > [2] https://akka.io/ > > > [3] https://www.lightbend.com/akka/license-faq > > > [4] https://github.com/mdedetrich/akka-apache-project > > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > > [6] > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: possible interest in forming a community fork of akka
Thanks Ralph for looking at this. It is early days but a number of people have expressed an interest in joining the new community. https://github.com/mdedetrich/akka-apache-project/discussions/3 There are some former Lightbend employees and some very active contributors. Most of the people appear to have contributed to akka or to related projects. So far, it looks like quite a diverse group with no company or interest group having too great a say. There are other discussions, including ones about goals and release plans at https://github.com/mdedetrich/akka-apache-project/discussions On Mon, 26 Sept 2022 at 23:25, Ralph Goers wrote: > > Before going too far with this I would be interested to know: > 1. Who the initial committers/PMC members would be. > 2. How much familiarity the proposed people already have with the code base. > 3. How diverse the community is from an employment point of view. > > In other words, I would be concerned if this is pushed by just 3 or 4 people, > none of which have ever spent much time in the code, and who all work for > the same employer. > > Ralph > > > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > > > Hi everyone, > > > > Apologies if this is not the right mailing list. If it is not, please > > let me know and I'll switch the thread to the right list. > > > > Lighbend [1], the company that maintains the popular open source > > framework, Akka [2], recently announced they are moving Akka to a > > non-OSS commercial license [3]. > > > > There is interest in the OSS community in forking Akka under a new > > name and maintaining it as an ASF project [4]. > > > > It is early days yet but there is some discussion online [5]. > > > > Reading the incubator cookbook, a new podling would need to have > > champions and mentors from within the Incubator PMC [6]. > > > > I would like to put my name forward for such a role, as an existing > > ASF member [7]. > > > > If anyone else in the Incubator PMC would like to get involved, that > > would be great. > > > > Regards, > > PJ > > > > [1] https://www.lightbend.com/ > > [2] https://akka.io/ > > [3] https://www.lightbend.com/akka/license-faq > > [4] https://github.com/mdedetrich/akka-apache-project > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > [6] > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: possible interest in forming a community fork of akka
Hi PJ! Thanks for moving the discussion to this list! For completeness' sake -- let me repeat the comments I made on the legal one: On Mon, Sep 26, 2022 at 9:12 PM PJ Fanning wrote: > > Hi everyone, > > Apologies if this is not the right mailing list. If it is not, please > let me know and I'll switch the thread to the right list. > > Lighbend [1], the company that maintains the popular open source > framework, Akka [2], recently announced they are moving Akka to a > non-OSS commercial license [3]. > > There is interest in the OSS community in forking Akka under a new > name and maintaining it as an ASF project [4]. > > It is early days yet but there is some discussion online [5]. I would absolutely agree that there's clearly a need for a community supported, neutrally governed version of Akka under the Apache License. The real question is how can we make sure we've exhausted all the options to work with the original maintainers to achieve that goal. As you probably know, ASF doesn't look kindly on "hostile forks", but the key word in that phrase is *hostile*. So let's try to avoid that (if we can). So my question to you and everyone else on this list is: do you think we can somehow steer the disussion (on the GitHub) to gauge the level of interest of Lightbend (or individuals employed by it) to actually work *with* ASF to try and see whether a win-win here is possible? > Reading the incubator cookbook, a new podling would need to have > champions and mentors from within the Incubator PMC [6]. > > I would like to put my name forward for such a role, as an existing > ASF member [7]. Same here! (*) > If anyone else in the Incubator PMC would like to get involved, that > would be great. Count me in. I'd like to be involved all the way in this effort (regardless of whether we build some win-win combo with existing Lightbend folks or decide to do it with a new community). Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: possible interest in forming a community fork of akka
No, fixes most definitely cannot be back ported. But someone can look at the code fix and describe in very general terms what the fix was and then someone else can implement it. But you cannot copy code and I wouldn’t even create psuedo code as doing that would almost certainly be copyright infringement. Yes, it would be a lot of work, which is why I think it is important to ensure there is a strong community around doing this before doing much more of anything at the ASF. Ralph > On Sep 26, 2022, at 6:30 PM, Willem Jiang wrote: > > After going through the FAQ of the Akka license, it looks like we > cannot backport the BSL codes to the Apache License branch. > >> If there is a newer version of the software under BSL, can I backport any of >> the code to an older, Open Source, version of Akka? > >> No. In this circumstance, you would either violate Lightbend’s copyright by >> re-releasing the code under Open Source, or you would violate the earlier >> Akka version’s Apache license by introducing incompatible BSL code (i.e., >> code subject to a use limitation not allowed by the Open Source Apache 2.0 >> license). > > It will cause us a lot of effort to maintain the code, even if we just > want to backport some critical bug fixes. > > [1]https://www.lightbend.com/akka/license-faq > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > >> On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers >> wrote: >> >> Before going too far with this I would be interested to know: >> 1. Who the initial committers/PMC members would be. >> 2. How much familiarity the proposed people already have with the code base. >> 3. How diverse the community is from an employment point of view. >> >> In other words, I would be concerned if this is pushed by just 3 or 4 people, >> none of which have ever spent much time in the code, and who all work for >> the same employer. >> >> Ralph >> On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: >>> >>> Hi everyone, >>> >>> Apologies if this is not the right mailing list. If it is not, please >>> let me know and I'll switch the thread to the right list. >>> >>> Lighbend [1], the company that maintains the popular open source >>> framework, Akka [2], recently announced they are moving Akka to a >>> non-OSS commercial license [3]. >>> >>> There is interest in the OSS community in forking Akka under a new >>> name and maintaining it as an ASF project [4]. >>> >>> It is early days yet but there is some discussion online [5]. >>> >>> Reading the incubator cookbook, a new podling would need to have >>> champions and mentors from within the Incubator PMC [6]. >>> >>> I would like to put my name forward for such a role, as an existing >>> ASF member [7]. >>> >>> If anyone else in the Incubator PMC would like to get involved, that >>> would be great. >>> >>> Regards, >>> PJ >>> >>> [1] https://www.lightbend.com/ >>> [2] https://akka.io/ >>> [3] https://www.lightbend.com/akka/license-faq >>> [4] https://github.com/mdedetrich/akka-apache-project >>> [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 >>> [6] >>> https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator >>> [7] https://whimsy.apache.org/roster/committer/fanningpj >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: possible interest in forming a community fork of akka
After going through the FAQ of the Akka license, it looks like we cannot backport the BSL codes to the Apache License branch. > If there is a newer version of the software under BSL, can I backport any of > the code to an older, Open Source, version of Akka? > No. In this circumstance, you would either violate Lightbend’s copyright by > re-releasing the code under Open Source, or you would violate the earlier > Akka version’s Apache license by introducing incompatible BSL code (i.e., > code subject to a use limitation not allowed by the Open Source Apache 2.0 > license). It will cause us a lot of effort to maintain the code, even if we just want to backport some critical bug fixes. [1]https://www.lightbend.com/akka/license-faq Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers wrote: > > Before going too far with this I would be interested to know: > 1. Who the initial committers/PMC members would be. > 2. How much familiarity the proposed people already have with the code base. > 3. How diverse the community is from an employment point of view. > > In other words, I would be concerned if this is pushed by just 3 or 4 people, > none of which have ever spent much time in the code, and who all work for > the same employer. > > Ralph > > > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > > > Hi everyone, > > > > Apologies if this is not the right mailing list. If it is not, please > > let me know and I'll switch the thread to the right list. > > > > Lighbend [1], the company that maintains the popular open source > > framework, Akka [2], recently announced they are moving Akka to a > > non-OSS commercial license [3]. > > > > There is interest in the OSS community in forking Akka under a new > > name and maintaining it as an ASF project [4]. > > > > It is early days yet but there is some discussion online [5]. > > > > Reading the incubator cookbook, a new podling would need to have > > champions and mentors from within the Incubator PMC [6]. > > > > I would like to put my name forward for such a role, as an existing > > ASF member [7]. > > > > If anyone else in the Incubator PMC would like to get involved, that > > would be great. > > > > Regards, > > PJ > > > > [1] https://www.lightbend.com/ > > [2] https://akka.io/ > > [3] https://www.lightbend.com/akka/license-faq > > [4] https://github.com/mdedetrich/akka-apache-project > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > > [6] > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > > [7] https://whimsy.apache.org/roster/committer/fanningpj > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: possible interest in forming a community fork of akka
Before going too far with this I would be interested to know: 1. Who the initial committers/PMC members would be. 2. How much familiarity the proposed people already have with the code base. 3. How diverse the community is from an employment point of view. In other words, I would be concerned if this is pushed by just 3 or 4 people, none of which have ever spent much time in the code, and who all work for the same employer. Ralph > On Sep 26, 2022, at 11:11 AM, PJ Fanning wrote: > > Hi everyone, > > Apologies if this is not the right mailing list. If it is not, please > let me know and I'll switch the thread to the right list. > > Lighbend [1], the company that maintains the popular open source > framework, Akka [2], recently announced they are moving Akka to a > non-OSS commercial license [3]. > > There is interest in the OSS community in forking Akka under a new > name and maintaining it as an ASF project [4]. > > It is early days yet but there is some discussion online [5]. > > Reading the incubator cookbook, a new podling would need to have > champions and mentors from within the Incubator PMC [6]. > > I would like to put my name forward for such a role, as an existing > ASF member [7]. > > If anyone else in the Incubator PMC would like to get involved, that > would be great. > > Regards, > PJ > > [1] https://www.lightbend.com/ > [2] https://akka.io/ > [3] https://www.lightbend.com/akka/license-faq > [4] https://github.com/mdedetrich/akka-apache-project > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > [6] > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > [7] https://whimsy.apache.org/roster/committer/fanningpj > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
possible interest in forming a community fork of akka
Hi everyone, Apologies if this is not the right mailing list. If it is not, please let me know and I'll switch the thread to the right list. Lighbend [1], the company that maintains the popular open source framework, Akka [2], recently announced they are moving Akka to a non-OSS commercial license [3]. There is interest in the OSS community in forking Akka under a new name and maintaining it as an ASF project [4]. It is early days yet but there is some discussion online [5]. Reading the incubator cookbook, a new podling would need to have champions and mentors from within the Incubator PMC [6]. I would like to put my name forward for such a role, as an existing ASF member [7]. If anyone else in the Incubator PMC would like to get involved, that would be great. Regards, PJ [1] https://www.lightbend.com/ [2] https://akka.io/ [3] https://www.lightbend.com/akka/license-faq [4] https://github.com/mdedetrich/akka-apache-project [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 [6] https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator [7] https://whimsy.apache.org/roster/committer/fanningpj - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
