[RESULT] [VOTE] Apache AGE (Incubating) 0.6.0 Release

2021-10-22 Thread Josh Innis 
Dear AGE Community,



I'm closing this vote and happy to announce the results of the vote for

Apache AGE 0.6.0 Incubating



This vote passes with 7 +1 votes (2 bindings and 5 non bindings) and no 0

or -1 votes.



+1 (Binding)

--

* Juan Pan

* Kevin Ratnasekera





There were no 0 or -1 votes. Thank you to all who helped make this happen.





Vote thread can be found here [1].



I'll continue with the next round of the voting process and update the

community as progress is

made.





[1]

https://lists.apache.org/thread.html/r7152a52ca973bc72282ff9a1591e49ec1662e69914aa2c9784c256a6%40%3Cdev.age.apache.org%3E



Best regards,

Josh Innis

Re: Re: Re: Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

2021-10-22 Thread Josh Innis 
Hi All,

I am closing this vote. We will announce the results shortly.
We create value for our clients by connecting the world's data.
Josh Innis Software Engineer
Core R Team
*P*: (831)278-0327
3945 Freedom Circle #260, Santa Clara, CA 95054

bitnine.net


On Mon, Oct 18, 2021 at 2:32 PM Josh Innis  wrote:

>
> What would be the definition of minor modification? AGE in general tries
> to conform to the ideas in Postgres as much as possible. Which means we are
> constantly calling Postgres functions to do work and at runtime queries
> will switch between Postgres source code and AGE source code often. When we
> cannot use a Postgres function but want to emulate similar behavior, we use
> that function as a template. For example, the Agtype data type that we use
> is heavily influenced by the JsonB data type in Postgres and the way we
> transform expressions is very close to Postgres. A function might have the
> same logical flow to it, but we need to pass in a different data structure,
> or we might have some special cases that must be handled differently, but
> otherwise is very similar to something in postgres.
>
> On Sun, Oct 17, 2021 at 2:17 PM Felix Cheung 
> wrote:
>
>> In such case, the inclusion of the license is required.
>>
>> Also, ideally, the 3rd party source code should be retained as separate
>> source files so we could keep the license header on each file. If they are
>> code snippet, then it is a bit of a grey area and we should attribute the
>> source in license (a practice I've seen in other projects)
>>
>> See
>> https://www.apache.org/legal/src-headers.html#3party
>> https://www.apache.org/legal/resolved.html#category-a
>> "
>> 4. Minor modifications/additions to third-party source files should
>> typically be licensed under the same terms as the rest of the third-party
>> source for convenience.
>>
>> 5. The project's PMC should deal with major modifications/additions to
>> third-party source files on a case-by-case basis."
>>
>>
>>
>>
>> On 2021/10/13 20:44:15 Josh Innis wrote:
>> > We resigned the files using an @apache.org account. There is source
>> code
>> > from Postgres in AGE. There are no files but there are some snippets.
>> > We create value for our clients by connecting the world's data.
>> > Josh Innis Software Engineer
>> > Core R Team
>> > *P*: (831)278-0327
>> > 3945 Freedom Circle #260, Santa Clara, CA 95054
>> > <
>>
>> https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
>> >
>> > bitnine.net
>> >
>> >
>> > On Sun, Oct 10, 2021 at 5:28 PM Felix Cheung  wrote:
>> >
>> > > There bundle also applies to the source release. However, if you are
>> > > certain none of the source code file or snippet is from the Postgres
>> code
>> > > base, then, correct, you don’t need to include Postgres license info.
>> > >
>> > > You might want to amend the license and notice, and re-sign with a key
>> with
>> > > @apache.org address from my comments earlier.
>> > >
>> > > I’m not sure if it will be flagged at IPMC, but it is best since you
>> have
>> > > changed the disclaimer in this release.
>> > >
>> > >
>> > > On 2021/10/05 16:54:29 Josh Innis wrote:
>> > > > Hi Felix,
>> > > >
>> > > > We do not have any binary code from Postgres. The key phrase I saw
>> was "
>> > > > LICENSE and NOTICE need only be modified to accommodate them *only
>> if
>> > > their
>> > > > bits are bundled*." The Apache AGE repository does not have any
>> binary
>> > > > source files in it. After reading the links you sent, it appears we
>> do
>> > > not
>> > > > have to keep the Postgres license info in NOTICE and LICENSE.
>> > > >
>> > > >
>> > > > On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung 
>> wrote:
>> > > >
>> > > > > Checking this release, not a blocker but a question:
>> > > > >
>> > > > >
>> > > > > - incubating in name
>> > > > >
>> > > > > - signature and hash fine
>> > > > >
>> > > > > KEYS file - you should try to sign files with @apache.org issuer
>> email
>> > > > >
>> > > > > - DISCLAIMER is fine
>> > > > >
>> > > > > - LICENSE and NOTICE
>> > > > >
>> > > > > The PostgreSQL license - is it because of code file taken from the
>> > > project
>> > > > > (and then is there license header for these files?)
>> > > > >
>> > > > > If it is not coming from code file, then is it because of a binary
>> > > > > dependency? If so, it should be in a separate LICENSE-binary file
>> like
>> > > > > https://github.com/apache/iotdb/blob/master/LICENSE-binary
>> > > > >
>> > > > > And potentially the license should be separately stored like
>> > > > > https://github.com/apache/iotdb/tree/master/licenses
>> > > > >
>> > > > > more info:
>> > > > >
>> https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
>> > > > >
>> > > > > - No unexpected binary files
>> > > > > - All source files have ASF headers
>> > > > >
>> > > > >
>> > > > >
>> > > > > On 2021/09/24 11:34:24 Kevin Ratnasekera

[GitHub] [incubator-age-website] JoshInnis merged pull request #21: Update documentation link

2021-10-22 Thread GitBox 


JoshInnis merged pull request #21:
URL: https://github.com/apache/incubator-age-website/pull/21


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [incubator-age-website] pdpotter opened a new pull request #21: Update documentation link

2021-10-22 Thread GitBox 


pdpotter opened a new pull request #21:
URL: https://github.com/apache/incubator-age-website/pull/21


   Update the documentation link on the project homepage


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [incubator-age-website] pdpotter opened a new pull request #20: Redirect to the docs master branch when visiting the docs root

2021-10-22 Thread GitBox 


pdpotter opened a new pull request #20:
URL: https://github.com/apache/incubator-age-website/pull/20


   When a user visit the docs root at https://age.apache.org/docs, currently a 
file and directory listing is displayed. This pull request adds an index.html 
at the docs root which redirects to the master version of the documentation 
(https://age.apache.org/docs/master/index.html).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org