Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

HI, The NOICE file has this: Apache AGE (incubating) Copyright 2019-2020 Bitnine Co., Ltd. Copyright 2020-2021 The Apache Software Foundation Which I don’t think is really correct. Bitnine Co., Ltd. did have copyright but that gave the ASF a grant right? And that original project wouldn’t have

Re: Re: Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hello Justin, Could you please take a look at the previous thread by Josh and confirm our LICENSE and NOTICE files so we can restart the vote. Thank you very much, Eya On 2021/11/05 16:22:30 Josh Innis wrote: > We have updated the NOTICE file to include the Bitnine copyright information >

Re: Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

We have updated the NOTICE file to include the Bitnine copyright information and removed the Postgres info as well, the Postgres license remains in the LICENSE file, and the files with Postgres code now have the postgres header, rather than the ASF header. These changes are all in the 0.6.0

Re:[CANCEL] [VOTE] Apache AGE (Incubating) 0.6.0 Release

Thank you very much for everyone that voted and provided feedback, due to some license and notice issues we are canceling this vote and will fix related issues. 1. Incorrect license headers - PostgreSQL headers 2. Other LICENSE and NOTICE issues need to be checked in addition to the above

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Thank you, Justin. We followed your advice and redirected the download links as requested. Also added KEY Files to the website. **Changed https://dist.apache.org/repos/dist/release/incubator/age/0.5.0.rc0/apache-age-0.5.0-incubating-src.tar.gz.sha512 to go via

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

I have updated the following files in question in my repository to use the Postgres header, and removed the ASF header. https://github.com/JoshInnis/incubator-age If this is correct we will correct in the repository and the release as well. It includes the full copyright with no mention of

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, That sounds like a good strategy to me. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, So, we are going to put the PostgreSQL license into all of our files that have any PostgreSQL code and remove the ASF license from them. Additionally, going forward we are going to move as much of the PostgreSQL code that can be moved, into their own files. Will this satisfy your

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > 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. I think inn general that

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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.

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, What is the ASF policy for including parts of external source files such as in functions? Again, we only include what we need and we generally modify that code. We don't copy files over, with the exception of one that I can think of. In this case do we just use the PostgreSQL

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

That statement is contained with the LICENSE https://github.com/JoshInnis/incubator-age/blob/master/LICENSE. Postgres headers do not include it. Its only contained in the COPYRIGHT. https://github.com/postgres/postgres/blob/master/src/backend/executor/execAsync.c

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

HI, It also doesn’t follow the terms of the PostgreSQL which states: "Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Can you please confirm that all files in question, with regards to Postgres, > should have the following header. This one way to deal with it, and is probably better than what is beening currently done, however IMO: - "Licensed to the Apache Software Foundation (ASF) under on or more

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, I setup my private github repository with the updates to the license headers. https://github.com/JoshInnis/incubator-age Can you please confirm that all files in question, with regards to Postgres, should have the following header: /* * Licensed to the Apache Software Foundation

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, Thank for your beneficial feedback. > Please change link to > https://dist.apache.org/repos/dist/release/incubator/age/0.5.0.rc0/apache-age-0.5.0-incubating-src.tar.gz.sha512 > to go via https://downloads.apache.org/ @AGE team, [1] shows you the download links and potential

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, Please change link to https://dist.apache.org/repos/dist/release/incubator/age/0.5.0.rc0/apache-age-0.5.0-incubating-src.tar.gz.sha512 to go via https://downloads.apache.org/ Please change link to

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, Could you please advise where the download link for 0.5.0 should be pointing out to? Thank you, Eya On Mon, Nov 1, 2021 at 7:10 PM Justin Mclean wrote: > Hi, > > Also note that the download link to 0.5 is not correct on your web site. > > Kind Regards, > Justin > >

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, Also note that the download link to 0.5 is not correct on your web site. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, It would be accurate because, most of our code is based off PostgreSQL. AGE is an openCypher language implementation built into PostgreSQL via their extension mechanism. It follows how PostgreSQL implements the SQL language. Additionally, we modify their parse and query trees in

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > 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

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

HI, > "Also you need to think about all of the code that has been copied but > probably has incorrect headers." > > Are you referring to a more general case of code other than PG or Bitnine? > Could you expand a bit on this please. I was referring to code from PostgreSQL. Thanks, Justin

Re: Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin, Additionally, for - "Also you need to think about all of the code that has been copied but probably has incorrect headers." Are you referring to a more general case of code other than PG or Bitnine? Could you expand a bit on this please. Thank you in advance! John On 2021/11/01

Re: Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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 wrote: > Hi, > > > Thank you for your feedback. The issue with hashes

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Postgres has not donated anything to our project. Then it probably should not be mentioned in NOTICE in that way. > We generally don't copy Postgres files over. So, no we haven't replaced their > copyright notice. But you’ve not copied it over either, which is slightly problematic.

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Justin, "Has code from PostgreSQL been donated to the project? Have files that had PostgreSQL copyright in their headers been replaced? " Postgres has not donated anything to our project. We generally don't copy Postgres files over. So, no we haven't replaced their copyright notice. What we

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > Could we please get some clarification on the following items - > > "- LICENSE is missing information from [1][2]” Sorry my mistake I do see that both copyright statements are in LICENSE. You can ignore this. > "- NOTICE is incorrect. There should be no need for "This product contains

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

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/ > It is under the download then versions page.

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > We need to figure out where these files came from. If they originated from > Bitnine, we should keep their original header and mention them in > NOTICE/LICENSE. If they were part of the original grant then I would change the headers to ASF ones and add teh required text to NOTICE. If

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi Justin Could we please get some clarification on the following items - "- LICENSE is missing information from [1][2]" What specifically is the missing information from [1][2]. Could you give us an example to help us understand and correct this? "- NOTICE is incorrect. There should be no

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, We need to figure out where these files came from. If they originated from Bitnine, we should keep their original header and mention them in NOTICE/LICENSE. Otherwise, only keep the ASF header for them. -- Juan

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hello Justin, 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/ It is under the download then versions

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, > I see Bitnine is the company that donated the project AGE to Apache, so the > header change seems to make sense? Perhaps? If that is the case then why is that not mentioned in the NOTICE file? If you remove (with permission) a copyright line for a header as part of a SGA then that

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

I see Bitnine is the company that donated the project AGE to Apache, so the header change seems to make sense? On Sat, Oct 23, 2021 at 5:27 PM Justin Mclean wrote: > Hi, > > Sorry but it’s -1 (binding) as there is no download page and the download > links on the home page do not have hashes

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

Hi, Sorry but it’s -1 (binding) as there is no download page and the download links on the home page do not have hashes and signatures. This was brought up on this list recently and was asked to be corrected. Also see other issues below. In the release: - incubating in name - signatures and

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

On Sat, 23 Oct 2021 at 02:00, Josh Innis wrote: > > Dear Apache Community, > > This is a call for releasing Apache AGE (Incubating) 0.6.0. > To learn more about Apache AGE (Incubating), please see http://age.apache.org/ > > * >

[VOTE] Apache AGE (Incubating) 0.6.0 Release

Dear Apache Community, This is a call for releasing Apache AGE (Incubating) 0.6.0. To learn more about Apache AGE (Incubating), please see http://age.apache.org/ * Apache AGE (incubating) community has voted and approved the