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

[Gian Merlino]

Thanks everyone for voting! It has been over 72 hours, so I will post a
result thread shortly.

On Tue, Dec 10, 2019 at 7:54 AM Makoto Yui  wrote:

> +1 (binding)
>
> Makoto
>
> 2019年12月10日(火) 6:39 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 M

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

[Gian Merlino]

The vote to recommend Apache Druid graduation to the board has passed with
10 +1 votes:

Bertrand Delacretaz
Dave Fisher
Furkan Kamaci
Julian Hyde
Junping Du
Justin Mclean
Makoto Yui
Paul King
Tianqi Chen
Von Gosling

No 0 or -1 votes.

The voting thread:
https://lists.apache.org/thread.html/431031af20682ce03c9181a9aedd5e458952019a87dcf85b1d233081%40%3Cgeneral.incubator.apache.org%3E

Thank you all for your participation in the vote. We'll submit the
resolution to the board.

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

[Gian Merlino]

+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.
>

Re: [DISCUSS] Recommend 'Apache Druid graduation to Top Level Project' resolution

[Gian Merlino]

Hi Justin,

When Druid originally discussed graduation earlier this year, it was
suggested and agreed on to make all interested committers members of the
initial PMC:
https://lists.apache.org/thread.html/b668ff2967dc1cb2a8e57663e24ae606ee102ffe7ef03d2323084ebc%40%3Cdev.druid.apache.org%3E.
This time around I applied that decision when drafting an updated
resolution. The four new people are three committers added since then, and
one person who originally said he was interested a bit too late to be
included in the last resolution. I mentioned this when calling a vote for
the new resolution:
https://lists.apache.org/thread.html/2385d5545fa5bd13baf45bd7258fafa7694334d9d14267489d21d99b%40%3Cdev.druid.apache.org%3E
.

On Sat, Dec 7, 2019 at 2:26 PM Justin Mclean 
wrote:

> Hi,
>
> Just out of interest why where these people added? I can’t see a
> discussion on-list about adding them, do you mind pointing me to it?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[Gian Merlino]

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 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 the initial Apache Druid Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Druid podling; and be it further

RESOLVED, that all responsibility pertaining to the Apache
Incubator Druid podling encumbered upon the Apache Incubator
PMC are hereafter discharged.

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

[Gian Merlino]

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

Re: [VOTE] Release Apache DataSketches-cpp (incubating) 1.0.0 [RC2]

[Gian Merlino]

+1 (binding)

- Tarball name is correct (project, version, "incubating").
- NOTICE, LICENSE, DISCLAIMER-WIP files are present.
- I didn't notice any LICENSE / NOTICE issues beyond what's already been
discussed in the thread.
- Verified .asc signatures and .sha512 checksums.
- git.properties is present and correct.
- Tarball contents match the expected git tag.
- Was able to build from source and run tests on macOS 10.14.6.

One file is missing a copyright header:

1) ./hll/include/hll.private.hpp

On Mon, Sep 9, 2019 at 12:05 PM Alexander Saydakov <
sayda...@verizonmedia.com> wrote:

> Dear IPMC and Community,
>
> This is a call for vote to release Apache DataSketches-cpp version
> 1.0.0-incubating
>
> This is a C++ version of the DataSketches core library with Python
> bindings.
>
> This is the first release of this component.
>
> We are not going to release any artifacts besides the source code.
>
> Results from the PPMC vote:
> 3 votes were cast. All of the votes were (+1). One of the votes was from a
> mentor.
>
> http://mail-archives.apache.org/mod_mbox/datasketches-dev/201909.mbox/thread
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/datasketches/cpp/1.0.0-incubating-rc2/
>
> Source repository:
> https://github.com/apache/incubator-datasketches-cpp
>
> Git tag for this release:
>
> https://github.com/apache/incubator-datasketches-cpp/releases/tag/1.0.0-incubating-rc2
>
> The artifact has been signed with key:
> pub  4096R/A8E8B4E0 2019-08-20 Alexander Saydakov (CODE SIGNING KEY) <
> al...@apache.org>
> Fingerprint=40A2 47F6 1E8C 6C75 678C  69C5 6848 6114 A8E8 B4E0
>
> The public signing key can be found in the KEYS file:
> https://dist.apache.org/repos/dist/dev/incubator/datasketches/KEYS
>
> Changes from the RC1:
> - added license to make files
> - building and running unit tests does not require pybind11 (dependency for
> Python bindings)
> - better build instructions
>
> This library was intended to be header-only, but this goal was not fully
> achieved yet with CPC sketch code. This work is in progress.
>
> Building and running unit tests requires CppUnit.
>
> Installing CppUnit on OSX: brew install cppunit
> Installing CppUnit on RHEL: yum install cppunit-devel
>
> There are currently two ways of building: using existing make files and
> generating make files using cmake. Exsisting make files might not work on
> all platforms or with all C++ compilers. Generating make files using cmake
> should solve this problem, but it currently requires cmake version 3.12.0
> or higher that might not be readily available as a package on all
> platforms.
>
> Installing the latest cmake on OSX: brew install cmake
>
> Building and running unit tests using existing make files:
> $ make
> $ make test
>
> Building and running unit tests using cmake:
> $ mkdir build
> $ cd build
> $ cmake ..
> $ make
> $ make test
>
> Building Python bindings requires cmake 3.12 or higher and pybind11.
> Please see the following document for details:
>
> https://github.com/apache/incubator-datasketches-cpp/blob/1.0.0-incubating-rc2/python/README.md
>
> This is the second stage vote. The vote will remain open for at least 72
> hours and at least 3 (+1) IPMC votes or a majority of (+1) are acquired.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Alexander Saydakov
> al...@apache.org
>

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

[Gian Merlino]

By the way, I am going to be away from email from tomorrow til Sunday; so,
assuming the vote proceeds successfully, and in the interest of timing with
respect to the next board meeting, another Druid PPMC member will likely
tally and post the results after the 72-hr period instead of me.

Thanks for the support everyone!

On Tue, Aug 13, 2019 at 6:02 PM Sheng Wu  wrote:

> +1 Good luck
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
> William Guo  于2019年8月14日周三 上午7:38写道：
>
> > +1
> >
> > Congratulations!!!
> >
> >
> > Thanks,
> > William
> >
> > On Wed, Aug 14, 2019 at 6:22 AM Ryan Blue 
> > wrote:
> >
> > > +1
> > >
> > > Congratulations!
> > >
> > > On Tue, Aug 13, 2019 at 2:03 PM Myrle Krantz  wrote:
> > >
> > > > +1 binding  I'm looking forward to welcoming you to the fold! : o)
> > > >
> > > > Best,
> > > > Myrle
> > > >
> > > > On Tue, Aug 13, 2019 at 9:10 PM Suneel Marthi 
> > > wrote:
> > > >
> > > > > +1 binding
> > > > >
> > > > > Congrats !!
> > > > >
> > > > > On Tue, Aug 13, 2019 at 3:06 PM Julian Feinauer <
> > > > > j.feina...@pragmaticminds.de> wrote:
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > Congratulations!
> > > > > >
> > > > > > Julian
> > > > > >
> > > > > >
> > > > > >  Ursprüngliche Nachricht 
> > > > > > Betreff: Re: [VOTE] Recommend 'Apache Druid graduation to Top
> Level
> > > > > > Project' resolution to the board
> > > > > > Von: Julian Hyde
> > > > > > An: general@incubator.apache.org
> > > > > > Cc:
> > > > > >
> > > > > > +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.
> > > > > > > >
> > > > >

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

[Gian Merlino]

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   (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 the initial Apache Druid Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Druid podling; and be it further

RESOLVED, that all responsibility pertaining to the Apache
Incubator Druid podling encumbered upon the Apache Incubator
PMC are hereafter discharged.

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

[Gian Merlino]

FYI- we gave the board a heads up too and received generally positive
feedback. I will set up a vote shortly!


On Tue, Jul 23, 2019 at 8:24 PM Gian Merlino  wrote:

> Hey Justin,
>
> In summary it was clear from comments on the podling name search JIRA that
> the community wanted to work to continue using the current name if at all
> possible (mostly due to its long history, in use since 2011). And so we are
> working towards that and would continue to do so throughout & after
> becoming a TLP. I sent you an update about current status privately —
> avoiding public comment for now since I am referencing conversations that
> happened on private@druid. Maybe you can help me decide what would be
> good to post publicly. The project is aware that if for some reason this
> cannot be worked out, a name change may be required.
>
> On Tue, Jul 23, 2019 at 6:59 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> > Yes, they (we) are aware, and have been in discussion with Mark Thomas &
>> > other relevant parties since the podling name search concluded about
>> > straightening out potential issues that arose during the search.
>>
>> My understanding is that this may require a name change and that it’s a
>> possibility that the board may not accept the proposal to graduate because
>> of this? Is that correct?
>>
>>  It might be good to get an update on where you are on this as the last
>> email about this that I can find is several months old.
>>
>> Thanks,
>> Justin
>> -
>> 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

[Gian Merlino]

Yep, that is definitely a good one. I joined their mailing list a couple of
weeks ago and have been chatting with Lee on it, after he mentioned on the
Druid list that he could use some help.

(Apologies for the digression btw)

On Mon, Aug 12, 2019 at 2:10 PM Julian Hyde  wrote:

> 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 hav

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

[Gian Merlino]

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

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

[Gian Merlino]

Hey Justin,

In summary it was clear from comments on the podling name search JIRA that
the community wanted to work to continue using the current name if at all
possible (mostly due to its long history, in use since 2011). And so we are
working towards that and would continue to do so throughout & after
becoming a TLP. I sent you an update about current status privately —
avoiding public comment for now since I am referencing conversations that
happened on private@druid. Maybe you can help me decide what would be good
to post publicly. The project is aware that if for some reason this cannot
be worked out, a name change may be required.

On Tue, Jul 23, 2019 at 6:59 PM Justin Mclean 
wrote:

> Hi,
>
> > Yes, they (we) are aware, and have been in discussion with Mark Thomas &
> > other relevant parties since the podling name search concluded about
> > straightening out potential issues that arose during the search.
>
> My understanding is that this may require a name change and that it’s a
> possibility that the board may not accept the proposal to graduate because
> of this? Is that correct?
>
>  It might be good to get an update on where you are on this as the last
> email about this that I can find is several months old.
>
> Thanks,
> Justin
> -
> 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

[Gian Merlino]

Hey Justin,

Yes, they (we) are aware, and have been in discussion with Mark Thomas &
other relevant parties since the podling name search concluded about
straightening out potential issues that arose during the search. From our
conversations my understanding is that this straightening-out process does
not block graduation, but is something the Apache Druid PPMC/PMC needs to
continue to work to drive to resolution both before and after graduation.
We're certainly aware of our responsibilities in this area.

On Tue, Jul 23, 2019 at 5:12 PM Justin Mclean 
wrote:

> Hi,
>
> > The other repos under https://github.com/druid-io contain projects
> loosely
> > affiliated with Apache Druid but that are not seen as part of the core
> > project. Some of them have ongoing discussions about whether the
> community
> > wants to migrate them to Apache (as sub projects, maybe, or as part of
> > Apache Druid proper) or perhaps sunset them.
>
> Are they are aware of the branding and trademark requirements re use of
> ApacheDruid name? I also didn’t get a reply to the trademark issue which is
> related [1]
>
> Thanks,
> Justin
>
> 1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-142
>
>
> -
> 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

[Gian Merlino]

Hi all,

Just wondering if anyone has anything else to add to this discussion.
Thanks!

On Thu, Jul 18, 2019 at 9:22 AM Gian Merlino  wrote:

> Hey Justin,
>
> Thanks for your comments.
>
> The other repos under https://github.com/druid-io contain projects
> loosely affiliated with Apache Druid but that are not seen as part of the
> core project. Some of them have ongoing discussions about whether the
> community wants to migrate them to Apache (as sub projects, maybe, or as
> part of Apache Druid proper) or perhaps sunset them. I expect these
> conversations to continue after graduation.
>
> On the topic of branding, the PPMC is definitely aware of its
> responsibilities in that area. Internally we have updated our own project
> site branding, and externally we've reached out in a few cases already to
> ask for the Apache Druid name to be used correctly and to clarify the
> independent nature of the project. We hadn't reached out before about the
> two specific documents you mentioned, but I just did a few minutes ago.
>
> On the topic of committers and PPMC members, from my POV the reason for
> adding a bunch of committers at once was that once we started thinking
> about adding more, a variety of names came up at once. I think in the
> future we’ll likely invite additional people in a more typical manner.
> We’ve recently invited all active committers to join the initial PMC slate,
> and I expect we’d continue a policy of having an inclusive PMC.
>
> Your point on committer merit as it relates to noncode contributions is
> noted. It is something that we should keep an open mind on.
>
> On Wed, Jul 17, 2019 at 6:33 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> I have a couple of questions/observations:
>>
>> What the situation/status of the repositories under
>> https://github.com/druid-io?
>> A quick google search turns up some branding/trademark issues e.g. [1][2]
>> is the PPMC aware of this?
>> Have the trademark issues been resolved?
>> I note you added a number of committers but no PPMC members. Why is this?
>> Is also seems that all these people were added at the same time, which
>> seems a little unusual. I’m curious to why was it done that way.
>> A recent discussion seems to imply that only people who commit code are
>> considered for committership. You might want to reconsider that.
>>
>> Thanks,
>> Justin
>>
>> 1.
>> https://medium.com/airbnb-engineering/druid-airbnb-data-platform-601c312f2a4c
>> 2. https://www.youtube.com/watch?v=JEhmHsN8jZI
>> -
>> 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

[Gian Merlino]

Hey Justin,

Thanks for your comments.

The other repos under https://github.com/druid-io contain projects loosely
affiliated with Apache Druid but that are not seen as part of the core
project. Some of them have ongoing discussions about whether the community
wants to migrate them to Apache (as sub projects, maybe, or as part of
Apache Druid proper) or perhaps sunset them. I expect these conversations
to continue after graduation.

On the topic of branding, the PPMC is definitely aware of its
responsibilities in that area. Internally we have updated our own project
site branding, and externally we've reached out in a few cases already to
ask for the Apache Druid name to be used correctly and to clarify the
independent nature of the project. We hadn't reached out before about the
two specific documents you mentioned, but I just did a few minutes ago.

On the topic of committers and PPMC members, from my POV the reason for
adding a bunch of committers at once was that once we started thinking
about adding more, a variety of names came up at once. I think in the
future we’ll likely invite additional people in a more typical manner.
We’ve recently invited all active committers to join the initial PMC slate,
and I expect we’d continue a policy of having an inclusive PMC.

Your point on committer merit as it relates to noncode contributions is
noted. It is something that we should keep an open mind on.

On Wed, Jul 17, 2019 at 6:33 PM Justin Mclean 
wrote:

> Hi,
>
> I have a couple of questions/observations:
>
> What the situation/status of the repositories under
> https://github.com/druid-io?
> A quick google search turns up some branding/trademark issues e.g. [1][2]
> is the PPMC aware of this?
> Have the trademark issues been resolved?
> I note you added a number of committers but no PPMC members. Why is this?
> Is also seems that all these people were added at the same time, which
> seems a little unusual. I’m curious to why was it done that way.
> A recent discussion seems to imply that only people who commit code are
> considered for committership. You might want to reconsider that.
>
> Thanks,
> Justin
>
> 1.
> https://medium.com/airbnb-engineering/druid-airbnb-data-platform-601c312f2a4c
> 2. https://www.youtube.com/watch?v=JEhmHsN8jZI
> -
> 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

[Gian Merlino]

Thanks for the vote of confidence, Julian!

Has anyone else got something they would like to share in this discussion?
If not I could start a vote.


On Mon, Jul 15, 2019 at 3:52 PM Julian Hyde  wrote:

> 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

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

[Gian Merlino]

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 the initial Apache Druid Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Druid podling; and be it further

RESOLVED, that all responsibility pertaining to the Apache
Incubator Druid podling encumbered upon the Apache Incubator
PMC are hereafter discharged.

Re: New disclaimer text

[Gian Merlino]

Speaking as a member of a currently-incubating project (Apache Druid) where
we have always strived to do releases with no known licensing issues, the
text sounds needlessly scary to downstream consumers. Especially this part:

> If you are planning to incorporate this work into your
> product/project, please be aware that you will need to conduct a
> thorough licensing review to determine the overall implications of
> including this work.

IMO this disclaims too much, and would chill adoption of incubating
software by people that care about having clean licensing. PPMCs should be
able to say "we believe this release is clean and have vetted it using a
normal Apache vetting process" or maybe even "we have vetted this release
and it is clean other than the following list of known issues". If they
can't say one of those two statements, then maybe it's not time to do their
first release yet.

And yeah, as a few others have mentioned, I believe that a more streamlined
voting process would make PPMCs more likely to adopt an attitude of doing
releases as cleanly as possible. I think mentors could play a valuable part
in streamlining the process, since they have binding votes from both the
PPMC and IPMC perspective, and are in theory plugged in to both communities.

On Wed, Jul 10, 2019 at 7:44 AM Jan Piotrowski  wrote:

> What is the requirement for this disclaimer text change?
> Is this coming from Legal? Or is this Incubator policy?
> Has this been decided on already or is this text suggestion to be used
> for a decision?
>
> J
>
> Am Mi., 10. Juli 2019 um 15:50 Uhr schrieb Matt Sicker :
> >
> > Since this is sort of a post-release set of info, I think it’d make sense
> > to have either a page specific to each version, or at least a section per
> > version all on a single page (similar to a security issues page might be
> or
> > a change log in general).
> >
> > On Tue, Jul 9, 2019 at 21:24, Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > The issue with having a detached disclaimer is that it can change and
> get
> > > out of sync with what was actually in a released version.
> > >
> > > However one possible compromise would be to list known issues in the
> > > disclaimer and list any other issues found by the IPMC in the release
> > > announcements and on the release page next to the download links. The
> > > DISCLAIMER in version control can also be updated and always reflect
> the
> > > current set of released issues are. What do other people think about
> this?
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > > --
> > Matt Sicker 
>
> -
> 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]

[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
> 
> )
>
> > 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:
> > > >
> > >
> https://lists.apache.org/thread.html/f4b1b708bcb7e6ec08e6a9cfcb2c0dfcb565fab353ccbb8c5f362218@%3Cdev.druid.apache.org%3E
> > > >
> > > > The release notes are available here:
> > > > https://github.com/apache/incubator-druid/issues/7854
> > > >
> > > > The release candidate has been tagged in GitHub as
> > > > druid-0.15.0-incubating-rc2 (44c9323), available here:
> > > >
> > >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.15.0-incubating-rc2
> > >
> > > I'm not sure that's the correct URL for the tag; it points to a couple
> > > of archives.
> > >
> > > I would expect a pointer to the source code.
> > > This should use the commit id that corresponds to the release
> > > candidate tag, i.e. the commit id that corresponds to
> > >
> https://github.com/apache/incubator-druid/tree/druid-0.15.0-incubating-rc2
> > > AIUI only commit ids are truly immutable
> > >
> > > The NOTICE and NOTICE.BINARY files look wrong to me; they have a lot
> > > of superfluous text.
> > >
> > > > The artifacts to be voted on are located here:
> > > >
> > >
> https://dist.apache.org/repos/dist/dev/incubator/druid/0.15.0-incubating-rc2/
> > > >
> > > > A staged Maven repository is available for review at:
> > > >
> https://repository.apache.org/content/repositories/orgapachedruid-1007/
> > > >
> > > > Release artifacts are signed with the key [95574000]:
> > > > https://people.apache.org/keys/committer/jihoonson.asc
> > > >
> > > > This key and the key of other committers can also be found in the
> > > project's
> > > > KEYS file here:
> > > > 

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

[Gian Merlino]

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

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

[Gian Merlino]

It didn't include the disclaimer - thanks for pointing that out.

By the way, one of our mentors has already voted +1 for this
0.14.0-incubating release on dev@druid, so I think that means we are just
looking for a couple more IPMC votes.

On Wed, Apr 3, 2019 at 6:10 AM sebb  wrote:

> Top-posting:
>
> Announcements of podling release should please include the standard
> Incubation disclaimer. (AFAICT this did not happen with the previous
> Druid announce)
>
> See for example:
>
>
> https://lists.apache.org/thread.html/d94b89e6c4e83f2364607b47020ca715aaa7fae1a3b97b374b93ca7f@%3Cgeneral.incubator.apache.org%3E
>
> https://lists.apache.org/thread.html/ec3d6b90a2b0054eb2f0a2e4ba2e09a594463720e2b28e75b315c693@%3Cgeneral.incubator.apache.org%3E
>
> https://lists.apache.org/thread.html/8993ecb33e0f73e69faabba8c1f07d3a9965a178df1698c42fc9f4b2@%3Cgeneral.incubator.apache.org%3E
>
> Please bear this in mind when the vote has finished.
>
> Thanks.
>
> On Wed, 3 Apr 2019 at 00:58, Jonathan Wei  wrote:
> >
> > Hi IPMC,
> >
> > The Apache Druid community has voted on and approved a proposal to
> release
> > Apache Druid (incubating) 0.14.0 (rc3).
> >
> > 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://www.mail-archive.com/dev@druid.apache.org/msg01924.html
> >
> > The release notes are available here:
> > https://github.com/apache/incubator-druid/issues/7126
> >
> > The release candidate has been tagged in GitHub as
> > druid-0.14.0-incubating-rc3 (f169ada), available here:
> >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.14.0-incubating-rc3
> >
> > The artifacts to be voted on are located here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/druid/0.14.0-incubating-rc3/
> >
> > A staged Maven repository is available for review at:
> > https://repository.apache.org/content/repositories/orgapachedruid-1003/
> >
> > 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 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.0
> > [ ]  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 PPMC,
> > Jon
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Review mailing list membership?

[Gian Merlino]

Thanks Taylor!

Do you know if this is something that the PPMCs are supposed to have access
to or should we be asking you for help if we want to check again?

On Tue, Apr 17, 2018 at 2:44 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:

> I sent the subscriber list for dev@druid and private@druid to
> private@druid.
>
> -Taylor
>
> > On Apr 17, 2018, at 5:31 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> >
> > I can do it when I’m back at a computer. Basically you have to send the
> ezlm email from an ASF machine. The easiest way is to ssh into minotaur.a.o
> and use the mail command to send the email.
> >
> > Do you want just the subscription list for dev@ or private@ as well?
> >
> > -Taylor
> >
> >> On Apr 17, 2018, at 5:18 PM, Julian Hyde <jh...@apache.org> wrote:
> >>
> >> I’m one of your (druid codling’s) mentors and, yes, I moderate the
> druid lists. I tried a week or so ago to list the members of druid’s lists
> and struck out.
> >>
> >> In twenty minutes, I couldn’t find the solutions listed below:  whimsy
> and dev-l...@druid.apache.org <mailto:dev-l...@druid.apache.org>. (I
> looked at https://mail-archives.apache.org/mod_mbox/druid-dev/ <
> https://mail-archives.apache.org/mod_mbox/druid-dev/> for instance, and
> emailed dev-h...@druid.apache.org <mailto:dev-h...@druid.apache.org>.)
> >>
> >> So either I’m stupid or the documentation needs improvement (or both).
> >>
> >>> On Apr 17, 2018, at 11:13 AM, Gian Merlino <g...@apache.org> wrote:
> >>>
> >>> I didn't know it existed until now - thanks! I just tried it from my
> apache
> >>> email and got the response "fatal: Command allowed only to moderators
> >>> (#5.7.1)". Maybe only our mentors are set up as moderators?
> >>>
> >>>> On Tue, Apr 17, 2018 at 11:08 AM, Christopher <ctubb...@apache.org>
> wrote:
> >>>>
> >>>> Have you tried the tool at
> >>>> https://whimsy.apache.org/committers/moderationhelper.cgi ?
> >>>>
> >>>>> On Tue, Apr 17, 2018 at 2:06 PM Gian Merlino <g...@apache.org>
> wrote:
> >>>>>
> >>>>> Hi incubators,
> >>>>>
> >>>>> Is there a tool somewhere to review the membership of a mailing list?
> >>>>>
> >>>>> We (Druid) are working on migrating our mailing lists now. As I work
> out
> >>>>> the logistics of doing that I am finding that it would help to know
> how
> >>>>> many people from the old list have subscribed to the new one, as we
> have
> >>>>> been encouraging people to do for about a month. If the overlap is
> good
> >>>>> then we know we are clear to migrate without leaving too many people
> >>>>> behind. If the overlap is poor then we know we need to do more
> outreach
> >>>> to
> >>>>> get people to subscribe to the new list.
> >>>>>
> >>>>> Gian
> >>>>>
> >>>>
> >>
>
>

Re: Review mailing list membership?

[Gian Merlino]

I didn't know it existed until now - thanks! I just tried it from my apache
email and got the response "fatal: Command allowed only to moderators
(#5.7.1)". Maybe only our mentors are set up as moderators?

On Tue, Apr 17, 2018 at 11:08 AM, Christopher <ctubb...@apache.org> wrote:

> Have you tried the tool at
> https://whimsy.apache.org/committers/moderationhelper.cgi ?
>
> On Tue, Apr 17, 2018 at 2:06 PM Gian Merlino <g...@apache.org> wrote:
>
> > Hi incubators,
> >
> > Is there a tool somewhere to review the membership of a mailing list?
> >
> > We (Druid) are working on migrating our mailing lists now. As I work out
> > the logistics of doing that I am finding that it would help to know how
> > many people from the old list have subscribed to the new one, as we have
> > been encouraging people to do for about a month. If the overlap is good
> > then we know we are clear to migrate without leaving too many people
> > behind. If the overlap is poor then we know we need to do more outreach
> to
> > get people to subscribe to the new list.
> >
> > Gian
> >
>

Review mailing list membership?

[Gian Merlino]

Hi incubators,

Is there a tool somewhere to review the membership of a mailing list?

We (Druid) are working on migrating our mailing lists now. As I work out
the logistics of doing that I am finding that it would help to know how
many people from the old list have subscribed to the new one, as we have
been encouraging people to do for about a month. If the overlap is good
then we know we are clear to migrate without leaving too many people
behind. If the overlap is poor then we know we need to do more outreach to
get people to subscribe to the new list.

Gian

Re: Default webpages for new podlings

[Gian Merlino]

Is there any ASF infra that would be usable for automatically running
Jekyll on the master branch and pushing the results to the "asf-git"
branch, where they can be served? Maybe CI/build infra, if we have that? It
would provide an experience that is somewhat like GitHub pages.

On Mon, Apr 16, 2018 at 9:53 AM, Julian Hyde  wrote:

> Just to clarify, in case people are not familiar with Jekyll. It is a code
> generator that a developer runs in their sandbox, and it generates the
> site. The developer then checks in the site to git or svn.
>
> So, the developer has complete control over the HTML that is checked in.
> They can manually post-process the files produced by Jekyll, if they wish.
>
> Jekyll is not in the code path running on ASF infrastructure that serves
> the site. The ASF infra just sees HTML, CSS style sheets and images.
>
> Julian
>
>
> > On Apr 16, 2018, at 8:21 AM, Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
> >
> > On Mon, Apr 16, 2018 at 4:39 PM, Matt Sicker  wrote:
> >> ...Most places I've seen the CMS still in use was because of svnpubsub,
> not
> >> necessarily cms.a.o. We use it to commit the output from
> maven-site-plugin,
> >> javadocs, scaladocs, etc. Am I confused here?...
> >
> > AFAIK both svnpubsub and gitpubsub are fully supported by ASF infra.
> >
> > It's the content management part of the ASF CMS that's deprecated.
> >
> > -Bertrand
> >
> > -
> > 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: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

[Gian Merlino]

Hi John,

What we were thinking in Druid is that we want to have _something_ up on
http://druid.incubator.apache.org/, but it didn't seem appropriate to move
over the full site before the SGA & CLAs have all been finalized (those are
in progress). So we put up a temporary placeholder.

IMO, a placeholder is better than a redirect, since it makes it more clear
that the pre-Apache site is not Apache-vetted nor Apache-operated. A
redirect from an Apache domain to a non-Apache domain is easy for a visitor
to fail to notice.

Gian

On Sun, Apr 15, 2018 at 6:22 AM, John D. Ament <johndam...@apache.org>
wrote:

> My input is a point for pagespeed to consider.  Personally, I'm not
> comfortable with what's proposed by Druid but it's not worth muddying up
> pagespeed's inquiry.  My preference is for a podling to get their website
> moved over quickly (and we need to figure out how to help them make that
> move quickly).  What I do believe though is that our branding requirements
> would propagate over to that website as well (which it sounds like Druid
> has a bit wrong, at least in my take).
>
> - Redirecting to another website that's hosting your docs doesn't remove
> the need for proper naming, so it should be Apache Druid (incubating) or
> Apache PageSpeed (incubating) upon first entry.
> - Even if the website is hosted elsewhere, I still expect to see the
> disclaimer.
> - The downloads page should indicate these are not Apache releases.
>
> Perhaps Mark T has some more input on the branding and naming aspects.
>
> John
>
> On Sat, Apr 14, 2018 at 12:02 AM Julian Hyde <jhyde.apa...@gmail.com>
> wrote:
>
> > I (as a Druid mentor) suggested the placeholder page, for the exact
> > reasons Greg describes. Short term, I promise, and better than a 404.
> >
> > Julian
> >
> > > On Apr 13, 2018, at 20:15, Greg Stein <gst...@gmail.com> wrote:
> > >
> > > One step at a time. If they want to throw a single page up *today*
> rather
> > > than wait six weeks to fully port their website... I would take the
> page.
> > > We already had an inquiry on Druid of where their site is.
> > >
> > > A placeholder is better than a 404. Unless, of course, you are
> personally
> > > volunteering to quickly move their entire site and workflow... ?
> > >
> > > Cheers,
> > > -g
> > >
> > >
> > >> On Fri, Apr 13, 2018, 22:03 John D. Ament <johndam...@apache.org>
> > wrote:
> > >>
> > >> Gian, Otto,
> > >>
> > >> I can tell you that the proposed plan from Druid is not an OK plan
> from
> > my
> > >> perspective.  One of your short term goals should be moving
> > infrastructure
> > >> over to the ASF.  This includes moving your website over.  Redirecting
> > your
> > >> ASF webpage to your old webpage will not fly.
> > >>
> > >> While we can't give the same level of support as you would see on
> github
> > >> pages (maybe we'll get there one day), setting up builds in Jenkins or
> > >> Buildbot is pretty straight forward.  Even the incubator website runs
> in
> > >> this model.
> > >>
> > >> It's perfectly acceptable to link to pre-Apache releases on your
> > website.
> > >> I'm not sure if any of the docs lead you to believe otherwise, but
> this
> > is
> > >> a fine thing to do.  They just need to be clearly marked as not Apache
> > >> releases.
> > >>
> > >> The disclaimer that we request is meant to be shown on all pages of
> the
> > >> podling's website.  Not just the landing page.  If these are user
> facing
> > >> documents, then they must have the disclaimer on them.
> > >>
> > >> John
> > >>
> > >>> On Fri, Apr 13, 2018 at 5:42 PM Gian Merlino <g...@imply.io> wrote:
> > >>>
> > >>> Hi Otto,
> > >>>
> > >>> I am just another podling committer, so this isn't authoritative
> > advice,
> > >>> but for Druid's incubating page we are planning to put up a
> placeholder
> > >>> page with a link to the current community site. It isn't up yet, but
> > the
> > >>> html we are planning to use is here:
> > >>>
> > >>
> > https://github.com/apache/incubator-druid-website/blob/
> asf-site/index.html
> > >>>
> > >>> Our rationale was:
> > >>>
> > >>> 1) Before the site is migrated, it's better to have a placeholder
>

Re: Redirecting pagespeed.incubator.apache.org to modpagespeed.com

[Gian Merlino]

Hi Otto,

I am just another podling committer, so this isn't authoritative advice,
but for Druid's incubating page we are planning to put up a placeholder
page with a link to the current community site. It isn't up yet, but the
html we are planning to use is here:
https://github.com/apache/incubator-druid-website/blob/asf-site/index.html

Our rationale was:

1) Before the site is migrated, it's better to have a placeholder than a
404.
2) A placeholder with a link can make it more clear that the releases on
druid.io are not Apache releases.
3) A placeholder helps satisfy the requirement that podling web sites must
have an incubation disclaimer (
https://incubator.apache.org/guides/branding.html).

When we migrate the community site to Apache infra then it would replace
the placeholder.

Gian

On Fri, Apr 13, 2018 at 2:09 PM, Otto van der Schaaf 
wrote:

> Hi all,
>
> Currently pagespeed.incubator.apache.org responds with a 404, which isn't
> very nice.
>
> So now we are wondering if there are any concerns with issueing a temporary
> redirect to
> modpagespeed.com.
>
> One concern could be that modpagespeed.com links to code / releases that
> have not yet been
> through the formal Apache release process. Would explicitly mentioning that
> fact
> be sufficient to address it?
>
> I would be grateful for any input / guidance on this topic.
>
> Kind regards,
>
> Otto
>

Re: [RESULT] [VOTE] Accept Druid into the Apache Incubator

[Gian Merlino]

Hi Craig,

I have added it to the list.

Gian

On Mon, Mar 5, 2018 at 3:42 PM, Craig Russell  wrote:

> Hi,
>
> Can you please add this proposal to https://wiki.apache.org/
> incubator/ProjectProposals so it can be found easily.
>
> Thanks,
>
> Craig
>
> > On Feb 28, 2018, at 12:27 PM, Nishant Bangarwa 
> wrote:
> >
> > Great!!. Thanks to all who voted.
> >
> > On Thu, 1 Mar 2018 at 01:52 Tom Barber  wrote:
> >
> >> Woohoo!
> >>
> >> On 28/02/18 20:21, Julian Hyde wrote:
> >>> More than 72 hours have passed. The vote to accept Druid into the
> Apache
> >> Incubator[1] has passed with 15 binding +1 votes, 19 non-binding +1
> votes,
> >> and no 0 or -1 votes.
> >>>
> >>> Binding +1:
> >>> * Andrew Purtell
> >>> * Ashutosh Chauhan
> >>> * Chris Mattmann
> >>> * Davor Bonaci
> >>> * James Taylor
> >>> * Jitendra Pandey
> >>> * John Ament
> >>> * Julian Hyde
> >>> * P. Taylor Goetz
> >>> * Ryan Blue
> >>> * Steve Blackmon
> >>> * Suneel Marthi
> >>> * Ted Dunning
> >>> * Tom Barber
> >>> * Willem Jiang
> >>>
> >>> Non-binding +1:
> >>> * Amol Kekre
> >>> * Anu Engineer
> >>> * Arpit Agarwal
> >>> * Ashish
> >>> * Atul K. Gupta
> >>> * Bhupesh Chawda
> >>> * Bolke de Bruin
> >>> * Chinmay Kolhatkar
> >>> * Hao Chen
> >>> * Hugo Lauro
> >>> * Jordan Zimmerman
> >>> * Jungtaek Lim
> >>> * Jyotirmoy Sundi
> >>> * Pramod Immaneni
> >>> * ShaoFeng Shi
> >>> * Von Gosling
> >>> * Xin Wang
> >>> * Yash Datta
> >>> * Zhanhui Li
> >>>
> >>> Thanks to all who voted. The large turnout shows that many people share
> >> my enthusiasm for this project.
> >>>
> >>> Julian
> >>>
> >>> [1] https://s.apache.org/druid-incubation-vote
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>
> >>
> >> --
> >>
> >>
> >> Spicule Limited is registered in England & Wales. Company Number:
> 09954122.
> >> Registered office: First Floor, Telecom House, 125-135 Preston Road,
> >> Brighton, England, BN1 6AF. VAT No. 251478891.
> >>
> >>
> >> All engagements are subject to Spicule Terms and Conditions of Business.
> >> This email and its contents are intended solely for the individual to
> whom
> >> it is addressed and may contain information that is confidential,
> >> privileged or otherwise protected from disclosure, distributing or
> copying.
> >> Any views or opinions presented in this email are solely those of the
> >> author and do not necessarily represent those of Spicule Limited. The
> >> company accepts no liability for any damage caused by any virus
> transmitted
> >> by this email. If you have received this message in error, please
> notify us
> >> immediately by reply email before deleting it from your system. Service
> of
> >> legal notice cannot be effected on Spicule Limited by email.
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Druid 0.12.0 release (pre incubation)

[Gian Merlino]

Thanks for the advice Julian.

For our next release after 0.12.0, with our normal schedule we would look
to start doing release candidates later this month and aim for a final
release in April / May (Druid release candidates usually bake for a month
or so). Whether we could do those release candidates in the incubator or
not depends on how fast we can get stuff migrated over -- I am optimistic
we can get it done fast enough but I am not totally sure.

Gian

On Fri, Mar 2, 2018 at 1:15 PM, Julian Hyde <jh...@apache.org> wrote:

> As a mentor of Druid, sounds good to me. It’s good to keep on releasing
> regularly - the community relies on it.
>
> Please mention this in the board report (due in about a week).
>
> When will the next release be, and will you be able to make that under the
> incubator process?
>
> Julian
>
>
> > On Mar 2, 2018, at 1:09 PM, Gian Merlino <g...@imply.io> wrote:
> >
> > Hi incubators,
> >
> > Druid was recently accepted into the incubator (yay) - I now want to
> bring
> > up a release vote we already had in progress and that we expect to
> complete
> > early next week:
> > https://groups.google.com/d/topic/druid-development/sK777vmZ
> cR0/discussion.
> > Since this release is likely just days away, we intend to publish it as
> our
> > final pre-incubation release. Of course, we won't call it Apache Druid,
> and
> > we'll release it on http://druid.io/, not on
> > http://druid.incubator.apache.org/.
> >
> > Are there any other precautions we should take to avoid confusion? We
> could
> > also include some explicit statement that this release is not an Apache
> > release, to avoid confusing anyone that may have heard that Druid is
> > starting incubation.
> >
> > Gian
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Druid 0.12.0 release (pre incubation)

[Gian Merlino]

Hi incubators,

Druid was recently accepted into the incubator (yay) - I now want to bring
up a release vote we already had in progress and that we expect to complete
early next week:
https://groups.google.com/d/topic/druid-development/sK777vmZcR0/discussion.
Since this release is likely just days away, we intend to publish it as our
final pre-incubation release. Of course, we won't call it Apache Druid, and
we'll release it on http://druid.io/, not on
http://druid.incubator.apache.org/.

Are there any other precautions we should take to avoid confusion? We could
also include some explicit statement that this release is not an Apache
release, to avoid confusing anyone that may have heard that Druid is
starting incubation.

Gian

[DISCUSS] Druid incubation proposal

[Gian Merlino]

arence@gmail.com) (Imply)
 * Eric Tschetter (ched...@apache.org) (Splunk)
 * Fangjin Yang (f...@imply.io) (Imply)
 * Gian Merlino (g...@apache.org) (Imply)
 * Himanshu Gupta (g.himan...@gmail.com) (Oath)
 * Jihoon Son (jihoon...@apache.org) (Imply)
 * Jonathan Wei (jon@imply.io) (Imply)
 * Maxime Beauchemin (maximebeauche...@gmail.com) (Lyft)
 * Mohamed Slim Bouguerra (slim.bougue...@gmail.com) (Hortonworks)
 * Nishant Bangarwa (nish...@apache.org) (Hortonworks)
 * Parag Jain (paragjai...@gmail.com) (Oath)
 * Roman Leventov (leventov...@gmail.com) (Metamarkets)
 * Xavier Léauté (xav...@leaute.com) (Confluent)

== Sponsors ==

 * Champion: Julian Hyde
 * Nominated mentors: Julian Hyde, P. Taylor Goetz, Jun Rao
 * Sponsoring entity: Apache Incubator

Write access to Incubator wiki

[Gian Merlino]

Hi all,

Could the account "GianMerlino" please be granted edit rights to the
Incubator wiki? (I am working on a proposal)

Thank you!