Thank you, Usama, for the beneficial information. @Justin Mclean @Juan Pan @Kevin Ratnasekera @Felix Cheung, could you please advise if the mentioned approach will be a good solution for the previous discussion regarding the Postgresql license?
Basically, keep the PostgreSQL copyright messages intact in all file headers that it copy/use from the PostgreSQL and just append Bitnine's copyright message to the header along with the PostgreSQL's message. And there is no need for PostgreSQL source files to be donated to the project as the PostgreSQL license already gives the permission to use/modify/distribute its code. Best regards, Eya On 2021/10/29 04:57:53, Muhammad Usama <m.us...@agedb.io> wrote: > Hi, > > I have just subscribed to the Apache AGE project and was going through > this thread, so thought to chime in with my two cents. > > As you know PostgreSQL is released under an OSI approved 'The PostgreSQL > License' [1], that is very liberal in nature and allows use, copy, modify, > and distribution of the code and its documentation for any purpose. It even > allows the proprietary commercialization and that is the reason we have > lots of proprietary variants of PostgreSQL like EnterpriseDB's Advance > Server and FUJITSU's Enterprise Postgres. > > Similarly, we also have open source variants like AgensGraph (the one we > are discussing here) and Greenplum database. > The reason I am mentioning all these forks of PostgreSQL is that, all of > these forks use and modifies the PostgreSQL code and doing that is totally > fine, as long as the copies keep the PostgreSQL's copyright notice. [2] > > For instance, have a look at Greenplum database, that is a PostgreSQL > variant and released under the Apache2 license. The source header in > Greenplum preserves the original PostgreSQL's copyright notices and adds > additional copyright messages (Greenplum's and VMWare's) on top of that [3]. > Similarly, Pgpool-II code is another example that copies lots of code from > PostgreSQL and uses the same portion copyright notice in the header without > removing the PostgreSQL's notice [4]. > > So, IMHO Apache AGE could follow the same approach, keep the PostgreSQL > copyright messages intact in all file headers that it copy/use from the > PostgreSQL and just append Bitnine's copyright message to the header along > with the PostgreSQL's message. And there is no need for PostgreSQL source > files to be donated to the project as the PostgreSQL license already gives > the permission to use/modify/distribute its code. > > > 1. https://opensource.org/licenses/postgresql > 2. https://www.postgresql.org/about/licence/ > 3. > https://github.com/greenplum-db/gpdb/blob/master/src/backend/parser/gram.y > 4. https://github.com/pgpool/pgpool2/blob/master/src/parser/gram.y > > Thanks > Best regards > Muhammad Usama > > On Thu, Oct 28, 2021 at 4:31 AM Eya Badal <e...@apache.org> wrote: > > > Hello Justin, > > > > I fixed the link refrence issue for the latest Apache AGE(incubating) > > release. Now it is pointing out to the correct location. > > http://age.apache.org/# > > > > Thank you, > > Eya > > > > On 2021/10/25 22:42:10, Justin Mclean <jus...@classsoftware.com> wrote: > > > Hi, > > > > > > > Thank you for your feedback. The issue with hashes and Signatures on > > the > > > > website for each download is fixed. We created a download page and > > > > added the required information as mentioned before: > > http://age.apache.org/ > > > > <http://age.apache.org/#> It is under the download then versions page. > > > > > > Thanks for that. The latest release should not use this URL > > https://archive.apache.org/ for downloading. > > > > > > > Based on your feedback should we remove "Postgresql Copyright" from our > > > > NOTICE and add "Copyright 2020 Bitnine Co., Ltd.”? > > > > > > I don’t have enough information to be able to answer that. Has code from > > PostgreSQL been donated to the project? Have files that had PostgreSQL > > copyright in their headers been replaced? > > > > > > Kind Regards, > > > Justin > > > --------------------------------------------------------------------- > > > 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
