You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Ryan Blue <bl...@apache.org> on 2020/05/12 22:32:43 UTC
Fwd: [VOTE] Graduate to a top-level project
Forwarding the graduation vote thread from the Iceberg community to let
everyone here know, per [1].
[1]:
https://incubator.apache.org/guides/graduation.html#community_graduation_vote
---------- Forwarded message ---------
From: Ryan Blue <bl...@apache.org>
Date: Tue, May 12, 2020 at 2:16 PM
Subject: [VOTE] Graduate to a top-level project
To: Iceberg Dev List <de...@iceberg.apache.org>
Hi everyone,
I propose that the Iceberg community should petition to graduate from the
Apache Incubator to a top-level project.
Here is the draft board resolution:
Establish the Apache Iceberg 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 managing huge analytic datasets using a standard at-rest
table format that is designed for high performance and ease of use..
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Iceberg Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Iceberg Project be and hereby is responsible
for the creation and maintenance of software related to managing huge
analytic datasets using a standard at-rest table format that is designed
for high performance and ease of use; and be it further
RESOLVED, that the office of "Vice President, Apache Iceberg" 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 Iceberg
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Iceberg
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 Iceberg Project:
* Anton Okolnychyi <ao...@apache.org>
* Carl Steinbach <cw...@apache.org>
* Daniel C. Weeks <dw...@apache.org>
* James R. Taylor <ja...@apache.org>
* Julien Le Dem <ju...@apache.org>
* Owen O'Malley <om...@apache.org>
* Parth Brahmbhatt <pa...@apache.org>
* Ratandeep Ratti <rd...@apache.org>
* Ryan Blue <bl...@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ryan Blue be appointed to
the office of Vice President, Apache Iceberg, 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 Iceberg Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Iceberg
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Iceberg podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Please vote in the next 72 hours.
[ ] +1 Petition the IPMC to graduate to top-level project
[ ] +0
[ ] -1 Wait to graduate because . . .
--
Ryan Blue
--
Ryan Blue
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <rb...@netflix.com.INVALID>.
> I would assume because it's a dependancy and not bundled in the source
release.
I searched for "copied from" to test that assumption and found code from
Apache Commons:
https://github.com/apache/tomcat/blob/bb0befeebe18a9b8ff50e686a3d06e84ccdfb108/java/org/apache/tomcat/util/http/fileupload/package-info.java#L20-L22
That lines up with my reading of LEGAL-234. If a copyright line for each
project was required in NOTICE, then the question of which dates are
required would not be relevant. And the conclusion to that question was
that "My [Mark T.] reading of [1] is that you only need the Accumulo dates."
On Wed, May 20, 2020 at 5:04 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Mark is talking about what they did for the Tomcat NOTICE, with no
> mention
> > of Commons: https://github.com/apache/tomcat/blob/master/NOTICE
>
> I would assume because it's a dependancy and not bundled in the source
> release. Even if that is the case older projects may not be in line with
> ASF policy or do thing in a different way because of other reasons.
>
> Only things that are bundled in the release need to be mentioned in
> LICENSE and NOTICE.
>
> > And the result was this Accumulo NOTICE:
> > https://github.com/apache/accumulo/blob/master/NOTICE
>
> Which from a casual glance looks fine, the license includes JQuery, Flat
> and code form OneLab. None of those are ALv2 or have other required notices
> so there’s no effect NOTICE.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Ryan Blue
Software Engineer
Netflix
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Mark is talking about what they did for the Tomcat NOTICE, with no mention
> of Commons: https://github.com/apache/tomcat/blob/master/NOTICE
I would assume because it's a dependancy and not bundled in the source release. Even if that is the case older projects may not be in line with ASF policy or do thing in a different way because of other reasons.
Only things that are bundled in the release need to be mentioned in LICENSE and NOTICE.
> And the result was this Accumulo NOTICE:
> https://github.com/apache/accumulo/blob/master/NOTICE
Which from a casual glance looks fine, the license includes JQuery, Flat and code form OneLab. None of those are ALv2 or have other required notices so there’s no effect NOTICE.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <rb...@netflix.com.INVALID>.
> You see in that Mark recommends including the project name/copyright line
in the NOTICE file as I’ve suggested to you.
Are you sure about that?
Mark is talking about what they did for the Tomcat NOTICE, with no mention
of Commons: https://github.com/apache/tomcat/blob/master/NOTICE
And the result was this Accumulo NOTICE:
https://github.com/apache/accumulo/blob/master/NOTICE
On Wed, May 20, 2020 at 3:56 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > 1. Should the entire file header be moved into NOTICE when a
> third-party
> > file is contributed, or should we edit it
>
> When a 3rd party file is contributed, it’s header stays were it is on the
> file, it’s not moved to NOTICE. It the file was part of a software grant
> then the copyright notice is added to NOTICE.
>
> > 2. When including all or part of another ASF project is the standard
> > NOTICE sufficient?
>
> No it depends on the content of it's NOTICE file (and what parts you have
> bundled).
>
> > I went back through legal-discuss and found that #2 has already been
> asked
> > and answered on https://issues.apache.org/jira/browse/LEGAL-234.
>
> You see in that Mark recommends including the project name/copyright line
> in the NOTICE file as I’ve suggested to you.
>
> > If the source file is submitted with a copyright notice included in it,
> the
> > copyright owner (or owner’s agent) must either:
> > a. remove such notices, or
> > b. move them to the NOTICE file associated with each applicable project
> > release, or
> > c. provide written permission for the ASF to make such removal or
> > relocation of the notices.
>
> You note it states to move the copyright notice not the header.
>
> License information belongs in LICENSE, other notices in NOTICE.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Ryan Blue
Software Engineer
Netflix
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> 1. Should the entire file header be moved into NOTICE when a third-party
> file is contributed, or should we edit it
When a 3rd party file is contributed, it’s header stays were it is on the file, it’s not moved to NOTICE. It the file was part of a software grant then the copyright notice is added to NOTICE.
> 2. When including all or part of another ASF project is the standard
> NOTICE sufficient?
No it depends on the content of it's NOTICE file (and what parts you have bundled).
> I went back through legal-discuss and found that #2 has already been asked
> and answered on https://issues.apache.org/jira/browse/LEGAL-234.
You see in that Mark recommends including the project name/copyright line in the NOTICE file as I’ve suggested to you.
> If the source file is submitted with a copyright notice included in it, the
> copyright owner (or owner’s agent) must either:
> a. remove such notices, or
> b. move them to the NOTICE file associated with each applicable project
> release, or
> c. provide written permission for the ASF to make such removal or
> relocation of the notices.
You note it states to move the copyright notice not the header.
License information belongs in LICENSE, other notices in NOTICE.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <bl...@apache.org>.
To summarize, it looks like there are two issues:
1. Should the entire file header be moved into NOTICE when a third-party
file is contributed, or should we edit it
2. When including all or part of another ASF project is the standard
NOTICE sufficient?
I went back through legal-discuss and found that #2 has already been asked
and answered on https://issues.apache.org/jira/browse/LEGAL-234. The
recommendation from Mark Thomas was to not copy the standard NOTICE
contents from other projects. Marvin Humphrey also notes that this
documentation is canonical:
http://www.apache.org/legal/src-headers.html#notice and the other with
confusing clause (“must be considered”) is advisory.
The same canonical documentation also covers source file headers for code
that was contributed. This is the document that we used when we brought in
the contribution with the full Cloudera header. It states:
If the source file is submitted with a copyright notice included in it, the
copyright owner (or owner’s agent) must either:
a. remove such notices, or
b. move them to the NOTICE file associated with each applicable project
release, or
c. provide written permission for the ASF to make such removal or
relocation of the notices.
That’s why we waited to merge the PR until someone from Cloudera had
consented to moving the header. We didn’t ask whether we could edit the
header at that time. Given that we are careful to document consent to move
the header in this situation, I don’t think that we should edit it years
after the contribution. Everyone at the time thought that the header was
the entire block of text; while I understand where you’re drawing a
distinction, I think it is reasonable to continue publishing the entire
header as it was found in the original contribution.
Are you satisfied with those answers, Justin?
On Mon, May 18, 2020 at 6:57 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > At the time, we considered the whole header to be the relevant "Copyright
> > notification". Do you think this practice is incorrect?
>
> I’ve not seem other projects do it this way, it's generally:
> "Portions of this software were developed at
> Acme Inc, copyright 20XX.”
>
> > Which ones are you referring to?
> >
> > I just went through the ones that you mentioned:
> > * Spark's NOTICE doesn't have relevant portions, considering what is used
> > is the check-license script and some Parquet vectorization code.
> > * Same for Hive's NOTICE because the only portion of Hive that is used
> is a
> > SQL file with metastore table definitions.
> > * The relevant portion of Parquet's notice is the code from Cloudera and
> > the Iceberg NOTICE contains the same text.
> > * Avro's NOTICE contains mostly entries for the C# project and the only
> > code from Avro is the decimal conversion code.
> > * The iBATIS NOTICE contains two full relocated copyright headers, with
> > Copyright attributed to the HSQL Development Group and the Hypersonic SQL
> > group. ScriptRunner that is included in Iceberg was written by Clinton
> > Begin, who started the ASF project, so those sections aren't relevant.
>
> The Spark notice contains:
> "Apache Spark
> Copyright 2014 and onwards The Apache Software Foundation.”
>
> The Hive notice contains:
> "Apache Hive
> Copyright 2008-2018 The Apache Software Foundation”
>
> etc
>
> This I believe would apply to your notice file.
>
> > Can you explain a bit more about this?
>
> See above.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Ryan Blue
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> At the time, we considered the whole header to be the relevant "Copyright
> notification". Do you think this practice is incorrect?
I’ve not seem other projects do it this way, it's generally:
"Portions of this software were developed at
Acme Inc, copyright 20XX.”
> Which ones are you referring to?
>
> I just went through the ones that you mentioned:
> * Spark's NOTICE doesn't have relevant portions, considering what is used
> is the check-license script and some Parquet vectorization code.
> * Same for Hive's NOTICE because the only portion of Hive that is used is a
> SQL file with metastore table definitions.
> * The relevant portion of Parquet's notice is the code from Cloudera and
> the Iceberg NOTICE contains the same text.
> * Avro's NOTICE contains mostly entries for the C# project and the only
> code from Avro is the decimal conversion code.
> * The iBATIS NOTICE contains two full relocated copyright headers, with
> Copyright attributed to the HSQL Development Group and the Hypersonic SQL
> group. ScriptRunner that is included in Iceberg was written by Clinton
> Begin, who started the ASF project, so those sections aren't relevant.
The Spark notice contains:
"Apache Spark
Copyright 2014 and onwards The Apache Software Foundation.”
The Hive notice contains:
"Apache Hive
Copyright 2008-2018 The Apache Software Foundation”
etc
This I believe would apply to your notice file.
> Can you explain a bit more about this?
See above.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <rb...@netflix.com.INVALID>.
On Mon, May 18, 2020 at 4:40 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> > Per NOTICE policy
> > <https://www.apache.org/dev/licensing-howto.html#mod-notice>: "Copyright
> > notifications which have been relocated, rather than removed, from source
> > files must be preserved in NOTICE”
>
> Yes the copyright line needs to be mentioned not the licenser header.
>
At the time, we considered the whole header to be the relevant "Copyright
notification". Do you think this practice is incorrect?
> > My understanding is that it is not necessary to modify NOTICE for an ASF
> > dependency, if it is the boiler-plate ASF NOTICE because the project's
> > notice contains "This product includes software developed at the Apache
> > Software Foundation", while the LICENSE contains the copyright
> information
> > for individual ASF projects.
>
> Yes but those notice files contain more than that and are not boiler-plate.
>
Which ones are you referring to?
I just went through the ones that you mentioned:
* Spark's NOTICE doesn't have relevant portions, considering what is used
is the check-license script and some Parquet vectorization code.
* Same for Hive's NOTICE because the only portion of Hive that is used is a
SQL file with metastore table definitions.
* The relevant portion of Parquet's notice is the code from Cloudera and
the Iceberg NOTICE contains the same text.
* Avro's NOTICE contains mostly entries for the C# project and the only
code from Avro is the decimal conversion code.
* The iBATIS NOTICE contains two full relocated copyright headers, with
Copyright attributed to the HSQL Development Group and the Hypersonic SQL
group. ScriptRunner that is included in Iceberg was written by Clinton
Begin, who started the ASF project, so those sections aren't relevant.
From double-checking, it appears that the last time we updated license
documentation, we did it correctly.
> > " though the ASF copyright line and any other portions of NOTICE must be
> considered for propagation.”
>
> I don’t believe your project have done this. You'll note the copyright
> line will be different depending on when you incorporated the code.
>
Can you explain a bit more about this? Do you think that we skipped it or
just didn't do it correctly? What about the copyright lines are not
correct? And what do you think we need to do to correct it?
--
Ryan Blue
Software Engineer
Netflix
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Per NOTICE policy
> <https://www.apache.org/dev/licensing-howto.html#mod-notice>: "Copyright
> notifications which have been relocated, rather than removed, from source
> files must be preserved in NOTICE”
Yes the copyright line needs to be mentioned not the licenser header.
> My understanding is that it is not necessary to modify NOTICE for an ASF
> dependency, if it is the boiler-plate ASF NOTICE because the project's
> notice contains "This product includes software developed at the Apache
> Software Foundation", while the LICENSE contains the copyright information
> for individual ASF projects.
Yes but those notice files contain more than that and are not boiler-plate.
> " though the ASF copyright line and any other portions of NOTICE must be considered for propagation.”
I don’t believe your project have done this. You'll note the copyright line will be different depending on when you incorporated the code.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <bl...@apache.org>.
On Mon, May 18, 2020 at 3:35 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > What license information are you referring to?
>
> " Licensed under the Apache License” by Cloudera
>
This is not a license, it is the original copyright header for files that
were contributed by Cloudera. Here's the commit
<https://github.com/apache/parquet-mr/commit/ddbeb4dd17d9c219b99b1e66d8be28efe37e3aa6>
.
Per NOTICE policy
<https://www.apache.org/dev/licensing-howto.html#mod-notice>: "Copyright
notifications which have been relocated, rather than removed, from source
files must be preserved in NOTICE"
> > Which entries in the LICENSE file? Many Apache-licensed projects don't
> have
> > NOTICE files.
>
> Yes but all ASF projects do, your license mentions Apache Avro, Apache
> Parquet, Apache iBATIS, Apache Hive and Apache Spark.
>
My understanding is that it is not necessary to modify NOTICE for an ASF
dependency, if it is the boiler-plate ASF NOTICE because the project's
notice contains "This product includes software developed at the Apache
Software Foundation", while the LICENSE contains the copyright information
for individual ASF projects.
NOTICE policy
<https://www.apache.org/dev/licensing-howto.html#bundle-asf-product>: "It
is not necessary to duplicate the line 'This product includes software
developed at the Apache Software Foundation...', though the ASF copyright
line and any other portions of NOTICE must be considered for propagation."
And the general guidance: "Do not add anything to NOTICE which is not
legally required."
Also kitesdk does have a notice file [1] as does presto [2]
>
Given the guidance, "Do not add anything to NOTICE which is not legally
required," and "The LICENSE and NOTICE files must exactly represent the
contents of the distribution they reside in," we have been including only
sections of third-party NOTICE files that apply to the code distributed by
Apache Iceberg.
The Kite NOTICE file credits the ASF (already covered) and Saxonica.
Because I was a Kite developer, I know that the Saxonica part does not
apply to the code that was included in Apache Iceberg. In fact, Iceberg
only includes classes from Kite that I wrote while I worked at Cloudera.
For the Presto, the code that we include is also clearly not covered by
either line of the Presto NOTICE: it is neither t-digest related nor
AVLTreeDigest related. Because this clearly doesn't apply to the code we
are using, we omitted it.
I should note that when it isn't clear which parts of a third-party NOTICE
apply to the code that a project uses, our practice is to copy the entire
contents of the third-party NOTICE into ours.
> What is the correct archive location?
>
>
> https://archive.apache.org/dist/incubator/iceberg/apache-iceberg-0.7.0-incubating/
>
Thanks, I'll open a PR to update it.
rb
--
Ryan Blue
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> What license information are you referring to?
" Licensed under the Apache License” by Cloudera
> Which entries in the LICENSE file? Many Apache-licensed projects don't have
> NOTICE files.
Yes but all ASF projects do, your license mentions Apache Avro, Apache Parquet, Apache iBATIS, Apache Hive and Apache Spark.
Also kitesdk does have a notice file [1] as does presto [2]
> What is the correct archive location?
https://archive.apache.org/dist/incubator/iceberg/apache-iceberg-0.7.0-incubating/
Thanks,
Justin
1. https://github.com/kite-sdk/kite/blob/master/NOTICE.txt
2. https://github.com/prestodb/presto/blob/master/NOTICES
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <rb...@netflix.com.INVALID>.
Hi Justin,
I have more questions for you inline:
On Sat, May 16, 2020 at 6:29 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
> 1. You have included some license information this should be in LICENSE
> not NOTICE
>
What license information are you referring to?
> 2. Going on what is listed in the LICENSE file you are missing content
> from bundled code NOTICE files [1] (see bundling an apache 2.0 licences
> dependancy)
>
Which entries in the LICENSE file? Many Apache-licensed projects don't have
NOTICE files. Maybe you are looking for a NOTICE entry for projects with no
NOTICE?
Re the download page, the older version 0.7 needs to point to the archive
> not the mirrors and not use https://dist.apache.org/repos/dist/
What is the correct archive location?
--
Ryan Blue
Software Engineer
Netflix
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Looking at your notice file in the last release it still needs some work:
1. You have included some license information this should be in LICENSE not NOTICE
2. Going on what is listed in the LICENSE file you are missing content from bundled code NOTICE files [1] (see bundling an apache 2.0 licences dependancy)
I would suggest making another release to correct this.
Re the download page, the older version 0.7 needs to point to the archive not the mirrors and not use https://dist.apache.org/repos/dist/
Thanks,
Justin
1. https://www.apache.org/dev/licensing-howto.html
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi Owen and Ryan,
Thanks for the detailed responses, I don’t think anything more is needed. I personally think it would be best if you did another release before exiting the incubator, but if you mentors are good with only making two than that should be OK. I’ll follow up on the NOTICE issue later today.
Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Graduate to a top-level project
Posted by Owen O'Malley <ow...@gmail.com>.
On Tue, May 12, 2020 at 10:44 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> I notice a few minor things that may need to be sorted out/dicussed:
- You have only made two releases and the last one had some issue around
> licensing and NOTICE files
>
Obviously the first release at Apache takes the longest as the code and
processes migrate over. The second release was about 6 months after the
first, which is probably a bit long for a young project. I think that
moving closer to quarterly is probably a good goal.
We'll also keep a watch on bugs that should get released in 0.8.1.
- Several of the proposed PMC members don’t seem to be subscribed to the
> projects private list
>
I have sent emails (cc'ed private) to get the relevant members to
subscribe. Thanks for pointing that out.
.. Owen
Re: [VOTE] Graduate to a top-level project
Posted by Ryan Blue <bl...@apache.org>.
Thanks for taking a look, Justin. I appreciate playing devil's advocate
here to ensure this is well thought through. I'll add replies inline.
On Tue, May 12, 2020 at 10:44 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Has the project filled in a maturity model? This is optional but give the
> project and the IPMC more information about the project.
>
We have not done a formal self-assessment, but the mentors, PPMC, and ASF
members on the dev list have agreed that the project is mature in terms of
what we expect of Apache projects. Communication is open and decisions are
made by the community; we have regular community sync meetings with notes
published to the dev list; and some of the major features we are working on
are the result of the community coming to an agreement on direction
(notably, requirements for row-level deletes).
In terms of releases, we have quality license documentation (I'll address
concerns below) and have made releases with convenience binaries. I updated
license documentation for both the Parquet and Avro top-level projects and
we applied the same conventions for Iceberg. Our release process
<https://iceberg.apache.org/how-to-release/> is well documented and our
convenience binaries are produced from the source release itself.
In the graduation discussion on our dev list, an Apache member brought up
the number of new committers and we realize it would be ideal to have more.
But we also don't think that this is something that is a problem affecting
the maturity of the community. The community has demonstrated the ability
to grow contributors into committers with the two that have been added, and
we also emphasize timely reviews that give enough context to help a
contributor improve on the path to becoming a committer.
In terms of helping to develop contributors, I think the community is doing
very well and that it is not necessary to wait until some committer
threshold has been met. From the votes and discussion in the community, the
community's mentors and (by my count) 3 non-mentor Apache members agree
with this assessment.
Last, I think representation in the PPMC is important to note. Of the
active PPMC members, two companies both employ 3 PPMC members and there are
two other members employed by other companies. There is no organization
with a majority in the PPMC.
> I notice a few minor things that may need to be sorted out/dicussed:
> - The incubator disclaimer missing on your web site!
>
The disclaimer is present <https://iceberg.apache.org/disclaimer/>. Whimsy
just doesn't pick it up because the text of the link doesn't match the text
"Incubation is required of all newly accepted projects". That text is
included in the disclaimer, but the link is labelled "Disclaimer". Whimsy
does note that "The podling website scan does the best it can."
> - You have only made two releases and the last one had some issue around
> licensing and NOTICE files
>
We've applied the same policies that top-level projects use (Parquet and
Avro). I think you missed my follow-up question about NOTICE files, but
we're happy to fix any issues you find and point out. I'm just not sure
what those are, since I've read through the ASF documentation many times,
spoken with third party legal counsel, and have produced NOTICE files that
comply with ASF policy and legal requirements from my experience.
> - Download page links needs fixing
>
Can you be specific? We just updated it to use downloads.apache.org. I'm
not aware of another migration.
> - Several of the proposed PMC members don’t seem to be subscribed to the
> projects private list
>
I'll look into this. I know that one mentor has not been active due to time
constraints and may not be subscribed.
> - I note this exists https://jitpack.io/p/netflix/iceberg which under
> status claims "Iceberg is under active development at Netflix.”
>
Above that, it clearly states "Iceberg has moved! Iceberg has been donated
to the Apache Software Foundation." I can update the README if there is an
issue with the old text; although it is accurate to say that Apache Iceberg
is under active development at Netflix. I don't personally don't think this
is confusing.
> - I also note some minor 3rd party branding issues e.g [1][2]
>
For the presentation at the first link
<https://databricks.com/session_eu19/acid-orc-iceberg-and-delta-lake-an-overview-of-table-formats-for-large-scale-storage-and-analytics>,
the slides correctly use "Apache Iceberg" headings. Maybe you're referring
to the title of the presentation? I'm not sure that I would request
changing the title of a talk (already presented) when it clearly refers to
the ASF project. Do you think this is a serious trademark issue that the
PPMC should address?
The second presentation
<https://conferences.oreilly.com/strata/strata-ny-2018/public/schedule/detail/69503>
happened
before the project was donated to Apache.
In fact, both presentations occurred before the ASF signed the trademark
agreement, on 2019-09-28.
> - I note your last report stated "Add more committers and PPMC members”
> and ”grow the community” as a graduation step. Has this happened since
> last month report?
>
Growing the community and adding committers/PPMC members is a general
aspiration. This was not intended to be a self-imposed requirement.
> - The last Committer/PMC addition was over 9 months ago. Do you have any
> currently people you might consider for committership? The last report
> mentioned "A contributor has built support for Spark streaming, which is
> under review”.
>
The last committer was added in February. Looks like we didn't update the
date in our last report because August 2019 is when the previous committer
was added. I addressed the broader question of maturity above. Yes, there
are contributors on the path to committer but we don't see value in a
requirement for some number of committers before graduation.
--
Ryan Blue
Re: [VOTE] Graduate to a top-level project
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
I think the incubator will need more information before voting on this.
Has the project filled in a maturity model? This is optional but give the project and the IPMC more information about the project.
I notice a few minor things that may need to be sorted out/dicussed:
- The incubator disclaimer missing on your web site!
- You have only made two releases and the last one had some issue around licensing and NOTICE files
- Download page links needs fixing
- Several of the proposed PMC members don’t seem to be subscribed to the projects private list
- I note this exists https://jitpack.io/p/netflix/iceberg which under status claims "Iceberg is under active development at Netflix.”
- I also note some minor 3rd party branding issues e.g [1][2]
- I note your last report stated "Add more committers and PPMC members” and ”grow the community” as a graduation step. Has this happened since last month report?
- The last Committer/PMC addition was over 9 months ago. Do you have any currently people you might consider for committership? The last report mentioned "A contributor has built support for Spark streaming, which is under review”.
Thanks,
Justin
1. https://databricks.com/session_eu19/acid-orc-iceberg-and-delta-lake-an-overview-of-table-formats-for-large-scale-storage-and-analytics
2. https://conferences.oreilly.com/strata/strata-ny-2018/public/schedule/detail/69503
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org