Hi Justin, Most of our code uses or is inspired by PostgreSQL's code, in some modified form or another. Additionally, we try to have our code work tightly with their code in order to reduce replication of code. As a core developer, and from your input, I wouldn't be comfortable with anything less than including PostgreSQL's license (along with ASF) in nearly all of our source files - to be safe. Would this be satisfactory to you?
My understanding of what you are saying about the Bitnine license is to leave it out. As Bitnine donated this code to ASF and merely stating it in the LICENSE or NOTICE file should be sufficient. Would this be satisfactory to you? Thank you in advance! John On 2021/10/30 22:09:00 Justin Mclean wrote: > Hi, > > > Basically, keep the PostgreSQL copyright messages intact in all file > > headers that it copy/use from the PostgreSQL > > I would do this. > > > and just append Bitnine's copyright message to the header along with the > > PostgreSQL's message. > > I would not do this, this is an ASF project not Bitnine’s project. > Technically copyright may belong to Bitnine (if for instance an employee of > Bitnine submits something to the project) but this doesn’t follow what is > recommend by ASF policy on headers. > > Also you need to think about all of the code that has been copied but > probably has incorrect headers. > > Thanks, > 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
