Re: Jira issues largely being ignored

[John Gemignani]

Hi,

I'll just give my 2 cents on this for the Apache AGE project, from my
perspective,...

In the early stages of Apache AGE we tried to use Jira. For a while, we
actually were using it for day to day activities. However, the constant
spam we had to remove daily, along with also having issues coming in
through Github, coupled with our limited resources, forced us to make a
choice between the two of them.

I also recall it taking months to get permissions just to remove the spam
that came in. While, I understand the delays involved with an open source
projects' infrastructure, being nearly everyone is a volunteer, all of
these items soured us on Jira. Github was just better suited to our needs,
integrated better, and didn't have spam.

We still do have discussions about using both, btw. However, for the size
of our team, it would cause us to spend more time on "paperwork" than on
design, research, issues, or code.

I would surmise that we aren't the only project that has had similar
internal discussions.

Hope this is helpful,

John

On Tue, Oct 3, 2023 at 8:04 AM Justin Mclean 
wrote:

> Hi,
>
> Like any project, we are all volunteers here and this may mean that
> sometimes issues may go unaddressed or unclosed. If something needs
> attention you could bring it up on the mailing list.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: PMC is a committee

[John Gemignani]

My 2 cents as being a PMC member and once part of incubation,...

To be honest, I've never really paid much attention when someone stated
they're a PMC. I knew what was meant and just auto corrected it in my head.
I have used, without fully thinking about it, PMC as, "I am a PMC" as well.
When I meant, or should have meant, "I am a PMC member", and I'm a native
English speaker.

As was mentioned, people from different cultures might have different ways
of using a term like PMC. I just don't feel that getting upset over,
arguably an innocuous misuse, engenders community.

And, we can all be tired, overworked, or lazy and say the wrong thing *or*
get into bad habits.

Again, my 2 cents.

john

On Tue, Jul 2, 2024 at 5:33 PM Dave Fisher  wrote:

> Hi Tison,
>
> I’m sympathetic as well.
>
> > On Jul 2, 2024, at 5:11 PM, tison  wrote:
> >
> > Hi Greg,
> >
> > I saw this kind of thread many times, and I also corrected it dozens
> > of times. Actually, this is part of the reason for [1] ("Maintainer"
> > as an alias of PMC Member?).
> >
> > [1] https://lists.apache.org/thread/xsjojmksqtnsdjcg0yf4vz0xy82llhmw
>
> That quickly turned into a not very sympathetic response from most. An
> easy what to name the Bikeshed. I think that most of our group are people
> whose second language is python, java, or fortran and their first language
> is some version of English.
>
> >
> > Somehow, I share the sympathy for non-native speakers to make an
> > analogy between committer and "PMC" since they're all one-word
> > phrases.
>
> Maybe explain it from your perspective as a speaker of Mandarin (or
> Cantonese?). How does the phrase Committee Member translate compared to
> Committee.
>
> Best,
> Dave
> >
> > Best,
> > tison.
> >
> > Greg Stein  于2024年7月2日周二 17:05写道：
> >>
> >> Hello all,
> >>
> >> I am getting really tired of seeing people refer to *MEMBERS* of a PMC
> as
> >> "PMCs".
> >>
> >> PMC stands for Project Management Committee.
> >>
> >> You have MEMBERS of that PMC.
> >>
> >> People are never to be called a PMC, nor a group of them as PMCs. People
> >> are not committees. The acronym "PMC" is short for a committee, not a
> >> person.
> >>
> >> Please stop the confusion. Teach the community how to use the proper
> terms.
> >>
> >> Thanks,
> >> Greg
> >
> > -
> > 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
>
>

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

[John Gemignani]

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 need for "This product contains 
software PostgreSQL…” unless headers have been replace with permission or there 
was a software grant from PostgreSQL. This has previously been mentioned (in 
vote on 0.4.0 release). Also see issue with [1][2]."

We are a bit confused here because AGE extensively uses PG code. Many times we 
have to copy over PG code (static functions in particular) into our files and 
we may modify that code to varying degrees. So, it feels like we should cite 
that usage. Is it that NOTICE is not the proper location?

"- If seem unlikely that [1][2] should have ASF headers? In general the 
licensing of the file should stay as it is unless significant modifications 
have ben done. Looking at the history it seems if was originally "Copyright 
2020 Bitnine Co., Ltd.” Why is this not mentioned in NOTICE? Was permission 
given to change the headers?"

My understanding was that when the code was donated to Apache, we needed to 
change all of the Bitnine headers to ASF headers. That is why those files (and 
all of the others) have ASF headers. Is it that we still need to include the 
Bitnine copyright in each file or just in the NOTICE file or both?

Thank you in advance,

John

On 2021/10/23 01:00:09, 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/
> 
> *
> Apache AGE (incubating) community has voted and approved the release.
> This vote passed with 7 +1 votes (2 bindings and 5 non bindings) and no 0 or 
> -1 votes.
> 
> +2 (Bindings)
> --
> * Juan Pan
> * Kevin Ratnasekera
> 
> *
> *The git tag to be discussed and voted upon:*
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
> 
> *The git commit hash:*
> commit 3681c90da68353507001db89eb429755d34857f7
> 
> *The release files for 0.6.0, can be found at:*
> https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> 
> *The signatures, files, etc. can be found at:*
> https://dist.apache.org/repos/dist/dev/incubator/age/
> 
> *Signatures used for AGE RCs can be found in this file:*
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> 
> *The fingerprint of key to sign release artifacts:*
> 2245 1CFA 0521 1612 A4EA 9F05 6EF7 BD28 B870 8B05
> 
> *For information about the contents of this release, see:*
> https://github.com/apache/incubator-age/releases/tag/v0.6.0
> 
> Vote thread can be found here [1].
> 
> [1]https://lists.apache.org/thread.html/r7152a52ca973bc72282ff9a1591e49ec1662e69914aa2c9784c256a6%40%3Cdev.age.apache.org%3E
> 
> The vote will be open for 72 hours.
> [ ] +1 release this package
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> Thank you for all your time.
> 
> Best regards,
> Josh Innis
> 
> -
> 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

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

[John Gemignani]

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 generally do is copy functions that we may need from Postgres into our 
source files. This is because we may need the functionality of their static 
(private) functions.

Does that help you to answer my questions?

Thanks in advance,

John

On 2021/10/25 22:42:10, Justin Mclean  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/
> >  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

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

[John Gemignani]

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

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

[John Gemignani]

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 18:12:05 John Gemignani wrote:
> 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
> 
> 

-
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

[John Gemignani]

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 order to implement the 
openCypher grammar and grammar transforms. This means using and modifying their 
code to work in the new functionality.

For the transform phase, we have to follow how PostgreSQL transforms their 
nodes so that we can properly transform ours. A lot of times, we have to copy 
and modify some of their static functions to allow us to correctly handle 
specific cases.

Our C files also include their C headers for access to public functions.

So, nearly every file has some PostgreSQL code in it, to some extent. There are 
a few exceptions, but they are in the minority.

I would just rather error on the safe side because, due to using their 
structures and functions, code that isn't PostgreSQL code can look just like 
PostgreSQL code.

John

On 2021/11/02 00:11:06 Justin Mclean wrote:
> 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 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?
> 
> That would be safe I guess, but would it be accurate? I also don’t think that 
> is in line with ASF policy on file headers. In general, code developed at the 
> ASF should have an ASF header, 3rd party code or code copied from elsewhere 
> should have the original header on it. Is it that hard to work out what code 
> was copied and what code was not?
> 
> > 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?
> 
> As per ASF policy it should be mentioned in NOTICE.
> 
> 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

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

[John Gemignani]

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 license for all of that work? And 
leave out the ASF license?

John

On 2021/11/02 21:01:49 Justin Mclean wrote:
> 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 
> contributor license agreements. “ is not going to be correct
> - it mentions the copyright but not the license of the included code. It's 
> the different license that is probably more important
> - It doesn’t follow ASF policy on file headers
> 
> 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

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

[John Gemignani]

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

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

[John Gemignani]

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 concerns with regards to this item?

Thanks in advance.

John

On 2021/11/02 23:53:22 Justin Mclean wrote:
> 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 would be best way of dealing with this. you may also 
> want to consider point 5 in [1] "The project's PMC should deal with major 
> modifications/additions to third-party source files on a case-by-case basis.”
> 
> Kind Regards,
> Justin
> 
> 1. 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

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

[John Gemignani]

Hi Justin, Felix, and others,

I keep hearing that the bar for a committer is too high for our project.

Could you clarify what would be considered too low of a bar for a committer? 
Or, if there is some document that I am not aware of that explains this, that 
would be great too.

I feel that we need good upper and lower bounds for this so that we are all on 
the same page on who qualifies to be a committer. Additionally, this way, when 
we submit a new committer, we can state the milestones that they have reached 
that makes us confident with them as a new committer and most would agree.

I would rather we don't bounce back and forth between, too high and too low.

Thanks!

John

On 2021/12/18 11:55:12 Justin Mclean wrote:
> Hi,
> 
> > Because of the nature of the project, committers require a broad range of
> > expertise in several areas including: Database (Postgres and SQL), Graph
> > Technology and Cyper, C language. While many contributors demonstrated
> > expertise in some areas, few had expertise in all disciplines. In addition
> > we restricted committer status to those who demonstrated consistent
> > contribution to the project over many months and across multiple and
> > diverse challenges. We felt this was the most prudent way to build a strong
> > and tight community.
> 
> IMO that bar is far too high, and I suggest the project needs to lower its 
> bar. No one should have to be an expert in all areas to become a committer in 
> a project. It would also be best to consider committers than contribute 
> things other than code.
> 
> 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

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

[John Gemignani]

contributors
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> 4 new committers and 1 new PPMC from 3 different
> > > >>>>> companies/institutions
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> Gathered > 500 GitHub stars
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> 4 Apache releases (0.3.0, 0.4.0, 0.5.0, 0.6.0) [3]
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> 6 mentors, 6 PPMC members (mentors excluded) and 4 committers
> > > >>>>> (mentors
> > > >>>>>>> and PPMC members excluded)
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> Contributions span more than 20 countries across the globe 
> > > >>>>>>> including
> > > >>>>>>> Australia, Belarus, Belgium, China, France, Germany, Ireland,
> > > >>>>> Israel,
> > > >>>>>>> Italy, Luxembourg, The Netherlands, Nigeria, The Philippines,
> > > >>>>> Russia, South
> > > >>>>>>> Korea, Thailand, UK, Ukraine, USA, and Vietnam
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> Developed and maintained Apache AGE website [4]
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> Created and automated documentation to support multiple versions 
> > > >>>>>>> of
> > > >>>>> AGE.
> > > >>>>>>> [5]
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> Developer conversations at d...@age.apache.org
> > > >>>>>>> -
> > > >>>>>>>
> > > >>>>>>> Assessed ourselves against the Apache Project maturity matrix [6]
> > > >>>>> and
> > > >>>>>>> didn't find any issues
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> [1] 
> > > >>>>>>> https://lists.apache.org/thread/q2cgbnhvpzk2k0m8yfh89lzc75qym9k9
> > > >>>>>>>
> > > >>>>>>> [2] 
> > > >>>>>>> https://lists.apache.org/thread/lr3x9bm8jyv6o5kvyh7cf3tyxrpp2kwm
> > > >>>>>>>
> > > >>>>>>> [3] Release at Apache AGE website <https://age.apache.org/#> under
> > > >> the
> > > >>>>>>> Releases menu.
> > > >>>>>>>
> > > >>>>>>> [4] https://age.apache.org/
> > > >>>>>>>
> > > >>>>>>> [5] Documentation at Apache AGE website <https://age.apache.org/#>
> > > >>>>> under
> > > >>>>>>> the Documentation menu.
> > > >>>>>>>
> > > >>>>>>> [6] Apache Project maturity matrix at Apache AGE website
> > > >>>>>>> <https://age.apache.org/#> under the COMMUNITY menu.
> > > >>>>>>>
> > > >>>>>>> Please see the proposed board resolution below and let us know 
> > > >>>>>>> what
> > > >> you
> > > >>>>>>> think.
> > > >>>>>>>
> > > >>>>>>> The discussion will remain open for at least 72 hours.
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>
> > > >> 
> > > >>>>>>>
> > > >>>>>>> Establish the Apache AGE Project
> > > >>>>>>>
> > > >>>>>>> WHEREAS, the Board of Directors deems it to be in the best 

Re: [VOTE] Apache AGE 1.0.0-rc1 Release

[John Gemignani]

Yes, it would be very much appreciated if the following mentors could
please take a look at this very major release for our community.



*@Kevin Ratnasekera @Felix Cheng @vongosling*

And thank all of you and our community for the support!

John

On Fri, Apr 15, 2022 at 3:40 PM Eya Badal  wrote:

> Hello IPMC,
>
> Could you please support us in moving forward with this release? We need
> two more binding votes and would appreciate your time and help here.
>
> Since @panjuan reviewed and voted +1 binding, other mentors @Kevin
> Ratnasekera @Felix Cheng @vongosling would appreciate your support as well.
>
> Thank you very much,
> Eya
>
> On 2022/04/06 00:22:00 Nicholas Sorrell wrote:
> > Dear Apache Community,
> >
> > This is an official vote for the Apache AGE 1.0.0-rc1 release.
> >
> > The Apache AGE community vote thread can be found here:
> > https://lists.apache.org/thread/wfqjhhz2pv5c3w33053b7h5s774dl1lm
> >
> > The results thread of the community vote can be found here:
> > https://lists.apache.org/thread/99bbvhd7yb2dh321dvl4s9j415pl9dz2
> >
> > **Vote Results**:
> > No 0 or -1 votes.
> >
> > 1 (+1) Binding Vote:
> > *Trista Pan
> >
> > 5 (+1) Non Binding:
> > *Josh Innis
> > *Andrew Ko
> > *John Gemegnani
> > *Muhammad Shoib
> > *VUONG QUOC Viet
> >
> > To learn more about Apache AGE, please see https://age.apache.org/
> >
> > Functionality included and addressed in this release:
> >
> > - Add an upgrading SQL script file from 0.5.0 to 0.6.0
> > - Add upgrading file age--0.6.0--0.7.0.sql
> > - Refactor function get_agtype_value_object_value
> > - Age load issue (issue #188)
> > - Refactor agtype_access_operator
> > - Bugfix - Remove INLINE from function declaration
> > - Rebase VLE code
> > - Implement Merge Clause
> > - Bugfix: chained union logic
> > - Allow a path of one vertex
> > - Created functions for load graph from CSV files
> > - Add UNION into EXPLAIN grammar rule
> > - Implement UNWIND clause(issue #173)
> > - Bugfix:(nodejs) Corrects parsing for independence value(issue #177)
> > - Feat: Implement OPTIONAL MATCH (issue #175)
> > - Update copyright in NOTICE
> >
> >
> > *
> >
> > The git tag to be discussed and voted upon:
> > https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc1
> >
> > The git commit hash:
> >   commit 282c24f4aa7150daceba15742966ac6be77a35c4
> >
> > The release files for 1.0.0, can be found at:
> >  https://dist.apache.org/repos/dist/dev/incubator/age/1.0.0.rc1/
> >
> > Signatures used for AGE RCs can be found in this file:
> > https://downloads.apache.org/incubator/age/KEYS
> >
> > The fingerprint of key to sign release artifacts:
> >   C3F1 A95F 43D0 CCF6 A5EF  92C5 4E03 406A 5227 E499
> >
> > For information about the contents of this release, see:
> > https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc1
> >
> > *
> >
> > Please vote:
> >
> > [ ] +1 Release this package as Apache AGE 1.0.0-rc1
> > [ ] 0  I won't get in the way
> > [ ] -1 Do not release this package because ...
> >
> >
> > This vote will be open for 72 hours.
> >
> > Thank you for your time.
> >
> >
> > Best Regards,
> > Nick Sorrell
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache AGE (Incubating) as a TLP

[John Gemignani]

untries) and elevated 4 committers to PPMC
> > > >-
> > > >
> > > >7 Apache releases (AGE 0.3, 0.4, 0.5, 0.6, 0.7 and 1.0 and
> > sub-project
> > > >AGE Viewer 1.0) from different release managers [3]
> > > >-
> > > >
> > > >4 mentors, 13 PPMC members / committers (mentors excluded)
> > > >-
> > > >
> > > >50+ unique contributors - Contributions span more than 20
> countries
> > > >across the globe
> > > >
> > > >
> > > >-
> > > >
> > > >Developed and maintained the Apache AGE website [4]
> > > >-
> > > >
> > > >Created an online user guide updated automatically to support new
> > > >version of AGE. [5]
> > > >-
> > > >
> > > >Assessed ourselves against the Apache Project maturity matrix [6]
> > and
> > > >didn't find any issues
> > > >
> > > >
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/q2cgbnhvpzk2k0m8yfh89lzc75qym9k9
> > > >
> > > > [2] https://lists.apache.org/thread/lr3x9bm8jyv6o5kvyh7cf3tyxrpp2kwm
> > > >
> > > > [3] Apache AGE website release page <
> > https://age.apache.org/?l=versions>
> > > >
> > > > [4] https://age.apache.org/
> > > >
> > > > [5] Online user guide at Apache AGE website <
> https://age.apache.org/#>
> > > > under the Documentation menu
> > > >
> > > > [6] Apache AGE maturity assessment <
> https://age.apache.org/?l=maturity
> > >
> > > >
> > > > Please see the proposed board resolution below and let us know what
> you
> > > > think.
> > > >
> > > > The discussion will remain open for at least 72 hours.
> > > >
> > > >
> > >
> >
> 
> > > >
> > > > Establish the Apache AGE Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> > > >
> > > > the Foundation and consistent with the Foundation's purpose to
> > establish
> > > >
> > > > a Project Management Committee charged with the creation and
> > maintenance
> > > >
> > > > of open-source software, for distribution at no charge to the public,
> > > >
> > > > related to a multi-model database that enables graph and relational
> > > >
> > > > models built on PostgreSQL.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > >
> > > > (PMC), to be known as the "Apache AGE Project", be and hereby is
> > > >
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache AGE Project be and hereby is responsible
> for
> > > >
> > > > the creation and maintenance of software related to a multi-model
> > > >
> > > > database that enables graph and relational models built on
> PostgreSQL;
> > > >
> > > > and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache AGE" be and
> hereby
> > > >
> > > > is created, the person holding such office to serve at the direction
> of
> > > >
> > > > the Board of Directors as the chair of the Apache AGE Project, and to
> > > >
> > > > have primary responsibility for management of the projects within the
> > > >
> > > > scope of responsibility of the Apache AGE Project; and be it further
> > > >
> > > > RESOLVED, that the persons listed immediately below be and hereby are
> > > >
> > > > appointed to serve as the initial members of the Apache AGE Project:
> > > >
> > > >  * Alex Kwak   
> > > >
> > > >  * Dehowe Feng 
> > > >
> > > >  * Eya Badal   
> > > >
> > > >  * Felix Cheung
> > > >
> > > >  * Jasper Blues
> > > >
> > > >  * John Gemignani  
> > > >
> > > >  * Josh Innis  
> > > >
> > > >  * Juan Pan
> > > >
> > > >  * Kevin Ratnasekera   
> > > >
> > > >  * Nick Sorrell
> > > >
> > > >  * Pieterjan De Potter 
> > > >
> > > >  * Von Gosling 
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eya Badal be appointed
> to
> > > >
> > > > the office of Vice President, Apache AGE, to serve in accordance with
> > > >
> > > > and subject to the direction of the Board of Directors and the Bylaws
> > of
> > > >
> > > > the Foundation until death, resignation, retirement, removal or
> > > >
> > > > disqualification, or until a successor is appointed; and be it
> further
> > > >
> > > > RESOLVED, that the Apache AGE Project be and hereby is tasked with
> the
> > > >
> > > > migration and rationalization of the Apache Incubator AGE podling;
> and
> > > >
> > > > be it further
> > > >
> > > > RESOLVED, that all responsibilities pertaining to the Apache
> Incubator
> > > >
> > > > AGE podling encumbered upon the Apache Incubator PMC are hereafter
> > > >
> > > > discharged.
> > > >
> > > >
> > > > Thank you,
> > > > Eya Badal
> > > >
> > > >- e...@apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Graduate Apache AGE (Incubating) as a TLP

[John Gemignani]

de at Apache AGE website <
> > https://age.apache.org/#>
> > > > > under the Documentation menu
> > > > >
> > > > > [7] Apache AGE maturity assessment <
> > https://age.apache.org/?l=maturity
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> 
> > > > >
> > > > > Establish the Apache AGE Project
> > > > >
> > > > > WHEREAS, the Board of Directors deems it to be in the best
> interests
> > of
> > > > >
> > > > > the Foundation and consistent with the Foundation's purpose to
> > > establish
> > > > >
> > > > > a Project Management Committee charged with the creation and
> > > maintenance
> > > > >
> > > > > of open-source software, for distribution at no charge to the
> public,
> > > > >
> > > > > related to a multi-model database that enables graph and relational
> > > > >
> > > > > models built on PostgreSQL.
> > > > >
> > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > >
> > > > > (PMC), to be known as the "Apache AGE Project", be and hereby is
> > > > >
> > > > > established pursuant to Bylaws of the Foundation; and be it further
> > > > >
> > > > > RESOLVED, that the Apache AGE Project be and hereby is responsible
> > for
> > > > >
> > > > > the creation and maintenance of software related to a multi-model
> > > > >
> > > > > database that enables graph and relational models built on
> > PostgreSQL;
> > > > >
> > > > > and be it further
> > > > >
> > > > > RESOLVED, that the office of "Vice President, Apache AGE" be and
> > hereby
> > > > >
> > > > > is created, the person holding such office to serve at the
> direction
> > of
> > > > >
> > > > > the Board of Directors as the chair of the Apache AGE Project, and
> to
> > > > >
> > > > > have primary responsibility for management of the projects within
> the
> > > > >
> > > > > scope of responsibility of the Apache AGE Project; and be it
> further
> > > > >
> > > > > RESOLVED, that the persons listed immediately below be and hereby
> are
> > > > >
> > > > > appointed to serve as the initial members of the Apache AGE
> Project:
> > > > >
> > > > >  * Alex Kwak   
> > > > >
> > > > >  * Dehowe Feng 
> > > > >
> > > > >  * Eya Badal   
> > > > >
> > > > >  * Felix Cheung
> > > > >
> > > > >  * Jasper Blues
> > > > >
> > > > >  * John Gemignani  
> > > > >
> > > > >  * Josh Innis  
> > > > >
> > > > >  * Juan Pan
> > > > >
> > > > >  * Kevin Ratnasekera   
> > > > >
> > > > >  * Nick Sorrell
> > > > >
> > > > >  * Pieterjan De Potter 
> > > > >
> > > > >  * Von Gosling 
> > > > >
> > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eya Badal be appointed
> > to
> > > > >
> > > > > the office of Vice President, Apache AGE, to serve in accordance
> with
> > > > >
> > > > > and subject to the direction of the Board of Directors and the
> Bylaws
> > > of
> > > > >
> > > > > the Foundation until death, resignation, retirement, removal or
> > > > >
> > > > > disqualification, or until a successor is appointed; and be it
> > further
> > > > >
> > > > > RESOLVED, that the Apache AGE Project be and hereby is tasked with
> > the
> > > > >
> > > > > migration and rationalization of the Apache Incubator AGE podling;
> > and
> > > > >
> > > > > be it further
> > > > >
> > > > > RESOLVED, that all responsibilities pertaining to the Apache
> > Incubator
> > > > >
> > > > > AGE podling encumbered upon the Apache Incubator PMC are hereafter
> > > > >
> > > > > discharged.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> *
> > > > > * Thank you,
> > > > > Eya Badal on behalf of the Apache AGE (incubating) community
> > > > >
> > > >
> > > --
> > > Muhammad *Shoaib, PhD*
> > > Data Scientist, Bioinformatician and AI Engineer
> > > PhD (Biomedical Engineering)
> > > Email: muhemmed.sho...@gmail.com
> > >
> >
>

Re: [VOTE] Graduate Apache AGE (Incubating) as a TLP

[John Gemignani]

Hi Justin,

The vote has been open for 72 hours. Eya was just giving everyone a heads
up that it will be closing shortly.

Hope that is helpful.

John

On Wed, May 11, 2022, 8:48 PM Justin Mclean 
wrote:

> Hi,
>
> In general, votes should last 72 hours to allow people to respond. It is
> unusual for a graduation vote to only be held for 24 hours. Is there any
> reason for needed for the short voting time?
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: PMC is a committee

[John Gemignani]

"I'd be interested to know whether there is any real semantic danger here
or whether it is a flavor of Misophonia. I've personally never
misunderstood someone in the context of their conversation."

I would say, from the responses so far, even including the original
complaint, that there is never any confusion on what was meant. It is, as
you say, a flavor of misophonia. Or, as I would say, someone unnecessarily
being a pedant.

Dare I ask, what are the penalties going to be for these
innocuous infractions of English? Verbal lashes? Loss of PMC status?
Correction, PMC member status? Timeouts or spinlocks in /dev/null?

What about misspellings or misuse of other words? Or, using a Chinese word
by mistake? How much is an extra capitalization going to cost me? Or a
missed sarcasm?

Seriously, I feel like we all need to know this before we continue this
discussion.

john

On Wed, Jul 3, 2024 at 8:02 AM larry mccay  wrote:

> I'd be interested to know whether there is any real semantic danger here or
> whether it is a flavor of Misophonia.
> I've personally never misunderstood someone in the context of their
> conversation.
>
> If there is a real danger like a decision being made for a whole community
> based on someone calling themselves a PMC and it is misunderstood to mean
> they are speaking as the entire PMC then perhaps we should rename it and
> make it more explicit. Of course, no one will stop using PMC either
> correctly or incorrectly - at least for a very long time.
>
> I'd also note that if a lot of folks are referring to themselves as an
> inappropriate acronym that perhaps there is a missing acronym for what they
> mean.
> It seems folks are looking for something more precise and important
> sounding.
>
> "Member" may be too generic and overloaded (even within Apache itself) to
> express what they are trying to say.
> ICM - Individual Committee Member?
> PCM - Project Committee Member? Too close...
>
> Anyway, my opinion is that we either accept it and move on or add something
> else. Trying to shove some semantic minutiae down everyone's throats isn't
> likely worth the effort.
>
>
> On Wed, Jul 3, 2024 at 10:19 AM Dave Fisher  wrote:
>
> >
> >
> > > On Jul 2, 2024, at 11:52 PM, Christofer Dutz <
> christofer.d...@c-ware.de>
> > wrote:
> > >
> > > I mean … I think I have never really been confused if someone used
> “PMC”
> > or “PMC member” as from the context it was clear.
> > > What however I really hate to see in emails is people using short forms
> > LMAA, WTF, IANAL, STFU, … this list is long and obviously I listed the
> ones
> > I knew.
> > > Quite often when people use these short forms, I feel a bit excluded
> and
> > have to search or ask what they mean, so if we freak out about people
> using
> > the short form PMC, then I would also argue to freak out on using other
> > short forms ;-)
> >
> > No disrespect but doesn’t Deutsch combine words to make longer words so
> > that PMC Member should according to Google Translate be "Mitglied des
> > Projektmanagementausschusses”?! Acronyms nein! Composition ja! Verzeihen
> > Sie mir meine kleine aber!
> >
> > Best,
> > Dave
> > >
> > > Chris
> > >
> > > Von: Yuanbo Liu 
> > > Datum: Mittwoch, 3. Juli 2024 um 05:24
> > > An: general@incubator.apache.org 
> > > Betreff: Re: PMC is a committee
> > > Also it's driving me crazy to see native speakers saying "...not...no
> > > more". Teachers tell me it is supposed to be "any more"..
> > >
> > > On Wed, Jul 3, 2024 at 11:03 AM tison  wrote:
> > >
> > >> ... and yes. For non-native speakers, it's possible to feel less
> > >> uncomfortable to use "PMC" as an abbr. to PMC members. Just .. as an
> > >> opaque term.
> > >>
> > >> Best,
> > >> tison.
> > >>
> > >> Xuanwo  于2024年7月2日周二 19:56写道：
> > >>>
> > >>> This thread reminds me of tison's proposal that use "Maintainer"
> > instead
> > >> of "PMC Member".
> > >>>
> > >>> https://lists.apache.org/thread/xsjojmksqtnsdjcg0yf4vz0xy82llhmw
> > >>>
> > >>> On Wed, Jul 3, 2024, at 10:04, Jiacai Liu wrote:
> > >>>>> And, we can all be tired, overworked, or lazy and say the wrong
> > >>>>> thing *or*
> > >>>>> get into bad habits.
> > >>>>
> > >>>> Thank John for your kindly 

Re: PMC is a committee

[John Gemignani]

I do believe that you spelled it incorrectly, it is bikeshedding, one word.

And, shouldn't it be, PMCM or PMCm? That makes more sense.

john

On Wed, Jul 3, 2024 at 10:32 AM Craig Russell  wrote:

> As long as we are bike shedding:
>
> We have PMC: Project Management Committee
> PPMC: Podling Project Management Committee
> MPMC: Member, Project Management Committee
>
> Craig
>
> > On Jul 2, 2024, at 23:52, Christofer Dutz 
> wrote:
> >
> > I mean … I think I have never really been confused if someone used “PMC”
> or “PMC member” as from the context it was clear.
> > What however I really hate to see in emails is people using short forms
> LMAA, WTF, IANAL, STFU, … this list is long and obviously I listed the ones
> I knew.
> > Quite often when people use these short forms, I feel a bit excluded and
> have to search or ask what they mean, so if we freak out about people using
> the short form PMC, then I would also argue to freak out on using other
> short forms ;-)
> >
> > Chris
> >
> > Von: Yuanbo Liu 
> > Datum: Mittwoch, 3. Juli 2024 um 05:24
> > An: general@incubator.apache.org 
> > Betreff: Re: PMC is a committee
> > Also it's driving me crazy to see native speakers saying "...not...no
> > more". Teachers tell me it is supposed to be "any more"..
> >
> > On Wed, Jul 3, 2024 at 11:03 AM tison  wrote:
> >
> >> ... and yes. For non-native speakers, it's possible to feel less
> >> uncomfortable to use "PMC" as an abbr. to PMC members. Just .. as an
> >> opaque term.
> >>
> >> Best,
> >> tison.
> >>
> >> Xuanwo  于2024年7月2日周二 19:56写道：
> >>>
> >>> This thread reminds me of tison's proposal that use "Maintainer"
> instead
> >> of "PMC Member".
> >>>
> >>> https://lists.apache.org/thread/xsjojmksqtnsdjcg0yf4vz0xy82llhmw
> >>>
> >>> On Wed, Jul 3, 2024, at 10:04, Jiacai Liu wrote:
> >>>>> And, we can all be tired, overworked, or lazy and say the wrong
> >>>>> thing *or*
> >>>>> get into bad habits.
> >>>>
> >>>> Thank John for your kindly understanding.
> >>>>
> >>>> Also as a non-native English speaker, when I see abbreviation like
> >>>> PMC,
> >>>> my first insight is this word could be used on its own, `PMC
> >>>> member` looks a little redundancy for me...
> >>>>
> >>>> on Wed, Jul 03, 2024 at 08:50:45 AM +0800, John Gemignani wrote:
> >>>>
> >>>>> My 2 cents as being a PMC member and once part of incubation,...
> >>>>>
> >>>>> To be honest, I've never really paid much attention when someone
> >>>>> stated
> >>>>> they're a PMC. I knew what was meant and just auto corrected it
> >>>>> in my head.
> >>>>> I have used, without fully thinking about it, PMC as, "I am a
> >>>>> PMC" as well.
> >>>>> When I meant, or should have meant, "I am a PMC member", and I'm
> >>>>> a native
> >>>>> English speaker.
> >>>>>
> >>>>> As was mentioned, people from different cultures might have
> >>>>> different ways
> >>>>> of using a term like PMC. I just don't feel that getting upset
> >>>>> over,
> >>>>> arguably an innocuous misuse, engenders community.
> >>>>>
> >>>>> And, we can all be tired, overworked, or lazy and say the wrong
> >>>>> thing *or*
> >>>>> get into bad habits.
> >>>>>
> >>>>> Again, my 2 cents.
> >>>>>
> >>>>> john
> >>>>>
> >>>>> On Tue, Jul 2, 2024 at 5:33 PM Dave Fisher 
> >>>>> wrote:
> >>>>>
> >>>>>> Hi Tison,
> >>>>>>
> >>>>>> I’m sympathetic as well.
> >>>>>>
> >>>>>>> On Jul 2, 2024, at 5:11 PM, tison 
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi Greg,
> >>>>>>>
> >>>>>>> I saw this kind of thread many times, and I also corrected it
> >>>>>>> dozens
> >>>>>>> of times. Actually, this is part of the reason for [