Re: [VOTE] Release Apache Baremaps 0.7.3-rc1 (incubating)

[Julian Hyde]

I am a mentor of Baremaps. Sorry that I didn't have time to vote on
this RC on dev@.

+1 (binding)

Downloaded, checked keys, compiled and ran tests (following
instructions in README), ran RAT.

I am not familiar with "Creative Commons Public License". Is it
compatible with ALv2?

Julian

On Mon, Apr 22, 2024 at 7:13 AM Julien Waddle
 wrote:
>
> Hello
>
> + 1
>
> - build it from source => ok
> - checked download => ok
> - verified signature => ok
>
> On Mon, Apr 22, 2024 at 3:21 PM Xuanwo  wrote:
>
> > +1 binding
> >
> > [x] Download links are valid.
> > [x] Checksums and signatures.
> >
> > gpg: Signature made Wed 10 Apr 2024 04:04:56 AM CST
> > gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> > gpg: checking the trustdb
> > gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> > gpg: depth: 0  valid:  27  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 27u
> > gpg: next trustdb check due at 2024-05-25
> > gpg: Good signature from "Bertil Chapuis " [ultimate]
> > ./apache-baremaps-0.7.3-incubating-bin.tar.gz: OK
> > gpg: Signature made Wed 10 Apr 2024 04:04:57 AM CST
> > gpg:using RSA key 16D7A0B27D5ADD52BD57932971751399FB39CB84
> > gpg: Good signature from "Bertil Chapuis " [ultimate]
> > ./apache-baremaps-0.7.3-incubating-src.tar.gz: OK
> >
> > [x] LICENSE/NOTICE files exist
> > [x] No unexpected binary files
> > [x] All source files have ASF headers
> > [x] Can compile from source on archlinux x86-64
> >
> > [INFO]
> > 
> > [INFO] Reactor Summary for baremaps 0.7.3:
> > [INFO]
> > [INFO] baremaps ... SUCCESS [
> > 0.454 s]
> > [INFO] baremaps-core .. SUCCESS [
> > 49.027 s]
> > [INFO] baremaps-server  SUCCESS [01:20
> > min]
> > [INFO] baremaps-cli ... SUCCESS [01:48
> > min]
> > [INFO]
> > 
> > [INFO] BUILD SUCCESS
> > [INFO]
> > 
> > [INFO] Total time:  03:58 min
> > [INFO] Finished at: 2024-04-22T21:16:39+08:00
> > [INFO]
> > 
> > mvn install  104.60s user 4.21s system 45% cpu 3:59.40 total
> >
> > On Mon, Apr 22, 2024, at 20:20, Bertil Chapuis wrote:
> > > Thanks a lot for taking the time to cast your votes.
> > >
> > > If we carry all the votes from the dev mailing list, we currently have
> > > 2 positive binding votes and 4 positive non-binding votes. I suggest we
> > > keep this thread open until we get a third positive binding vote from
> > > the PPMC.
> > >
> > > Best regards,
> > >
> > > Bertil
> > >
> > >> On 18 Apr 2024, at 13:06, Bertil Chapuis  wrote:
> > >>
> > >> Hello Everyone,
> > >>
> > >> This is a call for a vote to release Apache Baremaps 0.7.3
> > (incubating), release candidate 1. Apache Baremaps is a toolkit and a set
> > of infrastructure components for creating, publishing, and operating online
> > maps.
> > >>
> > >> We already voted for this release candidate in our dev mailing list:
> > >> https://lists.apache.org/thread/1gv0x622fpbkr5jvsmqppvy84q1sthxq
> > >>
> > >> We now would like to request the Incubator PMC members to review and
> > vote on this release.
> > >>
> > >> You can read the release notes here:
> > >> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3-rc1
> > >>
> > >> The commit to be voted upon:
> > >> https://github.com/apache/incubator-baremaps/tree/v0.7.3-rc1
> > >>
> > >> Its hash is 92081d22601aaabbc5121c972d58dec46cb58fbe.
> > >>
> > >> Its tag is v0.7.3-rc1.
> > >>
> > >> The artifacts to be voted on are located here:
> > >> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.3-rc1/
> > >>
> > >> The hashes of the artifacts are as follows:
> > >>
> > 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
> > ./apache-baremaps-0.7.3-incubating-src.tar.gz
> > >>
> > 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
> > ./apache-baremaps-0.7.3-incubating-bin.tar.gz
> > >>
> > >> Release artifacts are signed with the following key:
> > >> http://people.apache.org/keys/committer/bchapuis.asc
> > >> https://downloads.apache.org/incubator/baremaps/KEYS
> > >>
> > >> The README file for the src distribution contains instructions for
> > building and testing the release.
> > >>
> > >> Please vote on releasing this package as Apache Baremaps 0.7.3.
> > >>
> > >> The vote is open for the next 72 hours and passes if a majority of at
> > least three +1 PMC votes are cast.
> > >>
> > >> [ ] +1 Release this package as Apache Baremaps 0.7.3
> > >> [ ] 0 I don't feel strongly about it, but I'm okay with the release

Re: Registering a release

[Julian Hyde]

PJ,

You're probably right that a podling doesn't need to do this. But it's
good practice. Also, SDAP hopes to graduate soon, so hopefully this
release will appear in Reporter when they file their first report as a
TLP.

On Wed, Mar 20, 2024 at 4:34 PM PJ Fanning  wrote:
>
> I don't think this is required for a podling release. Reporter tool
> only seems to worry about TLP releases.
>
> The releases have to be announced on mailing lists including this one
> and the main ASF announce list.
>
> On Thu, 21 Mar 2024 at 00:30, Julian Hyde  wrote:
> >
> > Can someone remind me where I go (whimsy or reporter, I presume) to
> > register a release from a podling (in this case SDAP)?
> >
> > In Calcite, a top-level project that deploys Java artifacts to Maven
> > Central, the process has been straightforward. I believe I even
> > received an email from Reporter sending me to the registration page.
> > But for SDAP I can't figure out where to register the release.
> >
> > Thanks!
> >
> > Julian
> >
> > -
> > 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: Registering a release

[Julian Hyde]

Ah, that was it. Thank you, Francis.

https://reporter.apache.org/addrelease.html?incubator-sdap

> On Mar 20, 2024, at 4:49 PM, Francis Chuang  wrote:
> 
> The reporter for Calcite is at this link: 
> https://reporter.apache.org/addrelease.html?calcite
> 
> Not sure if it works for SDAP, but you should be able to see a list of all 
> your projects here: https://reporter.apache.org/wizard/
> 
> Francis
> 
> On 21/03/2024 10:36 am, Justin Mclean wrote:
>> Hi,
>> I’m not sure what you mean by registering a release. All ASF releases need 
>> to go here:
>> https://dist.apache.org/repos/dist/release/
>> Kind Regards,
>> Justin
>>> On 21 Mar 2024, at 10:29 am, Julian Hyde  wrote:
>>> 
>>> Can someone remind me where I go (whimsy or reporter, I presume) to
>>> register a release from a podling (in this case SDAP)?
>>> 
>>> In Calcite, a top-level project that deploys Java artifacts to Maven
>>> Central, the process has been straightforward. I believe I even
>>> received an email from Reporter sending me to the registration page.
>>> But for SDAP I can't figure out where to register the release.
>>> 
>>> Thanks!
>>> 
>>> Julian
>>> 
>>> -
>>> 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
> 

Registering a release

[Julian Hyde]

Can someone remind me where I go (whimsy or reporter, I presume) to
register a release from a podling (in this case SDAP)?

In Calcite, a top-level project that deploys Java artifacts to Maven
Central, the process has been straightforward. I believe I even
received an email from Reporter sending me to the registration page.
But for SDAP I can't figure out where to register the release.

Thanks!

Julian

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache SDAP (Incubating) as a Top Level Project

[Julian Hyde]

+1 (binding)

...and good luck!

Julian

On Fri, Mar 15, 2024 at 3:19 PM Riley Kuttruff  wrote:
>
> Hi all,
>
> Following the positive feedback we received in the DISCUSS thread [1],
> we would like to open the official VOTE to graduate now.
>
> Below are some facts and project highlights from the incubation phase as
> well as the draft resolution:
>
> - Our community consists of 21 committers, with 2 being mentors and
> the remaining 19 serving as our PPMC
> - Several pending and planned invites to bring on new committers and/or
> PPMC members from additional organizations
> - Completed 3 releases with 3 release managers
> - Our software is currently being utilized by organizations such as NASA
> Jet Propulsion Laboratory, NSF National Center for Atmospheric Research,
> Florida State University, and George Mason University in support of projects
> such as the NASA Sea Level Change Portal, Estimating the Circulation and
> Climate of the Ocean (ECCO) project, GRACE/GRACE-FO, Cloud-based
> Data Match-Up Service, Integrated Digital Earth Analysis System (IDEAS),
> and many others.
> - Opened 400+ PRs across 3 main code repositories, 350+ of which are
> merged or closed (some are pending our next release)
> - Maturity model self assessment [2]
>
> Please vote on the resolution below the line to graduate and establish
> Apache SDAP as a Top-Level Project
>
> [ ] +1 Graduate Apache SDAP from the Incubator to a TLP
> [ ] 0  No opinion
> [ ] -1 Do not graduate Apache SDAP because…
>
> This vote will remain open for at least 72 hours.
>
> We’d like to also extend a sincere thank you to our mentors, current and
> former for their invaluable insight and assistance with getting us to this
> point.
>
> Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael!
>
> We’d also like to thank the SDAP community as well as the Incubator
> community for your time and support in getting us to where we are now.
>
> [1] https://lists.apache.org/thread/pv21d9kf05166hkj89lv11s65oyvbdrk
> [2] https://github.com/apache/incubator-sdap-website/blob/asf-site/maturity.md
>
> ---
>
> Establish the Apache SDAP 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 an integrated data analytic center for Big Science problems.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SDAP Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache SDAP Project be and hereby is responsible
> for the creation and maintenance of software related to an integrated data
> analytic center for Big Science problems; and be it further
>
> RESOLVED, that the office of "Vice President, Apache SDAP" 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 SDAP
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache SDAP
> 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 SDAP Project:
>
> - Edward M Armstrong 
> - Nga Thien Chung 
> - Thomas Cram 
> - Frank Greguska 
> - Thomas Huang 
> - Julian Hyde 
> - Joseph C. Jacob 
> - Jason Kang 
> - Riley Kuttruff 
> - Thomas G Loubrieu 
> - Kevin Marlis 
> - Stepheny Perez 
> - Wai Linn Phyo 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> be appointed to the office of Vice President, Apache SDAP, 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 SDAP Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator SDAP
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> ---
>
> Thank you,
>
> Riley Kuttruff
>
> -
> 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] Release Apache SDAP (incubating) 1.2.0-rc4

[Julian Hyde]

Forwarding my vote from the dev@ list:

+1 (binding)

The points made by Sebb and PJ seem valid but they do not affect this vote.

Julian

On Fri, Mar 8, 2024 at 2:25 PM sebb  wrote:
>
> On Fri, 8 Mar 2024 at 22:17, PJ Fanning  wrote:
> >
> > Hi Stepheny,
> >
> > Can you remove the old RCs from
> > https://dist.apache.org/repos/dist/dev/incubator/sdap/ ?
> >
> > Is the signing key in
> > https://dist.apache.org/repos/dist/release/incubator/sdap/KEYS ? With
> > releases, you are supposed to point users to this file not provide a
> > link to https://keyserver.ubuntu.com
>
> The KEYS file must be linked from
>
> https://downloads.apache.org/incubator/sdap/KEYS
>
> The dist.apache.org host is for staging the files, not for general 
> publication.
>
>
> > On Fri, 8 Mar 2024 at 18:55, Stepheny Perez  wrote:
> > >
> > > Hello everyone,
> > >
> > > This is a call for a vote to release Apache SDAP (incubating) version 
> > > 1.2.0-rc4.
> > >
> > > The Apache SDAP community has voted to approve release of Apache SDAP 
> > > (incubating) version 1.2.0-rc4.
> > >
> > > We now request the Incubator PMC review and vote on this release.
> > >
> > > SDAP community thread:
> > > https://lists.apache.org/thread/h9g3cdok0py2vjp1pplz1wq4ofl4sbjx
> > >
> > > Changes made between previous candidate (rc3) and this one (rc4) are as 
> > > follows:
> > > - Updated SDAP to use Poetry package manager to more explicitly manage 
> > > dependencies and transitive dependencies. This was needed to ensure no 
> > > GPL license dependencies are used by the software.
> > > - Patch for domspurge helper script
> > >
> > > Instructions for building docker images from source can be found here:
> > > https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/build.rst
> > > Instructions for deploying locally to test can be found here:
> > > https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/quickstart.rst
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc4/
> > >
> > > For convenience, the tags we built the release artifacts to be voted on
> > > from are 1.2.0-rc4:
> > >
> > > - ingester:
> > > - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc4
> > > - Commit: 5c116badfaf913734d017d41acc765ed3fd978a1
> > >
> > > - nexus:
> > > - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc4
> > > - Commit: 3fce31f08b9057db446036724e8bc62dd6d1560a
> > >
> > > For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
> > > voting on are as follows:
> > >
> > > apache-sdap-ingester-1.2.0-incubating-src.tar.gz:
> > > 7301c54e765882c45f6efe4a06463b837ace62b6eea2ae5437113357466e52f1d905c3c9d46295f1b1058b9ecf5025942f8a89b2c53a1b0d6b69cd52a8890257
> > >
> > > apache-sdap-nexus-1.2.0-incubating-src.tar.gz:
> > > 1a2907f9c36dbf0b4b25d54c095303ab0602fa9e0a9423deceae402ffd9a360e21ba832c3ea497d8eccbc6c91fedd2926b3b33181a14c22d50d0ec996282bc75
> > >
> > > Release artifacts are signed with the following key:
> > > https://keyserver.ubuntu.com/pks/lookup?op=get=0x2E8418801953621FAA322169D6F360887071C194
> > >
> > > Please vote on releasing this package as Apache SDAP (incubating) 1.2.0.
> > >
> > > The vote is open for 72 hours and passes if at least 3 +1 PMC votes are 
> > > cast.
> > >
> > > [ ] +1 Release this package as Apache SDAP (incubating) 1.2.0
> > > [ ] +0 No opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thank you,
> > > Stepheny
> > >
> > > -
> > > 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
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

[Julian Hyde]

gt; > >
> > > > > We’d like to also extend a sincere thank you to our mentors, current 
> > > > > and
> > > > > former for their invaluable insight and assistance with getting us to 
> > > > > this
> > > > > point.
> > > > >
> > > > > Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael!
> > > > >
> > > > > ---
> > > > >
> > > > > Establish the Apache SDAP 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 an integrated data analytic center for Big Science 
> > > > > problems.
> > > > >
> > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > > (PMC), to be known as the "Apache SDAP Project", be and hereby is
> > > > > established pursuant to Bylaws of the Foundation; and be it further
> > > > >
> > > > > RESOLVED, that the Apache SDAP Project be and hereby is responsible
> > > > > for the creation and maintenance of software related to an integrated 
> > > > > data
> > > > > analytic center for Big Science problems; and be it further
> > > > >
> > > > > RESOLVED, that the office of "Vice President, Apache SDAP" 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 SDAP
> > > > > Project, and to have primary responsibility for management of the
> > > > > projects within the scope of responsibility of the Apache SDAP
> > > > > 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 SDAP Project:
> > > > >
> > > > > - Edward M Armstrong 
> > > > > - Nga Thien Chung 
> > > > > - Thomas Cram 
> > > > > - Frank Greguska 
> > > > > - Thomas Huang 
> > > > > - Julian Hyde 
> > > > > - Joseph C. Jacob 
> > > > > - Jason Kang 
> > > > > - Riley Kuttruff 
> > > > > - Thomas G Loubrieu 
> > > > > - Kevin Marlis 
> > > > > - Stepheny Perez 
> > > > > - Wai Linn Phyo 
> > > > >
> > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> > > > > be appointed to the office of Vice President, Apache SDAP, 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 SDAP Project be and hereby is tasked with
> > > > > the migration and rationalization of the Apache Incubator SDAP
> > > > > podling; and be it further
> > > > >
> > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > > > > SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> > > > > discharged.
> > > > >
> > > > > [1] https://lists.apache.org/thread/vjwjmp0h2f22dv423h262cvdg5x7jl03
> > > > > [2] https://lists.apache.org/thread/m9vqwv23jdsofwgmhgxg25f5l1v2j7nz
> > > > > [3] https://lists.apache.org/thread/4o1qjsk2cly2ppxcsmm2swzd6pcg3lxj
> > > > > [4] https://lists.apache.org/thread/qtxlxl4gj6n33wvm164vdxxnwdlppttl
> > > > > [5] https://lists.apache.org/thread/rr74c35fojc7ythmcgnoplyjllhbslj4
> > > > > [6] 
> > > > > https://github.com/apache/incubator-sdap-website/blob/asf-site/maturity.md
> > > > >
> > > > > -
> > > > > 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
> > >
> > >
> >
> > -
> > 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: [LICENSE QUESTION] Use jmh as a benchmark tool

[Julian Hyde]

PS Use of jmh was addressed explicitly:
https://issues.apache.org/jira/browse/LEGAL-399

On Fri, Dec 29, 2023 at 4:50 PM Julian Hyde  wrote:
>
> According to https://issues.apache.org/jira/browse/LEGAL-450, it's OK
> to use a GPL linter. And a project can use GPL "build tools provided
> they leave no code traces (licensed under a cat X license) in your
> final release artifacts".
>
> In Calcite we use jmh on the understanding that it does not produce
> any artifacts and therefore was acceptable.
>
> Can someone explain how a benchmarking utility is different from a linter?
>
> Julian
>
> On Wed, Dec 27, 2023 at 9:19 AM tison  wrote:
> >
> > > For instance, if your maven build is `-Pbenchmark` and it's clear
> > > that the user needs to include this license when compiling from source.
> >
> > Yeah. I'm going to collaborate with Fury to follow this approach and
> > document clearly how a developer can intentionally run benchmark with
> > JMH as a dep.
> >
> > Best,
> > tison.
> >
> > John D. Ament  于2023年12月28日周四 01:07写道：
> > >
> > > On Wed, Dec 27, 2023 at 11:38 AM tison  wrote:
> > >
> > > > > application, a developer has preinstalled the JDK (or using a manager 
> > > > > of
> > > > > some kind to install it - so not something we're forcing upon them).  
> > > > > In
> > > >
> > > > No. To running a Java Application in a normal way, the JRE is
> > > > required. Saying "not something we're forcing upon them" sounds
> > > > sophistry.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > tison  于2023年12月28日周四 00:27写道：
> > > > >
> > > > > Hi John,
> > > > >
> > > > > Glad to hear your feedback. Reply inline:
> > > > >
> > > > > > In the case of JMH, the repository I linked above forces the user to
> > > > download
> > > > > > the additional dependency from maven central (or similar repository)
> > > > rather
> > > > > > than relying on the system preinstalled library.
> > > > >
> > > > > From a technical view, this is not true because you can download the
> > > > > libs manually and place them under MAVEN_HOME. Then it can be regarded
> > > > > as a "system preinstalled library". It's the same as download JDK and
> > > > > place them under JAVA_HOME.
> > > >
> > >
> > > Except that's not how these libraries are listed within your pom file.  If
> > > there was a step where you required a developer to download these files,
> > > what you're describing would be accurate, but they're downloaded in an
> > > automated fashion.  Keep in mind, this isn't the JMH that's distributed
> > > with the JDK that you're using here, it's an add-on library you're using.
> > >
> > >
> > > > >
> > > > > > you can't use org.openjdk.jmh:* as a compile/test compile
> > > > > > dependency in your project
> > > > >
> > > > > fury-benchmark is not released in binary form. But we can of course
> > > > > make it an optional dependency (or the entire module optionally)
> > > > > behind a profile and deactivated by default so that it's the same as
> > > > > how ASF projects can optionally depend on MySQL Connector Java under
> > > > > the same license.
> > > >
> > >
> > > The question here isn't about binary form.  Keep in mind that first and
> > > foremost ASF projects produce source code releases, the convenience
> > > binaries are a separate artifact.  I'm presently approaching your thread
> > > focused on the source code release.  I can see your point though and 
> > > that's
> > > where I'm suggesting asking legal may give you additional guidance that I
> > > could see leading to a similar situation as Java 9 JavaScript embeddings.
> > > Just keep in mind that you're making a module optional to compile, rather
> > > than optional to use, even though it's only being used for testing 
> > > purposes
> > > and our expectation (even though it may differ from reality) is that we're
> > > reviewing the contents of the source bundle that a user downloads to
> > > compile your code, not the binary artifact they depend upon in their
> > > projects.
> > >
> > >
> > > > >
> > &

Re: [LICENSE QUESTION] Use jmh as a benchmark tool

[Julian Hyde]

According to https://issues.apache.org/jira/browse/LEGAL-450, it's OK
to use a GPL linter. And a project can use GPL "build tools provided
they leave no code traces (licensed under a cat X license) in your
final release artifacts".

In Calcite we use jmh on the understanding that it does not produce
any artifacts and therefore was acceptable.

Can someone explain how a benchmarking utility is different from a linter?

Julian

On Wed, Dec 27, 2023 at 9:19 AM tison  wrote:
>
> > For instance, if your maven build is `-Pbenchmark` and it's clear
> > that the user needs to include this license when compiling from source.
>
> Yeah. I'm going to collaborate with Fury to follow this approach and
> document clearly how a developer can intentionally run benchmark with
> JMH as a dep.
>
> Best,
> tison.
>
> John D. Ament  于2023年12月28日周四 01:07写道：
> >
> > On Wed, Dec 27, 2023 at 11:38 AM tison  wrote:
> >
> > > > application, a developer has preinstalled the JDK (or using a manager of
> > > > some kind to install it - so not something we're forcing upon them).  In
> > >
> > > No. To running a Java Application in a normal way, the JRE is
> > > required. Saying "not something we're forcing upon them" sounds
> > > sophistry.
> > >
> > > Best,
> > > tison.
> > >
> > > tison  于2023年12月28日周四 00:27写道：
> > > >
> > > > Hi John,
> > > >
> > > > Glad to hear your feedback. Reply inline:
> > > >
> > > > > In the case of JMH, the repository I linked above forces the user to
> > > download
> > > > > the additional dependency from maven central (or similar repository)
> > > rather
> > > > > than relying on the system preinstalled library.
> > > >
> > > > From a technical view, this is not true because you can download the
> > > > libs manually and place them under MAVEN_HOME. Then it can be regarded
> > > > as a "system preinstalled library". It's the same as download JDK and
> > > > place them under JAVA_HOME.
> > >
> >
> > Except that's not how these libraries are listed within your pom file.  If
> > there was a step where you required a developer to download these files,
> > what you're describing would be accurate, but they're downloaded in an
> > automated fashion.  Keep in mind, this isn't the JMH that's distributed
> > with the JDK that you're using here, it's an add-on library you're using.
> >
> >
> > > >
> > > > > you can't use org.openjdk.jmh:* as a compile/test compile
> > > > > dependency in your project
> > > >
> > > > fury-benchmark is not released in binary form. But we can of course
> > > > make it an optional dependency (or the entire module optionally)
> > > > behind a profile and deactivated by default so that it's the same as
> > > > how ASF projects can optionally depend on MySQL Connector Java under
> > > > the same license.
> > >
> >
> > The question here isn't about binary form.  Keep in mind that first and
> > foremost ASF projects produce source code releases, the convenience
> > binaries are a separate artifact.  I'm presently approaching your thread
> > focused on the source code release.  I can see your point though and that's
> > where I'm suggesting asking legal may give you additional guidance that I
> > could see leading to a similar situation as Java 9 JavaScript embeddings.
> > Just keep in mind that you're making a module optional to compile, rather
> > than optional to use, even though it's only being used for testing purposes
> > and our expectation (even though it may differ from reality) is that we're
> > reviewing the contents of the source bundle that a user downloads to
> > compile your code, not the binary artifact they depend upon in their
> > projects.
> >
> >
> > > >
> > > > A related discussion can be found at [1].
> > >
> >
> > Yes, and Hen's response is very appropriate to that situation.  It's not
> > really relevant to your situation though since the concern in this thread
> > is your source release, not binary release.  You can make something like
> > this optional, and if you keep the benchmark as optional you should be fine
> > as well.  For instance, if your maven build is `-Pbenchmark` and it's clear
> > that the user needs to include this license when compiling from source.
> >
> >
> > > >
> > > > >> THEY MAY BE RELIED UPON WHEN THEY SUPPORT AN OPTIONAL FEATURE
> > > > >> "Will the majority of users want to use my product without adding the
> > > optional components?"
> > > >
> > > > No. Benchmark is for testing; most users don't even know it and cannot
> > > > depend on it as a Maven artifact.
> >
> > >
> > > > P.S.
> > > > > don't approach things as "TLP [x] does it this way so
> > > > > it must be the preferred way"
> > > > Yeah .. Even I don't think Flink did it correctly, this expression
> > > > increases confusion. Most readers don't have the context to understand
> > > > the referred case. I'll avoid it.
> > > >
> > > > Best,
> > > > tison.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/LEGAL-437
> > > >
> > > > John D. Ament  于2023年12月27日周三 23:57写道：
> > > 

Re: [VOTE] Accept XTable into the ASF Incubator

[Julian Hyde]

+1 (binding)

Good luck!

On Sat, Dec 16, 2023 at 12:50 PM Austin Bennett  wrote:
>
> +1 [ non-binding ]
>
> On Fri, Dec 15, 2023 at 8:18 PM Jesus Camacho Rodriguez 
> wrote:
>
> > Hi All,
> >
> > Following the discussion in the incubator mailing list [1], I am starting
> > this official vote for the XTable project.
> >
> > Here is the proposal -
> > https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
> >
> > Please cast your vote:
> >
> > [ ] +1, bring XTable into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring XTable into the Incubator, because...
> >
> > This majority vote is open for at least 96 hours (due to the weekend).
> >
> > Only votes from Incubator PMC members are binding, but other votes are
> > welcome!
> >
> > Thanks,
> > Jesús
> >
> > [1] https://lists.apache.org/thread/rx9z8ffrf37qjhpkf1vp5rqg5lhht7jm
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Procedure for graduating an existing sub project to new top level project

[Julian Hyde]

For what it's worth, Arrow was created in Jan 2016 [1]. Here is the text of the 
Board resolution.

Julian

[1] 
https://www.apache.org/foundation/records/minutes/2016/board_minutes_2016_01_20.txt

---


  7. Special Orders

A. Establish the Apache Arrow 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 columnar in-memory processing and data 
   interchange

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache Arrow Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache Arrow Project be and hereby is
   responsible for the creation and maintenance of software
   related to columnar in-memory processing and data interchange;
   and be it further

   RESOLVED, that the office of "Vice President, Apache Arrow" 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 Arrow Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Arrow 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 Arrow Project:

   * Todd Lipcon 
   * Ted Dunning 
   * Michael Stack 
   * P. Taylor Goetz 
   * Reynold Xin 
   * Julian Hyde 
   * Julien Le Dem 
   * Jacques Nadeau 
   * James Taylor 
   * Jake Luciani 
   * Parth Chandra 
   * Alex Levenson 
   * Marcel Kornacker 
   * Steven Phillips 
   * Hanifi Gunes 
   * Jason Altekruse 
   * Abdel Hakim Deneche 

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jacques Nadeau
   be appointed to the office of Vice President, Apache Arrow, 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.
   
   RESOLVED, that the Apache Arrow Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Drill Arrow sub-project; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Drill Arrow sub-project encumbered upon the
   Apache Drill Project are hereafter discharged.

   Special Order 7A, Establish the Apache Arrow Project, was
   approved by Unanimous Vote of the directors present.

On 2023/12/15 16:02:15 Andrew Lamb wrote:
> Thank you Julian. This is very helpful. I will review the archives.
> 
> Andrew
> 
> On Fri, Dec 15, 2023 at 10:55 AM Julian Hyde  wrote:
> 
> > I believe the process is for the Board to create a new PMC whose IP and
> > PMC members are an exact copy of the parent PMC.  (Like the Unix “fork”
> > function.) And then both PMCs delete the stuff, and PMC members, they no
> > longer need.
> >
> > Arrow itself was created via this process (from Drill). You could search
> > the archives for the board resolution that created Arrow. The Incubator is
> > not involved in the process. (Except in some minor ways, such as a name
> > search.)
> >
> > Julian
> >
> > > On Dec 15, 2023, at 7:09 AM, Andrew Lamb  wrote:
> > >
> > > I apologize if this is not the right list on which to ask this question.
> > >
> > > Can someone point to information about the procedure to propose
> > > “graduating” an *existing* sub project to a new top level project?
> > >
> > > Specifically, we are working on a proposal to graduate the “Apache Arrow
> > > DataFusion”[1]  sub project to its own Top Level Project. The DataFusion
> > > project has sort of been “incubating” within the Arrow top level project
> > > for several years and has grown to the point where it can both stand on
> > its
> > > own as well as benefit from more focused community[2].
> > >
> > > I searched the archives of this list [3] and did not find anything that
> > > seemed relevant.
> > >
> > > I did find, farther back in history, that the Mahout, Avro and HBase
> > > projects appear to have previously “graduated” from sub projects of
> > Hadoop
> > > to their own top level projects but could not determi

Re: [DISCUSS] Procedure for graduating an existing sub project to new top level project

[Julian Hyde]

I believe the process is for the Board to create a new PMC whose IP and PMC 
members are an exact copy of the parent PMC.  (Like the Unix “fork” function.) 
And then both PMCs delete the stuff, and PMC members, they no longer need. 

Arrow itself was created via this process (from Drill). You could search the 
archives for the board resolution that created Arrow. The Incubator is not 
involved in the process. (Except in some minor ways, such as a name search.)

Julian

> On Dec 15, 2023, at 7:09 AM, Andrew Lamb  wrote:
> 
> I apologize if this is not the right list on which to ask this question.
> 
> Can someone point to information about the procedure to propose
> “graduating” an *existing* sub project to a new top level project?
> 
> Specifically, we are working on a proposal to graduate the “Apache Arrow
> DataFusion”[1]  sub project to its own Top Level Project. The DataFusion
> project has sort of been “incubating” within the Arrow top level project
> for several years and has grown to the point where it can both stand on its
> own as well as benefit from more focused community[2].
> 
> I searched the archives of this list [3] and did not find anything that
> seemed relevant.
> 
> I did find, farther back in history, that the Mahout, Avro and HBase
> projects appear to have previously “graduated” from sub projects of Hadoop
> to their own top level projects but could not determine how they did so.
> 
> Thank you for any guidance you may be able to provide,
> 
> Andrew
> 
> [1] https://arrow.apache.org/datafusion/
> 
> [2] https://github.com/apache/arrow-datafusion/discussions/6475
> 
> [3] https://lists.apache.org/list.html?general@incubator.apache.org
> [4]
> https://news.apache.org/foundation/entry/the_apache_software_foundation_announces4

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] OneTable proposal

[Julian Hyde]

Pronounced “eks table” I presume, and not “cross table” or “times table”? The 
Java package prefix would be org.apache.xtable, not x_table.

(It’s good to check. I’m still traumatized whenever I have to say “PostgreSQL” 
out loud.)

Julian

> On Dec 13, 2023, at 7:13 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi Jesus
> 
> Yes, we first have to trigger the vote to accept XTable into the
> incubator. As soon as the vote pass (hopefully), we have to trigger
> the name search.
> 
> Regards
> JB
> 
>> On Wed, Dec 13, 2023 at 4:06 PM Jesus Camacho Rodriguez
>>  wrote:
>> 
>> Thanks JB. Based on the guidelines described here [1], I was going to run
>> the name search process for XTable after the project is accepted for
>> incubation, but before we start to request resources.
>> 
>> -Jesús
>> 
>> [1] https://www.apache.org/foundation/marks/naming.html#startsearch
>> 
>> On Wed, Dec 13, 2023 at 2:02 AM Jean-Baptiste Onofré 
>> wrote:
>> 
>>> Thanks Jesus
>>> 
>>> XTable sounds good but we need a name search anyway to be sure it's
>>> suitable.
>>> 
>>> Regards
>>> JB
>>> 
>>> On Wed, Dec 13, 2023 at 4:30 AM Jesus Camacho Rodriguez
>>>  wrote:
>>>> 
>>>> I've updated the proposal with the new name: XTable. You can review it
>>>> here:
>>> https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
>>>> (please also see _Project Name_ subsection)
>>>> 
>>>> We hope this change addresses the concern that was raised during this
>>>> discussion, helping to convey a message of neutrality to anyone
>>> interested
>>>> in contributing to the project.
>>>> 
>>>> We look forward to hearing from you soon. If there are no further
>>> concerns,
>>>> we would love to move forward with the VOTE as soon as possible.
>>>> 
>>>> -Jesús
>>>> 
>>>> 
>>>> 
>>>> On Mon, Dec 11, 2023 at 10:09 PM Jesus Camacho Rodriguez <
>>>> jcama...@apache.org> wrote:
>>>> 
>>>>> Thanks Julian. I was mainly considering the code, but, as you
>>> mentioned,
>>>>> it's probably not the primary concern. The current proposal aligns with
>>>>> your feedback: The project will go through the vote (and hopefully be
>>>>> accepted into the incubator) using the new name, so all the infra and
>>>>> project setup can be done (hopefully) only once.
>>>>> 
>>>>> -Jesús
>>>>> 
>>>>> On Mon, Dec 11, 2023 at 5:29 PM Julian Hyde 
>>>>> wrote:
>>>>> 
>>>>>> Much easier to change the name before incubation. It’s not so much
>>> code
>>>>>> as all the infrastructure (mailing lists, git repos, web servers, svn
>>>>>> files, …) that goes along with a podling. It’s a lot of work for
>>> INFRA and
>>>>>> for the PPMC/champion.
>>>>>> 
>>>>>> Also, branding. Calcite entered incubation as ‘Optiq’ and then
>>> renamed,
>>>>>> but not before it had appeared in a few conference talks; people are
>>> still
>>>>>> asking me ‘What happened to Optiq?'
>>>>>> 
>>>>>> Julian
>>>>>> 
>>>>>> 
>>>>>>> On Dec 11, 2023, at 5:08 PM, Jesus Camacho Rodriguez <
>>>>>> jcama...@apache.org> wrote:
>>>>>>> 
>>>>>>> Thanks to everyone who expressed support and offered help. It's
>>> great to
>>>>>>> see that the project's mission resonates with so many different
>>> people.
>>>>>>> 
>>>>>>> Jacques, we acknowledge your concern about the project name. We are
>>>>>> working
>>>>>>> on selecting a new name for ASF incubation that avoids confusion
>>> with
>>>>>> any
>>>>>>> specific corporation or product in the space. Currently we are doing
>>>>>> some
>>>>>>> due diligence to minimize the risk of having to change it again
>>> during
>>>>>>> incubation; we'll update the proposal with the new name soon and
>>> share
>>>>>> it
>>>>>>> in this thread.
>>>>>>> 
>>>>>>> Regarding the name-changing process and yo

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc3

[Julian Hyde]

Forwarding my vote from the dev thread:

+1 (binding)

Julian 

> On Dec 13, 2023, at 9:05 AM, Stepheny Perez  wrote:
> 
> Hi everyone,
> 
> This is a friendly reminder that the Apache SDAP community is looking for 
> approval on our 1.2.0-rc3 release. I'll extend the vote another 72 hours.
> 
> Thank you!
> Stepheny Perez
> 
>> On 2023/12/08 23:37:50 Stepheny Perez wrote:
>> Hello everyone,
>> 
>> This is a call for a vote to release Apache SDAP (incubating) version 
>> 1.2.0-rc3.
>> 
>> The Apache SDAP community has voted to approve release of Apache SDAP 
>> (incubating) version 1.2.0-rc3.
>> 
>> We now request the Incubator PMC review and vote on this release.
>> 
>> SDAP community thread
>> https://lists.apache.org/thread/g9tww5hcklzvfbzln1b9xsj1c3qcr47t
>> 
>> Changes made between previous candidate (rc2) and this one (rc3) are as 
>> follows:
>> - Removed chardet dependency from all components
>> - Upgraded cassandra helm chart to version 9.1.7
>> - Upgraded cassandra protocol version from 3 to 4
>> - Improved documentation
>> 
>> Instructions for building docker images from source can be found here:
>> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc3/docs/build.rst
>> Instructions for deploying locally to test can be found here:
>> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc3/docs/quickstart.rst
>> 
>> The release files, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc3/
>> 
>> For convenience, the tags we built the release artifacts to be voted on
>> from are 1.2.0-rc3:
>> 
>> - ingester:
>> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc3
>> - Commit: dc36ff6fc163f170759a1c1b49a7be867d15f6ab
>> 
>> - nexus:
>> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc3
>> - Commit: 56a841c63a96d66dcca780249d5bb194a8ec32be
>> 
>> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
>> voting on are as follows:
>> 
>> apache-sdap-ingester-1.2.0-incubating-src.tar.gz:
>> a49401178f631ea50dfaad0f2c4627c7f9f373393db7594de388ce8abdc0ada699ebc5dcb843d41a63af2e5572ca3aeeeb5cf2de7747c0173b07ff4a00420f81
>> 
>> apache-sdap-nexus-1.2.0-incubating-src.tar.gz:
>> 09d50fe899979c962f023e033ea7a8c8c0acdb00bbfbe03a16d6810e0a34744f4106a130d202b5d4c4a1bd20cb3c12851e2f7752286ca1e9f5b117c7fcfe2f43
>> 
>> Release artifacts are signed with the following key:
>> https://keyserver.ubuntu.com/pks/lookup?op=get=0x2E8418801953621FAA322169D6F360887071C194
>> 
>> Please vote on releasing this package as Apache SDAP (incubating) 1.2.0-rc3.
>> 
>> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache SDAP (incubating) 1.2.0-rc3
>> [ ] +0 No opinion
>> [ ] -1 Do not release this package because ...
>> 
>> Thank you,
>> Stepheny Perez
>> 
>> -
>> 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: [DISCUSS] OneTable proposal

[Julian Hyde]

Much easier to change the name before incubation. It’s not so much code as all 
the infrastructure (mailing lists, git repos, web servers, svn files, …) that 
goes along with a podling. It’s a lot of work for INFRA and for the 
PPMC/champion.

Also, branding. Calcite entered incubation as ‘Optiq’ and then renamed, but not 
before it had appeared in a few conference talks; people are still asking me 
‘What happened to Optiq?'

Julian


> On Dec 11, 2023, at 5:08 PM, Jesus Camacho Rodriguez  
> wrote:
> 
> Thanks to everyone who expressed support and offered help. It's great to
> see that the project's mission resonates with so many different people.
> 
> Jacques, we acknowledge your concern about the project name. We are working
> on selecting a new name for ASF incubation that avoids confusion with any
> specific corporation or product in the space. Currently we are doing some
> due diligence to minimize the risk of having to change it again during
> incubation; we'll update the proposal with the new name soon and share it
> in this thread.
> 
> Regarding the name-changing process and your concerns about it, we're
> looking for advice based on past experiences. Specifically, we're
> considering whether it's better to change the project's name before pushing
> the code to the ASF, or if it's more practical to push the code to the ASF
> repository first and then proceed with the name change. Any insights or
> guidance on whether one option is better than the other based on previous
> instances would be appreciated.
> 
> Thanks,
> Jesús
> 
> 
> 
> On Mon, Dec 11, 2023 at 5:43 AM Jean-Baptiste Onofré 
> wrote:
> 
>> Of course, it's a big +1 one for me.
>> 
>> The purpose is interesting, creating "connection" with other Apache
>> projects.
>> Happy to be a mentor on this proposal and contribute to the project :)
>> 
>> Thanks !
>> Regards
>> JB
>> 
>> On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
>>  wrote:
>>> 
>>> Hi All,
>>> 
>>> I would like to propose a new project to the ASF incubator - OneTable.
>>> 
>>> OneTable[1] is an omni-directional converter for table formats that
>> facilitates interoperability across data processing systems and query
>> engines. Currently, OneTable supports widely adopted open-source table
>> formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
>>> 
>>> Here is the proposal -
>>> https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
>>> 
>>> I would be the Champion of the project. I will mentor and help the
>> project through the incubator with Hitesh Shah [hit...@apache.org],
>> Stamatis Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [
>> jbono...@apache.org].
>>> 
>>> We are looking forward to your feedback!
>>> 
>>> Thanks,
>>> Jesús
>>> 
>>> [1] https://github.com/onetable-io/onetable
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc2

[Julian Hyde]

I had voted +1 on dev@ but I'm changing my vote until we clarify the
use of chardet:

0 (binding)

Is there an automated way to check the licenses of Python dependencies
(analogous to how Java-based projects use RAT)? It would be useful for
me (not a Python expert but voting on releases) and the project
(automating their license hygiene).

Julian

On Sat, Nov 4, 2023 at 11:01 AM Justin Mclean  wrote:
>
> Hi,
>
> -1 (binding), as I think you may have an issue here as 
> apache-sdap-nexus-1.2.0-incubating-src depends on LGPL licensed chardet. [1] 
> ASF project can not depend on LGPL software unless it is optional. Is this 
> the case here?
>
> I checked:
> - incubating in names
> - signatures and hashes are fine
> - DISCLAIMER exists
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - Source files have ASF headers
> - I did not compile from source
>
> Kind Regards,
> Justin
>
> 1. https://issues.apache.org/jira/browse/LEGAL-572
> -
> 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: [RESULT][VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)

[Julian Hyde]

Yes; unfortunately, the concept of binding votes is one that you need to know. 
If and when Baremaps has graduated as a top-level project, the votes of 
Baremaps PMC members will be binding, but for the sake of inclusion and quality 
you will want as many votes as possible from other community members (including 
non-PMC committers). 

Julian

> On Oct 12, 2023, at 03:05, Bertil Chapuis  wrote:
> 
> Thanks a lot for the clarification, we will eventually get familiar with the 
> process 
> 
>> On 11 Oct 2023, at 21:02, Julian Hyde  wrote:
>> 
>> Note that 3 of those +1s (me, Calvin, JB) are binding because they are
>> Incubator PMC members, 2 are not (Bertil, Leonard).
>> 
>> 3 binding +1s is sufficient for the vote to pass.
>> 
>> Congratulations!
>> 
>> Julian
>> 
>>> On Tue, Oct 10, 2023 at 12:49 AM Bertil Chapuis  wrote:
>>> 
>>> Hello Everyone,
>>> 
>>> The vote for Apache Baremaps 0.7.2-rc3 (incubating) is now closed. The 
>>> results are summarised below. Thank you all for taking the time to provide 
>>> valuable feedbacks for this release, we are getting very close from being 
>>> fully compliant with the guidelines.
>>> 
>>> Binding Votes:
>>> 
>>> +1 votes [5]:
>>> - Leonard Cseres
>>> - Julian Hyde
>>> - Jean-Baptiste Onofré
>>> - Calvin Kirs
>>> - Bertil Chapuis
>>> 
>>> 0 votes [0]:
>>> None
>>> 
>>> -1 votes [0]:
>>> None
>>> 
>>> Best regards,
>>> 
>>> Bertil
>>> 
>>> 
>>> 
>>>> On 7 Oct 2023, at 07:08, Calvin Kirs  wrote:
>>>> 
>>>> +1 （binding）
>>>> 
>>>> I checked:
>>>> - incubating in name
>>>> - signatures and hashes are fine
>>>> - disclaimer-wip exists
>>>> - license and notice files look good
>>>> - file have correct ASF headers if necessary
>>>> 
>>>> On Thu, Oct 5, 2023 at 7:19 PM Jean-Baptiste Onofré  
>>>> wrote:
>>>>> 
>>>>> +1 (binding)
>>>>> 
>>>>> I checked:
>>>>> - signatures and hashes ok
>>>>> - asf headers
>>>>> - license, notice and disclaimer are there
>>>>> - no binary found in source distribution
>>>>> 
>>>>> Thanks
>>>>> Regards
>>>>> JB
>>>>> 
>>>>> Le mar. 3 oct. 2023 à 00:10, Bertil Chapuis  a écrit :
>>>>> 
>>>>>> Hello Everyone,
>>>>>> 
>>>>>> This is a call for a vote to release Apache Baremaps 0.7.2 (incubating),
>>>>>> release candidate 3. Apache Baremaps is a toolkit and a set of
>>>>>> infrastructure components for creating, publishing, and operating online
>>>>>> maps.
>>>>>> 
>>>>>> We would like to thanks everyone who has vetted the previous release
>>>>>> candidates and who has contributed to the project. This release candidate
>>>>>> fixes the issues identified in the previous vote thread:
>>>>>> https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f
>>>>>> 
>>>>>> We now would like to request the Incubator PMC members to review and vote
>>>>>> on this new release candidate.
>>>>>> 
>>>>>> You can read the release notes here:
>>>>>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3
>>>>>> 
>>>>>> The commit to be voted upon:
>>>>>> https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3
>>>>>> 
>>>>>> Its hash is 823b55507eec425776d996b64b489c8235f6bb37.
>>>>>> 
>>>>>> Its tag is v0.7.2-rc3.
>>>>>> 
>>>>>> The artifacts to be voted on are located here:
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/
>>>>>> 
>>>>>> The hashes of the artifacts are as follows:
>>>>>> 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b
>>>>>> ./apache-baremaps-0.7.2-incubating-src.tar.gz
>>>>>> 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915
>>

Re: [RESULT][VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)

[Julian Hyde]

Note that 3 of those +1s (me, Calvin, JB) are binding because they are
Incubator PMC members, 2 are not (Bertil, Leonard).

3 binding +1s is sufficient for the vote to pass.

Congratulations!

Julian

On Tue, Oct 10, 2023 at 12:49 AM Bertil Chapuis  wrote:
>
> Hello Everyone,
>
> The vote for Apache Baremaps 0.7.2-rc3 (incubating) is now closed. The 
> results are summarised below. Thank you all for taking the time to provide 
> valuable feedbacks for this release, we are getting very close from being 
> fully compliant with the guidelines.
>
> Binding Votes:
>
> +1 votes [5]:
> - Leonard Cseres
> - Julian Hyde
> - Jean-Baptiste Onofré
> - Calvin Kirs
> - Bertil Chapuis
>
> 0 votes [0]:
> None
>
> -1 votes [0]:
> None
>
> Best regards,
>
> Bertil
>
>
>
> > On 7 Oct 2023, at 07:08, Calvin Kirs  wrote:
> >
> > +1 （binding）
> >
> > I checked:
> > - incubating in name
> > - signatures and hashes are fine
> > - disclaimer-wip exists
> > - license and notice files look good
> > - file have correct ASF headers if necessary
> >
> > On Thu, Oct 5, 2023 at 7:19 PM Jean-Baptiste Onofré  
> > wrote:
> >>
> >> +1 (binding)
> >>
> >> I checked:
> >> - signatures and hashes ok
> >> - asf headers
> >> - license, notice and disclaimer are there
> >> - no binary found in source distribution
> >>
> >> Thanks
> >> Regards
> >> JB
> >>
> >> Le mar. 3 oct. 2023 à 00:10, Bertil Chapuis  a écrit :
> >>
> >>> Hello Everyone,
> >>>
> >>> This is a call for a vote to release Apache Baremaps 0.7.2 (incubating),
> >>> release candidate 3. Apache Baremaps is a toolkit and a set of
> >>> infrastructure components for creating, publishing, and operating online
> >>> maps.
> >>>
> >>> We would like to thanks everyone who has vetted the previous release
> >>> candidates and who has contributed to the project. This release candidate
> >>> fixes the issues identified in the previous vote thread:
> >>> https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f
> >>>
> >>> We now would like to request the Incubator PMC members to review and vote
> >>> on this new release candidate.
> >>>
> >>> You can read the release notes here:
> >>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3
> >>>
> >>> The commit to be voted upon:
> >>> https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3
> >>>
> >>> Its hash is 823b55507eec425776d996b64b489c8235f6bb37.
> >>>
> >>> Its tag is v0.7.2-rc3.
> >>>
> >>> The artifacts to be voted on are located here:
> >>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/
> >>>
> >>> The hashes of the artifacts are as follows:
> >>> 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b
> >>> ./apache-baremaps-0.7.2-incubating-src.tar.gz
> >>> 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915
> >>> ./apache-baremaps-0.7.2-incubating-bin.tar.gz
> >>>
> >>> Release artifacts are signed with the following key:
> >>> http://people.apache.org/keys/committer/bchapuis.asc
> >>> https://downloads.apache.org/incubator/baremaps/KEYS
> >>>
> >>> The README file for the src distribution contains instructions for
> >>> building and testing the release.
> >>>
> >>> Please vote on releasing this package as Apache Baremaps 0.7.2.
> >>>
> >>> The vote is open for the next 72 hours and passes if a majority of at
> >>> least three +1 PMC votes are cast.
> >>>
> >>> [ ] +1 Release this package as Apache Baremaps 0.7.2
> >>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> >>> [ ] -1 Do not release this package because...
> >>>
> >>> Best,
> >>>
> >>> Bertil
> >>>
> >
> >
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
> > -
> > 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] Release Apache Baremaps 0.7.2-rc3 (incubating)

[Julian Hyde]

+1 (binding)

Downloaded, checked signatures, README, LICENSE, NOTICE, DISCLAIMER-WIP; 
compared src-tar contents with git; built using OpenJDK 17/Maven 3.8.1 on 
Ubuntu/amd64; ran RAT. Checked that file headers are now correct.

Julian


> On Oct 3, 2023, at 11:48 AM, Leo  wrote:
> 
> +1 (binding)
> 
> Downloaded, checked signatures, checked checksums
> 
> Leonard
> 
>> On 3 Oct 2023, at 00:10, Bertil Chapuis  wrote:
>> 
>> Hello Everyone,
>> 
>> This is a call for a vote to release Apache Baremaps 0.7.2 (incubating), 
>> release candidate 3. Apache Baremaps is a toolkit and a set of 
>> infrastructure components for creating, publishing, and operating online 
>> maps.
>> 
>> We would like to thanks everyone who has vetted the previous release 
>> candidates and who has contributed to the project. This release candidate 
>> fixes the issues identified in the previous vote thread:
>> https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f
>> 
>> We now would like to request the Incubator PMC members to review and vote on 
>> this new release candidate.
>> 
>> You can read the release notes here:
>> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3
>> 
>> The commit to be voted upon:
>> https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3
>> 
>> Its hash is 823b55507eec425776d996b64b489c8235f6bb37.
>> 
>> Its tag is v0.7.2-rc3.
>> 
>> The artifacts to be voted on are located here:
>> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/
>> 
>> The hashes of the artifacts are as follows:
>> 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b
>>  ./apache-baremaps-0.7.2-incubating-src.tar.gz
>> 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915
>>  ./apache-baremaps-0.7.2-incubating-bin.tar.gz
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/keys/committer/bchapuis.asc
>> https://downloads.apache.org/incubator/baremaps/KEYS
>> 
>> The README file for the src distribution contains instructions for building 
>> and testing the release.
>> 
>> Please vote on releasing this package as Apache Baremaps 0.7.2.
>> 
>> The vote is open for the next 72 hours and passes if a majority of at least 
>> three +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Baremaps 0.7.2
>> [ ] 0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because...
>> 
>> Best,
>> 
>> Bertil
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Baremaps 0.7.2-rc2 (incubating)

[Julian Hyde]

-1 (binding)

I had voted +1 on the dev list but I am changing my vote in light of the header 
issues that Calvin discovered.

A typical java file in Baremaps has this header:

/*  
  
 * Licensed under the Apache License, Version 2.0 (the "License"); you may not 
use this file except   
 * in compliance with the License. You may obtain a copy of the License at  
  
 *  
  
 * http://www.apache.org/licenses/LICENSE-2.0   
  
 *  
  
 * Unless required by applicable law or agreed to in writing, software 
distributed under the License  
 * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY 
KIND, either express   
 * or implied. See the License for the specific language governing permissions 
and limitations under  
 * the License. 
  
 */

But should have the following:

/*  
  
 * Licensed to the Apache Software Foundation (ASF) under one or more   
  
 * contributor license agreements.  See the NOTICE file distributed with
  
 * this work for additional information regarding copyright ownership.  
  
 * The ASF licenses this file to you under the Apache License, Version 2.0  
  
 * (the "License"); you may not use this file except in compliance with 
  
 * the License.  You may obtain a copy of the License at
  
 *  
  
 * http://www.apache.org/licenses/LICENSE-2.0   
  
 *  
  
 * Unless required by applicable law or agreed to in writing, software  
  
 * distributed under the License is distributed on an "AS IS" BASIS,
  
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
  
 * See the License for the specific language governing permissions and  
  
 * limitations under the License.   
  
 */

Julian


> On Sep 25, 2023, at 7:06 AM, Calvin Kirs  wrote:
> 
> Hi,
> 
> sorry for my late check. I've been a little busy lately.
> 
> -1 (binding)
> 
> I checked:
> 
> - checked the asc and sha checksums
> - incubating in the name
> - LICENSE and NOTICE and DISCLAIMER-WIP present
> - can build from source
> - no unexpected compiled binaries in the source distribution
> 
> I don't have any other questions, but our license header is missing
> something crucial--Licensed to the Apache Software Foundation
> (ASF) under one or more contributor license agreements.
> 
> I think we've already filed the ICLA/CLA, so this statement is important.
> 
> On Mon, Sep 25, 2023 at 5:10 AM PJ Fanning  wrote:
>> 
>> +1 (binding) despite minor issues in DISCLAIMER-WIP
>> 
>> * checked the asc and sha checksums
>> * incubating in name
>> * LICENSE and NOTICE and DISCLAIMER-WIP present
>> * can build from source
>> * no unexpected compiled binaries in source distribution
>> 
>> The DISCLAIMER-WIP has not fixed a URL present in the file
>> - https://incubator.apache.org/projects/Apache Podling-Name.html
>> - this should probably be https://incubator.apache.org/projects/baremaps.html
>> 
>> Also, you should possibly remove the line in DISCLAIMER-WIP about the 
>> releases not being voted on. Or could you be more specific about which 
>> releases were not voted on?
>> - Releases may not have been voted on by the community.
>> 
>> 
>> 
>> 
>> 
>> On 2023/09/23 14:25:51 Bertil Chapuis wrote:
>>> Hello Everyone,
>>> 
>>> This is a call for a vote to release Apache Baremaps 0.7.2 (incubating), 
>>> release candidate 2. Apache Baremaps is a toolkit and a set of 
>>> infrastructure components for creating, publishing, and operating online 
>>> maps.
>>> 
>>> We would like to request the Incubator PMC members to review and vote on 
>>> this incubator release. The Apache Baremaps community has voted on and 
>>> approved a proposal to release Apache Baremaps 0.7.2 

Re: Feedback requested - How to deal with retired podling resources

[Julian Hyde]

In regard to assets, I see no particular reason to treat retired podlings 
differently from graduated podlings. Keep the foo.apache.org 
 hostname; retain the repository (read-only); keep the 
website (tagged with a notice ’This podling has retired. It may be contacted at 
…’.)

It is certainly useful for people to be able to access the podling’s source 
code as of the day it retired.

If there are other considerations (cost, security, legal) then we could 
reconsider.

Julian

> On Jul 31, 2023, at 3:51 AM, Daniel Gruno  wrote:
> 
> Hi incubator folks,
> over at Infra, we occasionally have requests to retire podlings, and while we 
> do have a specific set of policies for TLPs, it gets a bit vague when it 
> comes to podlings. I have tried looking for the IPMC's own guidelines, but it 
> seems that the retirement guide does not exist ( 
> https://incubator.apache.org/guides/retirement.html 404s!).
> 
> Thus, I would like to get the incubator's official opinion on how podling 
> retirements should be effectuated:
> 
> - Do we keep the podling foo.apache.org hostname in perpetuity?
> - Are repositories and other material removed? handed to the attic? moved to 
> a special incubator-retired-* prefix?
> - What happens to the podling websites?
> 
> With regards,
> Daniel on behalf of ASF Infra.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: Little "upsie" at the Wayang podling

[Julian Hyde]

As others have said, there’s no way to retract a release when it’s gone to 
Maven Central. (Many of us have noticed show-stopping bugs just after the 
release.) The only remedy is to make a superseding release. 

I don’t support adding a step where an IPMC member presses the release button. 
Mistakes happen, no many how many layers of process you add. Nexus already has 
a two-phase process, and it works well with the ASF release process. 

Wayang are going to need a new release number, not just a new RC of the same 
release. Otherwise their new binary artifacts won’t supersede those already out 
there. 

Julian 

> On Jul 25, 2023, at 6:22 AM, Christofer Dutz  
> wrote:
> 
> (Also fixed what my mail client thought I wanted to say, to what I said in 
> the subject ;-) )
> 
> And I think the main problem with the leftpad was the general usage of the 
> Maven equivalent of “LATEST” as a dependency version.
> So, anyone with a LATEST dependency that has built today, will have the 0.7.0 
> version everyone with a sensible build management won’t be affected.
> 
> Alternatively, most things that caused me to vote -1 actually don’t have an 
> effect on the produced binaries.
> It was mostly stuff that applies for the source-distribution.
> So, I would in this case be in favor that they stage a new release candidate 
> for 0.7.0, release that, and simply drop the nexus repo instead of 
> re-releasing it.
> 
> Chris
> 
> Von: PJ Fanning 
> Datum: Dienstag, 25. Juli 2023 um 14:54
> An: general@incubator.apache.org 
> Betreff: Re: Little "upside" at the Wayang podling
> The difference here is that this release has just been made and has
> only been announced on the Wayang dev list. I find no evidence of it
> on the Wayang web site nor in the Apache announce mailing list.
> 
> I understand the leftpad case but I don't think this is a similar
> case. Users who have upgraded to Wayang 0.7.0 can downgrade to Wayang
> 0.6.0.
> 
>> On Tue, 25 Jul 2023 at 13:19, tison  wrote:
>> 
>>> So I guess we have to check how we can remove the artifacts.
>> 
>> A central repository should not _remove_ artifacts. Rust's cargo crate can
>> mark as yanked and prevent further dependent but remain all the existing
>> one. Revoke artifacts can cause significant downstream effect - you may
>> take leftpad on npmjs as an example.
>> 
>> Best,
>> tison.
>> 
>> 
>> Christofer Dutz  于2023年7月25日周二 19:14写道：
>> 
>>> Hi PJ,
>>> 
>>> Unfortunately, I had to vote -1 on the release and there’s no way on earth
>>> it would pass Justin ;-) …
>>> So, there will be another one.
>>> 
>>> So I guess we have to check how we can remove the artifacts.
>>> 
>>> Chris
>>> 
>>> 
>>> Von: PJ Fanning 
>>> Datum: Dienstag, 25. Juli 2023 um 11:47
>>> An: general@incubator.apache.org 
>>> Betreff: Re: Little "upside" at the Wayang podling
>>> It does seem like a good idea to do a 2 phase release to the Apache Nexus
>>> Repository. I think a lot of Apache projects use that approach. It means
>>> that the binary artifacts can be checked during the release voting along
>>> side the source release. Nexus allows you the drop the artifacts or to
>>> release them and this can be a good way to handle unsuccessful and
>>> successful release votes (respectively).
>>> 
>>> It might make sense to bring the 0.7.0 release to an Incubator vote and if
>>> it passes then there isn't much harm. The Wayang team have announced this
>>> release on their dev mailing list but don't appear to have updated their
>>> download page [1] yet. Could we get them to respond to all the announcement
>>> emails to say that release vote is not yet complete and to ask people not
>>> use this release until the vote is finished?
>>> 
>>> If the Incubator vote fails, I'm not sure but it may be feasible to see if
>>> the Maven team can remove the 0.7.0 artifacts.
>>> 
>>> [1] https://wayang.apache.org/download/
>>> 
>>> On 2023/07/25 09:28:00 Christofer Dutz wrote:
 Hi all,
 
 yesterday the Wayang podling was following the “release documentation”
>>> of a TLP and “forgot” to do the round over the IPMC.
 However, they’ve already moved things to the release distro area (from
>>> where they’ve removed it after me contacting them) but in Nexus they
>>> clicked on “release” and the artifacts are out in the wild.
 
 How to generally deal with this situation? I think in general it would
>>> be good, if releasing maven artifacts in Nexus was a two step thing … a)
>>> the project clicks on “release” and then an IPMC member has to confirm that.
 
 Chris
 
 
>>> 
>>> -
>>> 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: 

Re: [VOTE] Release Apache SDAP (incubating) 1.1.0-rc0

[Julian Hyde]

(I am a mentor of SDAP but was too late to vote in the thread on dev@sdap.)

+1 (binding)

Checked signatures/hashes, compared with git, checked NOTICE, LICENSE.txt, 
DISCLAIMER-WIP; built Collection Manager and Granule Infester using Docker, 
following the instructions in README.

Notes:
* You should remove ‘APPENDIX: How to apply the Apache License to your work’ 
and onwards from LICENSE.txt.
* ‘Apache-SDAP’ directory prefix in the tar.gz files is a bit unusual, but fine.
* DISCLAIMER-WIP lists a couple of issues (missing headers and potential 
licensing issue with test data); with SDAP approaching graduation, when do you 
plan to solve this issues?

Julian



> On May 1, 2023, at 10:20 AM, Nga Chung  wrote:
> 
> Hello Incubator PMC,
> 
> This is a call for a vote to release Apache SDAP (incubating) version
> 1.1.0-rc0.
> 
> The Apache SDAP community has voted to approve the release of Apache SDAP
> (incubating) version 1.1.0-rc0.
> 
> We now request the Incubator PMC review and vote on this release.
> 
> SDAP community thread:
> https://lists.apache.org/thread/z5llljrb10zrq39368xvpm7h0bto65kh
> 
> CHANGELOG for version 1.1.0 are available here:
> https://github.com/apache/incubator-sdap-ingester/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
> 
> Instructions for building docker images from source can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/build.rst
> Instructions for deploying locally to test can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/quickstart.rst
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.1.0-rc0/
> 
> For convenience, the tags we built the release artifacts to be voted on
> from are 1.1.0-rc0:
> 
> - ingester:
> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.1.0-rc0
> - Commit: 8632b262eef9a33c816ec9b733c1ddc0156fa4c5
> 
> - nexus:
> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.1.0-rc0
> - Commit: 370190db8c4db86ce7837bc9fb3889c6658fac7f
> 
> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are
> voting on are as follows:
> 
> apache-sdap-ingester-1.1.0-incubating-src.tar.gz:
> ab243d84d0ab7dd33bc61ab84129080b1de0dc22f15d519950dda55ade41bf65cc8b02fe0b131c6640e0782613978c8ba9e9e573156a8657cb7ce14c599fbe7c
> 
> apache-sdap-nexus-1.1.0-incubating-src.tar.gz:
> c51340b040ffb4e82cdd9c8ba02ba3e8b54a9194826486bac781e966218491b700685b92effc200fd8a97ee10cffb301b618e6e9c73a3a21cd42d1b75a54670e
> 
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x1392A8A11801359247A803D8D2449E0EB5EF1E73
> 
> Please vote on releasing this package as Apache SDAP (incubating) 1.1.0.
> 
> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
> cast.
> 
> [ ] +1 Release this package as Apache SDAP (incubating) {version}
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Thank you,
> Nga


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [QUESTION] are binary distributions/releases required?

[Julian Hyde]

It’s useful to clarify the terminology. There’s no such thing as a “binary
release”. Release policy [1] says:

> Every ASF release MUST contain one or more source packages

> All releases are in the form of the source materials needed to make
changes
> to the software being released.
>
> As a convenience to users that might not have the appropriate tools to
build a
> compiled version of the source, binary/bytecode packages MAY be
distributed
> alongside official Apache releases.”

The binary packages that may accompany a release are generally referred to
as “binary artifacts” of the release.

Julian

[1] https://www.apache.org/legal/release-policy.html#artifacts

On Feb 8, 2023, at 7:19 AM, Dave Fisher  wrote:

Hi PJ,

Daffodil uses sbt and produces binary releases -
https://daffodil.apache.org/releases/3.4.0/
- https://GitHub.com/Apache/daffodil/

Best,
Dave

Sent from my iPhone

On Feb 8, 2023, at 6:33 AM, PJ Fanning  wrote:


Hi everyone,

The release management guide [1] only mentions 'source releases'. Every
Apache project that I am familiar with also does binary releases. For
applications, this makes sense - having a zip/tgz file that you can
download and extract - that you can then readily start the application
using a shell script. For libs, I'm sure these binary releases can be
useful too but I'm wondering if they are strictly required.


Apache Pekko is a set of libraries as opposed to an application. Our build
uses the sbt build tool and there isn't anything that I've come across that
would produce something like the binary releases that other Apache projects
release. This means we'd likely have to roll our own solution.


In terms of prioritising work towards a v1.0.0 release, it's useful to know
if we have items that could be de-prioritised.


If we do need to create binary releases, are there any guidelines to follow
- or do we just look at other Apache libs and use their binary releases as
a guide?


Regards,

PJ


[1] https://incubator.apache.org/guides/releasemanagement.html


-

To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc3

[Julian Hyde]

Forwarding my vote from the dev@sdap thread:

  +1 (binding)

To repeat what I said for RC2, I am the sole active mentor for SDAP, and we 
appreciate the time and attention of IPMC members doing due diligence on this 
release. In RC3, SDAP have taken pains to address the issues noted in RC2.

The vote has been open for almost 72 hours already and it would be great to get 
it done before the (US) weekend.

Thank you.

Julian




On 2023/01/10 18:43:22 Riley Kuttruff wrote:
> Hello everyone,
> 
> This is a call for a vote to release Apache SDAP (incubating) version 
> 1.0.0-rc3.
> 
> The Apache SDAP community has voted to approve release of Apache SDAP 
> (incubating) version 1.0.0-rc3.
> 
> We now request the Incubator PMC review and vote on this release.
> 
> SDAP community thread
> https://lists.apache.org/thread/4hyjnh1nf5jv9jkbgr5jypptj4145l8p
> 
> Changes made between previous candidate (rc2) and this one (rc3) are as
> follows:
> - Switched to DISCLAIMER-WIP
> - Removed Gradle wrapper from nexusproto source distribution & updated 
> developer build instruction for nexusproto
> - Updated release artifact structure to extract to single common directory & 
> updated release build instructions accordingly
> - Corrected NOTICE file and updated copyright statement to reflect correct 
> years
> - Updated naming for release artifacts 
> (apache-sdap-{module}-{version}-src.tar.gz -> 
> apache-sdap-{module}-{version}-incubating-src.tar.gz)
> 
> Instructions for building docker images from source can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/b6d002cc7f7192820ce9f4443cee9867d3bdbdd0/docs/build.rst
> Instructions for deploying locally to test can be found here:
> https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc3/
> 
> For convenience, the tags we built the release artifacts to be voted on from 
> are 1.0.0-rc3:
> 
> - nexusproto:
> - URL: https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc3
> - Commit: cc35046cd72d9e749a33b697c58e5ca9ccec5711
> - ingester:
> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc3
> - Commit: ae25aae70cc9b91bd0b05788e88e77edc77f0fd3
> - nexus:
> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc3
> - Commit: bf65205c8dae838d95843de34c94d6d46a579308
> 
> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are voting 
> on are as follows:
> 
> apache-sdap-ingester-1.0.0-incubating-src.tar.gz:
> f97f932d3f9c937316fd07f17d27af6f567681c9b9c5e3a4d9813a3372673e829455c96eed10e356200d7a6829d0ec178aff458b8138f0656698f06ca0e8d413
> 
> apache-sdap-nexus-1.0.0-incubating-src.tar.gz:
> 10d491484ff23cf670fd955c576deadea99d976e776b07457f0b38df9c8b06018e0a54888a5ee0704d44a01b83e57b518de6d72ad6d5b28b14cf557054ea54ca
> 
> apache-sdap-nexusproto-1.0.0-incubating-src.tar.gz:
> 1a42e02e859de639fc44a4900dccfa9815dbbde8aabf705600478ccf0d6d46cb98d2a8f76841cbce3bff15f08739725dc39af5e0e8ca052fe6dbf2ed2ed26032
> 
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x4e98c4a32026656e14e0b570fc20035a010e3b7b
> 
> Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
> 
> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Thank you,
> Riley
> 
> -
> 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] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

Thank you to Calvin, John, Justin, Larry for reviewing/voting. You raised some 
good points. SDAP is discussing on its dev@ list and I will argue there that 
they should address most or all in a new RC.

A couple of responses to specific remarks.

> On 2023/01/03 04:48:23 Justin Mclean wrote:
> 
> First off you need to vote on a release artefact not a GitHub tag.

The vote email contained this URL for staged artifacts:

  https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/

The GitHub tags mentioned elsewhere in the vote email were just intended to 
provide context.

I would be grateful if everyone can focus discussion on those artifacts, not 
the various branches and tags in GitHub.

> Riley Kuttruff wrote:
>
> Furthermore, with the new year, the copyright statements in the NOTICE
> files are now out of date as you observed. I'm assuming this will require
> a new release candidate?

I am not a lawyer, but I think that it's OK to make a release in 2023 with a 
copyright notice of 2022 that as long as the release doesn't contain any work 
done in 2023.

This is all moot, because it looks like this won't be final RC.

> Frank Greguska wrote:
>
> What does ASL refer to in this context?

I think that Larry meant 'Apache Software License'. Strictly, the license is 
these days called 'Apache License' and abbreviated 'AL'.

Julian

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

Good catch. But could you (and others) continue the process of
reviewing and voting on the release.

It is established that an official ASF release must not contain
gradle-wrapper.jar [1], but in my opinion this is a problem that could
be solved in the next incubating release. If a few IPMC members
surface several issues this time around, the second release should be
much cleaner.

Julian

[1] https://issues.apache.org/jira/browse/LEGAL-570

On Thu, Dec 29, 2022 at 5:44 PM Calvin Kirs  wrote:
>
> Hi,
>
> There has a compiled code (gradle-wrapper jar) in the source release.
>
> [1]https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/apache-sdap-nexusproto-1.0.0-src.tar.gz
>
> On Sat, Dec 24, 2022 at 5:46 AM Riley Kuttruff  wrote:
> >
> > Hello,
> >
> > In consideration of the upcoming holiday weekend, let's extend this vote to 
> > last to a week from now.
> >
> > Thank you,
> > Riley
> >
> > On 2022/12/23 03:19:10 Riley Kuttruff wrote:
> > > Hello everyone,
> > >
> > > This is a call for a vote to release Apache SDAP (incubating) version 
> > > 1.0.0-rc2.
> > >
> > > The Apache SDAP community has voted to approve release of Apache SDAP 
> > > (incubating) version 1.0.0-rc2.
> > >
> > > We now request the Incubator PMC review and vote on this release.
> > >
> > > SDAP community vote thread:
> > > https://lists.apache.org/thread/6nmknw8n1flwsqp4n3cromnrck21xmh9
> > >
> > > Instructions for building docker images from source can be found here:
> > > https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html
> > > Instructions for deploying locally to test can be found here:
> > > https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
> > >
> > > The tags to be voted on are 1.0.0-rc2:
> > >
> > > - nexusproto:
> > > - URL: 
> > > https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2
> > > - Commit: f3c726e69997436dd9ee6f9a993d4c95ee490b6f
> > > - ingester:
> > > - URL: 
> > > https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2
> > > - Commit: 2c8a9d35320f11a5db2534802f43366ddaff2fea
> > > - nexus:
> > > - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2
> > > - Commit: f60e98331ac29b57ca40322f8f96e98a5c69e553
> > >
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/
> > >
> > > For verification, the hashes of the .tar.gz artifacts we are voting on 
> > > are as follows:
> > >
> > > apache-sdap-ingester-1.0.0-src.tar.gz:
> > > db380c3002351e65ec3581a3ff0cacbb7092f46292b0a656a78a919e1409738442e845731050a2160a556a7818f22b2ab4bb6da437200bc0a62419332de49ad7
> > >
> > > apache-sdap-nexus-1.0.0-src.tar.gz:
> > > da34e9830cf5126bac498180d7cdd95bc2cfc13535c7b4355ba51de64e3589a385a969e0cf1a89fa77e436b30c99a48abffab4b4ef03b23982aa33c2e83e8dbd
> > >
> > > apache-sdap-nexusproto-1.0.0-src.tar.gz:
> > > 05dc8e96d9c49207750c1da13f630493e8d08f5e68733742c157ac6c85ede29aca25f3c94cd706acbbe21cee41ebc052a880b4d6ce859bf510bcc2d66d8f88b2
> > >
> > > Release artifacts are signed with the following key:
> > > https://keyserver.ubuntu.com/pks/lookup?op=get=0x4e98c4a32026656e14e0b570fc20035a010e3b7b
> > >
> > > Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
> > >
> > > The vote is open for 72 hours or until at least 3 “+1” PMC votes are cast 
> > > and passes if at least 3 +1 PMC votes are
> > > cast.
> > >
> > > [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> > > [ ] +0 No opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thank you,
> > > Riley
> > >
> > > -
> > > 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
> >
>
>
> --
> Best wishes！
> CalvinKirs
>
> -
> 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

SDAP release vote

[Julian Hyde]

Could some IPMC members please vote on the SDAP 1.0.0-rc2 release
thread? [1] The vote has been open for a week and there's only one
vote so far (from me).

(The podling has been in incubation for some time, and all of its
original mentors have drifted away. I joined as a mentor in November
because I think that with a small push they can graduate into a
successful TLP. They are making a real effort to make releases and to
graduate. I think that they deserve our support.)

Thanks!

Julian

[1] https://lists.apache.org/thread/t1nb81kbxlqwzv4p9hzk3om15jttqt23

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SDAP (incubating) 1.0.0-rc2

[Julian Hyde]

I am a mentor of SDAP. Forwarding my vote from the PPMC thread [1]:

   +1 (binding)

Julian

[1]
https://lists.apache.org/thread/vh9472q76kzndcs55pmpjmld8snzn1ny

On Thu, Dec 22, 2022 at 7:19 PM Riley Kuttruff  wrote:

> Hello everyone,
>
> This is a call for a vote to release Apache SDAP (incubating) version
> 1.0.0-rc2.
>
> The Apache SDAP community has voted to approve release of Apache SDAP
> (incubating) version 1.0.0-rc2.
>
> We now request the Incubator PMC review and vote on this release.
>
> SDAP community vote thread:
> https://lists.apache.org/thread/6nmknw8n1flwsqp4n3cromnrck21xmh9
>
> Instructions for building docker images from source can be found here:
> https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html
> Instructions for deploying locally to test can be found here:
> https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
>
> The tags to be voted on are 1.0.0-rc2:
>
> - nexusproto:
> - URL:
> https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2
> - Commit: f3c726e69997436dd9ee6f9a993d4c95ee490b6f
> - ingester:
> - URL:
> https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2
> - Commit: 2c8a9d35320f11a5db2534802f43366ddaff2fea
> - nexus:
> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2
> - Commit: f60e98331ac29b57ca40322f8f96e98a5c69e553
>
> The release files, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/
>
> For verification, the hashes of the .tar.gz artifacts we are voting on are
> as follows:
>
> apache-sdap-ingester-1.0.0-src.tar.gz:
>
> db380c3002351e65ec3581a3ff0cacbb7092f46292b0a656a78a919e1409738442e845731050a2160a556a7818f22b2ab4bb6da437200bc0a62419332de49ad7
>
> apache-sdap-nexus-1.0.0-src.tar.gz:
> da34e9830cf5126bac498180d7cdd95bc2cfc13535c7b4355ba51de64e3589a385a969e0cf1a89fa77e436b30c99a48abffab4b4ef03b23982aa33c2e83e8dbd
>
>
> apache-sdap-nexusproto-1.0.0-src.tar.gz:
> 05dc8e96d9c49207750c1da13f630493e8d08f5e68733742c157ac6c85ede29aca25f3c94cd706acbbe21cee41ebc052a880b4d6ce859bf510bcc2d66d8f88b2
>
>
> Release artifacts are signed with the following key:
>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x4e98c4a32026656e14e0b570fc20035a010e3b7b
>
> Please vote on releasing this package as Apache SDAP (incubating) 1.0.0.
>
> The vote is open for 72 hours or until at least 3 “+1” PMC votes are cast
> and passes if at least 3 +1 PMC votes are
> cast.
>
> [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Thank you,
> Riley
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

SDAP 1.0.0-rc2

[Julian Hyde]

Incubator PMC members,

Can I get some help inspecting a release candidate?

SDAP has been in incubation for several years, has only one remaining
active mentor (myself!) and has just produced a release candidate good
enough for me to vote +1.

In due course this RC will appear in a vote on this list, but could we
do them a favor and shorten the cycle a bit? If you are an IPMC member
and have some time to inspect an RC, can you please read their vote
email [1], inspect the artifacts, and reply with your feedback/vote.
Your feedback will help them get to a good release sooner.

Julian

[1] https://lists.apache.org/thread/6nmknw8n1flwsqp4n3cromnrck21xmh9

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Removed 'incubator.' from project status template

[Julian Hyde]

FYI, I removed 'incubator' from the project status template [1]. In
Baremaps we concluded that we wanted the shorter URL and email
addresses that would survive into graduation. And I figured that the
next podling would want to do the same.

If there are objections I can back it out.

Julian

[1] 
https://svn.apache.org/viewvc/incubator/public/trunk/content/projects/incubation-status-template.xml?r1=1882331=1904748_format=h

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Projects > 1000 days in Incubation

[Julian Hyde]

> SDAP - discussing steps to graduation (making a release)

Last week I joined SDAP as a mentor. I am encouraging them to reassess
what's left before graduation. As Justin says, the main thing is to
make a release. There's a lot of stuff that they *think* they need to
do (e.g. setting up CI) that they don't strictly need to do.

Sometimes the key step to graduate is the community waking up and
saying 'Yes, we're ready to graduate!'

Julian


Julian

On Wed, Oct 19, 2022 at 11:07 AM Justin Mclean  wrote:
>
> Hi,
>
> We have several projects that seem to have been hanging about in the 
> Incubator a little longer than they should. I took a look at all projects 
> that have been incubating for more than a 1000 days, and this seems to be the 
> state of play (corrections welcome):
>
> Annotator - discussing graduation
> Brpc - unknown
> DataLab - should have graduated
> Flagon - should have graduated
> Heron - discussing graduation
> Livy - undergoing   reboot
> Marvin-AI - role call
> Milagro - reboot / role call
> MXNet - has graduated
> Nemo - should have graduated
> NuttX - discussing graduation
> PageSpeed - lack of community growth
> Pony Mail - have discussed but no actions
> SDAP - discussing steps to graduation (making a release)
> Spot - Roll call
> StreamPipes - Discussing graduation
> Teaclave - Role call
> Toree - Role call
> Training - lack of community growth
> Tuweni - discussing graduation
>
> If you are a mentor of one of these projects, it would be great if you could 
> encourage the project to exist from the Incubator. If you are one of these 
> projects and your mentors are no longer engaged, please get in touch, and 
> we’ll see what we can do to help you.
>
> 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] What to do with long incubating projects?

[Julian Hyde]

One idea is to schedule a review after the project has been in the
incubator longer than the median time (say after 2 years). Deep-dive
into what is going right and wrong, identify things that can be fixed,
and set targets. And schedule another review a year later. Or schedule
a vote to retire.

One might even do this review (gasp!) over Zoom, so that people can
ask questions and have them answered in real time.

It sounds shockingly invasive, considering we at Apache tend to do
everything asynchronously. But it's better than the alternative, which
is a slow death as mentors and initial committers drift away.

Julian




On Tue, Oct 18, 2022 at 12:27 PM Justin Mclean  wrote:
>
> Hi,
>
> Looking at the longest incubating projects, one has graduated and needs some 
> cleanup, one had a reboot, one is discussing a reboot, and several have roll 
> calls in progress or are discussing retirement. However there are two or 
> three other projects that either should retire or graduate and have been 
> incubating for far too long.
>
> But taking a step back what can we do to make projects life though the 
> incubator shorter? Would having more resources help? (If so what resources?) 
> What else might we be able to do - offer training for instance?
>
> 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] Remove 72 hour waiting time to add PPMC members.

[Julian Hyde]

> If we now exercise our means to object [to] a nomination after it’s executed,
> we have this odd unpleasant situation of the person knowing what happened.

While this is a legitimate concern, as far as I know the Board and the
IPMC have not once exercised the right of veto, for hundreds if not
thousands of PMC and PPMC appointments. So, let's optimize the common
code path (approval without objection) over the rare path (veto from
the Board/IPMC).

On Sat, Oct 15, 2022 at 9:40 AM Christofer Dutz
 wrote:
>
> Hi,
>
> Well, I guess one of the reasons for the 72 hour was, that others can express 
> their doubts before the person is invited.
> If we now exercise our means to object a nomination after it’s executed, we 
> have this odd unpleasant situation of the person knowing what happened.
>
> But I guess we could try it and put it back in place if we see things go 
> south.
>
> Chris
>
>
> From: Justin Mclean 
> Date: Friday, 14. October 2022 at 17:39
> To: general@incubator.apache.org 
> Subject: Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.
> Hi,
>
> > I’m a bit worried that in contrast to PMCs PPMCs are usually not quite 
> > familiar with how things work at Apache.
> > Would we still have an option to intervene, if for example one PPMC bunch 
> > adds people from the same company, for example?
>
> I have a slight concern there as well, but this would very rarely occur. The 
> IPMC can remove people from the PPMC if they were inappropriately added.
>
> 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: [VOTE] Accept Baremaps into the Apache Incubator

[Julian Hyde]

+1 (binding)

Julian


On Thu, Oct 6, 2022 at 8:10 AM Josh Fischer  wrote:
>
> +1 (non-binding)
>
> On Thu, Oct 6, 2022 at 7:54 AM Bertrand Delacretaz 
> wrote:
>
> > Bertrand Delacretaz  wrote:
> > > ...I'm calling a vote to accept Baremap into the
> > > Apache incubator.
> > >...
> >
> > +1, bring Baremap into the Incubator!
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sent from A Mobile Device

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [Discuss] Baremaps Proposal

[Julian Hyde]

I’m happy to have this meeting if and when Baremaps starts incubation. But 
first let’s make the case to the IPMC that Baremaps should be in the Incubator, 
and get the vote passed.

Julian


> On Sep 28, 2022, at 12:45 AM, Bertil Chapuis  wrote:
> 
> 
>>> When I mentor a project (as I have volunteered to do for Baremaps) I
>>> usually host a Zoom meeting with the initial contributors explaining what
>>> really goes on during Incubation. I totally agree that learning the Apache
>>> Way and making releases are key activities. I usually invite other
>>> stakeholders (e.g. contributors’ managers) because people have a lot of
>>> questions, and it helps to set people’s expectations correctly early on.
> 
> This is a good idea. Should I already try to schedule the call? I guess that 
> a time slot between 2pm and 5pm (Zurich time) and between 8am and 11am 
> (Boston time) would be the best. Do you have particular constraints?
> 
 I think we should call out in the proposal of initial goals is learn the
>>> apache way how to make releases within the foundation.  There is much to
>>> learn in the incubating process.
> 
> Good point, I added this “to learn the apache way” at the top of the list.
> 
> 
> -
> 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] Baremaps Proposal

[Julian Hyde]

aries. In the long term, this will benefit our contributors, our users,
> >> and, more generally, the geospatial community.
> >> 
> >> == Documentation ==
> >> The documentation of baremaps can be found at: https://www.baremaps.com/ 
> >> <https://www.baremaps.com/>
> >> 
> >> == Initial Source ==
> >> The source code of baremaps can be found at:
> >> https://github.com/baremaps/baremaps <https://github.com/baremaps/baremaps>
> >> 
> >> The base map can be found at:
> >> https://github.com/baremaps/baremaps/tree/main/map 
> >> <https://github.com/baremaps/baremaps/tree/main/map>
> >> 
> >> == External Dependencies ==
> >> To our knowledge, none of the dependencies currently used in our main
> >> branch are a matter of concern (BSD, MIT, Apache).
> >> 
> >> == Cryptography ==
> >> There is no cryptography required in Apache Baremaps at present time.
> >> 
> >> = Required Resources =
> >> 
> >> == Mailing lists ==
> >> baremaps-...@incubator.apache.org 
> >> <mailto:baremaps-...@incubator.apache.org>
> >> baremaps-u...@incubator.apache.org 
> >> <mailto:baremaps-u...@incubator.apache.org>
> >> baremaps-comm...@incubator.apache.org 
> >> <mailto:baremaps-comm...@incubator.apache.org>
> >> baremaps-priv...@incubator.apache.org 
> >> <mailto:baremaps-priv...@incubator.apache.org>
> >> 
> >> == Git Repositories ==
> >> We would like to transfer our current github repository to the apache
> >> organization.
> >> 
> >> Source: https://github.com/baremaps/baremaps 
> >> <https://github.com/baremaps/baremaps>
> >> 
> >> Target: https://github.com/apache/baremaps 
> >> <https://github.com/apache/baremaps>
> >> 
> >> == Issue Tracking  ==
> >> We currently use GitHub to manage the issues and would also appreciate
> >> using a GitHub project.
> >> 
> >> https://github.com/orgs/apache/projects 
> >> <https://github.com/orgs/apache/projects>
> >> 
> >> == Initial Committers ==
> >> Names of initial committers with affiliation and current ASF status:
> >> - Bertil Chapuis (Heig-vd), Apache Committer, id: bchapuis
> >> - Andrea Borghi (Camptocamp)
> >> - James Smith (Heig-vd)
> >> - Antoine Drabble (Heig-vd)
> >> 
> >> = Sponsors =
> >> 
> >> == Champion ==
> >> Bertrand Delacretaz
> >> 
> >> == Mentors ==
> >> Martin Desruisseaux
> >> George Percivall
> >> Julian Hyde
> >> 
> >> == Sponsoring Entity ==
> >> The Apache Incubator
> >> 
> >> 
> >> 
> >> 
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> >> <mailto:general-unsubscr...@incubator.apache.org>
> >> For additional commands, e-mail: general-h...@incubator.apache.org 
> >> <mailto:general-h...@incubator.apache.org>
> >> 
> >> --
> > Sent from A Mobile Device
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> <mailto:general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org 
> <mailto:general-h...@incubator.apache.org>
> 
> -- 
> Sent from A Mobile Device

Re: [DISCUSS] Incubating Proposal for Datark

[Julian Hyde]

HW-Chao,

Your message is unreadable. Can you please resend without the HTML markup?

Julian

> On Sep 23, 2022, at 7:12 AM, HW-Chao Wang <576749...@qq.com.INVALID> wrote:
> 
>  This is an interesting project, +1 on the proposal. 
>   On 2022/09/23 13:06:00 Yu Li wrote:  Thanks all for the 
> positive feedback!@Willem  The proposal is updated and both 
> the project rename plan and github ids of  core developers have been 
> added. Please check it and let us know if any  further suggestions. 
> Thanks.Best Regards,  Yu  On Fri, 23 Sept 
> 2022 at 20:41, Xiaoqiao He  wrote: This is an interesting 
> project, +1 on the proposal and good luck to Datark! Best 
> Regards,   - He Xiaoqiao On Fri, Sep 23, 2022 at 
> 7:55 PM Willem Jiangwrote:  Hi Yu,  
>  Thanks for the explanation. Please add a rename plan 
> to the projectproposal.I'd be happy to be the 
> mentor of this project.   BTW,  Could you update 
> the Core Developers information with theirgithub id,  it 
> could be easy for us to track the contributions.  
> Willem Jiang   Twitter: 
> willemjiangWeibo: 姜宁willem   On 
> Fri, Sep 23, 2022 at 5:41 PM Yu Li  wrote:
>  Hi Willem, Referring to the 
> recent incubation process of streampark [1] and   uniffle   
>   [2], it seems they didn't rename their original project names 
> before entering apache incubator, thus we didn't plan to 
> change the original github project name but would 
> redirect it to the new project afterentering
>  incubation. OTOH, if such a rename is necessary before incubation, we 
>will need some internal approval to 
> process. Thanks. Best Regards,  
>Yu [1] 
> https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3   
>   [2] 
> https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h   
>   On Fri, 23 Sept 2022 at 
> 09:07, Willem Jiang wrote:
>   I just checked the source repo, it is still using the name of  
> RemoteShuffleService.  Is there 
> any plan for when we will change the project name?  
>  On Thu, Sep 22, 2022 at 11:45 AM Yu Li  wrote:  
>Hi All,
>  I would like to propose Datark 
> [1] as a new apache incubatorproject, and 
>   you can find the proposal [2] of Datark for more details.   
>   Datark is an intermediate 
> (shuffle and spilled) data service for   bigdata  
>  compute engines (Apache Spark, Apache Flink, Apache 
> Hive, etc.) toboost   
> performance, stability, and flexibility. It aims at enabling
> computing   engines to fully embrace the 
> disaggregated architecture. In a lot   of  
> cases,   intermediate data depends on large local 
> disks, and is often a   major  cause  
>  of inefficiency, instability, and inflexibility in 
> the lifecycle   of a   distributed job. 
> Datark solves the problems through the followingcore  
>  designs: 
> 1. Push-based shuffle plus partition data aggregation to 
> turn   randomIO   access 
> into sequential access.   2. FileSystem-like API 
> to support writing spilled data.   3. 
> Hierarchical storage from memory to DFS/object store to enable
> fast   cache and massive storage space.   
> 4. Engine-irrelevant APIs for easy integrating to various 
> engines.   5. Extended fault tolerance and data 
> replication to increasereliability  
>Datark is currently adopted in the 
> production environment at bothAlibaba 
>   and many other companies, serving petabytes of data per day. Beyond 
>that,   it has more open source 
> users including Shopee, NetEase, Bilibily,BOSS,   
> and Synnex. Most of these users have made contributions 
> to theproject,   forming an 
> active community with dozens of developers.   
>   The proposed initial committers are interested 
> in joining ASF to  reinforce  
>  extensive collaboration and build a more vibrant community. We   
>  believe  the   
> Datark project will provide tremendous value for the community if   
> itis   introduced into the Apache 
> incubator. I will 
> help this project as the champion and many thanks to our   four  
> other   mentors:   
>   * Becket Qin 
> (j...@apache.org)   * Duo Zhang 
> (zhang...@apache.org)   * Lidong Dai 
> (lidong...@apache.org)   * Willem Jiang 
> (ningji...@apache.org)
>  FWIW, although with different solutions, the issues Datark aims to  
> resolve   have some overlap 
> with Apache Uniffle (incubating) [3]. Actually we  
> noticed   this during the discussion phase of 
> Uniffle incubation (when we   werealso
>preparing for the incubation) and had some open and friendly 
>discussion  to 
>   see whether there could be a joint force [4], and 

Re: [VOTE] Accept StreamPark into the Apache Incubator

[Julian Hyde]

A few people on this thread are voting -1 with the rationale that
StreamPark is similar to existing projects. This is not a valid
reason. Apache does not try to ensure that projects don't overlap.

The 'community over code' mantra holds true: Apache does not pick
technologies, it builds communities. There are many examples of
'overlapping' projects that have built their own communities and
flourished (HTTP Server vs Tomcat, Spark vs Flink, Druid vs Pinot, ORC
vs Parquet).

Julian


On Sun, Aug 28, 2022 at 12:17 PM Zur Aviem  wrote:
>
> -1,
>
> Apache InLong[1] is a one-stop integration framework for massive data that
> provides automatic, secure and reliable data transmission capabilities.
> InLong supports both batch and stream data processing at the same time,
> which offers great power to build data analysis, modeling and other
> real-time applications based on streaming data.
>
> The streamxhub[2] aims to make stream processing easier! easy-to-use stream
> processing application development framework and one-stop stream processing
> operation platform.
>
> From my side, the planning and design of Apache Inlong and streamxhub
> projetc is consistent. Is it necessary to create a new project?
>
> And there are still many problems that have not been solved in the
> discussion email[3].
>
> Kind Regards,
> Beam, Aviem Zur
>
> [1] https://inlong.apache.org/
> [2] https://github.com/streamxhub/streampark
> [3] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3
>
> On 2022/08/24 03:55:26 tison wrote:
> > Hi all,
> >
> > Following up on the [DISCUSS] thread on StreamPark[1], I would like to
> call
> > a VOTE to accept StreamPark into the Apache Incubator, please check out
> the
> > StreamPark Proposal from the incubator wiki[2].
> >
> > Please cast your vote:
> >
> > [ ] +1, bring StreamPark into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring StreamPark into the Incubator, because...
> >
> > The vote will open at least for 72 hours, and only votes from the
> Incubator
> > PMC are binding, but votes from everyone are welcome.
> >
> > Best,
> > tison.
> >
> > [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3
> > [2]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Short process intro for exec's?

[Julian Hyde]

Rich,

Thanks for revising this presentation and sharing back. I hope others will find 
it useful.

Julian


> On Jul 23, 2022, at 8:58 AM, Salz, Rich  wrote:
> 
> Thanks Julian.
> 
> Here is the current draft intended to be a stand-alone introduction to Apache 
> and Incubation. Hope others find it useful, comments encouraged. 
> https://docs.google.com/presentation/d/1qbEfESTrihQsbh-8UupVf_NEms8GFzIyIvVAvl2heVM/edit?usp=sharing
> 
> 
> 
> -
> 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

Crail retirement is complete

[Julian Hyde]

As you know, the Crail podling retired as of 2022-06-20 [1].

I am pleased to report completion of the steps to clean up [2][3].

I note that Crail's retirement is mentioned in the draft Board report
for July [4].

Julian

[1] https://incubator.apache.org/projects/index.html#crail
[2] https://issues.apache.org/jira/browse/INFRA-23438
[3] https://lists.apache.org/thread/22c289sdp8vwn0p9qnjmgy6dlzj6ylp8
[4] https://cwiki.apache.org/confluence/display/INCUBATOR/July2022

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Short process intro for exec's?

[Julian Hyde]

Here’s the original Google slides. Feel free to make a copy. 

https://docs.google.com/presentation/d/1Q28ExXCggbsstqEa1KjnCuA3Ws4XWfR7itQzPmab8vk/edit?usp=sharing
 
<https://docs.google.com/presentation/d/1Q28ExXCggbsstqEa1KjnCuA3Ws4XWfR7itQzPmab8vk/edit?usp=sharing>

Julian


> On Jun 21, 2022, at 11:50 AM, Salz, Rich  wrote:
> 
> It seems that to download the slides, as opposed to just view them, you have 
> to set up a "Scribd" account which costs money if you forget to cancel within 
> the first 30 days.  I doubt that was your intent :)
> 
> The slides look great BTW, exactly what I can use as my starting point 
> internally.
> 
> On 6/17/22, 3:15 PM, "Julian Hyde"  wrote:
> 
>When I was mentoring the Hop podling a couple of years ago, I gave the 
> following talk to educate the initial committers about the process. But it is 
> probably suitable for executives:
> 
>https://www.slideshare.net/julianhyde/what-to-expect-when-youre-incubating 
>  
> 
>Julian
> 
> 
> 
> 
>> On Jun 17, 2022, at 10:50 AM, Salz, Rich  wrote:
>> 
>>>  Depends on what you mean by short.
>> 
>> Yeah, that's always the issue, innit.
>> 
>> I was hoping for something 10 minutes for exec's.  I've read the cookbook 
>> and might unfairly synopsize it.
>> 
>> 
>> 
>> -
>> 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: Short process intro for exec's?

[Julian Hyde]

When I was mentoring the Hop podling a couple of years ago, I gave the 
following talk to educate the initial committers about the process. But it is 
probably suitable for executives:

https://www.slideshare.net/julianhyde/what-to-expect-when-youre-incubating 


Julian




> On Jun 17, 2022, at 10:50 AM, Salz, Rich  wrote:
> 
>>   Depends on what you mean by short.
> 
> Yeah, that's always the issue, innit.
> 
> I was hoping for something 10 minutes for exec's.  I've read the cookbook and 
> might unfairly synopsize it.
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Retire Crail

[Julian Hyde]

With five binding +1 votes and no 0 or -1 votes, the vote passes.

Thanks to all who voted. I'll work with other mentors to carry out the 
post-retirement steps.

Julian


On 2022/06/06 19:48:20 Julian Hyde wrote:
> After years of declining activity[1][2], and following discussions on
> dev@ [3][4] the Crail podling has voted to retire from incubation
> [5][6]. Per policy [7] I am proposing an IPMC vote to retire Crail.
> 
> The vote is by lazy consensus and runs for 72 hours.
> 
> +1 [ ] Retire Crail from the Incubator
> -1 [ ] Do not retire Crail from the Incubator
> 
> Here is my vote:
> +1 [x] Retire Crail from the Incubator
> 
> Julian Hyde
> (Member IPMC, Crail mentor)
> 
> [1] https://incubator.apache.org/projects/crail.html
> [2] https://lists.apache.org/list?d...@crail.apache.org
> [3] https://lists.apache.org/thread/6hxkph98gobb5y7lrvx62rgr6ob9o91h
> [4] https://lists.apache.org/thread/9n08m29xgpshs4f2wxgspm4tlt44r98g
> [5] https://lists.apache.org/thread/xzss2o1oj2k85bbhvx883ojlrlozg3zm
> [6] https://lists.apache.org/thread/7165g55mrchzrlmhczfgybgzlnl2hxpj
> [7] https://incubator.apache.org/guides/retirement.html#deciding_to_retire
> 
> -
> 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

[VOTE] Retire Crail

[Julian Hyde]

After years of declining activity[1][2], and following discussions on
dev@ [3][4] the Crail podling has voted to retire from incubation
[5][6]. Per policy [7] I am proposing an IPMC vote to retire Crail.

The vote is by lazy consensus and runs for 72 hours.

+1 [ ] Retire Crail from the Incubator
-1 [ ] Do not retire Crail from the Incubator

Here is my vote:
+1 [x] Retire Crail from the Incubator

Julian Hyde
(Member IPMC, Crail mentor)

[1] https://incubator.apache.org/projects/crail.html
[2] https://lists.apache.org/list?d...@crail.apache.org
[3] https://lists.apache.org/thread/6hxkph98gobb5y7lrvx62rgr6ob9o91h
[4] https://lists.apache.org/thread/9n08m29xgpshs4f2wxgspm4tlt44r98g
[5] https://lists.apache.org/thread/xzss2o1oj2k85bbhvx883ojlrlozg3zm
[6] https://lists.apache.org/thread/7165g55mrchzrlmhczfgybgzlnl2hxpj
[7] https://incubator.apache.org/guides/retirement.html#deciding_to_retire

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Thank you

[Julian Hyde]

The kind words are much appreciated, Matt. We’re all volunteers; that’s why
we do this.

Regarding ‘expectation management’, and communication between mentors and
podlings. I think that we at Apache tend to rely on email a little too
much. Email works, but only once you have established a personal
connection. We started off Hop’s incubation with a Zoom call where the
mentors and most of the initial committers were present. I used a slide
deck [1] to set the agenda, but most of the meeting was spent just
answering questions on people's minds.

I would encourage other mentors/champions to follow a similar process
with their podlings. Ping me if you would like an editable copy of the
slides.

Julian

[1]
https://www.slideshare.net/julianhyde/what-to-expect-when-youre-incubating

On Jan 4, 2022, at 5:37 AM, Matt Casters 
wrote:

Dear ASF Incubator,

Now that Hop graduated as a TLP I would like to take a few moments to thank
everyone that was involved in helping us throughout the graduation
process.  First and foremost I want to thank our mentors who did an
excellent job in guiding us.  In particular Julian Hyde was very present
with practical advice and, I think, much needed expectation management in
the very beginning.

In the incubator we tried to follow the approach of structurally solving
advice and comments that were given.  This worked great I think.  Lots of
people chipped in with advice but Justin Mclean: thanks a lot, you really
made a difference.  You were always capable of digging up extra stuff and
honestly, our project is in a much better shape because of this.

Kind regards,
Matt

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

[Julian Hyde]

+1 (binding)

Good luck!

On Thu, Dec 2, 2021 at 10:38 AM Bart Maertens  wrote:
>
> Hi Incubator Community,
>
> After a discussion[1] with and vote by[2] the Hop community, we have
> discussed Apache Hop's graduation in the general@incubator [DISCUSS]
> thread[3], where no major issues were raised.
>
> With no objections brought up in the discussion, we would like to proceed
> with the voting process.
>
> Here is the official request to vote to graduate the Apache Hop project as
> a TLP.
>
> Please provide your vote as one of the following options:
>
> [ ] +1 - Recommend graduation of Apache Hop as a TLP
>
> [ ]  0 - I don't feel strongly about it, but don't object
>
> [ ] -1 - Do not recommend the graduation of Apache Hop because…
>
> The VOTE will remain open for at least 72 hours.
>
> The Hop community achievements since Hop joined the Incubator in September
> 2020:
> - over 3200 commits by 28 contributors
> - 4 releases (0.60, 0.70, 0.99, 1.0)
> - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors
> and PPMC members excluded)
> - diverse committers and PPMC, with regular contributions from at least 5
> different companies/institutes
> - Apache Hop website[4]
> - dev conversations at d...@hop.apache.org
> - assessed ourselves against the Apache Project maturity matrix[5] and
> didn't find any issues.
>
>
> [1] https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
> [2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
> [3] https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
> [4] https://hop.incubator.apache.org/
> [5] https://hop.apache.org/community/incubator/
>
> 
>
> Establish the Apache Hop 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 platform for data orchestration.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Hop Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Hop Project be and hereby is responsible for
> the creation and maintenance of software related to a platform for data
> orchestration; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Hop 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 Hop Project:
>
> * Bart Maertens 
> * Brandon Jackson 
> * Dave Campen 
> * Francois Papon 
> * Hans Van Akelyen 
> * Julian Hyde 
> * Kevin Ratnasekera 
> * Matt Casters 
> * Nicolas Adment 
> * Sergio Ramazzina 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
> appointed to the office of Vice President, Apache Hop, 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 Hop Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Hop podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Hop podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Julian Hyde]

Bart,

The typo in the resolution that (I believe) Sebb pointed out is still present. 
In the following, “A” should be “a” and “.” should be deleted:

> RESOLVED, that the Apache Hop Project be and hereby is responsible for
> the creation and maintenance of software related to A platform for data
> orchestration.; and be it further


Can you please fix it and re-start the vote?

Julian

> On Dec 2, 2021, at 5:57 AM, Bart Maertens  wrote:
> 
> Hi Incubator Community,
> 
> After a discussion[1] with and vote by[2] the Hop community, we have
> discussed Apache Hop's graduation in the general@incubator [DISCUSS] thread
> [3], where no major issues were raised.
> 
> With no objections brought up in the discussion, we would like to proceed
> with the voting process.
> 
> Here is the official request to vote to graduate the Apache Hop project as
> a TLP.
> 
> Please provide your vote as one of the following options:
> 
> [ ] +1 - Recommend graduation of Apache Hop as a TLP
> 
> [ ]  0 - I don't feel strongly about it, but don't object
> 
> [ ] -1 - Do not recommend the graduation of Apache Hop because…
> 
> The VOTE will remain open for at least 72 hours.
> 
> To summarize a few of the community's achievements:
> 
> The Hop community achievements since Hop joined the Incubator in September
> 2020:
> - over 3200 commits by 28 contributors
> - 4 releases (0.60, 0.70, 0.99, 1.0)
> - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors
> and PPMC members excluded)
> - diverse committers and PPMC, with regular contributions from at least 5
> different companies/institutes
> - Apache Hop website[4]
> - dev conversations at d...@hop.apache.org
> - assessed ourselves against the Apache Project maturity matrix[5] and
> didn't find any issues.
> 
> 
> [1] https://lists.apache.org/thread/470xwxw8x8qmm4fp82ckqys5zmrq9416
> [2] https://lists.apache.org/thread/s8vg1nh1g707s4hhcxjtg1zdccjpjh2k
> [3] https://lists.apache.org/thread/mrx8g5w1xfzx80wtg9l3mrm3q1lkh6ss
> [4] https://hop.incubator.apache.org/
> [5] https://hop.apache.org/community/incubator/
> 
> 
> 
> Establish the Apache Hop 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 platform for data orchestration.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Hop Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Hop Project be and hereby is responsible for
> the creation and maintenance of software related to A platform for data
> orchestration.; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
> have primary responsibility for management of the projects within the
> scope of responsibility of the Apache Hop 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 Hop Project:
> 
> * Bart Maertens 
> * Brandon Jackson 
> * Dave Campen 
> * Francois Papon 
> * Hans Van Akelyen 
> * Julian Hyde 
> * Kevin Ratnasekera 
> * Matt Casters 
> * Nicolas Adment 
> * Sergio Ramazzina 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
> appointed to the office of Vice President, Apache Hop, 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 Hop Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Hop podling; and
> be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Hop podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Julian Hyde]

Thanks for doing the research, Bertrand. That thread describes a case (from 
2019) that is virtually identical to this one.

I recommend Hop does the same as that case: remove that person’s name from the 
resolution, and vote them in as a PMC member after graduating. Since the effect 
is the same, they can do that without requiring a vote on dev@hop.

For the record, my reading of the thread is that resolutions MAY include 
non-Apache people but the candidate project removed the non-Apache people from 
the resolution in order to accommodate limitations in the tooling.

Julian
 

> On Nov 29, 2021, at 9:12 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> On Mon, Nov 29, 2021 at 5:56 PM Julian Hyde  wrote:
>> ...Let’s just assume that it’s OK to include people with non-Apache email 
>> addresses in the graduation resolution...
> 
> I don't think that's the case, in previous similar cases Board members
> asked for the resolutions to be modified to avoid including non-apache
> email addresses [1].
> 
> it's very easy for the PMC to fix that as soon as it's created, by
> voting in the "missing" member. To me that's the safe option here.
> 
> -Bertrand
> 
> [1] https://lists.apache.org/thread/v7b1l27zf1xbkm45y8ryzs6pc0dwcl9g
> (accessible to PMC chairs and ASF Members)
> 
> -
> 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 Hop (Incubating) as a TLP

[Julian Hyde]

> On Nov 29, 2021, at 7:50 AM, sebb  wrote:
> 
> On Mon, 29 Nov 2021 at 04:58, Julian Hyde  wrote:
>> 
>> 
>> Is it possible to give someone an Apache id even if though are not a 
>> committer or PMC member of any project? Maybe that would solve some of the 
>> tooling issues.
> 
> You will have to ask Infra about that.

Let’s just assume that it’s OK to include people with non-Apache email 
addresses in the graduation resolution.

Julian


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Julian Hyde]

> On Nov 26, 2021, at 6:05 AM, sebb  wrote:
> 
> On Fri, 26 Nov 2021 at 12:06, Matt Casters
> mailto:matt.cast...@neo4j.com.invalid>> 
> wrote:
> 
>> As for Ricardo: he is indeed not a committer (yet) but an advisor to the
>> project.  His insights as an educator have been very valuable and is in the
>> process of becoming a committer.  Our mentor Julian informed us that (and I
>> quote) "There’s no rule that the initial PMC can consist only of people who
>> were committers in the podling".
> 
> That is rather different from including people who are not yet ASF committers.
> 
> AFAIK, most of the Infra and Whimsy tooling assumes that PMC members
> have ASF ids.

Yes, I gave them that advice. It seemed rather pointless to vote someone in as 
a committer, just so that they could get an Apache ID, just so that they could 
be could be included in the graduation resolution. And then to have to repeat 
the vote for the graduation resolution because the email address has changed.

Is it possible to give someone an Apache id even if though are not a committer 
or PMC member of any project? Maybe that would solve some of the tooling issues.

Julian
 

Re: Report template generation changes

[Julian Hyde]

Justin,

Did you recently change the template to add text such as the "Are
things..." and "Are 3rd..." in the following?

  # Have your mentors been helpful and responsive?

  Are things falling through the cracks? If so, please list any open
issues that need to be addressed.

  # Is the PPMC managing the podling's brand / trademarks?

  Are 3rd parties respecting and correctly using the podlings name and
brand? If not what actions has the PPMC taken to correct this? Has the
VP, Brand approved the project name?

I assume that you intend podlings to remove that text. But one of the
podlings I mentor just left the text, and added comments. Do you think
it would help if you, say, enclosed the template text in brackets or
braces?

Also, "If not what actions..." should be "If not, what actions...".

Julian

On Wed, Nov 17, 2021 at 7:15 PM Justin Mclean  wrote:
>
> Hi,
>
> I just modified the report generation scripts so that individual podlings 
> template can be generated. This means that if for some reason a podling 
> report is missing that report can be generated and added to the wiki. 
> Although it may be just as easy to copy a previous report.
>
> I’ve also modified the scripts so they take year as an option so they can 
> generate reports in advance. If the report changes and you regenerate the 
> report it will tell you what changes have occurred.
>
> The only downside is that the shepherds need to be generated in advance. We 
> might need to add the ability to regenerate shepherds for future reports.
>
> 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 Hop (Incubating) as a TLP

[Julian Hyde]

I agree with Craig; the description of the project in the resolution definitely 
needs some work.

I noticed that the project has not held formal vote for graduation on dev@hop. 
I’ll remind the project that they need to have that vote before proceeding to a 
vote on general@incubator.

Julian


> On Oct 15, 2021, at 12:54 PM, Craig Russell  wrote:
> 
> Hi,
> 
> I'd strongly suggest that you improve the wording of the resolution "related 
> to short for the Hop Orchestration Platform". It's barely parseable. 
> 
> Perhaps make it simpler by removing the entire text after "related to short 
> for the Hop Orchestration Platform...easily used by other software" and 
> replacing it with "related to Java-based data orchestration tools". 
> 
> Warm regards,
> Craig
> 
>> On Oct 15, 2021, at 3:02 AM, Bart Maertens  wrote:
>> 
>> Hi All, 
>> 
>> After a discussion with the community[1], we believe Apache Hop (Incubating) 
>> is ready for graduation to a TLP, and we'd like to bring it up in discussion 
>> with the IPMC.
>> 
>> The Hop community achievements since Hop joined the Incubator in September 
>> 2020: 
>> 
>> - over 3000 commits by 27 contributors
>> - 4 releases (0.60, 0.70, 0.99, 1.0)
>> - 5 mentors, 6 PPMC members (mentors excluded) and 8 committers (mentors and 
>> PPMC members excluded)
>> - diverse committers and PPMC, with regular contributions from at least 4 
>> different companies/institutes
>> - Apache Hop website[2]
>> - dev conversations at d...@hop.apache.org 
>> - assessed ourselves against the Apache Project maturity matrix[3] and 
>> didn't find any issues.   
>> 
>> [1] 
>> https://lists.apache.org/thread.html/reab316256de8b7d8a8e2c73dbc412ca82a3f7c17243163061f848f9c%40%3Cdev.hop.apache.org%3E
>> [2] https://hop.incubator.apache.org/
>> [3] 
>> https://community.apache.org/apache-way/apache-project-maturity-model.html
>> 
>> 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 Hop 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 short for the Hop Orchestration Platform. Written completely
>> in Java it aims to provide a wide range of data orchestration tools,
>> including a visual development environment, servers, metadata analysis,
>> auditing services and so on. As a platform, Hop also wants to be a
>> reusable library so that it can be easily reused by other software.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache Hop Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache Hop Project be and hereby is responsible for
>> the creation and maintenance of software related to short for the Hop
>> Orchestration Platform. Written completely in Java it aims to provide a
>> wide range of data orchestration tools, including a visual development
>> environment, servers, metadata analysis, auditing services and so on. As
>> a platform, Hop also wants to be a reusable library so that it can be
>> easily reused by other software; and be it further
>> 
>> RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
>> have primary responsibility for management of the projects within the
>> scope of responsibility of the Apache Hop 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 Hop Project:
>> 
>> * Bart Maertens  
>> * Brandon Jackson
>> * Francois Papon 
>> * Hans Van Akelyen   
>> * Hiromu Hota
>> * Julian Hyde
>> * Kevin Ratnasekera  
>> * Matt Casters   
>> * Maximilian Michels 
>> * Nicolas Adment 
>> * Tom Barber 
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
>> appoint

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

[Julian Hyde]

;>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>>>> (PMC), to be known as the "Apache Hop Project", be and hereby is
>>>>> established pursuant to Bylaws of the Foundation; and be it further
>>>>> 
>>>>> RESOLVED, that the Apache Hop Project be and hereby is responsible for
>>>>> the creation and maintenance of software related to short for the Hop
>>>>> Orchestration Platform. Written completely in Java it aims to provide
>>> a
>>>>> wide range of data orchestration tools, including a visual development
>>>>> environment, servers, metadata analysis, auditing services and so on.
>>> As
>>>>> a platform, Hop also wants to be a reusable library so that it can be
>>>>> easily reused by other software; and be it further
>>>>> 
>>>>> RESOLVED, that the office of "Vice President, Apache Hop" 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 Hop Project, and to
>>>>> have primary responsibility for management of the projects within the
>>>>> scope of responsibility of the Apache Hop 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 Hop Project:
>>>>> 
>>>>> * Bart Maertens  
>>>>> * Brandon Jackson
>>>>> * Francois Papon 
>>>>> * Hans Van Akelyen   
>>>>> * Hiromu Hota
>>>>> * Julian Hyde
>>>>> * Kevin Ratnasekera  
>>>>> * Matt Casters   
>>>>> * Maximilian Michels 
>>>>> * Nicolas Adment 
>>>>> * Tom Barber 
>>>>> 
>>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hans Van Akelyen be
>>>>> appointed to the office of Vice President, Apache Hop, 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 Hop Project be and hereby is tasked with the
>>>>> migration and rationalization of the Apache Incubator Hop podling; and
>>>>> be it further
>>>>> 
>>>>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>>>>> Hop podling encumbered upon the Apache Incubator PMC are hereafter
>>>>> discharged.
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Best  wishes！
>>> Calvin Kirs
>>> 
>> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hop (incubating) 1.0.0-rc1

[Julian Hyde]

Forwarding my +1 (binding) from the podling vote.

> On Sep 26, 2021, at 11:58 PM, Hans Van Akelyen  
> wrote:
> 
> Hi All,
> 
> After a thorough testing period for Hop 0.99, we are ready to release
> version 1.0.0 to the public. All issues raised during the previous release
> have been resolved. Dubious code has either been rewritten or removed from
> this release.
> 
> This release contains no new features, only further cleanup and code
> hardening has been done. I would like to thank everyone that participated
> in filing, testing and resolving issues.
> 
> Build instructions can be found in the README included.
> 
> Hop community vote and result threads:
> Vote:
> https://lists.apache.org/thread.html/r429a306535b933737fb93ea66a0d78420dc8f6abc30ce5eeb8cafd2d%40%3Cdev.hop.apache.org%3E
> 
> Result:
> https://lists.apache.org/thread.html/r3e0605e7006aea3c03aba7d6a00eb3a748bb6662d47ba31c8348475a%40%3Cdev.hop.apache.org%3E
> 
> The tag to be voted on is 1.0.0rc1 (commit 8a1fc96 ):
> https://github.com/apache/incubator-hop/tree/1.0.0-rc1
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/hop/apache-hop-1.0.0-incubating-rc1/
> 
> The SHA512 Checksum for these artifacts is:
> Source: 
> b7e2fdf14fcacaf937bf3e4ffedba6870a0b97965c97e0be0013acde308e161035fce5dfcb5254f96194cfe7a944bcfd5b3d8541b51435f732d0a5f61e498550
> 
> Client: 
> f9dd913c09a547a21e0c0c26ec71040dd34b753e83d4638982a1e5b525f4219e2e33c54989305461c793ecdd779ffab953f65872f5d809267938fd62ddf123c2
> 
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x9a8a628dd4f4aa1e
> 
> For more information about the contents of this release, see:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324323=12350233
> 
> Please vote on releasing this package as Apache Hop (incubating) 1.0.0!
> 
> The vote is open for 72 hours and passes if
> a majority of at least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Hop (incubating) 1.0.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Best Regards,
> Hans


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Require websites to have standard download URL?

[Julian Hyde]

Also: if anyone visits http://podling.apache.org/download 
 it MUST redirect to 
https://podling.apache.org/download . 
(Note ‘http’ in first ‘https’ in second.)


> On Sep 17, 2021, at 6:26 AM, Alexander Alten  wrote:
> 
> Good idea, +1
> 
> —Alex 
> 
>> On 17. Sep 2021, at 15:23, sebb  wrote:
>> 
>> Many of the podling websites have a download page of the form:
>> 
>> https://.apache.org/download/
>> 
>> Given that every website must have a download page, and that the
>> /download/ URL can easily be redirected to an alternate page, it might
>> be worth considering making this URL a requirement for all podling
>> websites.
>> 
>> Sebb
>> 
>> -
>> 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] Release Apache Hop (incubating) 0.99-rc4

[Julian Hyde]

+1 (binding)

Downloaded, checked signatures, built using “./mvnw clean install -DskipTests" 
and Java 8 on Ubuntu 20.04.2 LTS. Followed build instructions in README.md. 
Checked LICENSE, NOTICE, DISCLAIMER; ran RAT.

Note: It’s nothing to do with this release, but before you go 1.0 I think you 
should remove the “a lot of things may be broken” language from README.md.

Julian


> On Aug 3, 2021, at 5:12 AM, fpa...@apache.org wrote:
> 
> +1 (binding)
> 
> regards,
> 
> François
> fpa...@apache.org
> 
> Le 02/08/2021 à 12:58, Hans Van Akelyen a écrit :
>> Hi All,
>> 
>> This release candidate resolves the issues around Imported Source code.
>> As discussed in the following mail thread [1] we identified the code that
>> was added from external sources after starting the incubator and removed
>> it.
>> 
>> This release candidate also includes all changes that were marked for the
>> 1.0 release.
>> For a detailed list on what was added after our initial 0.99 cutoff point
>> and now you can see list [2].
>> 
>> Build instructions can be found in the README included.
>> 
>> Hop community vote and result threads:
>> Vote:
>> https://lists.apache.org/thread.html/r43840a74ba1b126268915c1ae4afd42f8ef9cbfe77da84bf0adef21b%40%3Cdev.hop.apache.org%3E
>> 
>> Result:
>> https://lists.apache.org/thread.html/rdb792ed9542758c0c430db8aa3e1494a28006a35d6f39b9d58b66e2c%40%3Cdev.hop.apache.org%3E
>> 
>> The tag to be voted on is 0.99-rc4 (commit 069d67e):
>> https://github.com/apache/incubator-hop/tree/0.99-rc4
>> 
>> The release files, including signatures, digests, etc. can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/hop/apache-hop-0.99-incubating-rc4/
>> 
>> The SHA512 Checksum for these artifacts is:
>> Source: 
>> 38d3b318b8e7a19fe381be3727a467c0b842d5c46a7e534f8cc4671bed11e17124ad34af271e351101e54780b5084ad3366d0b8c2c06d1db11f608fada304804
>> 
>> Client: 
>> 97fccb1ac74b0198c1db63109a7374d48ff252eb8ffbe3721941229defcf0d136fb7185895bffcdfa096f111717d75770617f989e2b3fc4f73f55cf33419c333
>> 
>> Release artifacts are signed with the following key:
>> https://keyserver.ubuntu.com/pks/lookup?op=get=0x9a8a628dd4f4aa1e
>> 
>> For more information about the contents of this release, see:
>> https://issues.apache.org/jira/projects/HOP/versions/12350036
>> 
>> Please vote on releasing this package as Apache Hop (incubating) 0.99!
>> 
>> The vote is open for 72 hours and passes if
>> a majority of at least 3 +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Hop (incubating) 0.99
>> [ ] +0 No opinion
>> [ ] -1 Do not release this package because ...
>> 
>> Best Regards,
>> Hans
>> 
>> [1]
>> https://lists.apache.org/thread.html/r3b04392a62d7bbe45fa214e6a4e3bd3ec1ec34b8e2db660508785a50%40%3Cdev.hop.apache.org%3E
>> 
>> [2]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20HOP%20AND%20fixVersion%20%3D%200.99%20AND%20resolved%20%3E%3D%202021-06-06%20AND%20resolved%20%3C%3D%202021-07-28
>> 
> 
> -
> 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] Release Apache Hop (incubating) 0.99-rc1

[Julian Hyde]

Forwarding my vote from the PPMC poll:

+1 (binding)

On Wed, Jun 9, 2021 at 5:54 AM Xun Liu  wrote:
>
> +1 (non-binding) from me, I have checked the following items:
>
> - Incubating in name
> - NOTICE is fine
> - DISCLAIMER exists
> - All links are valid
> - No unexpected binary files
> - All ASF files have ASF headers
>
> Best regards
> Xun Liu
>
> On Wed, Jun 9, 2021 at 4:47 PM Hans Van Akelyen 
> wrote:
>
> > Hi All,
> >
> > This will be our preview 1.0 release, this release contains both the source
> > code and binary to run the client. This will also be our first release
> > without DISCLAIMER-WIP but the regular disclaimer.
> >
> > This release aims to get as much feedback as possible so we can remove some
> > final bugs before releasing 1.0.
> >
> > Build instructions can be found in the README included.
> >
> > Hop community vote and result threads:
> > Vote:
> >
> >
> > https://lists.apache.org/thread.html/ra0cb8d9286e3cabf3348f3544a6dc0e60dcdd87a58918a7c1a413d36%40%3Cdev.hop.apache.org%3E
> > Result:
> >
> > https://lists.apache.org/thread.html/ra6e1e447f5611bea927e8b41558d5ff790e8475e8e44629b7e872a14%40%3Cdev.hop.apache.org%3E
> >
> > The tag to be voted on is 0.99-rc1 (commit a29e5a7)
> > https://github.com/apache/incubator-hop/tree/0.99-rc1
> >
> > The release files, including signatures, digests, etc. can be found at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/hop/apache-hop-0.99-incubating-rc1/
> >
> > The SHA512 Checksum for these artifacts is:
> > code:
> >
> > ab62b90b311097fde622884cbcd3c67ccec75cfe0be2c70c7dd773528f34290994a0c3a166a1cecb04a5342d5eccb6953f258b87c0497e90e2ffd2c5f31723a3
> >
> > client:
> >
> > 99f28e78d4795c19ae686094bcef6e75e875fcd213c967c868108afcf3fc0bcd83a268e2566aee122ae74c0dc54cffdd1a7e43bfcf7fcf23f3dda50487d5b644
> >
> > Release artifacts are signed with the following key:
> > https://keyserver.ubuntu.com/pks/lookup?op=get=0x9a8a628dd4f4aa1e
> >
> > For more information about the contents of this release, see:
> > https://issues.apache.org/jira/projects/HOP/versions/12350036
> >
> > Please vote on releasing this package as Apache Hop (incubating) 0.99!
> >
> > The vote is open for 72 hours and passes if
> > a majority of at least 3 +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Hop (incubating) 0.99
> > [ ] +0 No opinion
> > [ ] -1 Do not release this package because ...
> >
> > Best Regards,
> > Hans
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Turn on GitHub Issues on apache/incubator

[Julian Hyde]

How much will this increase the email traffic?

> On Jun 3, 2021, at 9:39 AM, Dave Fisher  wrote:
> 
> Unless there is an objection I will turn on GitHub Issues on 
> https://github.com/apache/incubator next Monday.
> 
> I’ll also set notifications so that PRs and issues are sent to general@i.a.o
> 
> See https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> 
> This will make it easier to track observations like sebb’s on the retirement 
> page.
> 
> Regards,
> Dave
> -
> 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

[jira] [Commented] (INCUBATOR-245) Slider - Auditing Capability

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311754#comment-17311754
 ] 

Julian Hyde commented on INCUBATOR-245:
---

Good point. Can an admin please close it.

> Slider - Auditing Capability
> 
>
> Key: INCUBATOR-245
> URL: https://issues.apache.org/jira/browse/INCUBATOR-245
> Project: Incubator
>  Issue Type: Task
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
>
> As far as I understand, Slider outputs only logs for debugging use as details 
> of executing containers, and etc.
> Can we believe Slider doesn't have any logs for auditing of Slider itself? 
> (i.e. when & who used Slider for what application, etc.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-245) Slider - Auditing Capability

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311739#comment-17311739
 ] 

Julian Hyde commented on INCUBATOR-245:
---

[~jmclean], As an admin, can you please remove the spam attachments just added.

> Slider - Auditing Capability
> 
>
> Key: INCUBATOR-245
> URL: https://issues.apache.org/jira/browse/INCUBATOR-245
> Project: Incubator
>  Issue Type: Task
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
> Attachments: Twitter-Social-Icons (1).zip, iyyd.log, iyyd.log
>
>
> As far as I understand, Slider outputs only logs for debugging use as details 
> of executing containers, and etc.
> Can we believe Slider doesn't have any logs for auditing of Slider itself? 
> (i.e. when & who used Slider for what application, etc.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hop (incubating) 0.60-rc1

[Julian Hyde]

PS More environment info:

$ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T11:49:05-08:00)
Maven home: /usr/local/apache-maven-3.5.3
Java version: 1.8.0_271, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk1.8.0_271/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-64-generic", arch: "amd64", family: "unix"

$ java -version
java version "1.8.0_271"
Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)

On Sat, Jan 23, 2021 at 5:03 PM Julian Hyde  wrote:
>
> FWIW, I get the same error. Ubuntu 20.04, Java 8, "mvn clean compile".
>
> ...
> [INFO] Hop Assemblies Plugins Dist  SUCCESS [ 17.172 
> s]
> [INFO] Hop Assemblies Static Assets ... SUCCESS [  0.272 
> s]
> [INFO] Hop Assemblies Demo  SUCCESS [  0.007 
> s]
> [INFO] Hop Assemblies Libraries ... FAILURE [  3.737 
> s]
> [INFO] Hop Client . SKIPPED
> [INFO] Hop Assemblies Core  SKIPPED
> [INFO] Hop Assemblies Core Libraries .. SKIPPED
> [INFO] Hop Assemblies Debug 0.60 .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 03:52 min
> [INFO] Finished at: 2021-01-23T17:01:00-08:00
> [INFO] 
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.1.0:copy-dependencies
> (copy-libs) on project hop-assemblies-libs: Artifact has not been
> packaged yet. When used on reactor artifact, copy should be executed
> after packaging: see MDEP-187. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn  -rf :hop-assemblies-libs
>
> Julian
>
>
> On Sat, Jan 23, 2021 at 4:18 PM Justin Mclean  
> wrote:
> >
> > Hi,
> >
> > It's failing for me at:
> > [INFO] Hop Assemblies Plugins Dist  FAILURE [ 
> > 33.371 s]
> >
> > When I do an “mvn compile” but it works with a “man package”.
> >
> > 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: [VOTE] Release Apache Hop (incubating) 0.60-rc1

[Julian Hyde]

FWIW, I get the same error. Ubuntu 20.04, Java 8, "mvn clean compile".

...
[INFO] Hop Assemblies Plugins Dist  SUCCESS [ 17.172 s]
[INFO] Hop Assemblies Static Assets ... SUCCESS [  0.272 s]
[INFO] Hop Assemblies Demo  SUCCESS [  0.007 s]
[INFO] Hop Assemblies Libraries ... FAILURE [  3.737 s]
[INFO] Hop Client . SKIPPED
[INFO] Hop Assemblies Core  SKIPPED
[INFO] Hop Assemblies Core Libraries .. SKIPPED
[INFO] Hop Assemblies Debug 0.60 .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:52 min
[INFO] Finished at: 2021-01-23T17:01:00-08:00
[INFO] 
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.1.0:copy-dependencies
(copy-libs) on project hop-assemblies-libs: Artifact has not been
packaged yet. When used on reactor artifact, copy should be executed
after packaging: see MDEP-187. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :hop-assemblies-libs

Julian


On Sat, Jan 23, 2021 at 4:18 PM Justin Mclean  wrote:
>
> Hi,
>
> It's failing for me at:
> [INFO] Hop Assemblies Plugins Dist  FAILURE [ 33.371 
> s]
>
> When I do an “mvn compile” but it works with a “man package”.
>
> 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

[jira] [Commented] (INCUBATOR-245) Slider - Auditing Capability

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264435#comment-17264435
 ] 

Julian Hyde commented on INCUBATOR-245:
---

Great minds, [~elserj]!

> Slider - Auditing Capability
> 
>
> Key: INCUBATOR-245
> URL: https://issues.apache.org/jira/browse/INCUBATOR-245
> Project: Incubator
>  Issue Type: Task
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
> Attachments: 2021_01_10_07_45_25.mp4
>
>
> As far as I understand, Slider outputs only logs for debugging use as details 
> of executing containers, and etc.
> Can we believe Slider doesn't have any logs for auditing of Slider itself? 
> (i.e. when & who used Slider for what application, etc.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[jira] [Commented] (INCUBATOR-245) Slider - Auditing Capability

[Julian Hyde (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17264434#comment-17264434
 ] 

Julian Hyde commented on INCUBATOR-245:
---

The attachment '2021_01_10_07_45_25.mp4', just added today, looks like spam. 
[~jmclean], since I don't have admin privileges and you I presume you do, can 
you please remove the attachment?

> Slider - Auditing Capability
> 
>
> Key: INCUBATOR-245
> URL: https://issues.apache.org/jira/browse/INCUBATOR-245
> Project: Incubator
>  Issue Type: Task
>Reporter: Krishnadevan Purushothaman
>Priority: Critical
> Attachments: 2021_01_10_07_45_25.mp4
>
>
> As far as I understand, Slider outputs only logs for debugging use as details 
> of executing containers, and etc.
> Can we believe Slider doesn't have any logs for auditing of Slider itself? 
> (i.e. when & who used Slider for what application, etc.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Hop (incubating) 0.50-rc2

[Julian Hyde]

Forwarding my vote from the dev@hop thread: +1 (binding).

IPMC members, please note that 0.50 will be Hop’s first release in incubation. 
As such, there are issues with the release that would not be allowed in an 
official Apache release, namely:
* EPL-licensed source files (category B);
* some binary files whose license has not been fully checked;
* quite a few files are excluded from RAT checking.

Hop plans to fix these issues in a later incubating release. I hope that 
exceptions to release policy can be made for these and similar issues in this 
early-stage incubating release.

Julian (IPMC member & Hop mentor)



> On Jan 1, 2021, at 7:39 AM, Hans Van Akelyen  
> wrote:
> 
> Hi IPMC,
> 
> This is a call for vote to release Apache Hop (Incubating) 0.50-rc2.
> This will be our first Apache incubator release and want to thank everyone
> involved in the process.
> 
> Hop community vote and result threads:
> Vote:
> https://lists.apache.org/thread.html/r410e0f080772f33ea711197fa03cbf1f96902535636e69ce472efb43%40%3Cdev.hop.apache.org%3E
> 
> Result:
> https://lists.apache.org/thread.html/r5863968d1942ea5953f81ba107c4bcea993690c3d4d803ddc02d3b84%40%3Cdev.hop.apache.org%3E
> 
> The tag to be voted on is 0.50-rc2 (commit 204da03):
> https://github.com/apache/incubator-hop/commit/204da036e545441d36617906263c5a679ce6fbbc
> 
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/hop/apache-hop-0.50-incubating-rc2/
> 
> The SHA512 Checksum for these artifacts is:
> 128ca209f767aa150bdd4a222f7bda15afc01a34533cef4a204322733a99f7496ed1eb66f86a48a13a2723bae195fdf651b5d7608a70a39a1fc7313a8c48f5df
> apache-hop-0.50-incubating-rc2.tar.gz
> 
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x9a8a628dd4f4aa1e
> 
> For more information about the contents of this release, see:
> https://issues.apache.org/jira/projects/HOP/versions/12349247
> 
> Please vote on releasing this package as Apache Hop 0.50!
> 
> The vote will be open for at least 72 hours or until
> a majority of at least 3 +1 IPMC votes are cast.
> 
> [ ] +1 Release this package as Apache Hop 0.50
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
> 
> Best Regards,
> Hans


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Hop proposal

[Julian Hyde]

tter
  debugging)

* https://github.com/mattcasters/kettle-beam (Apache Beam
  support)

* https://github.com/mattcasters/pentaho-pdi-dataset (Unit
  Testing)

* https://github.com/mattcasters/kettle-needful-things (Bug
  fixes & workarounds)

* https://github.com/mattcasters/kettle-environment
  (Environment management)

The Hop repositories are currently hosted at:

* https://github.com/project-hop/

with the following repositories:

* Hop: source code for the Hop project
* Hop-doc: technical documentation for the Hop project
* Hop-website: Hop website and content repository
* Hop-docker: Docker containers, Kubernetes

## Source and Intellectual Property Submission Plan

The originating source code is already licensed under an
Apache 2 license:

* https://github.com/pentaho/pentaho-kettle/blob/8.2.0.7-R/LICENSE.txt
* https://github.com/HiromuHota/pentaho-kettle/blob/webspoon-8.3/LICENSE.txt
* https://github.com/mattcasters/kettle-debug-plugin/blob/master/LICENSE
* https://github.com/mattcasters/kettle-beam/blob/master/LICENSE
* https://github.com/mattcasters/pentaho-pdi-dataset/blob/master/LICENSE.txt
* https://github.com/mattcasters/kettle-needful-things/blob/master/LICENSE
* https://github.com/mattcasters/kettle-environment/blob/master/LICENSE

For all contributions we have an agreement in place:
https://cla-assistant.io/project-hop/hop

## External Dependencies

Over the course of the last year we removed non-essential
dependencies as much as possible and replaced them by
interfaces and plugin types. We did this to simplify the
architecture.

It’s important to note all external dependencies are
licensed under an Apache 2.0 or Apache-compatible
license. As we grow the Hop community we will configure our
build process to require and validate all contributions and
dependencies are licensed under the Apache 2.0 license or
are under an Apache-compatible license.

## Cryptography

## Required Resources

# Mailing lists

We currently use a mix of email and Mattermost. We will
migrate our existing mailing lists to the following:

* d...@hop.incubator.apache.org
* u...@hop.incubator.apache.org
* priv...@hop.incubator.apache.org
* comm...@hop.incubator.apache.org

# Git Repository

The Hop code is currently in git, we’d like to keep it that
way. We request a git repository for incubator-hop with
mirroring to GitHub.

# Issue Tracking

We request the creation of an Apache-hosted JIRA.

Jira ID: HOP

# Other Resources

To allow other projects to use Hop as a library we would
love to publish artifacts on a Maven server like
maven.apache.org.

## Initial Committers

* Nicholas Adment 
* Hans Van Akelyen 
* Lokke Bruyndonckx 
* Matt Casters 
* Jason Chu 
* Peter Fabricius 
* Rodrigo Haces 
* Dave Henry 
* Hiromu Hota 
* Brandon Jackson 
* Dan Keeley 
* Bart Maertens 
* Yannick Mols 
* Doug Moran 
* Gretchen Moran 
* Sergio Ramazzina 
* Maria Carina Roldan 
* David Rosenblum 
* Rafael Valenzuela 

# Affiliations

* Neo4J
** Matt Casters
** Rodrigo Haces
** David Rosenblum
* Know.bi
** Bart Maertens
** Hans Van Akelyen
** Lokke Bruyndonckx
** Yannick Mols
* eHealth Africa
** Doug & Gretchen Moran
* Schemetrica
** Dave Henry
* Beijing Auphi Data Co
** Jason Chu
* Serasoft Italy
** Sergio Ramazzina
* Hitachi Research
** Hiromu Hota

## Sponsors

Champion

* Maximilian Michels (m...@apache.org)

Nominated Mentors

* Tom Barber (magicaltr...@apache.org)
* Julian Hyde (jh...@apache.org)
* Maximilian Michels (m...@apache.org)
* Francois Papon (fpa...@apache.org)
* Kevin Ratnasekera (djkevi...@apache.org)


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Hop proposal

[Julian Hyde]

+1

I have known several of the members of the Hop community (Matt, Bart,
Rodrigo, Doug, Gretchen, Dave) for well over ten years; they were
contributing to Pentaho, Kettle and other projects while I was working
on Mondrian. They are good people, and they know how to build a great
product by first building a great community.

I volunteered to become a mentor of this project because I am excited
to see what they can achieve as part of Apache.

Julian

On Wed, Sep 16, 2020 at 6:29 AM Matt Casters
 wrote:
>
> Hi Apache,
>
> I'd like to call a vote on accepting Hop into the Apache Incubator.
> Please see the discussion thread [1].
>
> Please see the full proposal: 
> https://cwiki.apache.org/confluence/display/INCUBATOR/HopProposal
> Please cast your vote
>
> [ ] +1 Accept Hop into the Incubator
> [ ] +0 Indifferent to the acceptance of Hop
> [ ] -1 Do not accept Hop because …
>
> The vote will be open at least for 72 hours.
>
> Incubator PMC member votes are binding. Everyone else is welcomed to vote too
> (mark them as non-binding if you can)!
>
> Thanks in advance for your time.
>
> Regards,
> Matt
>
> [1] 
> http://apache-incubator-general.996316.n3.nabble.com/DISCUSS-Hop-proposal-td68232.html
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Giving our PMs and contributors triage rights on GitHub

[Julian Hyde]

By PM, I presume that you mean either Product Manager or Program Manager. I’ve 
worked at a few companies that practiced “commercial open source”, and there is 
inherent tension in the relationship with the “business” people.

The key questions are whether a PM can participate in the community (which 
means being active on the dev list), make contributions of value to the project 
(‘earn merit’), and can put aside their professional affiliation and act solely 
in the interests of the project. This is precisely what we require committers 
to do.

So, by this logic, a PM would earn committership in a few short months. But I 
guess you’re running into a chicken-and-egg problem: if the only contributions 
a PM can make are triaging bugs, then how can they earn enough merit to be made 
a contributor? One solution is for them to contribute in other ways, for 
example writing documentation and testing.

There is also a concern whether they can "act solely in the interests of the 
project”. Most of the PMs I know can do this, but a few cannot. Maybe it’s part 
of the ethics of “fiduciary responsibility” taught at business school; many PMs 
see themselves as potential officers of their company someday, and act 
accordingly.

Also beware establishing this model in a project where a majority of committers 
are employed by one company. The business people at such a company, even if 
they are entirely invisible on the dev list, have huge influence over the 
project by what development efforts they choose to fund, and how much time they 
give committers to review patches from outside the organization.

Julian



> On Aug 13, 2020, at 9:27 AM, Maxime Beauchemin  
> wrote:
> 
> xposting from d...@superset.apache.org - what's the right place to post this
> for ASF-infra's attention?
> 
> ---
> 
> Hi all,
> 
> It just came to my attention that GitHub added a new "triage" access level
> at the repo level.
> https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
> 
> In the past, we've identified that it was impossible for non-committers
> (especially our PMs and contributors-that-are-not-yet-committers) to help
> us triage issues, apply labels, assign reviews, close and reopen issues as
> needed. It's really clear to me that we really need all the help we can get
> in this area, and that not being able to involve more people into this
> process hurts us, and is a clear operational downside of using the ASF
> infra.
> 
> More technically, I think the way to make that easy and painless would be
> to add a new entry to the `.asf.yaml` file that would enable maintainers to
> assign the "triage" role to whoever they see fit. For reference, here's
> more context on that piece of automation I'd like to latch this onto here:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
> 
> Max


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: "Fork Me" on GitHub (was Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP)

[Julian Hyde]

Ah, thanks Justin. Sorry I didn't notice the board action and the
recommendation from trademarks.

I don't think there's much left to discuss. The board and trademarks
have made their policy clear. We (the incubator) should make podlings
aware of the policy.

I think "fork me on GitHub" is less contentious than it was 5 years
ago, so whatever was decided then will suffice for now.

Julian

On Sat, Mar 28, 2020 at 3:38 PM Justin Mclean  wrote:
>
> Hi,
>
> > I read the board@ thread and, unless I missed it, there was no edict from 
> > the board to not say “fork me on GitHub”.
>
> Did you note the board action and discussion in the board reports? Sally made 
> some alternative mock up to use (2015-01-21) I’m not sure what happened to 
> those. There was suggestion of a blog item on it, but I couldn’t find it.
>
>  Also this discussion one trademarks [1] (also private).
>
> Thanks
> Justin
>
> 1.https://lists.apache.org/thread.html/r1c39d11c1d84dbe84670bbd124b5fb627794d62cad9413e026e39a0a%40%3Ctrademarks.apache.org%3E
>
>
> -
> 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: "Fork Me" on GitHub (was Re: [DISCUSS] Graduate Apache ShardingSphere (incubating) as a TLP)

[Julian Hyde]

I read the board@ thread and, unless I missed it, there was no edict from the 
board to not say “fork me on GitHub”. 

Therefore it’s down to projects’ discretion how they promote themselves. 
(Consistent with branding policy etc.)

Unless and until the board speaks  I don’t think we need to tell projects (or 
polling) what to do. 

Julian

> On Mar 28, 2020, at 10:45 AM, Harbs  wrote:
> 
> I was wondering what the best place for this discussion would be. I couldn’t 
> really think of a better place than incubator.
> 
> I considered starting the discussion on board@ or members@, but I didn’t want 
> another private discussion. Not sure about infra and I don’t know how many 
> folks follow that list. It doesn’t seem like an infra question.
> 
> Maybe a branding discussion? Maybe comdev?
> 
> I figured incubator is as good a place as any, and the discussion was 
> triggered from here. Dunno.
> 
> If anyone has a strong preference to move it somewhere else, that’s fine with 
> me.
> 
> Thanks,
> Harbs
> 
>> On Mar 28, 2020, at 3:56 AM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>>> I also wonder if opinions might have changed in the 5 years since that 
>>> discussion. In that time, GitHub has only become more ubiquitous and more 
>>> adopted by many Apache projects.
>> 
>> Probably more a discussion for the board or Infra (as they own ASF 
>> distribution policy) than the incubator if you want to get policy changed or 
>> clarified.
>> 
>> 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: Tiered Storage Proposal

[Julian Hyde]

Neha,

Did you perhaps intend to send this to d...@pinot.apache.org?

This list covers all projects incubating at Apache, not just Pinot.

Julian

On Tue, Mar 17, 2020 at 10:32 AM Neha Pawar  wrote:
>
> Hi,
>
> Please review the proposal below for Tiered Storage in Pinot:
> https://docs.google.com/document/d/1Z4FLg3ezHpqvc6zhy0jR6Wi2OL8wLO_lRC6aLkskFgs/edit?usp=sharing
>
>
>
> Thanks,
> *Neha Pawar*
>
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release 0.5.2-incubating, release candidate #1

[Julian Hyde]

Good luck with the vote on your dev@ list. When you're ready for a
vote on general@ it will be helpful if you add 'hudi' to the subject,
something like this:

  [VOTE] Release apache-hudi-0.5.2-incubating, release candidate #1

We on general@ see many release vote threads...

Julian

On Thu, Mar 12, 2020 at 6:04 PM vino yang  wrote:
>
> Hi Vinoth,
>
> Yes, you are right. It's my mistake. Have sent a new vote thread.
>
> Best,
> Vino
>
> Vinoth Chandar  于2020年3月13日周五 上午1:13写道：
>
> > Hi Vino,
> >
> > We can include general@incubator once we have the vote on our podling's
> > own
> > dev list.  To avoid people responding to this thread and taking up inbox
> > space,
> >
> > I suggest we abandon this thread and open a new VOTE thread on the dev@hudi
> > mailing list alone.
> >
> > Please open a new thread on hudi's ML
> >
> > Thanks
> > Vinoth
> >
> >
> >
> >
> > On Thu, Mar 12, 2020 at 5:52 AM vino yang  wrote:
> >
> > > Hi everyone,
> > >
> > >
> > > We have prepared the third apache release candidate for Apache Hudi
> > > (incubating). The version is: 0.5.2-incubating-rc1. Please review and
> > vote
> > > on the release candidate #1 for the version 0.5.2, as follows:
> > >
> > > [ ] +1, Approve the release
> > >
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > >
> > > The complete staging area is available for your review, which includes:
> > >
> > > * JIRA release notes [1],
> > >
> > > * the official Apache source release and binary convenience releases to
> > be
> > > deployed to dist.apache.org [2], which are signed with the key with
> > > fingerprint C3A96EC77149571AE89F82764C86684D047DE03C [3],
> > >
> > >
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > >
> > > * source code tag "release-0.5.2-incubating-rc1" [5],
> > >
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > >
> > > Thanks,
> > >
> > > Vino
> > >
> > >
> > >
> > > [1]
> > >
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12322822=12346606
> > >
> > > [2]
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/hudi/hudi-0.5.2-incubating-rc1/
> > >
> > > [3] https://dist.apache.org/repos/dist/release/incubator/hudi/KEYS
> > >
> > > [4]
> > https://repository.apache.org/content/repositories/orgapachehudi-1018/
> > >
> > > [5]
> > >
> > https://github.com/apache/incubator-hudi/tree/release-0.5.2-incubating-rc1
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] March report signoff due Tuesday March 10

[Julian Hyde]

Ah, I had the right link but I think cwiki was temporarily down.

Justin, Many thanks for creating the redirect page. It will be very
helpful. I also created https://s.apache.org/incubator-report (as a
shortcut to your redirect page) if folks would prefer to add that to
their bookmarks.

Julian

On Fri, Mar 6, 2020 at 7:59 PM Justin Mclean  wrote:
>
> Hi,
>
> I’ve also just set up:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Report
>
> As a redirect, this will be updated monthly but that way you only need to 
> know one URL.
>
> 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: [MENTORS] March report signoff due Tuesday March 10

[Julian Hyde]

Is this the link i should be using? (It changes every month, so I never get 
around to bookmarking the link.)

https://cwiki.apache.org/confluence/display/incubator/March2020 



> On Mar 5, 2020, at 6:35 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> The ShardingSphere report is incomplete and need fixing ASAP.
> 
> Missing signoff currently are:
> Crail
> DolphinScheduler
> Marvin-AI
> PageSpeed
> Spot
> 
> Great to see full sign off for:
> BRPC
> 
> Thanks,
> Justin
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Apache Crail 1.2-incubating (rc2)

[Julian Hyde]

Changing my vote to +1. Be sure to fix the copyright date next time.

I noticed another "2018" in the source code -
https://github.com/apache/incubator-crail/blob/master/doc/source/conf.py#L38
- so change that too.

Julian

On Tue, Dec 10, 2019 at 4:31 AM Justin Mclean  wrote:
>
> Hi,
>
> > -1 (binding) due to copyright year.
>
> I not looked at the release yet but I would say this sort of issue is fix in 
> the next release for an incubating project. Did you use the work in progress 
> disclaimer?
>
> > * It is helpful to include basic build instructions in the distribution. I 
> > guessed to use JDK 8 and ‘mvn -DskipTests install’ and apparently I guessed 
> > right.
>
> Instructions on how to compile in the readme are helpful, please don’t make 
> people try to guess how to build your software. Making it easy for people to 
> review and votes on releases helps as well.
>
> 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: [VOTE] Apache Crail 1.2-incubating (rc2)

[Julian Hyde]

Checked signatures, LICENSE, NOTICE, DISCLAIMER; downloaded and compiled on 
Ubuntu/Linux 5.3.0/JDK 8, ran RAT.

-1 (binding) due to copyright year.

Problems:
 * In NOTICE, copyright is 2017-2018, should be 2019

Remarks:
 * In the vote email, it is better to use 
http://lists.apache.org/list.html?d...@crail.apache.org 
 than 
https://www.mail-archive.com/dev@crail.apache.org/ 
; Apache controls the 
latter, and can ensure that the link works in perpetuity.
* It is helpful to include basic build instructions in the distribution. I 
guessed to use JDK 8 and ‘mvn -DskipTests install’ and apparently I guessed 
right.

Julian


> On Dec 9, 2019, at 2:20 PM, Adrian Schuepbach  
> wrote:
> 
> Please vote to approve the source release of Apache Crail 1.2-incubating
> (rc2).
> 
> The podling dev vote thread:
> 
> https://www.mail-archive.com/dev@crail.apache.org/msg00745.html
> 
> The result:
> 
> https://www.mail-archive.com/dev@crail.apache.org/msg00751.html
> 
> Commit hash: 5597a87e9d6eab1877f18bf5e4e5935f172f866c
> 
> https://gitbox.apache.org/repos/asf?p=incubator-crail.git;a=commit;h=5597a87e9d6eab1877f18bf5e4e5935f172f866c
> 
> Release files can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/crail/1.2-rc2/
> 
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachecrail-1010
> 
> Release artifacts are signed with the following key:
> https://www.apache.org/dist/incubator/crail/KEYS
> 
> For information about the contents of this release, see:
> https://gitbox.apache.org/repos/asf?p=incubator-crail.git;a=blob;f=HISTORY.md;h=e68ec2546e4fa353c68c7c7940a8804c6968cd23;hb=5597a87e9d6eab1877f18bf5e4e5935f172f866c
> or https://github.com/apache/incubator-crail/blob/v1.2-rc2/HISTORY.md
> 
> The vote is open for at least 72 hours and passes if a majority of at
> least 3 +1 PMC votes are cast.
> 
> [ ] +1 Release this package as Apache Crail 1.0-incubating
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> Adrian
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Julian Hyde]

+1 (binding)

Julian

On Mon, Dec 9, 2019 at 3:32 AM Gosling Von  wrote:
>
> +1, binding
>
> Best Regards,
> Von Gosling
>
> > On Dec 8, 2019, at 5:55 AM, Gian Merlino  wrote:
> >
> > Earlier this year, Druid voted to graduate to a top level project. The vote
> > passed in the Druid community and the Incubator, and a resolution was
> > submitted to the Board, but needed to be shelved at the last minute. We are
> > now ready to proceed to graduation once again, and so I would like to call
> > another vote. The Druid project has re-voted and has notified the Board of
> > these developments. We now seek consent from the Incubator community to
> > propose a graduation resolution for the Dec 18 board meeting.
> >
> > The proposed graduation resolution is nearly the same as last time; the
> > only changes are the addition of four new initial members (fokko, furkan,
> > qmm, and vogievetsky).
> >
> > For reference,
> >
> > 1) The Druid vote that was just held:
> > https://lists.apache.org/thread.html/3b1432780b8d841fffce3033cd5cc39fe1fe0f46feccb96f036dbf01%40%3Cdev.druid.apache.org%3E
> >
> > 2) Our prior Incubator graduation vote, which passed earlier this year:
> > https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
> >
> > Please take a minute to vote on whether or not Apache Druid should graduate
> > to a Top Level Project by responding with one of the following:
> >
> > [ ] +1 Apache Druid should graduate
> > [ ]  0 No opinion
> > [ ] -1 Apache Druid should not graduate because...
> >
> > The VOTE is open for a minimum of 72 hours.
> >
> > ---
> >
> > Establish Apache Druid 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 analytical database
> > software, for distribution at no charge to the public.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "The Apache Druid Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that The Apache Druid Project be and hereby is
> > responsible for the creation and maintenance of an analytical
> > database software project; and be it further
> >
> > RESOLVED, that the office of "Vice President, Druid" 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
> > Druid Project, and to have primary responsibility for
> > management of the projects within the scope of responsibility of
> > The Apache Druid 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 Druid Project:
> >
> >  * Benedict Jin (asdf2...@apache.org)
> >  * Charles Allen(cral...@apache.org)
> >  * Clint Wylie  (cwy...@apache.org)
> >  * David Lim(david...@apache.org)
> >  * Dylan Wylie  (dylanwy...@apache.org)
> >  * Eric Tschetter   (ched...@apache.org)
> >  * Fangjin Yang (f...@apache.org)
> >  * Fokko Driesprong (fo...@apache.org)
> >  * Furkan Kamaci(kam...@apache.org)
> >  * Gian Merlino (g...@apache.org)
> >  * Himanshu Gupta   (himans...@apache.org)
> >  * Jihoon Son   (jihoon...@apache.org)
> >  * Jonathan Wei (jon...@apache.org)
> >  * Julian Hyde  (jh...@apache.org)
> >  * Kurt Young   (k...@apache.org)
> >  * Lijin Bin(binli...@apache.org)
> >  * Maxime Beauchemin(maximebeauche...@apache.org)
> >  * Mingming Qiu (q...@apache.org)
> >  * Niketh Sabbineni (nik...@apache.org)
> >  * Nishant Bangarwa (nish...@apache.org)
> >  * P. Taylor Goetz  (ptgo...@apache.org)
> >  * Parag Jain   (pja...@apache.org)
> >  * Roman Leventov   (leven...@apache.org)
> >  * Slim Bouguerra   (bs...@apache.org)
> >  * Surekha Saharan  (sure...@apache.org)
> >  * Xavier Léauté(x...@apache.org)
> >  * Vadim Ogievetsky (vogievet...@apache.org)
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> > be and hereby is appointed to the office of Vice P

Re: [VOTE] Release Apache Druid (incubating) 0.16.1 [RC2]

[Julian Hyde]

+1 (binding)

Download, check signatures, NOTICE, LICENSE, DISCLAIMER; compile on macOS.

> On Dec 9, 2019, at 10:56 AM, Gian Merlino  wrote:
> 
> +1 (binding)
> 
> - Proper NOTICE, LICENSE, DISCLAIMER files are present in both src and bin
> packages.
> - Verified .asc signatures and .sha512 checksums of both src and bin
> packages.
> - Source tarball git.version file is present and correct.
> - Source tarball builds and tests pass.
> - Ran through quickstart on binary tarball.
> 
> On Fri, Dec 6, 2019 at 9:28 PM Jonathan Wei  wrote:
> 
>> Hi IPMC,
>> 
>> The Apache Druid community has voted on and approved a proposal to release
>> Apache Druid (incubating) 0.16.1 (rc2).
>> 
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> Apache Druid (incubating) is a high performance analytics data store for
>> event-driven data.
>> 
>> The community voting thread can be found here:
>> 
>> https://lists.apache.org/thread.html/6f26ee33e429e652950b579fdc75368b323fdda1f39fc4140fdaadd0%40%3Cdev.druid.apache.org%3E
>> 
>> The concerns over licensing/distribution of the tutorial example data noted
>> in
>> the previous release have been resolved following the guidance from
>> https://issues.apache.org/jira/browse/LEGAL-480.
>> 
>> The release notes are available here:
>> https://github.com/apache/incubator-druid/issues/8972
>> 
>> The release candidate has been tagged in GitHub as
>> druid-0.16.1-incubating-rc2 (144bd782964cac3d3d31f21b9e03b3c215f7f42d),
>> available here:
>> 
>> https://github.com/apache/incubator-druid/releases/tag/druid-0.16.1-incubating-rc2
>> 
>> The artifacts to be voted on are located here:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/druid/0.16.1-incubating-rc2/
>> 
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachedruid-1010/
>> 
>> A Docker image containing the binary of the release candidate can be
>> retrieved via:
>> docker pull apache/incubator-druid:0.16.1-incubating-rc2
>> 
>> artifact checksums
>> src:
>> 
>> 5644217e475885782bca18928cdfcbc75f3e95ace55ea11238f4350ea25b39a7febbca3e58d7de7d5145633a1e549f9022596ec65486b963c1978537c9a138dc
>> bin:
>> 
>> f637453dfbdec4b22384e9bf8ebe93ccf17898e8f0ebc45312ca71aa7e3722dc79f558e6792fd67619d3c3abc21948e08e2fd8fe63d4c108a01330961fca
>> docker: 169ca79ea8f8623c08cef32d0570260b96c5c68fbb839e308afa41a75e2cec60
>> 
>> Release artifacts are signed with the key (1AC4483E):
>> https://people.apache.org/keys/committer/jonwei.asc
>> 
>> This key and the key of other committers can be found in the project's KEYS
>> file here:
>> https://www.apache.org/dist/incubator/druid/KEYS
>> 
>> Staged druid.apache.org website documentation is available here:
>> https://druid.staged.apache.org/docs/0.16.1-incubating/design/index.html
>> 
>> As part of the validation process, the release artifacts can be generated
>> from source by running:
>> mvn clean install -Papache-release,dist
>> 
>> The RAT license check can be run from source by:
>> mvn apache-rat:check -Prat
>> 
>> This vote will be open for at least 72 hours. The vote will pass if a
>> majority of at least three +1 IPMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Druid (incubating) 0.16.1
>> [ ]  0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because...
>> 
>> Thank you IPMC! We appreciate your efforts in helping the Apache Druid
>> community to validate this release.
>> 
>> On behalf of the Apache Druid Community,
>> Jon
>> 
>> Apache Druid (incubating) is an effort undergoing incubation at The Apache
>> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
>> required of all newly accepted projects until a further review indicates
>> that the infrastructure, communications, and decision making process have
>> stabilized in a manner consistent with other successful ASF projects. While
>> incubation status is not necessarily a reflection of the completeness or
>> stability of the code, it does indicate that the project has yet to be
>> fully endorsed by the ASF.
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.16.0 [RC3]

[Julian Hyde]

Forwarding my vote from the dev list: +1 (binding).

> On Sep 23, 2019, at 4:24 PM, Gian Merlino  wrote:
> 
> +1 (binding)
> 
> - NOTICE, LICENSE, DISCLAIMER files are present in both src and bin
> packages.
> - NOTICE / LICENSE look right to me. (The current versions represent a few
> rounds of iteration based on feedback.)
> - Verified .asc signatures and .sha512 checksums of both src and bin
> packages.
> - Source tarball git.version file is present and correct.
> - Source tarball builds and tests pass.
> - Ran through quickstart on binary tarball.
> 
> Clint, thanks for raising https://issues.apache.org/jira/browse/LEGAL-480.
> It doesn't look like a release blocker to me, since the discussion on that
> ticket is potentially going in a direction of deciding that the sample data
> file in question is able to be included. We will probably end up needing to
> add a note in LICENSE or NOTICE. Or if it turns out that the file ends up
> not being able to be included after all, we'll need to swap in a different
> sample data file in a future release.
> 
> On Wed, Sep 18, 2019 at 6:10 PM Clint Wylie  wrote:
> 
>> Hi IPMC,
>> 
>> The Apache Druid community has voted on and approved a proposal to release
>> Apache Druid (incubating) 0.16.0 (rc3).
>> 
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> Apache Druid (incubating) is a high performance analytics data store for
>> event-driven data.
>> 
>> The community voting thread can be found here:
>> 
>> https://lists.apache.org/thread.html/ea2f70b0533f403215288ae35294adc59f9ab33accabd9048eeb082f@%3Cdev.druid.apache.org%3E
>> 
>> We have already received 2 +1 votes from IPMC members (Julian Hyde and
>> Furkan KAMACI) during our community vote which I believe can be carried
>> over to this vote as +1 (binding).
>> 
>> During our previous IPMC release vote, a concern was raised about
>> licensing/distribution of a file containing example data, and we have
>> raised https://issues.apache.org/jira/browse/LEGAL-480 to get to the
>> bottom
>> of this. The discussion is currently ongoing there, but at this point it
>> seems possible that including this file might end up being acceptable, so I
>> have decided to proceed with this vote now. If it turns out that we cannot
>> distribute this file then we intend to switch to a different example data
>> file in a future release.
>> 
>> The release notes are available here:
>> https://github.com/apache/incubator-druid/issues/8369
>> 
>> The release candidate has been tagged in GitHub as
>> druid-0.16.0-incubating-rc3 (54d29e438a4df34d75e2385af6cefd1092c4ebb3),
>> available here:
>> 
>> https://github.com/apache/incubator-druid/releases/tag/druid-0.16.0-incubating-rc3
>> 
>> The artifacts to be voted on are located here:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/druid/0.16.0-incubating-rc3/
>> 
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachedruid-1009/
>> 
>> A Docker image containing the binary of the release candidate can be
>> retrieved via:
>> docker pull apache/incubator-druid:0.16.0-incubating-rc3
>> 
>> artifact checksums
>> src:
>> 
>> 1f25c55e83069cf7071a97c1e0d56732437dbac4ef373ed1ed72b5b618021b74c107269642226e80081354c8da2e92dc26f1541b01072a4720fd6cfe8dc161a8
>> bin:
>> 
>> 0c4b71f077e28d2f4d3bc3f072543374570b98ec6a1918a5e1828e1da7e3871b5efb04070a8bcdbc172a817e43254640ce28a99757984be7d8dd3d607f1d870e
>> docker: df9b900d3726ce123a5c054768da1ea08eba6efe635ced5abc3ad72d6c835e2c
>> 
>> Release artifacts are signed with the key (6190EEFC):
>> https://people.apache.org/keys/committer/cwylie.asc
>> 
>> This key and the key of other committers can be found in the project's KEYS
>> file here:
>> https://www.apache.org/dist/incubator/druid/KEYS
>> 
>> Staged druid.apache.org website documentation is available here:
>> https://druid.staged.apache.org/docs/0.16.0-incubating/design/index.html
>> 
>> As part of the validation process, the release artifacts can be generated
>> from source by running:
>> mvn clean install -Papache-release,dist
>> 
>> The RAT license check can be run from source by:
>> mvn apache-rat:check -Prat
>> 
>> This vote will be open for at least 72 hours. The vote will pass if a
>> majority of at least three +1 IPMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Druid (incubating) 0.16.0
>> [ ]  0 I don't feel

Re: [DISCUSS] Graduate Apache Rya (incubating) as a TLP

[Julian Hyde]

I’ve been monitoring Rya for a few years now. The project seems to have a 
steady level of activity from diverse contributors, operating according to the 
Apache Way. +1 to graduate, good luck!

Julian


> On Sep 3, 2019, at 6:27 PM, Adina Crainiceanu  wrote:
> 
> Hi,
> 
> 5 of the proposed PMC members are from Parsons, all others have different
> affiliations (different from Parsons and different from each other).
> Thanks,
> Adina
> 
> On Tue, Sep 3, 2019 at 6:50 PM Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>> Just out of interest what is the diversity (in terms of company
>> affiliation) of the proposed PMC like?
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> -- 
> Dr. Adina Crainiceanu
> Associate Professor
> Computer Science Department
> United States Naval Academy
> 410-293-6822
> ad...@usna.edu
> http://www.usna.edu/Users/cs/adina/


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Mentor guidance document

[Julian Hyde]

+1 This guidance document is worth pursuing. There is plenty of criticism of 
mentors on this list, it helps to have some guidelines. Thanks Justin.

> On Aug 20, 2019, at 9:41 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Sone thoughts inline.
> 
>> Documentation does not solve the problem.
> 
> I agree it doesn’t solve the whole problem. But it may give time poor mentors 
> more time to do other things if they can easily reference collective 
> knowledge on these issues.
> 
>> If someone doesn't already "get" this stuff then they should not be 
>> mentoring.
> 
> We have had on occasion people who are mentoring who may not get this stuff 
> but were passionate supports of their projects, should we exclude them? Some 
> of this is down to inexperience, and mentoring is one of the good ways to  
> improve this knowledge and become a better mentor. Even if you have gone 
> though incubation and mentored a project before you may of not come across 
> the same situation and it’s not always obvious how to apply the values, 
> especially in case where there’s conflict between those values (or ASF 
> policies).
> 
>> Having a document does not replace for selecting good mentors who have the 
>> time to do the job right.
> 
> 1-2 years (or more in some cases) a long commitment and life sometime  
> changes things, replacement mentors can’t in all cases be found, so even if 
> the initial condition is true, it may not be a year into teh project.
> 
> I had thought of making up a mentor capability / score card to help podlings 
> elect mentors if they don’t already have one. But haven't suggested it 
> previously as it would probably be unpopular and could be used unproductively.
> 
>> It's a good effort in the broader context, but doesn't solve the problem I 
>> see in the IPMC (insufficient high quality mentoring coupled with too much 
>> application of rules in the process). 
> 
> Is that because you think don’t we have enough high quality mentors? Or the 
> ones we do have are spread a little too thin? Or that we have these people 
> but they are not mentoring projects?
> 
>> How would I solve the problem? If I were championing another project into 
>> the ASF I would carefully select mentors, just as I have in the past.
> 
> Being here along time and your previous / current positions would make it 
> easy for to be able to get the best mentors we have that are a good fit for 
> the project. I’m not sure that all new incubating projects are able to do 
> that.
> 
>> I don't mean to say the effort you are putting in is wasted effort. Clarity 
>> in what is expected can help the podlings, 
> 
> Do any other mentors want to contribute to this or think it’s an idea worth 
> perusing? If not I’ll drop it and focus on something else.
> 
>> I don't see how this can really help those people I would already trust to 
>> be good mentors i.e. People who have a vested interest in the success of the 
>> project and already know how to apply the Apache Way to new communities so 
>> that they might flourish in their own way.
> 
> I not sure we actually have enough mentors with those abilities and knowledge 
> for all of the 50 odd podlings we have or a pool of idle mentors than new 
> projects can select from.
> 
> 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: [IP CLEARANCE] Apache Beam ZetaSQL Translator

[Julian Hyde]

Do you mean https://github.com/apache/beam/pull/9210 
 ? 6561 is the Dataflow Runner. 

> On Aug 13, 2019, at 2:07 PM, Kenneth Knowles  wrote:
> 
> Apache Beam has received a code donation of a ZetaSQL Translator
> 
> The IP clearance document is at
> http://incubator.apache.org/ip-clearance/beam-zetasql-translator.html
> 
> The pull request is https://github.com/apache/beam/pull/6561/
> 
> Please review in the next 72 hours, then IP clearance will proceed by lazy
> consensus.
> 
> Thanks!
> 
> Kenn

Re: [DISCUSS] Drop requirement that ASF members can join IPMC by just asking

[Julian Hyde]

I agree with a lot of Dave Fisher's points.

Some mentors will fail. Let's not waste effort trying to 'vet' them
beforehand; it's time-consuming and counter-productive. Let's instead
make it easier to detect when mentors fail (I think the "Have your
mentors been helpful?" question on podling reports helps with that,
but we need to do more), and let's try to increase the supply of
potential good mentors. That way, we'll end up with good mentors, and
we'll bring active new members into the Foundation.

Julian

On Tue, Aug 13, 2019 at 10:40 AM Hao Chen  wrote:
>
> I founded some apache project and graduated to TLP, and also keep
> contributing to some other apache projects but almost in code, wonder to
> know how to volunteer as IPMC to help some incubator projects graduate in
> Apache way.
>
> Hao Chen
>
> On Tue, Aug 13, 2019 at 7:43 AM Dave Fisher  wrote:
>
> >
> >
> > Sent from my iPhone
> >
> > > On Aug 13, 2019, at 2:39 AM, Justin Mclean 
> > wrote:
> > >
> > > HI,
> > >
> > > I think there's a couple of misconceptions in this thread. First off
> > currently you can join the IPMC two ways by being an ASF member and asking
> > to join, the other by being voted in. On average the people being voted in
> > tend to not go missing, review releases and sign off board reports more
> > frequently.
> > >
> > > This has come up on list the list before and some (ex)board members have
> > suggested that the IPMC shouldn’t;t allow people to be added this way.
> > >
> > > The suggestion here isn’t to be exclusionary, in fact we now allow
> > people who have experience in incubator to ask if they can join, as it
> > often hard for the IPMC to recognise merit, but they still need to be voted
> > in. [1] When a project graduates I go though the PMC list and see if there
> > are any likely IPMC candidates and contact them to see if they are
> > interested, you’ll notice that more people have been voted in in recent
> > times. In another thread I’ve gone one step further and suggested that
> > mentors look out for people on their projects list who are release managers
> > and vote on releases and suggest they be voted in as IPMC members. [2]
> > (Option D). I agree the bar should be low.
> > >
> > > I do find it strange that we would allow people from a privileged group
> > to auto join, when they possibly may not have shown merit and/or have not
> > being involved in the incubator or an incubating project before. Obviously
> > this doesn’t apply to all ASF members that ask join the incubator, but I
> > can point to examples where this has given rise to serious issues. We’ve
> > even had the occasional mentor who has never sent an email to their
> > podlings list, never voted on a release and never signed off a board report.
> >
> > This is a different problem. I’ve seen nonmember mentors who were voted in
> > who never really do anything. Let’s face it life intrudes in one way or
> > another. One hopes that such mentors will resign, but they usually fade
> > away.
> >
> > Let’s focus on service to podlings and try to replace mentors who for
> > whatever reason cannot help.
> >
> > Following through with your proposal creates an IPMC that is not fully
> > trusting the Membership. The membership of The ASF is the Foundation. These
> > people have attained merit.
> >
> > >
> > > I don’t mind if their's not consensus on this and letting this stay.
> > There may be better ways to make sure mentors who sign up do their job and
> > make mentors are more engaged. Please post your suggestions to this list
> > for discussion.
> >
> > I reject the use of the verb “make” for this problem. We should “help”
> > mentors and podling communities “be” more engaged. We should “help”
> > podlings and mentors when Incubation is not working.
> >
> > Mentoring is voluntary. So is Membership.
> >
> > We need to have strong Champions who know how to bring willing and able
> > podlings and mentors into the Incubator.
> >
> > Regards,
> > Dave
> >
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1.
> > https://lists.apache.org/thread.html/9ee3860bc9066ba682484542d34976ab21d9b62106f26a96f19d997f@%3Cgeneral.incubator.apache.org%3E
> > > 2.
> > https://lists.apache.org/thread.html/8c6e12bb040856dddb5d9b7b4821739e441455f3c61c6e469eb98f81@%3Cgeneral.incubator.apache.org%3E
> > > -
> > > 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: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Julian Hyde]

+1

Good luck! It has been great mentoring you guys.

On Tue, Aug 13, 2019 at 10:40 AM Andrei Savu  wrote:
>
> +1 (binding)
>
> Congrats! Great to see such an active community.
>
> -- Andrei Savu
>
> On Tue, Aug 13, 2019 at 12:03 AM Gian Merlino  wrote:
>
> > The Apache Druid community has recently discussed our readiness for
> > graduation [1] and voted on it affirmatively [2, 3]. We've also assessed
> > ourselves against the maturity model [4] and collaborated on a resolution
> > for graduation including PMC membership and PMC chair.
> >
> > The community's achievements since entering the Incubator in early 2018
> > include the following:
> >
> > - Accepted 1240 patches from 142 contributors
> > - Performed 5 releases with 4 different release managers
> > - Invited 10 new committers
> > - Some time later on, invited all 10 of those new committers to join the
> > PMC (those that have accepted are named in the resolution below)
> > - Migrated development to Apache's GitHub org:
> > https://github.com/apache/incubator-druid
> > - Migrated our web site to https://druid.apache.org/
> > - Migrated developer conversations to the list at d...@druid.apache.org
> >
> > Now the Druid community is bringing the attached resolution up for a formal
> > IPMC VOTE.
> >
> > Please take a minute to vote on whether or not Apache Druid should graduate
> > to a Top Level Project by responding with one of the following:
> >
> > [ ] +1 Apache Druid should graduate
> > [ ]  0 No opinion
> > [ ] -1 Apache Druid should not graduate because...
> >
> > The VOTE is open for a minimum of 72 hours.
> >
> > [1]
> >
> > https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E
> > [2]
> >
> > https://lists.apache.org/thread.html/10c615a7648db14a268759be91f4b1eff448960f5338e0d416c7373a@%3Cdev.druid.apache.org%3E
> > [3]
> >
> > https://lists.apache.org/thread.html/7517dd38fbeb28978b1188bed1d69e91445927d13d520a4c71ae9fcf@%3Cdev.druid.apache.org%3E
> > [4] https://gist.github.com/gianm/33ae4d61ebaa8b8714d9e2f51a11e7f7
> >
> > --
> >
> > Establish Apache Druid 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 analytical database
> > software, for distribution at no charge to the public.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee (PMC), to be known as the "The Apache Druid Project",
> > be and hereby is established pursuant to Bylaws of the
> > Foundation; and be it further
> >
> > RESOLVED, that The Apache Druid Project be and hereby is
> > responsible for the creation and maintenance of an analytical
> > database software project; and be it further
> >
> > RESOLVED, that the office of "Vice President, Druid" 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
> > Druid Project, and to have primary responsibility for
> > management of the projects within the scope of responsibility of
> > The Apache Druid 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 Druid Project:
> >
> >   * Benedict Jin (asdf2...@apache.org)
> >   * Charles Allen    (cral...@apache.org)
> >   * Clint Wylie  (cwy...@apache.org)
> >   * David Lim(david...@apache.org)
> >   * Dylan Wylie  (dylanwy...@apache.org)
> >   * Eric Tschetter   (ched...@apache.org)
> >   * Fangjin Yang (f...@apache.org)
> >   * Gian Merlino (g...@apache.org)
> >   * Himanshu Gupta   (himans...@apache.org)
> >   * Jihoon Son   (jihoon...@apache.org)
> >   * Jonathan Wei (jon...@apache.org)
> >   * Julian Hyde  (jh...@apache.org)
> >   * Kurt Young   (k...@apache.org)
> >   * Lijin Bin(binli...@apache.org)
> >   * Maxime Beauchemin(maximebeauche...@apache.org)
> >   * Niketh Sabbineni (nik...@apache.org)
> >   * Nishant Bangarwa (nish...@apache.org)
> >   * P. Taylor Goetz  (ptgo...@apache.org)
> >   * Parag Jain   (pja...@apache.org)
> >   * Roman Leventov

Re: [DISCUSS] Drop requirement that ASF members can join IPMC by just asking

[Julian Hyde]

Thanks, Gian. I bet you’re familiar with DataSketches (as it has 
ancestry/people in common with Druid) and I recall that recently they needed 
more mentors.


> On Aug 12, 2019, at 2:06 PM, Gian Merlino  wrote:
> 
> One more voice here: I'm not an ASF member, but I'd be interested in
> mentoring other podlings after Druid graduates. Julian has been very
> helpful to us while we've been incubating and I'd like to pay it forward.
> 
> On Mon, Aug 12, 2019 at 11:12 AM Julian Hyde  wrote:
> 
>> I don’t have a strong opinion on the subject of this thread - whether it
>> should be easy for ASF members to join the IPMC - but I have a strong
>> opinion about a related matter - namely, how easy it should be for non-ASF
>> members to join the IPMC.
>> 
>> The IPMC should be actively recruiting members of recently-graduated
>> projects to serve as mentors of the next generation of podlings.
>> 
>> I bet quite a few people people think that you have to be an ASF member to
>> be on the IPMC or mentor a project. And we certainly give the impression
>> that ASF members make the best mentors. But I claim that people who have
>> just been through the incubation process also make excellent mentors. They
>> have experienced the pain, and they know the answers to many of the IT- and
>> process-related questions because they have just solved them.
>> 
>> Like Sheng, I joined the IPMC before I was a member. The project I
>> founded, Calcite, was close to graduating and I was active on general@
>> because being a podling is hard and raises many questions. Some other
>> podlings were entering incubation and someone (I think Ted Dunning or Alan
>> Gates) asked me to be a mentor. From that, I was drawn into other Apache
>> projects, saw the broader Apache community, and was drawn into the worthy
>> task of helping to govern the Foundation. For me, serving as a mentor was a
>> way of saying ’thank you’ for the help I had received from mentors during
>> incubation. And for the IPMC, it provided an active and engaged mentor,
>> always a scarce resource.
>> 
>> Julian
>> 
>> 
>>> On Aug 8, 2019, at 10:29 PM, Sheng Wu  wrote:
>>> 
>>> Hi
>>> 
>>> My Apache journey started at Incubator, and as IPMC now(not asf member).
>> I
>>> noticed this requirement too.
>>> 
>>> From the members I known personally, most indeed know Apache way very
>> well.
>>> And truely there is exception.
>>> 
>>> Basically, I think removing this makes sense.
>>> 
>>> 1. if this member has been incubator journey, such as being initial
>>> committer of a podling, it is easy to know and should have taken part in
>>> incubator ml much.
>>> 
>>> 2. there are indeed asf members elected by other reasons, so, they are
>> not
>>> familiar w/ incubator, and need more time to learn too. Apache has so
>> many
>>> TLPs and ways to take part in, a member is not required used to be
>>> incubator.
>>> 
>>> My +1 on IPMC should have enough incubator experiences.
>>> 
>>> Also, very open to know the history reason of this.
>>> 
>>> Sheng
>>> 
>>> Justin Mclean 于2019年8月9日 周五下午1:04写道：
>>> 
>>>> Hi,
>>>> 
>>>> Current any ASF member can come along and ask to join the IPMC. I assume
>>>> this was put in place for two reasons: ( but don’t know the full history
>>>> behind it)
>>>> - There was a lack of mentors.
>>>> - Is is assumed that if you are an ASF member you know enough about the
>>>> Apache Way to mentor a project.
>>>> 
>>>> I’m not sure if this is the case anymore. And while the mentor situation
>>>> has improved I don’t think the above has solved the problem of having
>>>> active members or mentors having the required knowledge and skills they
>>>> need.
>>>> 
>>>> So if you want to be a IPMC member and mentor a project then I think you
>>>> need you have gone through the full incubation process yourself and/or
>> help
>>>> out with other incubator duties and get voted in as an IPMC member. Just
>>>> like every other ASF project.
>>>> 
>>>> What do other people think?
>>>> 
>>>> Thanks,
>>>> Justin
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> 
>>>> --
>>> Sheng Wu
>>> SkyWalking, Shardingsphere and Zipkin
>> 
>> 
>> -
>> 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] Release Apache Druid (incubating) 0.15.1 [RC2]

[Julian Hyde]

+1 (binding)

Checked hashes; in -src.tar.gz, checked license, notice, disclaimer, readme; 
compiled from source (skipping tests) on Ubuntu/JDK 8; ran RAT; checked that 
src tarball contents match git commit c698daa.

Did not examine -bin.tar.gz.

Julian


> On Aug 9, 2019, at 5:28 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +1 (binding)
> 
> I checked:
> - incubating in name
> - signatures and hashes fine
> - LICENSE is fine
> - NOTICE may need a little work
> - No unexpected binary files
> - Source files have ASF headers
> - Can compile from source
> 
> NOTICE mentions using code From Apache Hive, Apache Lucerne, Apache Hadoop 
> and Apache Calcite. Only Calcite is mentioned in your NOTICE file and all of 
> those projects have NOTICE files, Jets3t contains a NOTICE file [3] so I 
> think more needs to go in your NOTICE file.
> 
> I am sort of curious how this is licensed [1] and if that should go in 
> LICENSE? (which I don’t think is an issue) and if you had permission from the 
> people to use and distribute the content in [2]
> 
> Thanks,
> Justin
> 
> 1. core/src/test/resources/loremipsum.txt
> 2. 
> apache-druid-0.15.1-incubating-src/examples/quickstart/tutorial/wikiticker-2015-09-12-sampled.json.gz
> 3. https://bitbucket.org/jmurty/jets3t/src/default/NOTICE.txt
> -
> 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] Drop requirement that ASF members can join IPMC by just asking

[Julian Hyde]

I don’t have a strong opinion on the subject of this thread - whether it should 
be easy for ASF members to join the IPMC - but I have a strong opinion about a 
related matter - namely, how easy it should be for non-ASF members to join the 
IPMC.

The IPMC should be actively recruiting members of recently-graduated projects 
to serve as mentors of the next generation of podlings.

I bet quite a few people people think that you have to be an ASF member to be 
on the IPMC or mentor a project. And we certainly give the impression that ASF 
members make the best mentors. But I claim that people who have just been 
through the incubation process also make excellent mentors. They have 
experienced the pain, and they know the answers to many of the IT- and 
process-related questions because they have just solved them.

Like Sheng, I joined the IPMC before I was a member. The project I founded, 
Calcite, was close to graduating and I was active on general@ because being a 
podling is hard and raises many questions. Some other podlings were entering 
incubation and someone (I think Ted Dunning or Alan Gates) asked me to be a 
mentor. From that, I was drawn into other Apache projects, saw the broader 
Apache community, and was drawn into the worthy task of helping to govern the 
Foundation. For me, serving as a mentor was a way of saying ’thank you’ for the 
help I had received from mentors during incubation. And for the IPMC, it 
provided an active and engaged mentor, always a scarce resource.

Julian
 

> On Aug 8, 2019, at 10:29 PM, Sheng Wu  wrote:
> 
> Hi
> 
> My Apache journey started at Incubator, and as IPMC now(not asf member). I
> noticed this requirement too.
> 
> From the members I known personally, most indeed know Apache way very well.
> And truely there is exception.
> 
> Basically, I think removing this makes sense.
> 
> 1. if this member has been incubator journey, such as being initial
> committer of a podling, it is easy to know and should have taken part in
> incubator ml much.
> 
> 2. there are indeed asf members elected by other reasons, so, they are not
> familiar w/ incubator, and need more time to learn too. Apache has so many
> TLPs and ways to take part in, a member is not required used to be
> incubator.
> 
> My +1 on IPMC should have enough incubator experiences.
> 
> Also, very open to know the history reason of this.
> 
> Sheng
> 
> Justin Mclean 于2019年8月9日 周五下午1:04写道：
> 
>> Hi,
>> 
>> Current any ASF member can come along and ask to join the IPMC. I assume
>> this was put in place for two reasons: ( but don’t know the full history
>> behind it)
>> - There was a lack of mentors.
>> - Is is assumed that if you are an ASF member you know enough about the
>> Apache Way to mentor a project.
>> 
>> I’m not sure if this is the case anymore. And while the mentor situation
>> has improved I don’t think the above has solved the problem of having
>> active members or mentors having the required knowledge and skills they
>> need.
>> 
>> So if you want to be a IPMC member and mentor a project then I think you
>> need you have gone through the full incubation process yourself and/or help
>> out with other incubator duties and get voted in as an IPMC member. Just
>> like every other ASF project.
>> 
>> What do other people think?
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> --
> Sheng Wu
> SkyWalking, Shardingsphere and Zipkin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache Druid (incubating) as a TLP

[Julian Hyde]

I am a mentor of Druid. I think that Druid is more than ready to graduate. They 
have been operating according to the Apache Way for a long time, and they have 
a vibrant community.

Good luck!

Julian


> On Jul 15, 2019, at 3:42 PM, Gian Merlino  wrote:
> 
> Hi all,
> 
> Since Apache Druid (incubating) entered the incubator in early 2018, the
> community has grown more diverse, moved to ASF infrastructure, and adopted
> the Apache Way. The community's achievements include the following:
> 
> - Performed 5 releases with 4 different release managers
> - Invited 10 new committers
> - Some time later on, invited all 10 of those new committers to join the
> PMC (those that have accepted are named in the draft resolution)
> - Migrated development to Apache's GitHub org:
> https://github.com/apache/incubator-druid
> - Migrated our web site to https://druid.apache.org/
> - Migrated developer conversations to the list at d...@druid.apache.org
> 
> As a community we have discussed our readiness for graduation [1] and voted
> on it affirmatively [2, 3]. We've also assessed ourselves against the
> maturity model [4] and collaborated on a resolution for graduation
> including PMC membership and PMC chair.
> 
> Please refer to the draft resolution below and provide any comments or
> feedabck you have, as well as any general comments or feedback about our
> community and our endeavors.
> 
> This discussion will remain open for at least 72 hours.
> 
> [1]
> https://lists.apache.org/thread.html/68fcc3d2fc66c7f559e2c9dd02478d17f195565fecdb07ed53bc965e@%3Cdev.druid.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/10c615a7648db14a268759be91f4b1eff448960f5338e0d416c7373a@%3Cdev.druid.apache.org%3E
> [3]
> https://lists.apache.org/thread.html/7517dd38fbeb28978b1188bed1d69e91445927d13d520a4c71ae9fcf@%3Cdev.druid.apache.org%3E
> [4] https://gist.github.com/gianm/33ae4d61ebaa8b8714d9e2f51a11e7f7
> 
> --
> 
> Establish Apache Druid 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 analytical database
> software, for distribution at no charge to the public.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "The Apache Druid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that The Apache Druid Project be and hereby is
> responsible for the creation and maintenance of an analytical
> database software project; and be it further
> 
> RESOLVED, that the office of "Vice President, Druid" 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
> Druid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of
> The Apache Druid 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 Druid Project:
> 
>  * Benedict Jin (asdf2...@apache.org)
>  * Charles Allen(cral...@apache.org)
>  * Clint Wylie  (cwy...@apache.org)
>  * David Lim(david...@apache.org)
>  * Dylan Wylie  (dylanwy...@apache.org)
>  * Eric Tschetter   (ched...@apache.org)
>  * Fangjin Yang (f...@apache.org)
>  * Gian Merlino (g...@apache.org)
>  * Himanshu Gupta   (himans...@apache.org)
>  * Jihoon Son   (jihoon...@apache.org)
>  * Jonathan Wei (jon...@apache.org)
>  * Julian Hyde  (jh...@apache.org)
>  * Kurt Young   (k...@apache.org)
>  * Lijin Bin(binli...@apache.org)
>  * Maxime Beauchemin(maximebeauche...@apache.org)
>  * Niketh Sabbineni (nik...@apache.org)
>  * Nishant Bangarwa (nish...@apache.org)
>  * P. Taylor Goetz  (ptgo...@apache.org)
>  * Parag Jain   (pja...@apache.org)
>  * Roman Leventov   (leven...@apache.org)
>  * Slim Bouguerra   (bs...@apache.org)
>  * Surekha Saharan  (sure...@apache.org)
>  * Xavier Léauté(x...@apache.org)
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> be and hereby is appointed to the office of Vice President,
> Druid, 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 

Re: Podling expectations and some issues encountered in incubation

[Julian Hyde]

Thanks for making this list, Justin.

Next time I mentor a project, I shall probably convert the list into a 
presentation (with a few “and here’s the good news” slides at the beginning and 
end) and schedule a video meeting with a few of the initial committers, leaving 
plenty of time for questions.

I encourage other mentors to do the same. After all, many of our issues with 
podlings are communication issues.  

Julian

> On Jun 29, 2019, at 10:24 PM, Sheng Wu  wrote:
> 
> You are better about polishing English words than me
> The point is only, I received many feedback about the long release
> procedure is unexpected.
> 
> Justin Mclean 于2019年6月30日 周日下午1:13写道：
> 
>> Hi,
>> 
>>> In You will need to change the way you build and distribute software
 For instance, you now need to vote on releases over a 72 whole cycle,
>> and also have the IPMC vote on your releases.
>> 
>> Thanks for the suggestion, I’ll update that,. BTW I wasn’t trying to make
>> it comprehensive or repeat information put elsewhere as that can also cause
>> problems. I think adding link to where some of that information is would
>> also help.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> --
> Sheng Wu
> SkyWalking, Shardingsphere and Zipkin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.15.0 [RC2]

[Julian Hyde]

Forwarding my vote from the dev list:

+1 (binding)

I am grateful for Sebb’s thorough review but I don’t see anything that blocks 
the release (e.g. the commit hash is stated in the email even though not given 
as a link; the extra text in NOTICE files is a “should” not a “must”). The 
project should log bugs for all the points he raised and make sure to fix them 
before the next release. I strongly suggest that the project establishes a 
template email for release votes.

Also, let’s recognize that the expanded NOTICE files are the result of a 
concerted effort by the project since the previous release to include L of 
all dependencies. It’s hard to get this stuff right first, or even second, time.

Julian


> On Jun 25, 2019, at 9:22 AM, Jihoon Son  wrote:
> 
> Hi Sebb,
> 
> those 2 PRs have been merged into master now. Thanks again for your help.
> 
> BTW, I'm wondering what your vote is.
> Would you mind clarifying it?
> 
> Jihoon
> 
> On Sat, Jun 22, 2019 at 7:20 AM ซ่อยค่อย ลืมเขาแน่ <0989132858...@gmail.com>
> wrote:
> 
>> ในวันที่ ส. 22 มิ.ย. 2019 04:21 Gian Merlino  เขียนว่า:
>> 
 I'll leave that to others to decide, but if I were release manager, I
 would fix them before release.
>>> 
>>> Thanks for taking the time to inspect our release!
>>> 
>>> I'm not the release manager here, but my thoughts are that for issues
>> such
>>> as this, it makes sense to fix them for the next release rather than the
>>> current one. The reason is just that the cycle time is quite long for
>>> cutting RCs (72 hour vote on the project list + 72 hour vote on the
>>> Incubator list, the latter of which often takes longer than 72 hours due
>> to
>>> IPMC folks being a busy bunch).
>>> 
>>> On Fri, Jun 21, 2019 at 3:02 AM sebb  wrote:
>>> 
 On Fri, 21 Jun 2019 at 02:12, Jihoon Son  wrote:
> 
> Thank you for your detailed review!
> 
> We will address your comments on signing keys in the future votes.
> 
> Regarding the commit id, "44c9323" is the correct commit id for the
>>> tag.
> Maybe the link is not valid.
> Is https://github.com/apache/incubator-druid/commits/44c9323 or
> 
 
>>> 
>> https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2
 more
> valid one?
 
 The first one is immutable but not obvious, the second is not
 guaranteed immutable.
 
 However you could use:
 
 
>>> 
>> https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2
 (44c9323
 <
>>> 
>> https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2(44c9323
 
 )
 
> Finally, would you elaborate more on what looks wrong to you in
>> NOTICE
 and
> NOTICE.BINARY files?
 
 NOTICE files should contain only what is strictly required for the
 files actually contained in the bundle to which they apply.
 See:
 [1]
 
>>> 
>> http://www.apache.org/dev/licensing-howto.html#assembling-license-and-notice
 
 The header looks OK, but most of the rest looks unnecessary.
 
 No need to mention Apache Licensed code unless the bit you have copied
 has a required notice in its NOTICE file.
 
 In the case of the other products, they may or may not require entries
 in NOTICE.
 That depends on their license.
 As per [1], generally BSD and MIT code does not require an entry in
>>> NOTICE.
 
 The last section (JetS3t) does not make sense.
 
 Similar considerations apply to NOTICE.BINARY
 In the case of commons-codec-1.7.jar, does the binary bundle actually
 include the file
 DoubleMetaphoneTest ? It seems unlikely -- if not present, the entry
 is not required.
 
 The LICENSE file likewise is generally OK (assuming it corresponds
 with the software that is in the source bundle). It's good that the
 software versions are mentioned. However the license pointer is
 missing for the Porter Stemmer. It can be guessed from the previous
 entry, so that is not a blocker.
 
> We will fix them if necessary for this release.
 
 I'll leave that to others to decide, but if I were release manager, I
 would fix them before release.
 
> Jihoon
> 
> On Thu, Jun 20, 2019 at 9:46 AM sebb  wrote:
> 
>> On Thu, 20 Jun 2019 at 03:39, Jihoon Son 
>>> wrote:
>>> 
>>> Hi IPMC,
>>> 
>>> The Apache Druid community has voted on and approved a proposal
>> to
>> release
>>> Apache Druid (incubating) 0.15.0 (rc2).
>>> 
>>> We now kindly request the Incubator PMC members review and vote
>> on
 this
>>> incubator release.
>>> 
>>> Apache Druid (incubating) is a high performance analytics data
>>> store
 for
>>> event-driven data.
>>> 
>>> The community voting thread can be found here:
>>> 
>> 
 
>>> 
>> 

Re: [IMPORTANT] Board proposal on podling releases

[Julian Hyde]

We’re trying to nail down the definition of “serious”.  May I suggest that we 
divide the guidelines into MAY, SHOULD and MUST. Anything with MUST is 
mandatory for all podling releases. 

The list may or may not be the same as for TLP releases. 

Julian



Sent from my iPad
> On Jun 7, 2019, at 5:56 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> 1) Is it legal to include GPL licensed software in releases?  The
>> answer is yes... as long as we comply with the terms of that license.
>> In the case of strong copyleft licenses, that could mean that the
>> podling release itself may need also be GPL licensed.
> 
> And in cases where this has happened, it’s been ALv2 licensed, so I guess 
> that wouldn’t be legal. But we also allow minor stuff like this a lot of the 
> time e.g forgetting to add  MIT license text to LICENSE. 
> 
>> 2) Is it legal to include compiled code in releases?  Yes.
> 
> But certainly against ASF policy and one of it core values.
> 
>> 3) Is it legal to include copyright violations in releases?  No.
> 
> In most cases, where this has occurred this has been minor, like including a 
> cat photo, and can be easily sorted by removing or asking for permission. If 
> someone did come along as say you don’t have permission to do that, we’d say 
> we were very sorry and fix it. 
> 
> Perhaps rewording the proposal to say "serious issue typically found in 
> podling releases” would help? Podlings generally make some effort to try and 
> get things right.
> 
> Thanks,
> Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.14.2 [RC1]

[Julian Hyde]

I saw that vote, and I disagree with his opinion; in my opinion, a high-quality 
project releases fixes whenever there is a serious bug; if serious bugs occur 
too frequently, the thing to fix is not the release cadence.

This project is overdue to graduate; that, not the release cadence, is why 
mentors are a bit burned out.

Julian


> On May 21, 2019, at 6:05 PM, Dave Fisher  wrote:
> 
> I noticed a 0 vote by a PPMC member saying the cadence is too frequent for a 
> database product and thinking it may impact perceived stability.
> 
> Just a data point.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On May 21, 2019, at 5:36 PM, Julian Hyde  wrote:
>> 
>> No.
>> 
>> In my defense, Druid has produced quite a few RCs recently and I’ve found it 
>> difficult to keep up. The other mentors have been quiet for a couple of 
>> months.
>> 
>> Julian
>> 
>> 
>>> On May 21, 2019, at 4:50 PM, Justin Mclean  wrote:
>>> 
>>> Hi,
>>> 
>>> Did any mentor or other rIPMC member vote on this release on your dev list?
>>> 
>>> 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
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.14.2 [RC1]

[Julian Hyde]

No.

In my defense, Druid has produced quite a few RCs recently and I’ve found it 
difficult to keep up. The other mentors have been quiet for a couple of months.

Julian


> On May 21, 2019, at 4:50 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> Did any mentor or other rIPMC member vote on this release on your dev list?
> 
> 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: [VOTE] Release Apache Druid (incubating) 0.14.2 [RC1]

[Julian Hyde]

+1

Downloaded, checked LICENSE, NOTICE, DISCLAIMER, compiled on Linux/JDK 8, ran 
RAT.

Checked that contents of src tarball correspond to git 1053684f38.

Did not look at bin tarball.

LICENSE and NOTICE files have grown significantly since the previous release. I 
would appreciate if Justin or another L expert looked them over. 

Julian


> On May 21, 2019, at 11:43 AM, Clint Wylie  wrote:
> 
> Hello IPMC,
> 
> I wanted to bump the Apache Druid (incubating) 0.14.2 release vote to try
> to get some traction. This release has some important bug fixes that we
> would like to get to our users, and we still need 3 IPMC +1 votes, so we
> would greatly appreciate if you could help us out.
> 
> Cheers,
> Clint
> 
> On Wed, May 15, 2019 at 6:55 PM Clint Wylie  wrote:
> 
>> Hi IPMC,
>> 
>> The Apache Druid community has voted on and approved a proposal to release
>> Apache Druid (incubating) 0.14.2 (rc1).
>> 
>> We now kindly request the Incubator PMC members review and vote on this
>> incubator release.
>> 
>> Apache Druid (incubating) is a high performance analytics data store for
>> event-driven data.
>> 
>> The community voting thread can be found here:
>> https://lists.apache.org/thread.html/2a72c3029206ef66abd7a8d99333c9906fa1067eb73b8a3a2d81b934@%3Cdev.druid.apache.org%3E
>> 
>> The release notes are available here:
>> https://github.com/apache/incubator-druid/issues/7628
>> 
>> The release candidate has been tagged in GitHub as
>> druid-0.14.2-incubating-rc1 (1053684), available here:
>> 
>> https://github.com/apache/incubator-druid/releases/tag/druid-0.14.2-incubating-rc1
>> 
>> The artifacts to be voted on are located here:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/druid/0.14.2-incubating-rc1/
>> 
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachedruid-1005/
>> 
>> Release artifacts are signed with the key:
>> https://people.apache.org/keys/committer/cwylie.asc
>> 
>> This key and the key of other committers can also be found in the
>> project's KEYS file here:
>> https://dist.apache.org/repos/dist/release/incubator/druid/KEYS
>> 
>> To compile and test, run:
>> mvn clean install
>> 
>> As part of the validation process, the release artifacts can be generated
>> from source by running:
>> mvn clean install -Papache-release,dist
>> 
>> The RAT license check can be run from source by:
>> mvn apache-rat:check -Prat
>> 
>> This vote will be open for at least 72 hours. The vote will pass if a
>> majority of at least three +1 IPMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Druid (incubating) 0.14.2
>> [ ]  0 I don't feel strongly about it, but I'm okay with the release
>> [ ] -1 Do not release this package because...
>> 
>> Thank you IPMC! We appreciate your efforts in helping the Apache Druid
>> community to validate this release.
>> 
>> Cheers,
>> Clint
>> 
>> Apache Druid (incubating) is an effort undergoing incubation at The Apache
>> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
>> required of all newly accepted projects until a further review indicates
>> that the infrastructure, communications, and decision making process have
>> stabilized in a manner consistent with other successful ASF projects. While
>> incubation status is not necessarily a reflection of the completeness or
>> stability of the code, it does indicate that the project has yet to be
>> fully endorsed by the ASF.
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.14.1 [RC1]

[Julian Hyde]

+1 (binding)

Downloaded; checked sigs and hashes, LICENSE, NOTICE and DISCLAIMER;
compiled under JDK 8 on Linux; checked that release contains the same
code as the corresponding git commit; ran RAT.

Caveats:
* I did not inspect the -bin.tar.gz file.
* I got some test failures:
org.apache.druid.storage.s3.TestAWSCredentialsProvider.testWithFileSessionCredentials(org.apache.druid.storage.s3.TestAWSCredentialsProvider)
  Run 1: TestAWSCredentialsProvider.testWithFileSessionCredentials:98
» SdkClient Unabl...

Julian

On Wed, May 1, 2019 at 3:20 PM Clint Wylie  wrote:
>
> Hi IPMC,
>
> The Apache Druid community has voted on and approved a proposal to release
> Apache Druid (incubating) 0.14.1 (rc1).
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Project description: Apache Druid (incubating) is a high performance
> analytics data store for event-driven data.
>
> The community voting thread can be found here:
> https://lists.apache.org/thread.html/8f341dffae962d34d514379862b7388d43fe9988f3f502762190af13@%3Cdev.druid.apache.org%3E
>
> The release notes are available here:
> https://github.com/apache/incubator-druid/issues/7553
>
> The release candidate has been tagged in GitHub as
> druid-0.14.1-incubating-rc1 (e8a8816), available here:
> https://github.com/apache/incubator-druid/releases/tag/druid-0.14.1-incubating-rc1
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/druid/0.14.1-incubating-rc1/
>
> A staged Maven repository is available for review at:
> https://repository.apache.org/content/repositories/orgapachedruid-1004/
>
> Release artifacts are signed with the key:
> https://people.apache.org/keys/committer/cwylie.asc
>
> This key and the key of other committers can also be found in the project's
> KEYS file here:
> https://dist.apache.org/repos/dist/release/incubator/druid/KEYS
>
> As part of the validation process, the release artifacts can be generated
> from source by running:
> mvn clean install -Papache-release,dist
>
> The RAT license check can be run from source by:
> mvn apache-rat:check -Prat
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Druid (incubating) 0.14.1
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thank you IPMC! We appreciate your efforts in helping the Apache Druid
> community to validate this release.
>
> Apache Druid (incubating) is an effort undergoing incubation at The Apache
> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review indicates
> that the infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects. While
> incubation status is not necessarily a reflection of the completeness or
> stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>
> Cheers,
> Clint

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC3]

[Julian Hyde]

Forwarding my vote from the PPMC vote:

+1 (binding)


> On Apr 8, 2019, at 8:25 AM, Mohammad Asif Siddiqui  
> wrote:
> 
> +1 (binding)
> 
> Checks Done :
> - incubating in name
> - signatures and hashes are good
> - LICENSE, NOTICE and DISCLAIMER exists
> - Source files have ASF header
> 
> Regards
> Asif
> 
> On Mon, Apr 8, 2019 at 8:49 PM Gian Merlino  wrote:
> 
>> Thanks Justin!
>> 
>> Would anyone else on the IPMC mind taking a look? Assuming Julian Hyde's
>> vote on dev@druid [1] counts as an IPMC vote too, I believe that means we
>> need one more for this release.
>> 
>> [1]
>> 
>> https://lists.apache.org/thread.html/c8d880ca0a4c64734304e24a57ab567162e948ef62e982ab9dc9470c@%3Cdev.druid.apache.org%3E
>> 
>> On Fri, Apr 5, 2019 at 10:50 PM Justin Mclean 
>> wrote:
>> 
>>> Hi,
>>> 
>>> +1 (binding)
>>> 
>>> I checked:
>>> - incubating in name
>>> - signatures and hashes fine
>>> - DISCLAIMER exists
>>> - LICENSE and NOTICE ok
>>> - No unexpected binary files
>>> - All source files have ASF headers
>>> - Can compile from source
>>> 
>>> 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: Podling use of StackOverflow

[Julian Hyde]

It can be frustrating when someone posts a question to both the user list and 
to StackOverflow. It means that the community has to answer the question in two 
places.

But like many problems, that is an opportunity. Answering StackOverflow 
questions is a great way for people to contribute without writing code. If you 
take the view that everyone reading or writing StackOverflow is part of the 
community — and I do — then StackOverflow is an excellent way to grow community.

Julian


 

> On Apr 4, 2019, at 10:33 AM, Ted Dunning  wrote:
> 
> Just subscribe to appropriate tags on stack overflow and direct
> notifications to the dev list.
> 
> Then encourage the community to answer on stack overflow.
> 
> 
> On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher  wrote:
> 
>> I think a user@ mailing list is better for the project’s sustainability
>> and Apache.
>> 
>> I have examples related to POI where there is substantial StackOverflow
>> support happening.
>> 
>> 12 years ago I became a POI committer for answering user questions.
>> 
>> Recently we asked an active StackOverflow answer if he was interested in
>> being a committer and StackOverflow was his community.
>> 
>> Apache records are always better than stuff at another company. Gmane and
>> markmail email links have rotted away.
>> 
>> I would encourage a user list for the visibility for the PMC in
>> understanding what’s happening along with a more coherent community!
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Apr 3, 2019, at 6:02 PM, Alan Gates  wrote:
>>> 
>>> The superset podling is working out their processes around FAQs and
>>> answering user questions.  One thing that they have suggested is that
>> they
>>> encourage people to use StackOverflow for questions and answers given the
>>> ease of searching old questions, etc.  You can see the mail thread at
>>> 
>> https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E
>>> 
>>> Personally I think encouraging podlings to use tools they and everyone
>> are
>>> comfortable with and that meet our criteria of being open to all is a
>> good
>>> thing, but I wanted to check if there was official policy on this before
>>> they proceed with it.
>>> 
>>> Alan.
>> 
>> 
>> -
>> 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] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Julian Hyde]

Per my reading http://www.apache.org/legal/release-policy.html#release-approval 
 it’s not OK 
to stop when you reach 3 +1 votes. Because it’s not 3 +1s absolute, it’s 3 more 
+1s than -1s. So, you have to have a fixed, reasonable timeframe for the vote 
to give those -1s time to accrue.

Release policy says the timeframe SHOULD be 72 hours. I can think of scenarios 
where it could be less, but you still have to give PMC members adequate notice.

When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not intending 
to rewrite foundation policy.

Also note in that same section:

>  Before casting +1 binding votes, individuals are REQUIRED to download
> all signed source code packages onto their own hardware, verify that they
> meet all requirements of ASF policy on releases as described below,
> validate all cryptographic signatures, compile as provided, and test the
> result on their own platform.

This clearly establishes the minimum required of mentors voting for a podling 
release.

Lastly, I absolutely agree with the question in the subject line. Yes, Mentors 
SHOULD vote on podling releases prior to asking IPMC to vote.

As mentors are busy, and are not 100% focused on the podling, the podling 
should give them a little nudge and a little leeway. Case in point: Druid 0.14 
started a vote at 4.08pm on Friday. It is now 3.08pm on Monday, i.e. we’re at 
71 hours. I voted but the other 2 mentors (whom I would describe as “engaged”) 
have not yet. I just emailed them to ask them to vote. If they do not vote in 
the next hour, the release manager should keep the vote open for a while to 
give them chance to vote.

Julian



> On Apr 1, 2019, at 2:59 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> 72 hours is a guide. As long as your project community is agreeable you can 
>> say "72hrs or 3 +1”.
> 
> 72 hours is a guide, but recommended, as it gives a chance for all PPMC 
> members to have a look at the release. They may be in different timezone or 
> have day jobs or other things going on, we are all volunteers here and not 
> all of us work full time on a project. If that 72 hours was constantly 
> reduced it would exclude certain groups of people looking at the release and 
> I don’t think we want to do that. For instance I don’t think it would be OK 
> if those 3 +1’s came in an hour of announcing the release candidate.
> 
> Thanks,
> Justin

Re: List of Projects that went straight to Top Level Projects

[Julian Hyde]

> On Apr 1, 2019, at 11:19 AM, Greg Stein  wrote:
> 
> I would disagree with your latter statement; they went to TLP based
> on oversight, rather than on userbase/impact.

I didn’t mean to suggest that we treated them differently because they had a 
large user base.

By “important” I meant “worthy of discussion in this thread”.

Julian


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org