Hi Justin, I feel it is important to point out that we are constantly adding PostgreSQL code to our project as we add in new components. A lot of our work is transforming PostgreSQL's implementation to work with our added functionality i.e. our work is very mixed with PostgreSQL code.
Unfortunately, this isn't and won't be a one time thing for us. This is what makes it so challenging and why we are trying very hard to nail down what exactly (or precisely) we need to do to please everyone. So, my understanding is that for all of our files that have any PostgreSQL code (anything from a PostgreSQL source file), modified or not, we need their license and not the ASF license. For work that doesn't have PostgreSQL code, we need the ASF license. Is this correct? Does this make sense? Thank you in advance, John On 2021/11/02 21:47:01 Justin Mclean wrote: > Hi, > > > What is the ASF policy for including parts of external source files such as > > in functions? > > There is no explicit policy. However the header policy states that for code > developed at the ASF the ASF header should be used. Treatment of 3rd party > works [2] covers code not submitted by the copyright owner and states that > copyright and license should stay intact (this seems to cover the case here), > the 3rd party license needs to be included, and that the ASF header should > not be added to the code. If minor modifications are made then it still > should keep the original license. > > Kind Regards, > Justin > > 1. https://www.apache.org/legal/src-headers.html#headers > 2. https://www.apache.org/legal/src-headers.html#3party > > > --------------------------------------------------------------------- > 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
