Re: [VOTE] Accept StormCrawler Into the ASF Incubator

[P. Taylor Goetz]

+1 (binding)

I have a great deal of faith in the success of this project.

- Taylor

> On Mar 12, 2024, at 4:33 PM, PJ Fanning  wrote:
> 
> Hi everyone,
> 
> Following the discussion about the StormCrawler proposal [1], I am
> starting this official vote for the StormCrawler podling. Here is the
> proposal:
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal
> 
> Please cast your vote:
> [ ] +1, bring into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring StormCrawler into the Incubator, because...
> 
> The vote will open for one week from today, 12 March, 2024.
> 
> Thanks,
> PJ
> 
> [1] https://lists.apache.org/thread/sjht4k1ojhcgfnzszxb809g1dh2t1dlw
> 
> -
> 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] Incubating Proposal for StormCrawler

[P. Taylor Goetz]

I would definitely vote +1 (binding) on this proposal..

StormCrawleer has had, and likely will continue to have, a very positive impact 
on the Apache Storm project and community.

The listed mentors and initial contributors all seem to have considerable 
Apache experience, and earned have my trust and, more importantly, that of the 
community. The Apache Storm project recently had a brush with the Antic, and it 
was largely the contributors listed in this proposal who stepped up to keep the 
project active.

There would undoubtedly be a symbiotic relationship between the two projects.

While I don’t currently have the bandwidth to mentor the project, I trust the 
proposed mentors, initial committers,  and mentor volunteers. I would 
definitely monitor the community and would certainly step in if I saw anything 
run atstray. 

- Taylor (Former VP, Apache Storm)



> On Mar 3, 2024, at 6:24 PM, PJ Fanning  wrote:
> 
> Hi everyone,
> 
> I would like to propose StormCrawler [1] as a new Apache Incubator project,
> and you can examine the proposal [2] for more details.
> 
> StormCrawler is a collection of resources for building low-latency,
> customisable and scalable web crawlers on Apache Storm.
> 
> Proposal
> 
> The aim of StormCrawler is to help build web crawlers that are:
> 
> * scalable
> * resilient
> * low latency
> * easy to extend
> * polite yet efficient
> 
> StormCrawler achieves this partly with Apache Storm, which it is based
> on. To use an analogy, Apache Storm is to StormCrawler what Apache
> Hadoop is to Apache Nutch.
> 
> StormCrawler is mature (26 releases to date) and is used by many
> organisations world-wide.
> 
> Initial Committers
> 
> Julien Nioche [jnio...@apache.org https://github.com/jnioche]
> Sebastian Nagel [sna...@apache.org https://github.com/sebastian-nagel]
> Richard Zowalla [r...@apache.org  https://github.com/rzo1]
> Tim Allison [talli...@apache.org https://github.com/tballison]
> Michael Dinzinger [michael.dinzin...@uni-passau.de
> https://github.com/michaeldinzinger]
> 
> Most of the existing StormCrawler contributors are existing ASF
> committers and are looking to build a vibrant community following the
> Apache Way.
> 
> I will help this project as the champion and mentor. We would welcome
> additional mentors, if anyone has an interest in helping.
> 
> We are looking forward to your questions and feedback.
> 
> Thanks,
> PJ
> 
> [1] https://github.com/DigitalPebble/storm-crawler
> [2] 
> https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal
> 
> -
> 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] Research on the incubator / mentor interviews

[P. Taylor Goetz]

They contacted me directly and I agreed. Apparently I was the first interview 
today.

They are super nice and extremely appreciative of participation. What they are 
doing is also really interesting and the results of the study will likely 
benefit the Incubator and the ASF.

I highly recommend other mentors, whether past or present, participate if 
requested.

-Taylor 

> On Apr 7, 2021, at 8:57 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> A National Science Foundation-funding research team may be asking you for an 
> interview to help them understand the ASF mentoring program. 
> 
> They are interested in mentors experiences and perspectives in the Incubator 
> and understand how mentors contribute to the successful graduation of 
> podlings. The team is sending requests to some mentors for an interview. I’ll 
> be taking part, and I hope you do as well. They are interested in sharing any 
> results of their research with us. I think their insights would be a great 
> help to the Incubator and current and future mentors.
> 
> Here’s a brief overview of the project: 
> 
> “Jumpstarting Successful Open-Source Software Projects With Evidence-Based 
> Rules and Structures” is a National Science Foundation-funded project that 
> aims to understand how governance impacts the success of open source 
> software. The multidisciplinary research team includes empirical software 
> engineers and social scientists with diverse expertise in research 
> methods--including publicly available data, interviews, and surveys--working 
> together to understand sustainability in contributions to open-source 
> software.
> 
> If you want to know more about the project, please ask.
> 
> Kind Regards,
> Justin


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

Re: [VOTE] Myriad retirement

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jan 23, 2020, at 10:13 AM, Javi Roman  wrote:
> 
> Unfortunately, despite an effort to reboot the project about more than one
> year, we weren't successful in keeping the existing committers active. At
> this point, a decision to retire the podling was taken, and a vote was done
> on the PPMC:
> 
> Discussion:
> https://lists.apache.org/thread.html/ea7567bede20e2c0fc9d0c3ea2713e2b2a7442897ceafdeb1aa95b05%40%3Cdev.myriad.apache.org%3E
> 
> Result:
> https://lists.apache.org/thread.html/r5d8a123ad051f748379904066cde17b93974ed2628593ebd69dee028%40%3Cdev.myriad.apache.org%3E
> 
> According to https://incubator.apache.org/guides/retirement.html I'm
> starting a vote on the incubator mailing list to be ratified the retirement.
> 
> 
> [ ] +1   : retire Myriad
> [ ] +/-0 : No opinion
> [ ] -1   : Don't retire Myriad.
> 
> 
> Many thanks.
> 
> --
> Javi Roman
> 
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
> Apache Id: javiroman


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

[P. Taylor Goetz]

+1 (binding)

- signatures are good
-  LICENCE, NOTICE, and DISCLAIMER present and look okay.
- was able to build from source.

-Taylor

> On Sep 23, 2019, at 9:11 PM, Julian Hyde  wrote:
> 
> 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 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 

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

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Aug 13, 2019, at 3: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   (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

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

[P. Taylor Goetz]

I posted the following in a private@ thread:

Traditionally ASF membership + expressed interest has been the main path to the 
IPMC. Honestly, I think “someone who has significantly helped a project 
navigate incubation through to successful graduation” holds at least as much 
merit as ASF membership. 

There’s the added benefit of recent experience. My experience with the 
incubator 5-6 years ago is likely different than what podlings experience 
today. The core values haven’t changed, but some processes have. 

That is where I see new blood brings value.

———

I see value in lowing the bar for entry to the IPMC. I also see value in 
allowing interested Members to auto-join. Default to inclusivity.

-Taylor

> On Aug 12, 2019, at 7:29 PM, Greg Stein  wrote:
> 
> On Mon, Aug 12, 2019 at 5:26 PM Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>>> I will also note that if the IPMC switches to *voting* Members into the
>>> IPMC, that the Apache Member will be observing that vote take place on
>>> private@ through a subscription (they can reply!) or via the archives. …
>> 
>> Which is also the same for any project who votes in a ASF member as a
>> committer or PMC member.
>> 
> 
> I would counter that any project which creates such a bar for ASF Members
> may be doing it Wrong :)
> 
> (this goes into my general feeling that projects generally need to lower
> their bars, and become more inclusive)
> 
> Cheers,
> -g

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

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jun 19, 2019, at 10:38 PM, 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
> 
> 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:
> 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.15.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,
> Jihoon
> 
> 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] Zipkin leave incubator, return back to OpenZipkin

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jun 17, 2019, at 9:21 PM, Sheng Wu  wrote:
> 
> Hi
> 
> This is a call for official vote of Zipkin leave from incubator, and return 
> back to OpenZipkin.
> 
> PPMC have voted.[1], carried two IPMC +1 vote from Sheng Wu and Willem Jiang
> 
> There is no trademark, logo transfer, so, Zipkin community is OK to still use 
> the name(io.zipkin or zipkin + xxx) and logo. 
> `org.apache.zipkin` is not allowed or going to be used.
> All 9 repositories(GitHub repo) will be transferred back to OpenZipkin 
> org(GitHub).
> incubator-zipkin --> https://github.com/openzipkin/zipkin 
> ncubator-zipkin-dependencies --> 
> https://github.com/openzipkin/zipkin-dependencies 
> incubator-zipkin-api --> https://github.com/openzipkin/zipkin-api 
> incubator-zipkin-b3-propagation --> 
> https://github.com/openzipkin/b3-propagation 
> incubator-zipkin-reporter-java --> 
> https://github.com/openzipkin/zipkin-reporter-java 
> incubator-zipkin-brave --> https://github.com/openzipkin/brave 
> incubator-zipkin-brave-cassandra --> 
> https://github.com/openzipkin/brave-cassandra 
> incubator-zipkin-brave-karaf --> https://github.com/openzipkin/brave-karaf 
> incubator-zipkin-layout-factory --> 
> https://github.com/openzipkin/zipkin-layout-factory 
> 
> Voting will start now (2019-6-18 9:20 UTC+8) and will remain open 72 hours 
> only for consensus, Request all IPMC members to give their vote.
> [ ] +1 Agree
> [ ] +0 No opinion.
> [ ] -1 Do not agree because
> 
> [1] 
> https://lists.apache.org/thread.html/fbeb254f569d9852e9740d55532ee338580287ec384e26c7d9107964@%3Cdev.zipkin.apache.org%3E
>  
> 
> 
> 
> 
> Sheng Wu
> Apache Skywalking, ShardingSphere, Zipkin
> 
> 
> 


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

Re: [VOTE]: Release Apache DLab (incubating) 2.1 (RC2)

[P. Taylor Goetz]

+1 (binding)

- Signature good
- DISCLAIMER file exists
- L & N look good
- ASF headers present
- No binaries is source release

-Taylor



> On Apr 8, 2019, at 5:53 AM, Bohdan Hliva  wrote:
> 
> Hello Incubator Community,
> 
> The Apache DLab community has voted on and approved a proposal to release 
> Apache DLab (incubating) version 2.1 (RC2).
> 
> We now kindly request the Incubator PMC members review and vote in this 
> release.
> 
> DLab is a platform for creating self-service, exploratory data science 
> environments in the cloud using best-of-breed data science tools.
> DLab includes a self-service web console, used to create and manage 
> exploratory environments. It allows teams to spin up analytical environments 
> with just a single click of a mouse. 
> Once established, the environment can be managed by an analytical team 
> itself, leveraging simple and easy-to-use web-based interface.
> 
> DLab community vote thread:
>   • 
> https://lists.apache.org/thread.html/9fd53b487701557362d60e962986aa3fd8c1eb438b25d5cc17665dff@%3Cdev.dlab.apache.org%3E
> 
> Vote result thread:
>   • 
> https://lists.apache.org/thread.html/be72de69909182907b74e1fa215af75a5c1fc50e8f464a7c15bf08c1@%3Cdev.dlab.apache.org%3E
> 
> The release candidate:
>   • https://dist.apache.org/repos/dist/dev/incubator/dlab/2.1-RC2/
> 
> Git tag for the release:
>   • https://github.com/apache/incubator-dlab/tree/2.1-RC2
> 
> Release notes:
>   • https://github.com/apache/incubator-dlab/blob/2.1-RC2/RELEASE_NOTES.md
> 
> The artifacts signed with PGP key 5C3C66D1, corresponding to 
> bhl...@apache.org, that can be found in keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dlab/KEYS
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Thanks,
> The Apache DLab (Incubating) Team
> 
> -
> 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: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot

[P. Taylor Goetz]

> On Dec 7, 2018, at 3:15 PM, Justin Mclean  wrote:
> 
> Do you know why this is the case?

I forgot, and until today didn’t have access to the machine with all my Apache 
credentials.

> Reminder were sent to the dev list and this list. Are the mentors signed up 
> to the dev list or this list? Are the mentors active? Does the project need 
> new mentors?

2/3 mentors are active. 3/3 are signed up for both lists. I don’t feel the 
project needs additional mentors, but am open to adding a mentor if there’s 
interest.

My apologies for the inconvenience.

-Taylor

Re: IPMC Board report - missing podling reports for DLab, Marvin-AI and Pinot

[P. Taylor Goetz]

Hi Justin,

DLab prepared a report and posted it to the dev@ list, but unfortunately we 
mentors failed to get it posted to the wiki.

I’ve since posted it. I’ll work with the podling to get them access to the wiki.

-Taylor

> On Dec 6, 2018, at 5:29 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> 3 podlings have failed to report on time and will be asked to report next 
> month. They are Dlab, Marvin-AI and Pinot.
> 
> If the mentors of these projects would be so kind to make the following 
> happen it would be appreciated:
> a) That the PPMC  is encouraged to discuss the report (preferable on-list) 
> ahead of the deadline.
> b) That all the PPMC members are signed up to the dev and private lists and 
> so see the report reminders or email about late reports.
> c) That the PPMC is aware that it is their responsibility to create and 
> submit the report.
> d) Someone responds to the report reminders so it's known it’s been worked on.
> e) That the next report now due in a month is submitted before the deadline.
> 
> A good indication of mentor inactivity is not submitting reports in on time, 
> and while missing one is not a big deal but if several in a row are missed it 
> a good indication that the podling probably needs new mentors. Podlings if 
> you mentors are not helping you (and I’ve not looked to see if they are) 
> please bring this up on the the general@ incubator list and we’ll try to help.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
> For additional commands, e-mail: dev-h...@dlab.apache.org
> 


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

Re: [VOTE] Heron Release 0.20.0-incubating Candidate 5

[P. Taylor Goetz]

+1 (binding)

- Checksum and signature look good
- L & N files look okay
- DISCLAIMER present
- ASF headers present
- No wayward binaries

(Note I didn’t try to build, I just examined that source package.)

-Taylor


> On Oct 31, 2018, at 1:31 PM, Neng Lu  wrote:
> 
> Hi All,
> 
> This is the 5th release candidate for Apache Heron, version
> 0.20.0-incubating. Thanks everyone for providing various feedback for the
> previous release candidates at the @dev mailing list voting process. This
> release candidate passed the project's dev voting process so we are
> bringing it to a broader voting process.
> 
> It is the starting point of Heron and contains heron's main features, such
> as core streaming
> processing, stateful processing, streamlet API, API server, eco support,
> etc.
> 
> The full list of changes and fixes are available:
> https://github.com/apache/incubator-heron/compare/0.17.8...release/v-0.20.0-incubating
> 
> *** Please download, test and vote on this release. This vote will stay open
> for at least 72 hours ***
> 
> Source files:
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.0-incubating-candidate-5/
> 
> SHA-512 checksums:
> 27890ab30fc3e69b627f47d58d178d1a7dffa9dbe4ebbb5a5aa77caaac882fdc2b6f98b3b76210020db0fa3fd86e294cba214f86072e449837e1b7615cd6124a
> incubator-heron-v-0.20.0-incubating-candidate-5.tar.gz
> 
> The tag to be voted upon:
> v0.20.0-incubating-candidate-5 (45043bb6dcef1e8089c0834f17f8be0cc3f451d3)
> https://github.com/apache/incubator-heron/releases/tag/v-0.20.0-incubating-candidate-5
> 
> Please download the source package, and follow the compiling guide(
> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/)
> to build and run the Heron locally.
> 
> -- 
> Best Regards,
> Neng


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

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

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Sep 10, 2018, at 11:48 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> The Apache Pulsar project is ready to graduate as a TLP. They entered 
> Incubation on June 1, 2017, have had many releases and have grown the 
> community.
> 
> At the mentors request they did a maturity model analysis [1] and wrote 
> contribution guidelines. [2]
> 
> The Graduation Proposal was written and discussed on the dev list. [3] At the 
> mentor's recommendation the By-Laws Clause was removed.
> 
> The new prospective PMC is set and the VOTE thread in the podling is here [4] 
> with these results. [5]
> 
> Let’s see if there is any discussion here on general@incubator before moving 
> onto a VOTE.
> 
> Regards,
> Dave
> 
> [1] 
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
>  
> <https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar>
> [2] http://pulsar.incubator.apache.org/en/contributing/ 
> <http://pulsar.incubator.apache.org/en/contributing/>
> [3] 
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E>
> [4] 
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E>
> [5] 
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E>
> 
> 
> 
> 
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
> 
> * Boyang Jerry Peng mailto:jerryp...@apache.org>>
> * Brad McMillen mailto:bra...@apache.org>>
> * David Fisher mailto:w...@apache.org>>
> * Francis Christopher Liu mailto:tof...@apache.org>>
> * Hiroyuki Sakai mailto:hrsa...@apache.org>>
> * Ivan Brendan Kelly mailto:iv...@apache.org>>
> * Jai Asher mailto:j...@apache.org>>
> * Jia Zhai mailto:zhai...@apache.org>>
> * Jim Jagielski mailto:j...@apache.org>>
> * Joe Francis mailto:j...@apache.org>>
> * Ludwig Pummer mailto:ludw...@apache.org>>
> * Masahiro Sakamoto mailto:massa...@apache.org>>
> * Masakazu Kitajo mailto:mas...@apache.org>>
> * Matteo Merli mailto:mme...@apache.org>>
> * Nozomi Kurihara mailto:nkuri...@apache.org>>
> * P. Taylor Goetz mailto:ptgo...@apache.org>>
> * Rajan Dhabalia mailto:rdhaba...@apache.org>>
> * Sahaya Andrews mailto:andr...@apache.org>>
> * Sanjeev Kulkarni mailto:sanjee...@apache.org>>
> * Sebastiá

Re: Graduation Resolutions Should Not Include Project Bylaws Clause

[P. Taylor Goetz]

> On Sep 3, 2018, at 12:10 AM, Greg Stein  wrote:
> 
> Personally, I'd prefer that the concept of project bylaws disappear. Move
> to "community guides". A *guide* rather than a *ruleset*. The Board has
> kinda gone quiet on the discussion, but hopefully it will pick it back up,
> to provide some guidance here.

++1

All projects need is sane (in ASF terms) developer guidelines. 

-Taylor

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

Re: Graduation Resolutions Should Not Include Project Bylaws Clause

[P. Taylor Goetz]

Greg,

I agree with Justin.

I know from experience what the “defaults” are, but to a newcomer, it’s likely 
anything but clear. The project-specific ones you reference make no reference 
to being bylaws, hence my description of them as “policy.”

If we could clearly delineate between Foundation Bylaws and Project Bylaws, 
with both preferably outlined on a single page, I think that would help resolve 
some of the confusion.

-Taylor

> On Sep 2, 2018, at 7:57 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> There are two types of "bylaws" at the Foundation level. The official ones
>> you're referring to, and the project ones under dev/ (the "how it works"
>> stuff).
> 
> And the issue with the later is not 100% clear what they are, and while they 
> are mostly documented in various places and reasonably well understood 
> there’s some cracks and some things are open to interpretation. While having 
> “the default" certainly works in just about all cases, it can fall down in 
> situations where it’s probably most needed.
> 
> It could possibly be a good idea, if the board took a look as some existing 
> TLP projects bylaws, picked a set they agree with and we could made that the 
> default set for new projects to use.
> 
> 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

Gossip Retirement Complete

[P. Taylor Goetz]

All the steps for retiring the Gossip podling are now complete.

-Taylor

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

Re: Graduation Resolutions Should Not Include Project Bylaws Clause

[P. Taylor Goetz]

Aren’t the foundation-level bylaws about how the ASF operates as a non-profit 
business?

I may be missing something, but ASF bylaws don’t address project management, 
ASF policy does.

-Taylor

> On Sep 2, 2018, at 5:25 PM, John D. Ament  wrote:
> 
> -private list for now.
> 
> 
> I disagree with removing the bylaws clause.  It's assumed your going to use
> the ASF level bylaws if you don't have another one.
> 
>> On Sun, Sep 2, 2018, 14:29 Dave Fisher  wrote:
>> 
>> Note the cross-posting between public and private mailing lists.
>> 
>> Sent from my iPhone
>> 
>>> On Sep 2, 2018, at 11:22 AM, Kevin A. McGrail 
>> wrote:
>>> 
>>> Good point, Dave.  +board as this was an issue with emeritus pmc and
>>> project bylaws
>>> 
 On Sun, Sep 2, 2018, 12:37 Dave Fisher  wrote:
 
 Hi -
 
 Pulsar is currently discussing a graduation proposal and Taylor noticed
 the following that came out of the whimsy boilerplate.
 
 Quick question:
 
 RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked
 with the creation of a set of bylaws intended to encourage open
 development and increased participation in the Apache Pulsar Project;
 and be it further
 
 
 Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required),
>> or
 are the Apache defaults acceptable?
 
 One option is to simply not have bylaws, which means you would simply
 adhere to [1] and [2], and put any clarifications in a contributors’
>> guide
 (which you’ve done).
 
 -Taylor
 
 [1] http://www.apache.org/foundation/voting.html
 [2] http://www.apache.org/dev/pmc.html
 
 
 I think that this clause needs to be removed from the template.
 
 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

Re: Poddlings length of time in the incubator

[P. Taylor Goetz]

I’d be a +1.

-Taylor

> On Aug 31, 2018, at 6:35 PM, Ted Dunning  wrote:
> 
> On Fri, Aug 31, 2018 at 3:30 PM Justin Mclean 
> wrote:
> 
>> ...
>>> FWIW, for the DLab proposal [1], we added a voluntary incubation period
>> max of 2 years, essentially saying we didn’t want to become a resource
>> drain. I haven’t checked to see if any other projects have done this.
>> 
>> Nice idea. I think we shovel add to the template “How long do you think
>> you'll spend in incubation” to the proposal template - what do others
>> think? At least they sets some expectations even if it’s not binding.
>> 
> 
> I think that is a great suggestion.

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

Re: Dealing with Unresponsive Mentors

[P. Taylor Goetz]

I increasingly tend to agree. However, if we put the onus on PPMCs to police 
inactive mentors, there should probably be a documented process in place (which 
it is [1]).

My concern with that policy is the potential for a chilling effect. Mentors are 
more often than not ASF Members. I can easily imagine situations where podlings 
might avoid such a move out of fear of offending an ASF Member.

-Taylor


[1] https://incubator.apache.org/guides/ppmc.html#removing_a_mentor

> On Aug 29, 2018, at 7:33 PM, Julian Hyde  wrote:
> 
> There was a long thread about absent mentors a few months ago[1]. The 
> consensus on the thread seemed to be to introduce some metrics. I was and am 
> skeptical of that approach because it requires constant attention from the 
> IPMC.
> 
> The solution I advocated in that thread is to encourage podlings to ask for 
> help if they are not getting service from their mentors. And perhaps to add a 
> "Have your mentors been helpful and responsive?” question to the report 
> template.
> 
> Julian
> 
> [1] 
> https://lists.apache.org/thread.html/e80a611ea233a5f854aae5f63374e6490af70a5ecbe886874111037c@%3Cgeneral.incubator.apache.org%3E
>  
> 
> 
>> On Aug 29, 2018, at 1:46 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>>> What is the process of essentially off-boarding unresponsive and inactive
>>> mentors with the sole aim of attracting new mentors who can inject life
>>> into various aspects of podling maturity?
>> 
>> I’d just ask them if they can continue in the role or still have the cycles 
>> to help. If they can’t continue or are unresponsive then just ask for more 
>> mentors for the project on this list.
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 

Re: Poddlings length of time in the incubator

[P. Taylor Goetz]

> On Aug 28, 2018, at 9:01 PM, Roman Shaposhnik  wrote:
> 
>> On Sun, Aug 26, 2018 at 1:40 PM, Julian Hyde  wrote:
>> Regarding Quickstep. I am a mentor. (One mentor resigned earlier this
>> year, but the other mentor, Roman, is sufficiently engaged.)
>> 
>> I am concerned that Quickstep is not going to graduate. They are
>> functioning well as an academic project, as evidenced by papers at top
>> conferences[1], but all of their contributors are from the same
>> university department. They have made a few efforts at community
>> building, but do not seem to be building a user base, or attracting
>> outside contributions.
>> 
>> (Note that traffic for July and August is lower than usual, due to
>> their contributors being in academia. Traffic on the dev list should
>> pick up somewhat in September.)
>> 
>> Embrace of Apache has been half-hearted. Note, for instance, that
>> their twitter account [2] still references their pre-Apache home page
>> [3] rather than their Apache page [4].
>> 
>> Quickstep made their first release in March 2017 but have not made
>> further releases. I am going encourage them to make a new release
>> soon. That will stimulate some community activity. But I am dubious
>> that this will attract outside contributors.
> 
> Basically, I'm +1 on every single point that Julian makes, but having
> said this I'm unsure as to where can we go from here.
> 
> In the past we typically shied away from setting deadlines for certain
> milestones in community development within podlings. This, in my view,
> somewhat encouraged this phenomenon of an "eternal podling" (active
> enough not to be in the attic, not active/ApacheWay'y enough to
> graduate). I feel like Quickstep, for example, can exist in this state
> indefinitely.

FWIW, for the DLab proposal [1], we added a voluntary incubation period max of 
2 years, essentially saying we didn’t want to become a resource drain. I 
haven’t checked to see if any other projects have done this.

I’m also not sure if that’s in any way binding, or what the mechanics of that 
would be. I imagine at the 2-year mark there would be a PPMC vote to either a) 
retire, or b) request additional time from the IPMC. If b, then the IPMC would 
either approve or deny the extension request.

> 
> 
> Thanks,
> Roman.

-Taylor

[1] https://wiki.apache.org/incubator/DLabProposal

> 
>> Julian
>> 
>> [1] http://www.vldb.org/pvldb/vol11/p663-patel.pdf
>> 
>> [2] https://twitter.com/ApacheQuickstep
>> 
>> [3] http://quickstep.cs.wisc.edu/
>> 
>> [4] http://quickstep.apache.org/
>>> On Sun, Aug 26, 2018 at 10:17 AM Mark Thomas  wrote:
>>> 
 On 26/08/18 02:30, Justin Mclean wrote:
 Hi,
 
> I’ve discussed this some on the ODF toolkit dev list. Development was 
> recently moved to Git. The Incubator needs to decide if we will turnover 
> the domains that were donated in 2011 by IBM(?) to the only consistent 
> developer. If that is true then we can quickly let them retire, but 
> survive on Github.
 
 I also saw you mentioned it in a previous incubator report for the 
 podling. What are the domain names in question? I think doing as you 
 suggested sounds like a good idea do you want to take that back to the 
 PPMC and discuss and/or vote on doing that.
 
 Any other IPMC members think differently?
>>> 
>>> The podling PMC can make a recommendation but the decision to release a
>>> domain name to a third party needs the approval of VP Brand Management.
>>> 
>>> We also need to find the transfer agreements (if any) for those domains
>>> to see what the ASF agreed to at the time of donation. It is not unheard
>>> of for such agreements to include a clause that ownership reverts to the
>>> donor if the podling does not graduate.
>>> 
>>> Mark
>>> 
>>> -
>>> 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] Retire Gossip podling

[P. Taylor Goetz]

Josh, can we close this vote?

-Taylor

> On Aug 10, 2018, at 12:22 PM, Josh Elser  wrote:
> 
> Thanks, Taylor. Appreciate that!
> 
> On 8/9/18 8:51 PM, P. Taylor Goetz wrote:
>> +1 (binding)
>> As the champion for this project, I’ll volunteer to take care of the 
>> retirement tasks.
>> -Taylor
>>> On Aug 9, 2018, at 6:52 PM, Josh Elser  wrote:
>>> 
>>> Hi,
>>> 
>>> The Gossip podling has voted to retire from incubation.
>>> 
>>> DISCUSS: 
>>> https://lists.apache.org/thread.html/8acab107a15a6bc50253cb20aa633a3ac36b70364294f149660fc6c4@%3Cdev.gossip.apache.org%3E
>>> VOTE: 
>>> https://lists.apache.org/thread.html/d725e5f03ecbd516613b9a75abd9178936e578b38c3793933f571caf@%3Cdev.gossip.apache.org%3E
>>> 
>>> Please see the relevant discussion and vote threads from the dev list 
>>> above. This is not a unanimous decision (one dissenting voice out of 7), 
>>> but the podling has been operating with little to no activity for about a 
>>> year. As such, I think this is the right path forward with the 
>>> understanding that Gossip can return to the Incubator in the future if 
>>> there is renewed interest in the project.
>>> 
>>> Please vote to ratify this request for retirement. We'll keep this open for 
>>> at least 72hrs as customary (until 2018/08/12 2300 GMT).
>>> 
>>> Here is my +1 (binding)
>>> 
>>> - Josh
>>> 
>>> -
>>> 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
> 



signature.asc
Description: Message signed with OpenPGP

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

[P. Taylor Goetz]

Awesome. Thanks Cos. I’ll add you as a mentor.

-Taylor

> On Aug 20, 2018, at 2:11 PM, Konstantin Boudnik  wrote:
> 
> Looks like I am bit late and vote is closed, but I still want to cast
> my +1 - I have helped this project during my time at EPAM and wish it
> all the success!
> 
> If the project needs more mentors at this point - I have some spare
> cycles to burn.
> 
> Thanks!
> --
>  With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> 
> Disclaimer: Opinions expressed in this email are those of the author,
> and do not necessarily represent the views of any company the author
> might be affiliated with at the moment of writing.
> 
> 
> On Mon, Aug 20, 2018 at 6:13 PM, P. Taylor Goetz  wrote:
>> The 72 hour voting period has elapsed, and with 4 binding +1 votes and no -1 
>> or 0 votes this vote passes.
>> 
>> Vote tally (* indicates a binding vote):
>> 
>> +1:
>> - Dave Fisher*
>> - Ted Dunning*
>> - P. Taylor Goetz*
>> - Matt Sicker*
>> 
>> Thanks to all who voted. I will begin the bootstrapping process shortly.
>> 
>> -Taylor
>> 
>>> On Aug 15, 2018, at 12:27 PM, P. Taylor Goetz  wrote:
>>> 
>>> After a brief discussion [1] I would like to call a VOTE to accept DLab 
>>> into the Apache Incubator. The full proposal is available on the wiki[2] 
>>> and is pasted below in text form as well.
>>> 
>>> This vote will run at least 72 hours. Please VOTE as follows:
>>> 
>>> [ ] +1 Accept DLab into the Apache Incubator
>>> [ ] +0 No opinion
>>> [ ] -1 Do not accept DLab into the Apache Incubator because…
>>> 
>>> -Taylor
>>> 
>>> [1] 
>>> https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E
>>> [2] https://wiki.apache.org/incubator/DLabProposal
>>> 
>>> 
>>> = DLab Proposal =
>>> 
>>> == Abstract ==
>>> DLab is a platform for creating self-service, exploratory data science 
>>> environments in the cloud using best-of-breed data science tools.
>>> 
>>> DLab includes a self-service web console, used to create and manage 
>>> exploratory environments. It allows teams to spin up analytical 
>>> environments with just a single click of a mouse. Once established, the 
>>> environment can be managed by an analytical team itself, leveraging simple 
>>> and easy-to-use web-based interface.
>>> 
>>> == Proposal ==
>>> In order to work effectively, data scientists rely on a varying suite of 
>>> analytics tools that are readily available. However, many of those tools 
>>> are non-trivial to set up in terms of hardware provisioning, software 
>>> installation, configuration, and deployment. Setting up a collaborative, 
>>> multi-tenant development environment for data scientists consumes 
>>> substantial IT and DevOps resources, as well as time. These factors often 
>>> combine to hinder the agility and effectiveness of data science teams 
>>> within an organization. Current solutions are largely closed source and/or 
>>> proprietary, and committing to a given solution introduces the potential 
>>> for vendor lock-in.
>>> 
>>> EPAM Systems developed DLab in response to the lack of open source, 
>>> permissibly licensed solutions to better enable data science workflows. The 
>>> ALv2 was selected to encourage open development and user adoption. DLab was 
>>> open sourced on Dec 29, 2016 and is under active development with support 
>>> from EPAM Systems.
>>> 
>>> We believe DLab is a unique solution with no current open source 
>>> equivalent. Our primary goals of incubation are to grow and diversify the 
>>> DLab community to ensure its long-term sustainability.
>>> 
>>> == Rationale ==
>>> DLab is a platform that provides data scientists with the ability to 
>>> self-provision, without IT support, exploratory and production environments 
>>> with their preferred set of tools installed and pre-configured. Tool 
>>> options include, but are not limited to:
>>> 
>>> * Apache Spark
>>> * Apache Flink (planned)
>>> * Apache Zeppelin
>>> * Jupyter
>>> * TensorFlow + Jupyter
>>> * Deep Learning + Jupyter
>>> 
>>> DLab leverages cloud computing providers for virtual hardware provisioning 
>>> and currently supports the following:
>>>

[RESULT] [VOTE] Accept DLab into the Apache Incubator

[P. Taylor Goetz]

The 72 hour voting period has elapsed, and with 4 binding +1 votes and no -1 or 
0 votes this vote passes.

Vote tally (* indicates a binding vote):

+1:
- Dave Fisher*
- Ted Dunning*
- P. Taylor Goetz*
- Matt Sicker*

Thanks to all who voted. I will begin the bootstrapping process shortly.

-Taylor

> On Aug 15, 2018, at 12:27 PM, P. Taylor Goetz  wrote:
> 
> After a brief discussion [1] I would like to call a VOTE to accept DLab into 
> the Apache Incubator. The full proposal is available on the wiki[2] and is 
> pasted below in text form as well.
> 
> This vote will run at least 72 hours. Please VOTE as follows:
> 
> [ ] +1 Accept DLab into the Apache Incubator
> [ ] +0 No opinion
> [ ] -1 Do not accept DLab into the Apache Incubator because…
> 
> -Taylor
> 
> [1] 
> https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E
> [2] https://wiki.apache.org/incubator/DLabProposal
> 
> 
> = DLab Proposal =
> 
> == Abstract ==
> DLab is a platform for creating self-service, exploratory data science 
> environments in the cloud using best-of-breed data science tools.
> 
> DLab includes a self-service web console, used to create and manage 
> exploratory environments. It allows teams to spin up analytical environments 
> with just a single click of a mouse. Once established, the environment can be 
> managed by an analytical team itself, leveraging simple and easy-to-use 
> web-based interface.
> 
> == Proposal ==
> In order to work effectively, data scientists rely on a varying suite of 
> analytics tools that are readily available. However, many of those tools are 
> non-trivial to set up in terms of hardware provisioning, software 
> installation, configuration, and deployment. Setting up a collaborative, 
> multi-tenant development environment for data scientists consumes substantial 
> IT and DevOps resources, as well as time. These factors often combine to 
> hinder the agility and effectiveness of data science teams within an 
> organization. Current solutions are largely closed source and/or proprietary, 
> and committing to a given solution introduces the potential for vendor 
> lock-in.
> 
> EPAM Systems developed DLab in response to the lack of open source, 
> permissibly licensed solutions to better enable data science workflows. The 
> ALv2 was selected to encourage open development and user adoption. DLab was 
> open sourced on Dec 29, 2016 and is under active development with support 
> from EPAM Systems.
> 
> We believe DLab is a unique solution with no current open source equivalent. 
> Our primary goals of incubation are to grow and diversify the DLab community 
> to ensure its long-term sustainability.
> 
> == Rationale ==
> DLab is a platform that provides data scientists with the ability to 
> self-provision, without IT support, exploratory and production environments 
> with their preferred set of tools installed and pre-configured. Tool options 
> include, but are not limited to:
> 
> * Apache Spark
> * Apache Flink (planned)
> * Apache Zeppelin
> * Jupyter
> * TensorFlow + Jupyter
> * Deep Learning + Jupyter
> 
> DLab leverages cloud computing providers for virtual hardware provisioning 
> and currently supports the following:
> 
> * Amazon Web Services (AWS)
> * Microsoft Azure
> * Google Compute Platform (GCP) (under development)
> 
> DLab offers git-based collaboration tools for data scientists and developers 
> and integrates with the following git service providers:
> 
> * GItHub
> * GitLab
> * BitBucket
> 
> Additionally, DLab includes the option to configure the UnGit tool in an 
> environment to facilitate collaboration.
> Finally, DLab integrates closely with many security and SSO offerings, 
> including:
> 
> * LDAP
> * Microsoft Active Directory
> * AWS Identity Access Management service
> 
> DLab was designed from the ground up to be highly configurable, flexible, and 
> extensible platform. We believe these qualities will encourage community 
> growth by enabling contributors to easily add new integrations and extensions.
> 
> == Initial Goals ==
> The initial goal will be to move the existing codebase to Apache and 
> integrate with the Apache development process and infrastructure. A primary 
> goal of incubation will be to grow and diversify the DLab PPMC. We are well 
> aware that the project community is comprised of individuals from a single 
> company. We aim to change that during incubation.
> 
> == Current Status ==
> As previously mentioned, DLab is under active development at EPAM Systems, 
> and is being used in a number of production deployments:
> 
> * [An investment company] is us

Re: [DISCUSS] Marvin-AI Incubator Proposal

[P. Taylor Goetz]

Sounds interesting, and I would support it, but I’m currently maxed out on 
mentorship.

That may change. I’m mentoring one podling that is moving toward graduation, 
and another that is moving toward retirement.

-Taylor

> On Aug 15, 2018, at 7:16 PM, sebb  wrote:
> 
>> On 15 August 2018 at 23:37, Luciano Resende  wrote:
>> Thanks for the heads up Sebastian, we will have that in mind and remove the
>> hyphen if that's what causes the issue (e.g. using to MarvinAI)
> 
> Or just Marvin?
> 
> Note that the display name can remain as Marvin-AI, however the
> project id/mailing-list should not have an embedded hyphen.
> 
>>> On Wed, Aug 15, 2018 at 3:29 PM sebb  wrote:
>>> 
>>> A warning: there are some areas of Infra which assume that project
>>> names don't include hyphens.
>>> There is one existing project with a hyphen (Empire-db); various
>>> scripts have to be special-cased to handle this.
>>> 
>>> It would be best not to use marvin-ai as the project id (the display
>>> name does not matter).
>>> 
 On 15 August 2018 at 20:13, Luciano Resende  wrote:
 We would like to start a discussion on accepting Marvin-AI as an Apache
 Incubator project.
 
 The proposal is available at the incubator wiki, and also copied below:
 https://wiki.apache.org/incubator/Marvin-AI
 
 As part of the initial due diligence, we have done a preliminary name
 search and the results are available on the JIRA below:
 
 https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144
 
 We are also looking for two additional mentors.
 
 
 Thanks in advance for your time reviewing and providing feedback.
 
 ===
 
 = Marvin-AI =
 
 == Abstract ==
 
 Marvin-AI is an open-source artificial intelligence (AI) platform that
 helps data scientists, prototype and productionalize complex solutions
>>> with
 a scalable, low-latency, language-agnostic, and standardized architecture
 while simplifies the process of exploration and modeling.
 
 == Proposal ==
 
 Marvin helps non-experienced developers create industry-grade AI
 applications. It has three core components:  a development environment to
 be used during data exploration and hypothesis validation (Toolbox), a
 library which should be extended to create Marvin engines, and a Scala
 application server which interprets engines (Engine Executor).
 A basic premise of Marvin is that it should be language-agnostic, able to
 interpret engines implemented in different programming languages.
 
 == Background ==
 
 The Marvin AI project was initiated as an internal project at B2W Digital
 (Brazil), the largest e-commerce company in Latin America. Nowadays, it
>>> is
 used by all data scientists within the B2W team. Oftentimes, data
 scientists don't have an extensive background in software engineering,
>>> yet
 are in charge of creating AI applications that need to scale to high
 throughput and provide millisecond-level response times. At B2W, Marvin
>>> AI
 plays an important role in this process, abstracting advanced software
 engineering procedures, allowing data scientists to focus on their
 knowledge domain.
 
 == Rationale ==
 
 With recent advances in computer architecture and a corresponding
>>> increase
 in the amount of data generated by always-connected devices, AI
>>> algorithms
 offer a solution to problems that have long troubled modern corporations.
 Since AI developers come from various fields, such as statistics,
>>> physics,
 and math, there exists a strong need for platforms which enable them to
 move from prototypes to enterprise applications. Although some tools
>>> claim
 to offer this service, in reality, there is no reliable open-source
 solution.
 
 == Initial Goals ==
 
 The initial goals will most likely be to merge the existing codebase
>>> into a
 single repository, migrate it to Apache, and then integrate with the
>>> Apache
 development process. Furthermore, we plan for incremental development and
 releases, as per Apache guidelines.
 
 == Current Status ==
 
 === Meritocracy ===
 
 Marvin already works under principles of meritocracy. Today, Marvin
>>> already
 has some contributors that are part of other institutions. Although there
 is no formal process defined to become a committer, contributors that
>>> make
 major changes/improvements to the platform are naturally granted write
 access to the repository.
 
 
 === Community ===
 
 Acceptance into the Apache foundation would substantially boost both
 Marvin's user and developer communities. The current community includes a
 few experienced developers that have either academic or professional
 experience with AI. The community is largely comprised of data scientists
 working at B2W 

Re: [VOTE] Accept DLab into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Aug 15, 2018, at 12:38 PM, Ted Dunning  wrote:
> 
> +1
> 
> 
> 
> On Wed, Aug 15, 2018 at 9:36 AM Dave Fisher  wrote:
> 
>> +1 (binding)
>> 
>> Sent from my iPhone
>> 
>>> On Aug 15, 2018, at 9:27 AM, P. Taylor Goetz  wrote:
>>> 
>>> After a brief discussion [1] I would like to call a VOTE to accept DLab
>> into the Apache Incubator. The full proposal is available on the wiki[2]
>> and is pasted below in text form as well.
>>> 
>>> This vote will run at least 72 hours. Please VOTE as follows:
>>> 
>>> [ ] +1 Accept DLab into the Apache Incubator
>>> [ ] +0 No opinion
>>> [ ] -1 Do not accept DLab into the Apache Incubator because…
>>> 
>>> -Taylor
>>> 
>>> [1]
>> https://lists.apache.org/thread.html/9c96873d49f53da33260e21dc698f7c9b82eec256caf97a0e3f54943@%3Cgeneral.incubator.apache.org%3E
>>> [2] https://wiki.apache.org/incubator/DLabProposal
>>> 
>>> 
>>> = DLab Proposal =
>>> 
>>> == Abstract ==
>>> DLab is a platform for creating self-service, exploratory data science
>> environments in the cloud using best-of-breed data science tools.
>>> 
>>> DLab includes a self-service web console, used to create and manage
>> exploratory environments. It allows teams to spin up analytical
>> environments with just a single click of a mouse. Once established, the
>> environment can be managed by an analytical team itself, leveraging simple
>> and easy-to-use web-based interface.
>>> 
>>> == Proposal ==
>>> In order to work effectively, data scientists rely on a varying suite of
>> analytics tools that are readily available. However, many of those tools
>> are non-trivial to set up in terms of hardware provisioning, software
>> installation, configuration, and deployment. Setting up a collaborative,
>> multi-tenant development environment for data scientists consumes
>> substantial IT and DevOps resources, as well as time. These factors often
>> combine to hinder the agility and effectiveness of data science teams
>> within an organization. Current solutions are largely closed source and/or
>> proprietary, and committing to a given solution introduces the potential
>> for vendor lock-in.
>>> 
>>> EPAM Systems developed DLab in response to the lack of open source,
>> permissibly licensed solutions to better enable data science workflows. The
>> ALv2 was selected to encourage open development and user adoption. DLab was
>> open sourced on Dec 29, 2016 and is under active development with support
>> from EPAM Systems.
>>> 
>>> We believe DLab is a unique solution with no current open source
>> equivalent. Our primary goals of incubation are to grow and diversify the
>> DLab community to ensure its long-term sustainability.
>>> 
>>> == Rationale ==
>>> DLab is a platform that provides data scientists with the ability to
>> self-provision, without IT support, exploratory and production environments
>> with their preferred set of tools installed and pre-configured. Tool
>> options include, but are not limited to:
>>> 
>>> * Apache Spark
>>> * Apache Flink (planned)
>>> * Apache Zeppelin
>>> * Jupyter
>>> * TensorFlow + Jupyter
>>> * Deep Learning + Jupyter
>>> 
>>> DLab leverages cloud computing providers for virtual hardware
>> provisioning and currently supports the following:
>>> 
>>> * Amazon Web Services (AWS)
>>> * Microsoft Azure
>>> * Google Compute Platform (GCP) (under development)
>>> 
>>> DLab offers git-based collaboration tools for data scientists and
>> developers and integrates with the following git service providers:
>>> 
>>> * GItHub
>>> * GitLab
>>> * BitBucket
>>> 
>>> Additionally, DLab includes the option to configure the UnGit tool in an
>> environment to facilitate collaboration.
>>> Finally, DLab integrates closely with many security and SSO offerings,
>> including:
>>> 
>>> * LDAP
>>> * Microsoft Active Directory
>>> * AWS Identity Access Management service
>>> 
>>> DLab was designed from the ground up to be highly configurable,
>> flexible, and extensible platform. We believe these qualities will
>> encourage community growth by enabling contributors to easily add new
>> integrations and extensions.
>>> 
>>> == Initial Goals ==
>>> The initial goal will be to move the

[VOTE] Accept DLab into the Apache Incubator

[P. Taylor Goetz]

 extensions and plug-ins. We also understand that any 
such component, if it requires a dependency forbidden by Apache license policy, 
would not be eligible for inclusion in an Apache release, and would have to be 
hosted, supported, etc. outside of ASF infrastructure and labeled appropriately.

=== External dependencies licensed under Apache License 2.0: ===
MongoDB Java Driver - org.mongodb:mongo-java-driver 
(http://mongodb.github.io/mongo-java-driver/3.2/driver)

Dropwizard (https://github.com/dropwizard/dropwizard)

Dropwizard Template Config 
(https://github.com/tkrille/dropwizard-template-config)

Apache Directory Server (https://github.com/apache/directory-server)

Jackson (https://github.com/FasterXML/jackson)

AWS Java SDK (https://github.com/aws/aws-sdk-java)

Boto3 (https://github.com/boto/boto3)

=== External dependencies licensed under the MIT License: ===
angular2-app (https://www.npmjs.com/package/angular2-app)

angular2-seed (https://www.npmjs.com/package/angular2-seed)

angular2-seed-advanced (https://www.npmjs.org/package/angular2-seed-advanced)

angular2-seed-n3UX (https://www.npmjs.com/package/angular2-seed-n3UX)

http-status-enum (https://www.npmjs.com/package/http-status-enum)
Mockito (https://github.com/mockito/mockito)

ng2-translate (https://www.npmjs.com/package/ng2-translate)

SLF4J (http://www.slf4j.org/)

=== External dependencies licensed under the CDDL License: ===
Jersey (https://github.com/jersey/jersey)

=== External dependencies licensed under the Python Software License Version 2: 
===
jython (https://github.com/jythontools/jython)

=== ASF Projects: ===
Apache Spark, Apache Toree (incubating), Apache Zeppelin

== Cryptography ==
Not applicable.

== Initial Committers ==
 * Dmytro Liaskovskyi dmytro_liaskovs...@epam.com
 * Volodymyr Veres volodymyr_ve...@epam.com
 * Oleh Hrynets oleh_hryn...@epam.com
 * Oleh Hrynyk oleh_hry...@epam.com
 * Oleh Martushevskyi oleh_martushevs...@epam.com
 * Oleh Moskovych oleh_moskov...@epam.com
 * Vadym Kuznetsov vadym_kuznet...@epam.com
 * Usein Faradzhev usein_faradz...@epam.com
 * Bohdan Hliva bohdan_hl...@epam.com
 * Oleksandr Melnychuk oleksandr_melnych...@epam.com
 * Mikhail Teplitskiy mikhail_teplits...@epam.com
 * Vira Vitanska vira_vitan...@epam.com
 * Andriana Kovalyshyn andriana_kovalys...@epam.com
 * Oleksandr Chaparin oleksandr_chapa...@epam.com
 * Denys Shliakhov denys_shliak...@epam.com
 * Nazar Barabash nazar_barab...@epam.com
 * Yuriy Holinko yuriy_holi...@epam.com
 * Petro Kotsiuba petro_kotsi...@epam.com
 * Bogdan Rudyi bogdan_ru...@epam.com
 * Mikhail Teplitskyi mikhail_teplits...@epam.com

== Sponsors ==

=== Champion ===
 * P. Taylor Goetz ptgo...@apache.org

=== Nominated Mentors ===
 * P. Taylor Goetz ptgo...@apache.org
 * Henry Saputra hsapu...@apache.org

=== Interested Contributors ===
 * Debo Dutta ddu...@apache.org

=== Sponsoring Entity ===
 * The Apache Incubator



signature.asc
Description: Message signed with OpenPGP

Re: [PROPOSAL] DLab for Apache Incubator

[P. Taylor Goetz]

If there’s no further discussion, I will call for a VOTE tomorrow.

-Taylor

> On Aug 6, 2018, at 10:47 AM, P. Taylor Goetz  wrote:
> 
> I would like to propose DLab as an Apache Incubator project.
> 
> The text of the proposal can be found below as well as on the Incubator wiki:
> 
> https://wiki.apache.org/incubator/DLabProposal
> 
> We are seeking additional mentors and would welcome anyone who would like to 
> volunteer.
> 
> -Taylor
> 
> 
> = DLab Proposal =
> 
> == Abstract ==
> DLab is a platform for creating self-service, exploratory data science 
> environments in the cloud using best-of-breed data science tools.
> 
> DLab includes a self-service web console, used to create and manage 
> exploratory environments. It allows teams to spin up analytical environments 
> with just a single click of a mouse. Once established, the environment can be 
> managed by an analytical team itself, leveraging simple and easy-to-use 
> web-based interface.
> 
> == Proposal ==
> In order to work effectively, data scientists rely on a varying suite of 
> analytics tools that are readily available. However, many of those tools are 
> non-trivial to set up in terms of hardware provisioning, software 
> installation, configuration, and deployment. Setting up a collaborative, 
> multi-tenant development environment for data scientists consumes substantial 
> IT and DevOps resources, as well as time. These factors often combine to 
> hinder the agility and effectiveness of data science teams within an 
> organization. Current solutions are largely closed source and/or proprietary, 
> and committing to a given solution introduces the potential for vendor 
> lock-in.
> 
> EPAM Systems developed DLab in response to the lack of open source, 
> permissibly licensed solutions to better enable data science workflows. The 
> ALv2 was selected to encourage open development and user adoption. DLab was 
> open sourced on Dec 29, 2016 and is under active development with support 
> from EPAM Systems.
> 
> We believe DLab is a unique solution with no current open source equivalent. 
> Our primary goals of incubation are to grow and diversify the DLab community 
> to ensure its long-term sustainability.
> 
> == Rationale ==
> DLab is a platform that provides data scientists with the ability to 
> self-provision, without IT support, exploratory and production environments 
> with their preferred set of tools installed and pre-configured. Tool options 
> include, but are not limited to:
> 
> * Apache Spark
> * Apache Flink (planned)
> * Apache Zeppelin
> * Jupyter
> * TensorFlow + Jupyter
> * Deep Learning + Jupyter
> 
> DLab leverages cloud computing providers for virtual hardware provisioning 
> and currently supports the following:
> 
> * Amazon Web Services (AWS)
> * Microsoft Azure
> * Google Compute Platform (GCP) (under development)
> 
> DLab offers git-based collaboration tools for data scientists and developers 
> and integrates with the following git service providers:
> 
> * GItHub
> * GitLab
> * BitBucket
> 
> Additionally, DLab includes the option to configure the UnGit tool in an 
> environment to facilitate collaboration.
> Finally, DLab integrates closely with many security and SSO offerings, 
> including:
> 
> * LDAP
> * Microsoft Active Directory
> * AWS Identity Access Management service
> 
> DLab was designed from the ground up to be highly configurable, flexible, and 
> extensible platform. We believe these qualities will encourage community 
> growth by enabling contributors to easily add new integrations and extensions.
> 
> == Initial Goals ==
> The initial goal will be to move the existing codebase to Apache and 
> integrate with the Apache development process and infrastructure. A primary 
> goal of incubation will be to grow and diversify the DLab PPMC. We are well 
> aware that the project community is comprised of individuals from a single 
> company. We aim to change that during incubation.
> 
> == Current Status ==
> As previously mentioned, DLab is under active development at EPAM Systems, 
> and is being used in a number of production deployments:
> 
> * [An investment company] is using DLab as an AWS-based analytics platform 
> for their data scientists to provide a convenient way to perform multi-tenant 
> data analytics. This enables data scientists to easily provision work 
> environments with integrated data sources based on Elasticsearch, Apache 
> HBase, and Neo4j, and utilizing Apache Spark. This enabled a “one click”, 
> self service option for users to provision an environment with the necessary 
> tools and data.
> 
> * [An electronics manufacturing company] leverages 

Re: [VOTE] Apache Toree 0.2.0-incubating (RC6)

[P. Taylor Goetz]

Got it. Thanks for explaining.

+1 (binding)

- Checked signatures.
- Looked for binaries
- Spot-checked license headers.
- Checked L files.

-Taylor

> On Aug 13, 2018, at 2:39 PM, Luciano Resende  wrote:
> 
> The source package which has no dependencies only has the boilerplate
> LICENSE file.
> 
> The PIP distribution, which is the binary distribution, then has the
> dependencies listed as part of the LICENSE file.
> 
> On Mon, Aug 13, 2018 at 11:34 AM P. Taylor Goetz  wrote:
> 
>> I noticed the LICENSE and NOTICE files are boilerplate with no additions,
>> but looking at /project/Dependencies.scala I see a number of dependencies
>> with various licenses such as BSD and MIT. Is there a reason those
>> components aren’t listed in the LICENSE file per [1]?
>> 
>> If this question has been answered before, I apologize, this is the first
>> Three release I’ve reviewed.
>> 
>> -Taylor
>> 
>> [1] http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> 
>>> On Aug 9, 2018, at 12:13 PM, Luciano Resende 
>> wrote:
>>> 
>>> Please vote to approve the release of Apache Toree 0.2.0-incubating
>> (RC6).
>>> 
>>> The podling dev vote thread:
>>> 
>> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01798.html
>>> 
>>> And the result:
>>> 
>> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01821.html
>>> 
>>> Tag: v0.2.0-incubating-rc6 (eae2da61828a0c88e2ab64a7ffb9ff7647909a2c)
>>> 
>>> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc6
>>> 
>>> All distribution packages, including signatures, digests, etc. can be
>> found
>>> at:
>>> 
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0-incubating-rc6/
>>> 
>>> Staging artifacts can be found at:
>>> 
>>> https://repository.apache.org/content/repositories/orgapachetoree-1013
>>> 
>>> 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 Toree 0.2.0-incubating
>>> [ ] -1 Do not release this package because ...
>>> 
>>> --
>>> Luciano Resende
>>> http://twitter.com/lresende1975
>>> http://lresende.blogspot.com/
>> 
>> 
> 
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache Toree 0.2.0-incubating (RC6)

[P. Taylor Goetz]

I noticed the LICENSE and NOTICE files are boilerplate with no additions, but 
looking at /project/Dependencies.scala I see a number of dependencies with 
various licenses such as BSD and MIT. Is there a reason those components aren’t 
listed in the LICENSE file per [1]?

If this question has been answered before, I apologize, this is the first Three 
release I’ve reviewed.

-Taylor

[1] http://www.apache.org/dev/licensing-howto.html#permissive-deps

> On Aug 9, 2018, at 12:13 PM, Luciano Resende  wrote:
> 
> Please vote to approve the release of Apache Toree 0.2.0-incubating (RC6).
> 
> The podling dev vote thread:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01798.html
> 
> And the result:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01821.html
> 
> Tag: v0.2.0-incubating-rc6 (eae2da61828a0c88e2ab64a7ffb9ff7647909a2c)
> 
> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc6
> 
> All distribution packages, including signatures, digests, etc. can be found
> at:
> 
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0-incubating-rc6/
> 
> Staging artifacts can be found at:
> 
> https://repository.apache.org/content/repositories/orgapachetoree-1013
> 
> 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 Toree 0.2.0-incubating
> [ ] -1 Do not release this package because ...
> 
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache Toree 0.2.0-incubating (RC6)

[P. Taylor Goetz]

I’m trying evaluate the RC, but I can’t find the KEYS file for the project. It 
doesn’t appear to be in any of the typical locations.

-Taylor

> On Aug 9, 2018, at 12:13 PM, Luciano Resende  wrote:
> 
> Please vote to approve the release of Apache Toree 0.2.0-incubating (RC6).
> 
> The podling dev vote thread:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01798.html
> 
> And the result:
> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01821.html
> 
> Tag: v0.2.0-incubating-rc6 (eae2da61828a0c88e2ab64a7ffb9ff7647909a2c)
> 
> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc6
> 
> All distribution packages, including signatures, digests, etc. can be found
> at:
> 
> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0-incubating-rc6/
> 
> Staging artifacts can be found at:
> 
> https://repository.apache.org/content/repositories/orgapachetoree-1013
> 
> 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 Toree 0.2.0-incubating
> [ ] -1 Do not release this package because ...
> 
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Apache Toree 0.2.0-incubating (RC6)

[P. Taylor Goetz]

If it can wait until Monday, I’ll volunteer.

-Taylor

> On Aug 11, 2018, at 12:46 PM, Luciano Resende  wrote:
> 
> We already have two IPMC binding votes from the dev list (myself and Ryan)
> and we need one more vote.
> We would like to announce this release at a conference a week from Monday
> ... Any volunteers to help with the release vote?
> 
>> On Thu, Aug 9, 2018 at 9:13 AM Luciano Resende  wrote:
>> 
>> Please vote to approve the release of Apache Toree 0.2.0-incubating
>> (RC6).
>> 
>> The podling dev vote thread:
>> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01798.html
>> 
>> And the result:
>> https://www.mail-archive.com/dev@toree.incubator.apache.org/msg01821.html
>> 
>> Tag: v0.2.0-incubating-rc6 (eae2da61828a0c88e2ab64a7ffb9ff7647909a2c)
>> 
>> https://github.com/apache/incubator-toree/tree/v0.2.0-incubating-rc6
>> 
>> All distribution packages, including signatures, digests, etc. can be
>> found at:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/toree/0.2.0
>> -incubating-rc6/
>> 
>> Staging artifacts can be found at:
>> 
>> https://repository.apache.org/content/repositories/orgapachetoree-1013
>> 
>> 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 Toree 0.2.0-incubating
>> [ ] -1 Do not release this package because ...
>> 
>> --
>> Luciano Resende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>> 
> 
> 
> -- 
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

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

Re: [VOTE] Retire Gossip podling

[P. Taylor Goetz]

+1 (binding)

As the champion for this project, I’ll volunteer to take care of the retirement 
tasks.

-Taylor

> On Aug 9, 2018, at 6:52 PM, Josh Elser  wrote:
> 
> Hi,
> 
> The Gossip podling has voted to retire from incubation.
> 
> DISCUSS: 
> https://lists.apache.org/thread.html/8acab107a15a6bc50253cb20aa633a3ac36b70364294f149660fc6c4@%3Cdev.gossip.apache.org%3E
> VOTE: 
> https://lists.apache.org/thread.html/d725e5f03ecbd516613b9a75abd9178936e578b38c3793933f571caf@%3Cdev.gossip.apache.org%3E
> 
> Please see the relevant discussion and vote threads from the dev list above. 
> This is not a unanimous decision (one dissenting voice out of 7), but the 
> podling has been operating with little to no activity for about a year. As 
> such, I think this is the right path forward with the understanding that 
> Gossip can return to the Incubator in the future if there is renewed interest 
> in the project.
> 
> Please vote to ratify this request for retirement. We'll keep this open for 
> at least 72hrs as customary (until 2018/08/12 2300 GMT).
> 
> Here is my +1 (binding)
> 
> - Josh
> 
> -
> 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: [PROPOSAL] DLab for Apache Incubator

[P. Taylor Goetz]

Thanks Debo,

Traditionally/in practice/lately, those who are not IPMC members are listed as 
“Interested Contributors”. Are you okay with that?

I’ll gladly add it and invite anyone else who is interested to join that group.

As we tried to make clear in the proposal, we understand the current community 
is limited to one company, and the first order of business is to diversify the 
community.

-Taylor

> On Aug 7, 2018, at 9:11 PM, Debo Dutta (dedutta)  
> wrote:
> 
> I am happy to help (either mentor or volunteer). This is a good idea. Have 
> helped out in Apache projects before. 
> 
> Debo 
> 
> Sent from my iPhone
> 
>> On Aug 7, 2018, at 6:08 PM, P. Taylor Goetz  wrote:
>> 
>> Henry Saputra (hsaputra) has been added to the mentor list.
>> 
>> We are still interested in proposal feedback and mentor volunteers.
>> 
>> -Taylor
>> 
>>> On Aug 6, 2018, at 10:47 AM, P. Taylor Goetz  wrote:
>>> 
>>> I would like to propose DLab as an Apache Incubator project.
>>> 
>>> The text of the proposal can be found below as well as on the Incubator 
>>> wiki:
>>> 
>>> https://wiki.apache.org/incubator/DLabProposal
>>> 
>>> We are seeking additional mentors and would welcome anyone who would like 
>>> to volunteer.
>>> 
>>> -Taylor
>>> 
>>> 
>>> = DLab Proposal =
>>> 
>>> == Abstract ==
>>> DLab is a platform for creating self-service, exploratory data science 
>>> environments in the cloud using best-of-breed data science tools.
>>> 
>>> DLab includes a self-service web console, used to create and manage 
>>> exploratory environments. It allows teams to spin up analytical 
>>> environments with just a single click of a mouse. Once established, the 
>>> environment can be managed by an analytical team itself, leveraging simple 
>>> and easy-to-use web-based interface.
>>> 
>>> == Proposal ==
>>> In order to work effectively, data scientists rely on a varying suite of 
>>> analytics tools that are readily available. However, many of those tools 
>>> are non-trivial to set up in terms of hardware provisioning, software 
>>> installation, configuration, and deployment. Setting up a collaborative, 
>>> multi-tenant development environment for data scientists consumes 
>>> substantial IT and DevOps resources, as well as time. These factors often 
>>> combine to hinder the agility and effectiveness of data science teams 
>>> within an organization. Current solutions are largely closed source and/or 
>>> proprietary, and committing to a given solution introduces the potential 
>>> for vendor lock-in.
>>> 
>>> EPAM Systems developed DLab in response to the lack of open source, 
>>> permissibly licensed solutions to better enable data science workflows. The 
>>> ALv2 was selected to encourage open development and user adoption. DLab was 
>>> open sourced on Dec 29, 2016 and is under active development with support 
>>> from EPAM Systems.
>>> 
>>> We believe DLab is a unique solution with no current open source 
>>> equivalent. Our primary goals of incubation are to grow and diversify the 
>>> DLab community to ensure its long-term sustainability.
>>> 
>>> == Rationale ==
>>> DLab is a platform that provides data scientists with the ability to 
>>> self-provision, without IT support, exploratory and production environments 
>>> with their preferred set of tools installed and pre-configured. Tool 
>>> options include, but are not limited to:
>>> 
>>> * Apache Spark
>>> * Apache Flink (planned)
>>> * Apache Zeppelin
>>> * Jupyter
>>> * TensorFlow + Jupyter
>>> * Deep Learning + Jupyter
>>> 
>>> DLab leverages cloud computing providers for virtual hardware provisioning 
>>> and currently supports the following:
>>> 
>>> * Amazon Web Services (AWS)
>>> * Microsoft Azure
>>> * Google Compute Platform (GCP) (under development)
>>> 
>>> DLab offers git-based collaboration tools for data scientists and 
>>> developers and integrates with the following git service providers:
>>> 
>>> * GItHub
>>> * GitLab
>>> * BitBucket
>>> 
>>> Additionally, DLab includes the option to configure the UnGit tool in an 
>>> environment to facilitate collaboration.
>>> Finally, DLab integrates closely with many security and SSO offerings, 
>>> including:
>>>

Re: [PROPOSAL] DLab for Apache Incubator

[P. Taylor Goetz]

Henry Saputra (hsaputra) has been added to the mentor list.

We are still interested in proposal feedback and mentor volunteers.

-Taylor

> On Aug 6, 2018, at 10:47 AM, P. Taylor Goetz  wrote:
> 
> I would like to propose DLab as an Apache Incubator project.
> 
> The text of the proposal can be found below as well as on the Incubator wiki:
> 
> https://wiki.apache.org/incubator/DLabProposal
> 
> We are seeking additional mentors and would welcome anyone who would like to 
> volunteer.
> 
> -Taylor
> 
> 
> = DLab Proposal =
> 
> == Abstract ==
> DLab is a platform for creating self-service, exploratory data science 
> environments in the cloud using best-of-breed data science tools.
> 
> DLab includes a self-service web console, used to create and manage 
> exploratory environments. It allows teams to spin up analytical environments 
> with just a single click of a mouse. Once established, the environment can be 
> managed by an analytical team itself, leveraging simple and easy-to-use 
> web-based interface.
> 
> == Proposal ==
> In order to work effectively, data scientists rely on a varying suite of 
> analytics tools that are readily available. However, many of those tools are 
> non-trivial to set up in terms of hardware provisioning, software 
> installation, configuration, and deployment. Setting up a collaborative, 
> multi-tenant development environment for data scientists consumes substantial 
> IT and DevOps resources, as well as time. These factors often combine to 
> hinder the agility and effectiveness of data science teams within an 
> organization. Current solutions are largely closed source and/or proprietary, 
> and committing to a given solution introduces the potential for vendor 
> lock-in.
> 
> EPAM Systems developed DLab in response to the lack of open source, 
> permissibly licensed solutions to better enable data science workflows. The 
> ALv2 was selected to encourage open development and user adoption. DLab was 
> open sourced on Dec 29, 2016 and is under active development with support 
> from EPAM Systems.
> 
> We believe DLab is a unique solution with no current open source equivalent. 
> Our primary goals of incubation are to grow and diversify the DLab community 
> to ensure its long-term sustainability.
> 
> == Rationale ==
> DLab is a platform that provides data scientists with the ability to 
> self-provision, without IT support, exploratory and production environments 
> with their preferred set of tools installed and pre-configured. Tool options 
> include, but are not limited to:
> 
> * Apache Spark
> * Apache Flink (planned)
> * Apache Zeppelin
> * Jupyter
> * TensorFlow + Jupyter
> * Deep Learning + Jupyter
> 
> DLab leverages cloud computing providers for virtual hardware provisioning 
> and currently supports the following:
> 
> * Amazon Web Services (AWS)
> * Microsoft Azure
> * Google Compute Platform (GCP) (under development)
> 
> DLab offers git-based collaboration tools for data scientists and developers 
> and integrates with the following git service providers:
> 
> * GItHub
> * GitLab
> * BitBucket
> 
> Additionally, DLab includes the option to configure the UnGit tool in an 
> environment to facilitate collaboration.
> Finally, DLab integrates closely with many security and SSO offerings, 
> including:
> 
> * LDAP
> * Microsoft Active Directory
> * AWS Identity Access Management service
> 
> DLab was designed from the ground up to be highly configurable, flexible, and 
> extensible platform. We believe these qualities will encourage community 
> growth by enabling contributors to easily add new integrations and extensions.
> 
> == Initial Goals ==
> The initial goal will be to move the existing codebase to Apache and 
> integrate with the Apache development process and infrastructure. A primary 
> goal of incubation will be to grow and diversify the DLab PPMC. We are well 
> aware that the project community is comprised of individuals from a single 
> company. We aim to change that during incubation.
> 
> == Current Status ==
> As previously mentioned, DLab is under active development at EPAM Systems, 
> and is being used in a number of production deployments:
> 
> * [An investment company] is using DLab as an AWS-based analytics platform 
> for their data scientists to provide a convenient way to perform multi-tenant 
> data analytics. This enables data scientists to easily provision work 
> environments with integrated data sources based on Elasticsearch, Apache 
> HBase, and Neo4j, and utilizing Apache Spark. This enabled a “one click”, 
> self service option for users to provision an environment with the necessary 
> tools and d

[PROPOSAL] DLab for Apache Incubator

[P. Taylor Goetz]

 appropriately.

=== External dependencies licensed under Apache License 2.0: ===
MongoDB Java Driver - org.mongodb:mongo-java-driver 
(http://mongodb.github.io/mongo-java-driver/3.2/driver)

Dropwizard (https://github.com/dropwizard/dropwizard)

Dropwizard Template Config 
(https://github.com/tkrille/dropwizard-template-config)

Apache Directory Server (https://github.com/apache/directory-server)

Jackson (https://github.com/FasterXML/jackson)

AWS Java SDK (https://github.com/aws/aws-sdk-java)

Boto3 (https://github.com/boto/boto3)

=== External dependencies licensed under the MIT License: ===
angular2-app (https://www.npmjs.com/package/angular2-app)

angular2-seed (https://www.npmjs.com/package/angular2-seed)

angular2-seed-advanced (https://www.npmjs.org/package/angular2-seed-advanced)

angular2-seed-n3UX (https://www.npmjs.com/package/angular2-seed-n3UX)

http-status-enum (https://www.npmjs.com/package/http-status-enum)
Mockito (https://github.com/mockito/mockito)

ng2-translate (https://www.npmjs.com/package/ng2-translate)

SLF4J (http://www.slf4j.org/)

=== External dependencies licensed under the CDDL License: ===
Jersey (https://github.com/jersey/jersey)

=== External dependencies licensed under the Python Software License Version 2: 
===
jython (https://github.com/jythontools/jython)

=== ASF Projects: ===
Apache Spark, Apache Toree (incubating), Apache Zeppelin

== Cryptography ==
Not applicable.

== Initial Committers ==
 * Dmytro Liaskovskyi dmytro_liaskovs...@epam.com
 * Volodymyr Veres volodymyr_ve...@epam.com
 * Oleh Hrynets oleh_hryn...@epam.com
 * Oleh Hrynyk oleh_hry...@epam.com
 * Oleh Martushevskyi oleh_martushevs...@epam.com
 * Oleh Moskovych oleh_moskov...@epam.com
 * Vadym Kuznetsov vadym_kuznet...@epam.com
 * Usein Faradzhev usein_faradz...@epam.com
 * Bohdan Hliva bohdan_hl...@epam.com
 * Oleksandr Melnychuk oleksandr_melnych...@epam.com
 * Mikhail Teplitskiy mikhail_teplits...@epam.com
 * Vira Vitanska vira_vitan...@epam.com
 * Andriana Kovalyshyn andriana_kovalys...@epam.com
 * Oleksandr Chaparin oleksandr_chapa...@epam.com
 * Denys Shliakhov denys_shliak...@epam.com
 * Nazar Barabash nazar_barab...@epam.com
 * Yuriy Holinko yuriy_holi...@epam.com
 * Petro Kotsiuba petro_kotsi...@epam.com
 * Bogdan Rudyi bogdan_ru...@epam.com
 * Mikhail Teplitskyi mikhail_teplits...@epam.com

== Sponsors ==

=== Champion ===
 * P. Taylor Goetz ptgo...@apache.org

=== Nominated Mentors ===
 * P. Taylor Goetz ptgo...@apache.org

=== Sponsoring Entity ===
 * The Apache Incubator



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Graduate Apache HAWQ (incubating)

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jul 27, 2018, at 10:13 PM, Roman Shaposhnik  wrote:
> 
> Hi!
> 
> after a very positive discussion in the HAWQ community
> and at the IPMC level:
> https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193cc110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E
> https://lists.apache.org/thread.html/3a142d758ef5ae119e421071893615992ea5ee937b5d02007f5e@%3Cgeneral.incubator.apache.org%3E
> 
> I'd like to bring the following resolution for a formal vote.
> 
> Please vote on the resolution pasted below to graduate
> Apache HAWQ from the incubator to top level project.
> 
> [ ] +1 Graduate Apache HAWQ from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache HAWQ from the Incubator because...
> 
> This vote will be open for at least 72 hours.
> 
> Many thanks to our mentors and everyone else for the support,
> Roman (on behalf of the Apache HAWQ PPMC).
> 
> ## Resolution to create a TLP from graduating Incubator podling
> 
>X. Establish the Apache HAWQ 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 Hadoop native SQL query engine that
>   combines the key technological advantages of MPP database
>   with the scalability and convenience of Hadoop.
> 
>   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>   Committee (PMC), to be known as the "Apache HAWQ Project",
>   be and hereby is established pursuant to Bylaws of the
>   Foundation; and be it further
> 
>   RESOLVED, that the Apache HAWQ Project be and hereby is
>   responsible for the creation and maintenance of software
>   related to Hadoop native SQL query engine that
>   combines the key technological advantages of MPP database
>   with the scalability and convenience of Hadoop;
>   and be it further
> 
>   RESOLVED, that the office of "Vice President, Apache HAWQ" 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 HAWQ Project, and to have primary responsibility
>   for management of the projects within the scope of
>   responsibility of the Apache HAWQ 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 HAWQ Project:
> 
>* Alan Gates   
>* Alexander Denissov   
>* Amy Bai  
>* Atri Sharma  
>* Bhuvnesh Chaudhary   
>* Bosco
>* Chunling Wang
>* David Yozie  
>* Ed Espino
>* Entong Shen  
>* Foyzur Rahman
>* Goden Yao
>* Gregory Chase
>* Hong Wu  
>* Hongxu Ma
>* Hubert Zhang 
>* Ivan Weng
>* Jesse Zhang  
>* Jiali Yao
>* Jun Aoki 
>* Kavinder Dhaliwal
>* Lav Jain 
>* Lei Chang
>* Lili Ma  
>* Lirong Jian  
>* Lisa Owen
>* Ming Li  
>* Mohamed Soliman  
>* Newton Alex  
>* Noa Horn 
>* Oleksandr Diachenko  
>* Paul Guo 
>* Radar Da Lei 
>* Roman Shaposhnik 
>* Ruilong Huo  
>* Shivram Mani 
>* Shubham Sharma   
>* Tushar Pednekar  
>* Venkatesh Raghavan   
>* Vineet Goel  
>* Wen Lin  
>* Xiang Sheng  
>* Yi Jin   
>* Zhanwei Wang 
>* Zhenglin Tao 
> 
>   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lei Chang
>   be appointed to the office of Vice President, Apache HAWQ, 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 HAWQ PMC be and hereby is
>   tasked with the creation of a set of bylaws intended to
>   encourage open development and increased participation in the
>   Apache HAWQ Project; and be it further
> 
>   RESOLVED, that the Apache HAWQ Project be and hereby
>   is tasked with the migration and rationalization of the Apache
>   Incubator HAWQ podling; and be it 

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[P. Taylor Goetz]

Repeating my +1 (binding)

-Taylor

> On May 11, 2018, at 8:53 PM, Dave Fisher  wrote:
> 
> IPMC - please note that this vote received 3 IPMC votes from the mentors on 
> the dev list.
> 
> I’ll repeat my +1 (binding)
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On May 11, 2018, at 4:09 PM, Matteo Merli  wrote:
>> 
>> This is the third release candidate for Apache Pulsar, version
>> 2.0.0-rc1-incubating.
>> 
>> Pulsar is a highly scalable, low latency messaging platform running on
>> commodity hardware. It provides simple pub-sub semantics over topics,
>> guaranteed at-least-once delivery of messages, automatic cursor management
>> for subscribers, and geo-replication.
>> 
>> Link to the voting thread on pulsar dev list:
>> https://lists.apache.org/thread.html/79e78ddc1e1348b8a625e6dcc485cdbb145030fa6546546149d6b1a4@%3Cdev.pulsar.apache.org%3E
>> 
>> It fixes the following issues:
>> https://github.com/apache/incubator-pulsar/milestone/12?closed=1
>> 
>> *** Please download, test and vote on this release. This vote will stay open
>> for at least 72 hours ***
>> 
>> Note that we are voting upon the source (tag), binaries are provided for
>> convenience.
>> 
>> Source and binary files:
>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-3/
>> 
>> SHA-1 checksums:
>> b1a392c5935448da195eb927520fe6deb20182fc
>> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
>> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
>> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
>> 
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
>> 
>> The tag to be voted upon:
>> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef)
>> https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-incubating-candidate-3
>> 
>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>> 
>> Please download the the source package, and follow the README to build
>> and run the Pulsar standalone service.
>> 
>> -- 
>> Matteo Merli
>> 
>> -- 
>> Matteo Merli
>> 
> 
> 
> -
> 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] Graduate Traffic Control to a top level project

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Apr 20, 2018, at 2:02 PM, Dave Neuman  wrote:
> 
> [ ] +1 Graduate Traffic Control from the incubator



signature.asc
Description: Message signed with OpenPGP

Re: Review mailing list membership?

[P. Taylor Goetz]

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



signature.asc
Description: Message signed with OpenPGP

Re: Review mailing list membership?

[P. Taylor Goetz]

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  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 . (I looked at 
> https://mail-archives.apache.org/mod_mbox/druid-dev/ 
>  for instance, and 
> emailed 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  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  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  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
 
>>> 
> 

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

Re: [VOTE] Retire the HTrace Podling

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Apr 16, 2018, at 9:28 AM, Ralph Goers  wrote:
> 
> +1 (binding)
> 
> Ralph
> 
>> On Apr 11, 2018, at 4:40 PM, lewis john mcgibbney  wrote:
>> 
>> Hi Folks,
>> Please excuse the error on my part, which essentially missed this important
>> stage of VOTE'ing on general@ for official retirement of the HTrace Podling.
>> However, we are here now. The VOTE will be open for a minimum of 72 hours.
>> The previous community VOTE [0] took place on the HTrace dev@ list with a
>> lot of participation. I closed this off today with the RESULT [1].
>> I would like to explicitly note that a subsequent parallel thread was
>> initiated [2] which essentially suggested HTrace staying alive as a
>> Subproject. Unfortunately this thread petered out... my inclination is that
>> this outcome is that for HTrace to become a Subproject, essentially work
>> would need to be done by some people... which brings us back to the initial
>> reason for drafting the retirement email thread in the first place e.g.
>> no-one has the time to work on HTrace any more.
>> Please DISCUSS or VOTE as below
>> 
>> [ ] +1 retire the HTrace podling
>> [ ] -1 NOT NOT retire the HTrace podling (please provide justification)
>> 
>> Thanks,
>> Lewis
>> P.S. Here is my +1
>> 
>> 
>> [0] VOTE: https://s.apache.org/2sGB
>> [1] RESULT: https://s.apache.org/e22i
>> [2] https://s.apache.org/MlLn
>> 
>> --
>> http://home.apache.org/~lewismc/
>> http://people.apache.org/keys/committer/lewismc
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Accept Druid into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Feb 22, 2018, at 2:03 PM, Julian Hyde  wrote:
> 
> Hi all,
> 
> After some discussion on the Druid proposal[1], I'd like to
> start a vote on accepting Druid into the Apache Incubator,
> per the ASF policy[2] and voting rules[3].
> 
> A vote for accepting a new Apache Incubator podling is a
> majority vote for which only Incubator PMC member votes are
> binding. Votes from other people are also welcome as an
> indication of people's enthusiasm (or lack thereof).
> 
> Please do not use this VOTE thread for discussions.  If
> needed, start a new thread instead.
> 
> This vote will run for at least 72 hours. Please VOTE as
> follows:
> [ ] +1 Accept Druid into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Druid into the Apache Incubator
>because ...
> 
> The proposal is listed below, but you can also access it on
> the wiki[4].
> 
> Julian
> 
> [1] 
> https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
> 
> [2] 
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> 
> [3] http://www.apache.org/foundation/voting.html
> 
> [4] https://wiki.apache.org/incubator/DruidProposal
> 
> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Retire Wave

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jan 8, 2018, at 1:56 PM, John D. Ament  wrote:
> 
> All,
> 
> This is a call to vote for the retirement of the Wave podling.
> 
> The podling has positively voted to retire [1].  I now call upon the IPMC
> to confirm this retirement.
> 
> [ ] +1 to retire
> [ ] +/- 0 to retire
> [ ] -1 don't retire because...
> 
> The podling is working on a migration plan, it seems they will move the
> code to github somewhere, and will work on it as seen fit there.
> 
> John
> 
> [1]:
> https://lists.apache.org/thread.html/fe4b7a240facbebeded29d7d9d8c733c0e5e624f07b7a110887c2f16@%3Cwave-dev.incubator.apache.org%3E



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Graduate Apache Mnemonic project from Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Sep 19, 2017, at 1:16 PM, Gang(Gary) Wang  wrote:
> 
> Hello IPMC and everyone,
> 
> The Mnemonic community has voted on its Dev list to graduate, The vote
> passed with
> 14 +1s (including  +9s from the PPMC) and 0 -1s.
> 
> Here is the vote result thread in the Dev list:
> https://lists.apache.org/thread.html/bbc187108b73d57fddec0d6a6c294527b626c7c439a7cdab991ea84e@%3Cdev.mnemonic.apache.org%3E
> 
> and the vote thread:
> https://lists.apache.org/thread.html/a49e82d507bb00839413e90b05cb8b9448ea242aeb021622f5deb323@%3Cdev.mnemonic.apache.org%3E
> 
> With the discussion having settled down, I would now like to call for
> a recommendation VOTE to present the ASF board with the following
> resolution
> to graduate from incubation and establish Apache Mnemonic
> as a top-level project (TLP).
> https://lists.apache.org/thread.html/94664579041db58bfe2893af6e9d54957652653b278d4007e914c672@%3Cgeneral.incubator.apache.org%3E
> 
> Apache Mnemonic entered incubation in March 2016. Since then there have
> been nine releases and four committers and two PMC candidate members
> have been added to the project. For each release, source artifacts
> have been made available. Based on the completed maturity evaluation,
> we believe that the project is ready to graduate from the incubator.
> More checklist info about graduation, please refer to
> https://cwiki.apache.org/confluence/display/MNEMONIC/Maturity+Evaluation
> 
> Please vote on whether to graduate Mnemonic from incubator and
> recommend the following graduation resolution to the ASF Board.
> 
> [ ] +1 Graduate Apache Mnemonic from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Apache Mnemonic from the Incubator because...
> 
> This VOTE will be open for at least 72 hours.
> Thanks to all Mentors and Apache Mnemonic Project members
> for their support and contributions again.
> 
> The full text of the resolution is below.
> If approved by the Apache Incubator PMC members,
> the proposed resolution will be submitted to
> the Board of Directors for their consideration.
> --
> Establish the Apache Mnemonic 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 transparent nonvolatile hybrid memory oriented library for
> Big data, High-performance computing, and Analytics.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Mnemonic Project", be and hereby is
> established pursuant to Bylaws of the Foundation, and be it further
> 
> RESOLVED, that the Apache Mnemonic Project be and hereby is responsible
> for the creation and maintenance of software related to a transparent
> nonvolatile hybrid memory oriented library for Big data,
> High-performance computing and Analytics; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Mnemonic" 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 Mnemonic
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Mnemonic
> 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 Mnemonic
> Project:
> 
> * Andrew Kyle Purtell  
> * Debojyoti Dutta  
> * Gang Wang
> * Hao Cheng
> * James R. Taylor  
> * Johnu George 
> * Kai Zheng
> * Patrick D. Hunt  
> * Rakesh Radhakrishnan 
> * Uma Maheswara Rao G  
> * Yanping Wang 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gang Wang be appointed to
> the office of Vice President, Apache Mnemonic, 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 Mnemonic PMC be and hereby is tasked
> with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Mnemonic Project;
> and be it further
> 
> RESOLVED, that the Apache Mnemonic Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Mnemonic
> podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to 

Re: Heron Grant Status & Monthly Reporting

[P. Taylor Goetz]

;>>> Gearpump has been incubating since 2016-03-08.
>>>>>> 
>>>>>> Three most important issues to address in the move towards
>> graduation:
>>>>>> 
>>>>>> 1. Have frequent release cycles.
>>>>>> 2. Continue to evolve community interest and support.
>>>>>> 3. Increase user adoption.
>>>>>> 
>>>>>> 
>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>> be
>>>> aware
>>>>>> of?
>>>>>> - None.
>>>>>> 
>>>>>> 
>>>>>> How has the community developed since the last report?
>>>>>> - Gearpump took part in Google Summer of Code 2017 project and it
>> has
>>>> been
>>>>>> succeffully accompolished by student, Buddhi Ayesha, who is
>> interested
>>>> in
>>>>>> making more contributions beyond the project.
>>>>>> 
>>>>>> How has the project developed since the last report?
>>>>>> - 32 issues created and 20 issues resolved.
>>>>>> - Gearpump Runner has been merged into Apache Beam trunk.
>>>>>> - An experimental SQL support has been added and state management is
>>>> under
>>>>>> development.
>>>>>> 
>>>>>> How would you assess the podling's maturity?
>>>>>> 
>>>>>> [ ] Initial setup
>>>>>> [ ] Working towards first release
>>>>>> [ ] Community building
>>>>>> [ ] Nearing graduation
>>>>>> [ ] Other:
>>>>>> 
>>>>>> Date of last release:
>>>>>> 2017-07-17
>>>>>> 
>>>>>> 
>>>>>> When were the last committers or PMC members elected?
>>>>>> No new committers or PMC members elected yet.
>>>>>> 
>>>>>> Signed-off-by:
>>>>>> 
>>>>>> [X](gearpump) Jean-Baptiste Onofré
>>>>>>   Comments:
>>>>>> [ ](gearpump) Andrew Purtell
>>>>>>   Comments:
>>>>>> [ ](gearpump) Jarek Jarcec Cecho
>>>>>>   Comments:
>>>>>> [ ](gearpump) Reynold Xin
>>>>>>   Comments:
>>>>>> [ ](gearpump) Todd Lipcon
>>>>>>   Comments:
>>>>>> [ ](gearpump) Xuefu Zhang
>>>>>>   Comments:
>>>>>> 
>>>>>> IPMC/Shepherd notes:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Gobblin
>>>>>> 
>>>>>> Gobblin is a distributed data integration framework that simplifies
>>>> common
>>>>>> aspects of big data integration such as data ingestion, replication,
>>>>>> organization and lifecycle management for both streaming and batch
>>> data
>>>>>> ecosystems.
>>>>>> 
>>>>>> Gobblin has been incubating since 2017-02-23.
>>>>>> 
>>>>>> Three most important issues to address in the move towards
>> graduation:
>>>>>> 
>>>>>> 1. Cut our first release
>>>>>> 
>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>> be
>>>>>> aware of?
>>>>>> 
>>>>>> None
>>>>>> 
>>>>>> How has the community developed since the last report?
>>>>>> 
>>>>>> * We are working towards our first release.
>>>>>> * Email stats for last month:
>>>>>> u...@gobblin.incubator.apache.org : 14
>>>>>> d...@gobblin.incubator.apache.org : 259
>>>>>> * There have been 54 Commits in last month:
>>>>>>  git log --format='%ci' | grep -cE '2017-0(8)'
>>>>>> * 30 of those commits were by non-committers:
>>>>>> git log --format='%ae %ci' | grep -E '2017-0(8)' | cut -d ' ' -f 1
>> |
>>>>>> sort | uniq -c | sort -n
>>>>>> * A video conference based meetup happened last month.
>>>>>> 
>>>>>> How has the project developed since the last report?
>>>>>> 
>>>>>> * Site has been setup.
>>>>>> * Apache wiki has been populat

Fwd: [DRAFT] Incubator PMC Board Report - September 2017

[P. Taylor Goetz]

Forgot to cc general@...

Begin forwarded message:

> From: "P. Taylor Goetz" <ptgo...@gmail.com>
> Date: September 12, 2017 at 8:10:55 PM EDT
> To: d...@pulsar.incubator.apache.org
> Subject: Re: [DRAFT] Incubator PMC Board Report - September 2017
> 
> I'll also sign off/comment on Heron and Pulsar shortly.
> 
>> On Sep 12, 2017, at 6:02 PM, Dave Fisher <dave2w...@comcast.net> wrote:
>> 
>> Pulsar is now signed off and also shepherd notes done.
>> 
>> Heron is a little slow moving over should we keep them monthly until the 
>> repos is moved?
> 
> In my opinion, yes. Will comment on the report.
> 
>> 
>> Regards,
>> Dave
>> 
> 
> -Taylor
> 
>>> On Sep 12, 2017, at 2:40 PM, Dave Fisher <dave2w...@comcast.net> wrote:
>>> 
>>> I'll be signing Pulsar shortly.
>>> 
>>> Sent from my iPhone
>>>> 

Re: [DISCUSS] Notice to Podlings RE Facebook BSD+Patents License

[P. Taylor Goetz]

Hi John,

The only thing I would add is that it might help to point out some of the 
projects that use the Facebook BSD+Patents License — namely React which 
constitutes the greatest exposure among projects.

-Taylor

> On Aug 19, 2017, at 11:31 PM, John D. Ament  wrote:
> 
> All,
> 
> I plan to send the below email, or some form of it, to all podlings in the
> coming days.  I don't think anything on here is private or confidential so
> I don't think it's an issue discussing it in the open.  Podlings who may be
> reading this, please understand that this is a draft only.  Feel free to
> discuss and provide input on this list as well.  Do not take the contents
> of this email as a final decision or path forward until you have received
> it on your dev list.
> 
> ---
> Dear Podlings,
> 
> I'm writing to inform you of a legal decision that has been made that may
> impact your podling.  During a recent request [1], the foundation reviewed
> the license on a project called RocksDB which at that time was licensed
> under the Facebook BSD+Patents License.  Based on the foundation's review,
> it was determined that software that used this license fell under what we
> call Category X, the category for all licenses that may not be included in
> Apache products.  In turn, RocksDB was relicensed to the Apache license.
> This license is used in a number of other Facebook Open Source projects.  A
> request was then made to relicense other software under the Apache
> License.  This request was declined.
> 
> I wanted to reach out to all podlings at this point to reiterate the goals
> of incubation.  We don't expect that you have perfect releases while in the
> incubator, but that by the time you exit the incubator you are complying
> with foundation policy around all of your releases.  So what does this
> mean? Basically, while you are incubating if you are using a project that
> is shipped with this license you should follow these guidelines:
> 
> - While producing a source release, ensure that no source code with this
> license is in your release.
> - Avoid creating a binary release with this software in it.
> - Podlings who are not already using software with this license should not
> add it as a dependency.
> - By the time you graduate, you must have removed this as a dependency
> within your project.
> 
> Basically, we are counting on the fact that a disclaimer is present in your
> release bundle to mitigate the foundation defined incorrect release
> structure.  There may be some podlings that feel that the libraries in
> question are critical to their functionality.  Many of these libraries have
> alternatives to consider which you may find useful.  However, if you get to
> a point where you feel that switching is a blocker to being a successful
> project, please bring it up with your mentors and/or other IPMC members so
> that we can help you plan for a way forward.
> 
> Regards,
> 
> John D. Ament
> VP, Apache Incubator
> 
> [1]: https://issues.apache.org/jira/browse/LEGAL-303


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

Re: [VOTE] Apache Pulsar 1.19.0-incubating Release Candidate 0

[P. Taylor Goetz]

+1 (binding)

- DISCLAIMER exists
- L look good
- spot checked for ALv2 license headers
- no binaries in source dist
- can build from source (though I had to skip tests due to a failure)
- checksum and signature good

> On Aug 4, 2017, at 3:10 PM, Josh Elser  wrote:
> 
> It looks like you're missing a Copyright propagation for work by Trevor 
> Robinson in your NOTICE file. The license headers are for ASL (you are 
> correct to have omitted this from LICENSE), but I believe you still need to 
> propagate the copyright notice to your NOTICE in the src release for the 
> "com/scurrilous/circe" work you include in src-form.


In addition to what Josh mentioned, should Yahoo be listed in the NOTICE file? 
I know it has been listed in other projects Yahoo has contributed to.

-Taylor

> On Aug 3, 2017, at 8:23 PM, Matteo Merli  wrote:
> 
> This is the first release candidate for Apache Pulsar, version
> 1.19.0-incubating.
> 
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management
> for subscribers, and cross-datacenter replication.
> 
> Link to the voting thread from the dev@pulsar mailing list:
> https://lists.apache.org/thread.html/396ffc9c8fe171bc272691414a39307e0929d40639d9ec631ea3aa15@%3Cdev.pulsar.apache.org%3E
> 
> Major changes included in this release are:
> * Added stateless Pulsar proxy
> * Support for non-persistent topics
> * Upgraded RocksDB to comply with ASF policy
> * Instrumentation of ZooKeeper client to expose metrics
> * Fixes for TLS auth in WebSocket proxy
> 
> Complete list of changes can be found at:
> https://github.com/apache/incubator-pulsar/milestone/8?closed=1
> 
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-1.19.0-incubating-candidate-0/
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1000/
> 
> The tag to be voted upon:
> v1.19.0-incubating-candidate-0 (5125279b50f7a3da8c211b698580e1d2f4dd65e2)
> 
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> 
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
> 
> This vote will stay open for at least 72 hours.
> 
> Thanks!
> Matteo
> 
> --
> Matteo Merli
> 
> -- 
> Matteo Merli
> 


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

Re: Urgent: Regarding Java package name change to org.apache.*

[P. Taylor Goetz]

When Storm was incubating, our package names started with backtype.* and 
storm.* and it stayed that way through graduation and there was never any 
mention of a need to change. In fact, Storm only moved to org.apache.* with the 
1.0 release in April 2016, about 1.5 years after graduation.

There are implications for Heron since it maintains backtype.* and storm.* 
packages presumably for backward compatibility with older versions of Storm. 
I’m not sure what that means.

I think it would be prudent to better clarify and document the policy around 
this.

-Taylor

> On Aug 3, 2017, at 12:34 PM, John D. Ament  wrote:
> 
> One caveat - if your packages are "com.theoldcompany.someproject" they
> should be renamed to "org.apache.someproject" before graduation.  If you
> have "org.someproject" already or just "someproject" as your package names,
> that's not a naming issue so I don't see that ever blocking graduation.
> 
> John
> 
> On Thu, Aug 3, 2017 at 12:25 PM Alex Harui  wrote:
> 
>> OK, so to summarize a more refined recommendation:
>> 
>> 1) package names with reverse domains MUST be renamed before graduation or
>> have an IPMC approved plan for renaming
>> 2) Projects who expect that their future users outnumber current users are
>> highly encouraged to rename packages
>> 3) Other projects are not required to rename packages and backward
>> compatibility is sufficient reason to not rename packages.
>> 
>> Or should #2 also be a MUST?
>> 
>> -Alex
>> 
>> On 8/3/17, 8:34 AM, "Andy Seaborne"  wrote:
>> 
>>> 
>>> 
>>> On 03/08/17 15:51, Julian Hyde wrote:
 It rarely comes down to the IPMC or the Board dictating how a project
 names its java classes (does anyone recall an instance?), so it’s mainly
 the project’s discretion. In my opinion, where the project is on its
 adoption curve is an important consideration.
>>> 
>>> +1
>>> 
 Most projects that enter the incubator are early on the adoption curve.
 Their future users outnumber their current users. The earlier these
 projects make the change to org.apache, the fewer people they will
 ultimately impact. It seems that gobblin is in this category.
 
 A few projects, such as Flex, are already near the top of their
 adoption curve. The cost/benefit of renaming is not as compelling.
>>> 
>>> Jena was not early on the adoption curve. Long term compatibility has
>>> been, and is, a major element of the project culture.  Importantly,
>>> there are active users who answer questions (here, elsewhere), external
>>> web tutorials, books etc referring to the pre-ASF API.  We have a
>>> responsibility to them as well.
>>> 
>>> "add an API" is more stuff that a small set of volunteer contributors
>>> (Jena has had no paid contributors working on) could not have coped
>>> with.  If a project has the capacity, sure. Not all project will.
>>> 
>>> Set the expectations too high and it is implicitly a filter for a
>>> certain kind of project in size and structure.
>>> 
>>>Andy
>>> 
>>> 
 
 Julian
 
 
> On Aug 3, 2017, at 7:37 AM, Alex Harui 
> wrote:
> 
> From the peanut gallery:
> 
> Does the PPMC get to decide what constitutes a "very good reason" or
> does
> the IPMC and after graduation, the board?
> 
> Flex has not changed its packages in the 5 years at Apache.  We felt
> backward compatibility was and is a "very good reason".  It was way
> more
> important to not require folks to alter their code in order to move to
> the
> Apache versions of Flex.  Also, we are not using Java/Maven so there
> isn't
> really a shading option.
> 
> On the other hand, it seems like it could be confusing for Apache
> projects
> to have packages starting with "com.".  Flex's packages start with
> "mx" or
> "spark" (the component set names).
> 
> Seems like a more refined guidance would be that:
> 1) packages starting with "com" (and maybe
> org.somethingOtherThanApache)
> should be changed as soon as possible/practical
> 2) there is no recommendation for other package prefixes
> 
> My 2 cents,
> -Alex
> 
> On 8/3/17, 5:42 AM, "Shane Curcuru"  > wrote:
> 
>> John D. Ament wrote on 8/2/17 9:13 PM:
>>> On Wed, Aug 2, 2017 at 8:54 PM Roman Shaposhnik
>>> 
>>> wrote:
>>> 
 On Wed, Aug 2, 2017 at 5:40 PM, Abhishek Tiwari 
 wrote:
> Hi all,
> 
> In regards to the recently incubated project - Gobblin, we were
> wondering
> about the policy around renaming Java package names to
> org.apache.* Is
 it a
> mandatory requirement or good to have?
> 
> The reason to ask this is that while we see many 

Re: [VOTE] Graduate Apache Streams project from Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jul 10, 2017, at 11:09 AM, sblackmon  wrote:
> 
>  
> In concert with the discussion started last week [1], please vote on the 
> draft resolution which establishes Apache Streams as a new top-level project 
> at the Apache Software Foundation, as follows:  
> 
> [ ] +1, Graduate Apache Streams from the Incubator.  
> [ ] +0, Don't care.  
> [ ] -1, Don't graduate Apache Streams from the Incubator (provide details)  
> 
> The full text of the resolution is below.  
> 
> If approved by the Apache Incubator PMC members, the proposed resolution will 
> be submitted to the Board of Directors for their consideration.  
> 
> Thanks ! 
> 
> [1] 
> https://lists.apache.org/thread.html/60d676ad7b190323f8479bccff8ae996f98bf5fcd0d0ff4d54b71006@
> 
> Establish the Apache Streams 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 
> interoperability of online profiles and activity feeds. 
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to 
> be known as the "Apache Streams Project", be and hereby is established 
> pursuant to Bylaws of the Foundation; and be it further 
> 
> RESOLVED, that the Apache Streams Project be and hereby is responsible for 
> the creation and maintenance of software related to interoperability of 
> online profiles and activity feeds; and be it further 
> 
> RESOLVED, that the office of "Vice President, Apache Streams" 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 Streams Project, and to have 
> primary responsibility for management of the projects within the scope of 
> responsibility of the Apache Streams 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 Streams Project:
> 
>  * Stephen D Blackmon   
>  * Robert Baker Douglas 
>  * Ate Douma
>  * Ryan Edward Ebanks   
>  * Matt Franklin
>  * Joey Frazee  
>  * Trevor Grant 
>  * Suneel Marthi
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephen D Blackmon be appointed 
> to the office of Vice President, Apache Streams, 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 Streams PMC be and hereby is tasked with 
> the creation of a set of bylaws intended to encourage open development and 
> increased participation in the Apache Streams Project; and be it further 
> 
> RESOLVED, that the Apache Streams Project be and hereby is tasked with the 
> migration and rationalization of the Apache Incubator Streams podling; and be 
> it further 
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator 
> Streams 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
> 


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

Re: [VOTE] Retire Sirona

[P. Taylor Goetz]

+1 for retirement.

We’ve been marching in that direction for a while. Every time it’s come up 
(multiple times) there’s a little push to move forward, but nothing ever comes 
of it. The report situation is telling. I think it’s safe to say Apache isn’t 
the right fit, and the community should explore other options if it wants to 
move the project forward.

-Taylor

> On Jun 26, 2017, at 12:50 PM, John D. Ament  wrote:
> 
> All,
> 
> This is a call to vote the Sirona podling.
> 
> A vote was called for on the dev list for Sirona [1], of which one mentor
> commented and that's all.
> 
> Sirona at this point is behind 6 months on reports, has shown little
> activity since joining the incubator.  Its not clear there are 3 PPMCs
> available for a vote if need be.  Based on the prior discussions ([2] &
> [3]) and these items, I'd like to call for a vote and unilateral decision
> by the IPMC to retire Sirona.
> 
> [ ] +1 to retire Sirona
> [ ] -1 don't retire Sirona because...
> 
> Here is my +1.
> 
> John
> 
> [1]:
> https://lists.apache.org/thread.html/673daa1452150ed5ef0df4aa77f587dbac6e5a4a63670c6bf4809b17@%3Cdev.sirona.apache.org%3E
> [2]:
> https://lists.apache.org/thread.html/0a70d486680f0339bfcb4baae23c2540095fda90ca83eb414104a6fd@%3Cgeneral.incubator.apache.org%3E
> [3]:
> https://lists.apache.org/thread.html/438298290de9a3573b5e315b12e77191b27f8d91b50cf9f97e90cba8@%3Cgeneral.incubator.apache.org%3E


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

Re: [VOTE] Heron to enter Apache Incubator

[P. Taylor Goetz]

 in the streaming compute space and we are
> long time supporters of the Apache brand. This proposal is not for the
> purpose of generating publicity through. Rather, the primary benefits to
> joining Apache are those of community building and open decision making
> outlined in the Rationale section.
> 
> == Documentation ==
> 
> This proposal exists online as
> http://wiki.apache.org/incubator/HeronProposal. Extensive documentation can
> be found on github at https://twitter.github.io/heron and the source code
> is well documented.
> 
> == Source and Intellectual Property Submission Plan ==
> 
> The Heron codebase is currently hosted on Github:
> https://github.com/twitter/heron. During incubation, the codebase will be
> migrated to Apache infrastructure. The source code is already ASF 2.0
> licensed.
> 
> == External Dependencies ==
> 
> All external libraries have ASF 2.0 compatible licenses except for pylint.
> The pylint library is GPL licensed, but is only used for pre-build Python
> style checks and is neither bundled with, nor relied upon by, the Heron
> source or binary release artifacts.
> 
> == Cryptography ==
> 
> Heron does not use any cryptography libraries.
> 
> = Required Resources =
> 
> == Mailing lists ==
> 
> * priv...@heron.incubator.apache.org (with moderated subscriptions)
> * d...@heron.incubator.apache.org
> * comm...@heron.incubator.apache.org
> * u...@heron.incubator.apache.org
> 
> == Subversion Directory ==
> 
> Git is the preferred source control system: git://git.apache.org/heron
> 
> == Issue Tracking ==
> 
> JIRA: Heron (HERON)
> 
> == Initial Committers ==
> 
> * Andrew Jorgensen (andrew at andrewjorgensen dot com)
> * Ashvin Agrawal (ashvin at apache dot org)*
> * Avrilia Floratou (avrilia dot floratou at gmail dot com)
> * Bill Graham (billgraham at apache dot org)*
> * Brian Hatfield (bmhatfield at gmail dot com)
> * Chris Kellogg (cckellogg at gmail dot com)
> * Huijun Wu (huijun dot wu dot 2010 at gmail dot com)
> * Karthik Ramasamy (karthik at gmail dot com)
> * Maosong Fu (maosongfu at gmail dot com)
> * Neng Lu(freeneng at gmail dot com)
> * Runhang Li (obj dot runhang at gmail dot com)
> * Sanjeev Kulkarni (sanjeevrk at gmail dot com)
> * Supun Kamburugamuve (supun at apache dot org)*
> * Thomas Sun (tom dot ssf at gmail dot com)
> * Yaliang Wang (yaliang dot w dot wang at ieee dot org)
> 
> == Affiliations ==
> 
> * Andrew Jorgensen (Google)
> * Ashvin Agrawal (Microsoft)
> * Avrilia Floratou (Microsoft)
> * Bill Graham (Twitter)
> * Brian Hatfield (Google)
> * Chris Kellogg (Twitter)
> * Huijun Wu (Twitter)
> * Karthik Ramasamy (Streamlio)
> * Maosong Fu (Twitter)
> * Neng Lu (Twitter)
> * Runhang Li (Twitter)
> * Sanjeev Kulkarni (Streamlio)
> * Supun Kamburugamuve (Indiana University)
> * Thomas Sun (Twitter)
> * Yaliang Wang (Twitter)
> 
> = Sponsors =
> 
> == Champion ==
> 
> * Julien Le Dem (julien at apache dot org)
> 
> == Nominated Mentors ==
> 
> * Jake Farrell (jfarrell at apache dot org)
> * Jacques Nadeau (jacques at apache dot org)
> * Julien Le Dem (julien at apache dot org)
> * P. Taylor Goetz (ptgoetz at apache dot org)
> 
> == Sponsoring Entity ==
> 
> The Apache Incubator
> 
> == Footnotes ==
> 
> * 1 - Papers detailing Heron are available at
> http://dl.acm.org/citation.cfm?id=2742788 and
> http://sites.computer.org/debull/A15dec/p15.pdf.
> * 2 - http://home.apache.org/phonebook.html?uid=billgraham
> * 3 - http://home.apache.org/phonebook.html?uid=ashvin
> * 4 - http://home.apache.org/phonebook.html?uid=supun


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

Re: [VOTE] Retire the Blur Podling

[P. Taylor Goetz]

+1 with a reminder that retiring is not a failure, just another path out of the 
Incubator.

-Taylor



> On Jun 18, 2017, at 12:30 PM, John D. Ament  wrote:
> 
> All,
> 
> This is a call to vote to retire the Blur podling.  Blur has been
> incubating for nearly 5 years and has not grown a community.  It is
> mutually felt that it is time to retire Blur.  There was a successful vote
> on the podling's dev list at [1].  I'm now calling for the Incubator vote
> on the same subject.
> 
> [ ] +1 to retire Blur
> [ ] -1 Don't retire Blur because...
> 
> Here is my own +1
> 
> John
> 
> [1]:
> https://lists.apache.org/thread.html/d6e8050a0f94fd9871e69a529d50690c639c9aa0f5d27ef8b52109c1@%3Cblur-dev.incubator.apache.org%3E

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

Re: [PROPOSAL] Heron

[P. Taylor Goetz]

Thanks for the clarification Bill!

-Taylor


> On Jun 15, 2017, at 1:24 PM, Bill Graham <billgra...@gmail.com> wrote:
> 
> Hi Taylor,
> 
> The Heron team engaged with members of the Apache Storm community through
> private channels before the project was made available as open source. We
> recognize this is not the ideal approach and going forward we will use more
> collaborative methods as we progress and grow the Heron community.
> 
> One of our goals during incubation will be to use open forums of
> communication, like the Apache mailing lists, and work to foster a truly
> collaborative environment for both Apache Storm and Heron community members
> to work within together.
> 
> The Fabric team at Google uses Heron extensively.
> 
> thanks,
> Bill
> 
> On Thu, Jun 15, 2017 at 10:42 AM, Debo Dutta (dedutta) <dedu...@cisco.com>
> wrote:
> 
>> Am happy to help too!
>> 
>> Thx
>> Debo
>> 
>> Sent from my iPhone
>> 
>>> On Jun 14, 2017, at 8:05 PM, William Markito Oliveira <
>> william.mark...@gmail.com> wrote:
>>> 
>>> Howdy!
>>> 
>>> If Heron is looking for some help around incubation process, I'd love to
>>> help while Geode experience is still fresh in my mind and given that
>> it's a
>>> project/space that I do have interest. Since I'm not an ASF member, I
>> don't
>>> think I can offer to be a mentor, but can probably still help and
>>> participate on the process.
>>> 
>>> Thanks!
>>> 
>>>> On Wed, Jun 14, 2017 at 7:54 PM, P. Taylor Goetz <ptgo...@gmail.com>
>> wrote:
>>>> 
>>>> Hi Bill/Supun,
>>>> 
>>>> Sorry for not being a little more clear. I was asking more about how the
>>>> Heron community would seek to engage with Storm community at the
>>>> *community* level as opposed to the technical level (i.e. “Community
>> over
>>>> Code”).
>>>> 
>>>> I’ve been asked by many why this has never happened, and have always
>>>> struggled to answer. Maybe you could help answer that question as well
>> as
>>>> if and how that might change if Heron were to incubate.
>>>> 
>>>> Another quick question: The proposal mentions Heron being used in
>>>> production at Google, but some Google employees I recently spoke to
>> seemed
>>>> to contradict that. Could you explain? Note that’s nothing that would
>>>> preclude the project from incubating, I’m just curious.
>>>> 
>>>> -Taylor
>>>> 
>>>>> On Jun 14, 2017, at 7:35 AM, Supun Kamburugamuve <supu...@gmail.com>
>>>> wrote:
>>>>> 
>>>>> Hi Taylor,
>>>>> 
>>>>> For me, one of the interesting differences between Heron and Storm is
>> the
>>>>> execution model. Storm uses a shared memory model while Heron uses a
>>>>> process based model. It will be interesting to see how these two
>> evolve.
>>>>> 
>>>>> Thanks,
>>>>> Supun..
>>>>> 
>>>>> On Mon, Jun 12, 2017 at 4:15 PM, Bill Graham <billgra...@gmail.com>
>>>> wrote:
>>>>> 
>>>>>> Hi Taylor,
>>>>>> 
>>>>>> Thanks for the mentor offer, we'd be glad to have your help.
>>>>>> 
>>>>>> I think the best place for collaboration would be around the evolution
>>>> of
>>>>>> the API. In addition we plan to look more into DSL solutions which we
>>>> could
>>>>>> potentially collaborate on. This could be Trident, or Beam or
>> something
>>>>>> else, but there could be synergies for future development here.
>>>>>> 
>>>>>> thanks,
>>>>>> Bill
>>>>>> 
>>>>>> On Fri, Jun 9, 2017 at 8:53 PM, P. Taylor Goetz <ptgo...@gmail.com>
>>>> wrote:
>>>>>> 
>>>>>>> Hi Bill,
>>>>>>> 
>>>>>>> Could you comment on how/if the Heron community would be willing to
>>>> work
>>>>>>> with the Storm community? I've seen a number of new features in Storm
>>>>>> being
>>>>>>> ported to Heron, but I have yet to see any attempt by the Heron
>>>> community
>>>>>>> to engage with the Apache Storm community.
>>>>>>> 
>>

Re: [PROPOSAL] Heron

[P. Taylor Goetz]

Hi Bill/Supun,

Sorry for not being a little more clear. I was asking more about how the Heron 
community would seek to engage with Storm community at the *community* level as 
opposed to the technical level (i.e. “Community over Code”).

I’ve been asked by many why this has never happened, and have always struggled 
to answer. Maybe you could help answer that question as well as if and how that 
might change if Heron were to incubate.

Another quick question: The proposal mentions Heron being used in production at 
Google, but some Google employees I recently spoke to seemed to contradict 
that. Could you explain? Note that’s nothing that would preclude the project 
from incubating, I’m just curious.

-Taylor

> On Jun 14, 2017, at 7:35 AM, Supun Kamburugamuve <supu...@gmail.com> wrote:
> 
> Hi Taylor,
> 
> For me, one of the interesting differences between Heron and Storm is the
> execution model. Storm uses a shared memory model while Heron uses a
> process based model. It will be interesting to see how these two evolve.
> 
> Thanks,
> Supun..
> 
> On Mon, Jun 12, 2017 at 4:15 PM, Bill Graham <billgra...@gmail.com> wrote:
> 
>> Hi Taylor,
>> 
>> Thanks for the mentor offer, we'd be glad to have your help.
>> 
>> I think the best place for collaboration would be around the evolution of
>> the API. In addition we plan to look more into DSL solutions which we could
>> potentially collaborate on. This could be Trident, or Beam or something
>> else, but there could be synergies for future development here.
>> 
>> thanks,
>> Bill
>> 
>> On Fri, Jun 9, 2017 at 8:53 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>>> Hi Bill,
>>> 
>>> Could you comment on how/if the Heron community would be willing to work
>>> with the Storm community? I've seen a number of new features in Storm
>> being
>>> ported to Heron, but I have yet to see any attempt by the Heron community
>>> to engage with the Apache Storm community.
>>> 
>>> I don't think it would be too far off to say that the relationship
>> between
>>> Heron and Apache Storm has been somewhat adversarial. The pre- and
>>> post-open sourcing marketing around Heron seemed, at least to me,
>> somewhat
>>> aggressively negative toward Storm.
>>> 
>>> As a peer to Apache Storm, how would the proposed "Apache Heron"
>> community
>>> work to collaborate with the Storm community? If Heron is adopting API
>>> changes in Storm, then it seems there is an opportunity for
>> collaboration.
>>> 
>>> Don't take any of this as an objection to incubating the project. I would
>>> support it. I would also be willing to be a mentor, if you would consider
>>> taking on another.
>>> 
>>> -Taylor
>>> 
>>>> On Jun 8, 2017, at 1:23 PM, Bill Graham <billgra...@gmail.com> wrote:
>>>> 
>>>> Dear Apache Incubator Community,
>>>> 
>>>> We are excited to share our proposal for discussion and feedback
>>>> for entering Apache Incubation. Heron is a real-time, distributed,
>>>> fault-tolerant stream processing engine.
>>>> 
>>>> Our proposal can be found at https://wiki.apache.org/
>>> incubator/HeronProposal
>>>> and is included below.
>>>> 
>>>> 
>>>> Thank you,
>>>> 
>>>> Bill Graham on behalf of the Heron developers
>>>> 
>>>> 
>>>> # Heron Proposal
>>>> 
>>>> ## Abstract
>>>> Heron is a real-time, distributed, fault-tolerant stream processing
>>> engine
>>>> initially developed by Twitter.
>>>> 
>>>> ## Proposal
>>>> 
>>>> Heron is a real-time stream processing engine built for high
>> performance,
>>>> ease of manageability, performance predictability and developer
>>>> productivity[1]. We wish to develop a community around Heron to
>> increase
>>>> contributions and see Heron thrive in an open forum.
>>>> 
>>>> ## Background
>>>> 
>>>> Heron provides the ability for developers to compose directed acyclic
>>>> graphs (DAGs) of real-time query execution logic (i.e. a topology) and
>>>> submit the topology to execute on a pluggable job scheduling system
>>> (e.g.,
>>>> Apache Aurora, YARN, Marathon, etc). Users can employ either the native
>>>> Heron API or the Apache Storm API to develop the topology. Heron
>> support

Re: [PROPOSAL] Heron

[P. Taylor Goetz]

Hi Bill,

Could you comment on how/if the Heron community would be willing to work with 
the Storm community? I've seen a number of new features in Storm being ported 
to Heron, but I have yet to see any attempt by the Heron community to engage 
with the Apache Storm community.

I don't think it would be too far off to say that the relationship between 
Heron and Apache Storm has been somewhat adversarial. The pre- and post-open 
sourcing marketing around Heron seemed, at least to me, somewhat aggressively 
negative toward Storm.

As a peer to Apache Storm, how would the proposed "Apache Heron" community work 
to collaborate with the Storm community? If Heron is adopting API changes in 
Storm, then it seems there is an opportunity for collaboration.

Don't take any of this as an objection to incubating the project. I would 
support it. I would also be willing to be a mentor, if you would consider 
taking on another.

-Taylor

> On Jun 8, 2017, at 1:23 PM, Bill Graham  wrote:
> 
> Dear Apache Incubator Community,
> 
> We are excited to share our proposal for discussion and feedback
> for entering Apache Incubation. Heron is a real-time, distributed,
> fault-tolerant stream processing engine.
> 
> Our proposal can be found at https://wiki.apache.org/incubator/HeronProposal
> and is included below.
> 
> 
> Thank you,
> 
> Bill Graham on behalf of the Heron developers
> 
> 
> # Heron Proposal
> 
> ## Abstract
> Heron is a real-time, distributed, fault-tolerant stream processing engine
> initially developed by Twitter.
> 
> ## Proposal
> 
> Heron is a real-time stream processing engine built for high performance,
> ease of manageability, performance predictability and developer
> productivity[1]. We wish to develop a community around Heron to increase
> contributions and see Heron thrive in an open forum.
> 
> ## Background
> 
> Heron provides the ability for developers to compose directed acyclic
> graphs (DAGs) of real-time query execution logic (i.e. a topology) and
> submit the topology to execute on a pluggable job scheduling system (e.g.,
> Apache Aurora, YARN, Marathon, etc). Users can employ either the native
> Heron API or the Apache Storm API to develop the topology. Heron supports
> the Storm API for ease of migration, but beyond that Heron’s architecture
> differs considerably from Storm’s.
> 
> Users submit a topology to the scheduler using the Heron client, which uses
> the Heron binary libraries to deploy all daemons required to run and manage
> the topology. The topology therefore has no reliance on centrally managed
> Heron services, only on a generic job scheduling system, which lends itself
> well to be run on top of Apache Aurora/Mesos or Apache Hadoop/YARN (among
> others).
> 
> The scheduler runs each topology as a job consisting of multiple
> containers. One of the containers runs the topology master, responsible for
> managing the topology. The remaining containers each runs a stream manager
> responsible for data routing, a metrics manager that collects and reports
> various metrics and a number of processes called Heron instances which run
> the user-defined logic on the stream of tuples. Parallelism is achieved via
> process-based isolation of Heron instances, which provides predictable
> performance while simplifying debugging. The containers are allocated and
> managed by the scheduler framework based on resource availability of nodes
> in the cluster. The metadata for the topology, such as the physical plan
> and execution details, are stored in the pluggable Heron State Manager
> (e.g. Apache ZooKeeper).
> 
> ## Rationale
> 
> Heron is a general-purpose, modular and extensible platform that can be
> leveraged to support common, real-time analytics use cases. There is an
> increasing demand for open-source, scalable real-time analytics systems. We
> believe that Heron can be leveraged by other organizations to build
> streaming applications that can benefit from its robustness, high
> performance, adaptability to cloud environments and ease of use. Moreover,
> we hope that open-sourcing Heron will help to further evolve the technology
> as the project attracts contributors with diverse backgrounds and areas of
> expertise.
> 
> We believe the Apache foundation is a great fit as the long-term home for
> Heron, as it provides an established process for community-driven
> development and decision making by consensus. This is exactly the model we
> want for future Heron development.
> 
> ## Initial Goals
> 
> * Move the existing codebase, website, documentation, and mailing lists to
> Apache-hosted infrastructure.
> * Integrate with the Apache development process.
> * Ensure all dependencies are compliant with Apache License version 2.0.
> * Incrementally develop and release per Apache guidelines.
> 
> ## Current Status
> 
> Heron is a stable project used in production at Twitter since 2014 and open
> sourced under the ASL v2 license in 2016. The Heron source 

Re: [VOTE] Graduate Apache Mynewt podling

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Jun 7, 2017, at 1:03 AM, Greg Stein <gst...@gmail.com> wrote:
> 
> +1 (binding, Mentor)
> 
>> On Tue, Jun 6, 2017 at 12:52 PM, aditi hilbert <ad...@runtime.io> wrote:
>> 
>> Hello IPMC,
>> 
>> We have had the discussion thread for the graduation of Apache Mynewt
>> podling
>> to TLP open for >72 hours. All the issues raised there have been addressed.
>> I propose that we graduate Apache Mynewt from the incubator.
>> The full text of the proposal is below. The [DISCUSS] thread is:
>> https://lists.apache.org/thread.html/8d8b40b5de2cff4fca1b300870bcf1
>> f5b5ac92b2e4b2a8ddf2db3e17@%3Cgeneral.incubator.apache.org%3E
>> 
>> Please vote on the resolution:
>> 
>> [ ] +1 Graduate Apache Mynewt from the Incubator.
>> [ ] +0 No opinion
>> [ ] -1 Don't graduate Apache Mynewt from the Incubator (please provide
>> the reason)
>> 
>> This VOTE will be opened for the next 72 hours.
>> 
>> Thanks to all Mentors and Apache Mynewt Project members for their
>> support and contributions.
>> 
>> Thanks,
>> Aditi
>> 
>> ---
>> 
>> Resolution:
>> 
>> Establish the Apache Mynewt 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 software related to
>> an embedded OS optimized for networking and built for remote management
>> of constrained devices that are incapable of running either Linux or
>> Android.
>> 
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Mynewt Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>> 
>> RESOLVED, that the Apache Mynewt Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to an embedded OS optimized for networking and built
>> for remote management of constrained devices that are incapable of
>> running either Linux or Android.
>> 
>> RESOLVED, that the office of "Vice President, Apache Mynewt" 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 Mynewt Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Mynewt 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 Mynewt Project:
>> *Justin Mclean” <jmcl...@apache.org>
>> P. Taylor Goetz” <ptgo...@apache.org>,
>> Greg Stein <gst...@apache.org>,
>> Jim Jagielski <j...@apache.org>,
>> Sterling Hughes <sterl...@apache.org>,
>> Marko Kiiskila <ma...@apache.org>,
>> will sanfilippo <w...@apache.org>,
>> Christopher Collins <ccoll...@apache.org>,
>> Vipul Rahane <vipulrah...@apache.org>,
>> Fabio Utzig <ut...@apache.org>,
>> Andrzej Kaczmarek <a...@apache.org>,
>> Michał Narajowski <na...@apache.org>,
>> Szymon Janc <j...@apache.org>,
>> Łukasz Rymanowski <ry...@apache.org>,
>> Neel Natu <n...@apache.org>,
>> Peter Snyder <pete...@apache.org>,
>> Paul Dietrich <paulfdietr...@apache.org,
>> Julian Ingram <jul...@apache.org>,
>> Kevin Townsend <kt...@apache.org>,
>> Aditi Hilbert <ad...@apache.org>
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Justin Mclean
>> be appointed to the office of Vice President, Apache Mynewt, 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 Mynewt PMC be and hereby is
>> tasked with the creation of a set of bylaws intended to
>> encourage open development and increased participation in the
>> Apache Mynewt Project; and be it further
>> 
>> RESOLVED, that the Apache Mynewt Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator Mynewt podling; and be it further
>> 
>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator Mynewt podling encumbered upon the Apache Incubator
>> Project are hereafter discharged.
>> -
>> 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] Graduate Apache MADlib podling

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On May 27, 2017, at 3:56 AM, FENG, Xixuan (Aaron)  
> wrote:
> 
> Greetings IPMC!
> 
> The discussion seems to have died down, so I'm calling the
> vote:  I propose that we graduate Apache MADlib from the Incubator.
> The full text of the proposal is below.  The discuss thread can be found
> here:
>https://lists.apache.org/thread.html/535f9871636f6e10c13e47f1ec6e41
> 5eca7f666e1580d8b762d8a42d@%3Cgeneral.incubator.apache.org%3E
> 
> Please vote on the resolution:
> 
> [ ] +1 Graduate Apache MADlib from the Incubator.
> [ ] +0 No opinion
> [ ] -1 Don't graduate Apache MADlib from the Incubator (please provide
> the reason)
> 
> This VOTE will be opened for the next 72 hours.
> 
> Thanks to all Mentors and Apache MADlib Project members for their
> support and contributions.
> 
> Thanks,
> Aaron.
> 
> Resolution:
> 
> Establish the Apache MADlib 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 scalable, Big Data, SQL-driven machine
> learning framework for Data Scientists.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache MADlib Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache MADlib Project be and hereby is
> responsible for the creation and maintenance of software
> related to a scalable, Big Data, SQL-driven machine
> learning framework for Data Scientists.
> 
> RESOLVED, that the office of "Vice President, Apache MADlib" 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 MADlib Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache MADlib 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 MADlib Project:
> 
> Sarah Aerni 
> Greg Chase 
> Aaron Feng 
> Rahul Iyer 
> Jim Jagielski 
> Nandish Jayaram 
> Anirudh Kondaveeti 
> Orhan Kışlal 
> Frank McQuillan 
> Srivatsan R 
> Rashmi Raghu 
> Roman Shaposhnik 
> Atri Sharma 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Aaron Feng
> be appointed to the office of Vice President, Apache MADlib, 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 MADlib PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache MADlib Project; and be it further
> 
> RESOLVED, that the Apache MADlib Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator MADlib podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator MADlib podling encumbered upon the Apache Incubator
> Project are hereafter discharged.

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

Re: Good examples of licensing in ASF produced web apps?

[P. Taylor Goetz]

> On May 26, 2017, at 5:54 PM, Roman Shaposhnik  wrote:
> 
> But that's actually not important -- you're right bundling
> dependencies is OK, but
> doing that makes it even more important to do proper LICENSE and NOTICE.

IMO, you hit the nail on the head right there. I would hope the war file would 
contain both and they reflect the dependencies contained in the war file (as 
opposed to the official source distribution, which may not).

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

Re: Call for a new mentor for Apache Slider

[P. Taylor Goetz]

Vinod,

You are already a mentor [1].

It sounds like Gour is just looking for mentors to engage and sign off on 
reports. The technical aspects seem secondary to that request.

-Taylor

[1] http://incubator.apache.org/projects/slider.html


> On May 24, 2017, at 2:23 PM, Vinod Kumar Vavilapalli  
> wrote:
> 
> I am from Hadoop PMC and am involved a bit in these transition.
> 
> If the idea is to continue doing bug-fix releases on Apache Slider incubator, 
> you can count me in.
> 
> Thanks
> +Vinod
> 
>> On May 24, 2017, at 11:14 AM, Gour Saha  wrote:
>> 
>> Apache Slider is at a transition phase from being an independent incubator 
>> project into Apache Hadoop as a module. The Apache Slider and Apache Hadoop 
>> team has been working together on this for the past 1 year or so. During 
>> this transition the Apache Slider incubating code will continue to be 
>> supported, of course with fewer releases mainly with bug fixes and no major 
>> features.
>> 
>> At this interesting phase in Apache Slider's lifecycle, we are occasionally 
>> missing mentor sign-offs on our reports. So we are looking for an additional 
>> mentor who can assist the Slider community and the project through the 
>> remainder of this transition into Apache Hadoop.
>> 
>> Kindly let us know if you are interested in this role.
>> 
>> -Gour
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Pulsar into the Apache Incubator

[P. Taylor Goetz]

D)
> * SLF4J API (MIT)
> 
> == Required Resources ==
> 
> === Mailing lists ===
> * us...@pulsar.incubator.apache.org
> * d...@pulsar.incubator.apache.org
> * comm...@pulsar.incubator.apache.org
> * priv...@pulsar.incubator.apache.org (with moderated subscriptions)
> 
> === Git Repository ===
> * https://git-wip-us.apache.org/repos/asf/incubator-pulsar
> 
> === Issue Tracking ===
> * JIRA Pulsar (PULSAR)
> 
> == Initial Committers ==
> * Matteo Merli - <mme...@apache.org>
> * Joe Francis - <j...@yahoo-inc.com>
> * Rajan Dhabalia - <rdhaba...@yahoo-inc.com>
> * Sahaya Andrews Albert - <sandr...@yahoo-inc.com>
> * Maurice Barnum - <m...@yahoo-inc.com>
> * Ludwig Pummer - <lud...@yahoo-inc.com>
> * Jai Asher - <j...@yahoo-inc.com>
> * Siddharth Boobna - <sboo...@apache.org>
> * Nozomi Kurihara - <nkuri...@yahoo-corp.jp>
> * Yuki Shiga - <yush...@yahoo-corp.jp>
> * Masakazu Kitajo - <mas...@apache.org>
> * Sebastián Schepens - <sebastian.schep...@mercadolibre.com>
> * Brad McMillen - <bra...@yahoo-inc.com>
> * Bobbey Reese - <bre...@yahoo-inc.com>
> * Masahiro Sakamoto <massa...@yahoo-corp.jp>
> * Hiroyuki Sakai <hsa...@yahoo-corp.jp>
> 
> == Affiliations ==
> * Matteo Merli - Streamlio
> * Joe Francis - Yahoo
> * Rajan Dhabalia - Yahoo
> * Sahaya Andrews Albert - Yahoo
> * Maurice Barnum - Yahoo
> * Ludwig Pummer - Yahoo
> * Jai Asher - Yahoo
> * Siddharth Boobna - Salesforce
> * Nozomi Kurihara - Yahoo! Japan
> * Yuki Shiga - Yahoo! Japan
> * Masakazu Kitajo - Apple
> * Sebastián Schepens - Mercado Libre
> * Brad McMillen - Yahoo
> * Bobbey Reese - Yahoo
> 
> == Sponsors ==
> 
> === Champion ===
> * Bryan Call
> 
> === Nominated Mentors ===
> * Dave Fisher
> * Jim Jagielski
> * P. Taylor Goetz
> * Francis Liu
> 
> === Sponsoring Entity ===
> * The Apache Incubator PMC   
> 
> 
> 
> -
> 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] MADlib v1.11-rc3

[P. Taylor Goetz]

+1 (binding)

* Signature good.
* DISCLAIMER exists
* L files look good.
* Apache headers in source files where appropriate [1]
* No binaries in source archive

-Taylor

[1] Pretty complex licensing situation required some “light” reading to get the 
full story (LEGAL-293 + background, etc.) ;)


> On May 10, 2017, at 3:44 AM, Rashmi Raghu  wrote:
> 
> Hello Incubator PMC,
> 
> The Apache MADlib (incubating) community has voted on and approved the
> proposal to release MADlib v1.11-rc3.
> 
> The voting result is available at:
> http://mail-archives.apache.org/mod_mbox/incubator-madlib-dev/201705.mbox/%3CCAMtNjo%3Dwq0qQmJRTqAnef%2BtuTawXm508pQmLAcvWho0fOfkEmQ%40mail.gmail.com%3E
> 
> This will be the 5th release for Apache MADlib (incubating).
> 
> The main goals of this release are:
> * new module (PageRank for graph analytics with grouping support included)
> * improvements to existing modules (add grouping support to Single Source
> Shortest Path, reduce memory footprint of DT and RF, include NULL features
> in training DT, add support for array and svec output for Pivot module,
> utility to unnest 2-D arrays into rows of 1-D arrays)
> * platform updates (GPDB 5)
> * updates for Apache Top Level Project readiness and build process on
> Apache infrastructure
> * bug fixes
> * doc improvements
> 
> For more information including release notes, please see:
> https://cwiki.apache.org/confluence/display/MADLIB/MADlib+1.11
> 
> To run check RAT, please do:
> 
> $mvn verify
> 
> first to get the correct RAT output.  Look inside of pom.xml to see the
> classes of exceptions we're managing there for RAT.
> 
> We're voting upon the source and convenience binaries below:
> 
> Source Repository (tag):  rc/1.11-rc3
> https://github.com/apache/incubator-madlib/tree/rc/1.11-rc3
> 
> Source Files and convenience Binaries:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/1.11-incubating-rc3/
> 
> Commit:
> https://github.com/apache/incubator-madlib/commit/8e2778a3921aa99f009962756881ce4bea5eee16
> 
> KEYS file containing PGP Keys we use to sign the release:
> https://dist.apache.org/repos/dist/dev/incubator/madlib/KEYS
> 
> For your convenience, the recent ASF licensing guidance to the MADlib
> community is summarized here:
> https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance
> 
> Please vote:
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> *** The vote will be open until Monday May 15 at 6 pm Pacific time. ***
> 
> Regards,
> Rashmi Raghu
> 
> -- 
> Rashmi Raghu, Ph.D.
> Pivotal Data Science


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

Re: [PROPOSAL] Pulsar - proposal for Apache Incubation

[P. Taylor Goetz]

Hi Dheeban,

tl;dr;: You've kind of stumbled into an early procedural process for adding new 
ASF projects, but your interest is very much appreciated.

That's great that you want to get involved! One of the important things 
new/potential Apache projects need to do is develop a community. Your interest 
is a good sign.

At this point the project is an a proposal phase. If the proposal discussion is 
positive (meaning most IPMC members appear to support incubating the project), 
it will move on to a vote. If the vote passes, the project will be 
bootstrapped: code imported, mailing lists and bug tracker created, website 
domain registered, etc.

Admittedly, our documentation can be bit hard to navigate, but I assume that 
you're aware of the ASF Incubator website [1] since you are subscribed to this 
list. Perusing that site will give you more insight into what the Incubator is 
about and how the ASF works.

-Taylor

[1] http://incubator.apache.org/

> On May 11, 2017, at 4:43 PM, Dheeban Govindarajan <sgdhee...@gmail.com> wrote:
> 
> Hi Team,
> 
> I am newbie in the open-source contribution world. I have not actively
> contributed to any open source code base, but am interested in being a part
> of this one. I have used a lot of open source code. Have debugged some open
> source code, out of curiosity, have always wondered how such big software
> gets built in a distributed fashion.
> 
> Not even sure, if this is the right forum. Please excuse if its not. I see
> this project is in proposal phase, please let me know, if any coding help
> is required. Would like to be part of a project such as this, and learn
> something, and contribute as well. Just a bit of background, I am a
> Software Engineer at eBay, have 5+ years experience coding large scale
> projects.
> 
> Thanks
> Dheeban
> 
>> On Thu, May 11, 2017 at 1:11 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>> 
>>> On May 11, 2017, at 2:44 PM, Bryan Call <bc...@apache.org> wrote:
>>> 
>>> I added the 3 mentors to the Wiki.  Should we put it up for a vote now?
>>> 
>>> -Bryan
>> 
>> Discussion has died down and the project has enough mentors, so I would
>> say go ahead.
>> 
>> -Taylor

Re: [PROPOSAL] Pulsar - proposal for Apache Incubation

[P. Taylor Goetz]

> On May 11, 2017, at 2:44 PM, Bryan Call  wrote:
> 
> I added the 3 mentors to the Wiki.  Should we put it up for a vote now?
> 
> -Bryan

Discussion has died down and the project has enough mentors, so I would say go 
ahead.

-Taylor

Re: [PROPOSAL] Pulsar - proposal for Apache Incubation

[P. Taylor Goetz]

I’d be willing to mentor as well.

-Taylor


> On May 11, 2017, at 2:29 PM, Dave Fisher  wrote:
> 
> Hi All -
> 
> That's 2 mentors. Is there a third?
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On May 6, 2017, at 7:10 AM, Jim Jagielski  wrote:
>> 
>> To be clear, yes, I would.
>> 
>>> On May 5, 2017, at 11:51 AM, Dave Fisher  wrote:
>>> 
>>> Hi -
>>> 
>>> Anyone else interested in mentoring?
>>> 
>>> Regards,
>>> Dave
>>> 
>>> Sent from my iPhone
>>> 
 On May 1, 2017, at 4:55 PM, Dave Fisher  wrote:
 
 Hi -
 
 I had a discussion with Joe and another gentleman involved in Pulsar.
 
 They asked how long incubation takes. I answered that it depends. We 
 reviewed some of the steps needed in Incubation particularly:
 
 - Release process with correct LICENSE and NOTICE
 - Community building requirement - especially accepting and promoting 
 someone new from outside the initial committers.
 - Everything on the ML meaning decisions which might be made in 
 conversation need to be there for a review over a few rotations of the 
 planet. I mentioned BFDLs not being what is wanted and told the 10 year 
 old story of POI’s OOXML flame.
 - Build infrastructure questions regarding unit tests some of which will 
 be preferred on clusters. Some are currently proprietary. I’m not sure 
 what Apache Infra currently supports so negotiation is required.
 
 I think that there is a good chance for a diverse community that will not 
 be wholly dependent on Yahoo.
 
 End result - I am willing to sign up as a Mentor for Pulsar.
 
 Regards,
 Dave
 
> On Apr 28, 2017, at 7:56 AM, Dave Fisher  wrote:
> 
> Hi John,
> 
> I am trying to decide if I personally wish to mentor Pulsar and will be 
> asking technical questions. IMO this is not appropriate to an Incubator 
> discussion. Anything that surfaces that is appropriate can be brought 
> back to this discussion.
> 
> There is no intension to subvert Incubator process.
> 
> I certainly understand asynchronous global teams. I've spent many years 
> working with development teams in Moscow and India.
> 
> We can have a separate discussion about how misunderstandings can cause 
> email threads to totally blow up.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On Apr 28, 2017, at 4:20 AM, John D. Ament  wrote:
>> 
>> I'm sorry but I'm a bit dumb founded by this part of the thread.  I'll
>> apologize up front for my bluntness.
>> 
>> In the incubator, we're trying to teach projects to deal with 
>> asynchronous
>> communication.  The last thing we should be doing is encouraging phone
>> calls/real time meetings.  If there are technical questions, and you feel
>> they need to be answered prior to starting incubation that's perfectly 
>> fine
>> - but try to get the answers in ways we would expect, via public mailing
>> lists.
>> 
>> John
>> 
>>> On Thu, Apr 27, 2017 at 10:17 PM Dave Fisher  
>>> wrote:
>>> 
>>> Hi -
>>> 
>>> I am in California and could do a webex this Monday.
>>> 
>>> Regards,
>>> Dave
>>> 
>>> Sent from my iPhone
>>> 
 On Apr 27, 2017, at 1:41 AM, Jochen Theodorou  
 wrote:
 
 
 
> On 26.04.2017 23:19, Joe Francis wrote:
> 
> Dear Apache Incubator Community,
> 
> 
> We would like to submit the Pulsar proposal to the incubator.  Our
>>> draft is
> available at:
> https://wiki.apache.org/incubator/PulsarProposal
> 
> A quick overview of Pulsar:
> 
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor
>>> management for
> subscribers, and cross-datacenter replication.
 
 Without really knowing the details of a messaging platform and even 
 with
>>> the danger of comparing apples and oranges... how would you compare for
>>> example hazelcast based messaging to pulsar?
 
 bye Jochen
 
 -
 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 

Re: Podling release vote terminology

[P. Taylor Goetz]

I think that would be a good way to clear up some of the confusion. +1


> On May 9, 2017, at 2:00 PM, Craig Russell  wrote:
> 
> I've seen a few (recent) incubator votes that imply that there are two 
> separate, distinct votes: one in the podling and one in the incubator 
> general. And lots of questions about binding votes and carried-over votes and 
> whose votes are counted.
> 
> I'd like to suggest:
> 
> There is one vote for a podling release candidate. The first phase of the 
> vote takes place on the podling dev list. Anyone can vote. An affirmative 
> vote by three PPMC members (including mentors) is sufficient to start the 
> second phase, which takes place on the incubator general list. An 
> individual's vote can be changed any time during either phase until the final 
> vote is tallied.
> 
> All votes are counted. Only IPMC member votes are binding. The final tally 
> counts affirmative, neutral, and negative votes from both phases combined and 
> affirmative, neutral and negative binding votes from both phases combined.
> 
> This terminology answers questions about:
> 
> Whether PPMC votes are binding. They are not. 
> Whether IPMC member votes on the first phase of voting carry over to the 
> second phase. They do. 
> Whether public votes in either phase count. They do. 
> Whether public votes in either phase are binding. They are not.

Are you proposing to include these questions/answers in the docs? I think it 
would help prevent any misinterpretation of the terminology.


> 
> If we agree on the terminology, I'll see what documents need to be updated.
> 
> Craig L Russell
> c...@apache.org
> 

-Taylor


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

Re: [RESULT] [VOTE] Release Apache Airflow 1.8.1 (incubating)

[P. Taylor Goetz]

Disregard. I just saw your question about carrying over IPMC votes. Yes, they 
can be carried over. Just make sure you include them/state that in the result 
email.

-Taylor


> On May 9, 2017, at 1:18 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> Hi Chris,
> 
> Unless I’m missing something, you’re one vote shy of the requirement of 
> having 3 IPMC +1 votes [1].
> 
> Were there mentor +1 votes on the dev@ vote thread that can be carried over?
> 
> -Taylor
> 
> [1] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> 
> 
> 
>> On May 9, 2017, at 12:52 PM, Chris Riccomini <criccom...@apache.org> wrote:
>> 
>> Hey all,
>> 
>> The vote has passed after 72+ hours.
>> 
>> There were two +1 votes:
>> 
>> Josh Elser, John D. Ament
>> 
>> No 0/-1 votes. I'm going to wrap up the release.
>> 
>> @John, thanks for the feedback. We'll take this into account on the next
>> release. Some items have actually already been fixed, just not
>> cherry-picked into the 1.8.1 branch.
>> 
>> Cheers,
>> Chris
>> 
>> On Sun, May 7, 2017 at 2:08 PM, John D. Ament <johndam...@apache.org> wrote:
>> 
>>> +1, however there's a few issues with the LICENSE file:
>>> 
>>> - Would be good to list out the locations of each file (or path to a group
>>> of files) (some have this, and others do not so its hard to follow)
>>> - There's errant /* .. */ around each license declaration, which should be
>>> removed.
>>> - Missing license bodies for FooTable v2, jQuery Clock Plugin,
>>> 
>>> Likewise, your NOTICE has copyright 2011-2017, however Airflow hasn't been
>>> incubating that long.  If you like, you can give origination notices to the
>>> original creators here to specify the original copyright dates.
>>> 
>>> I would challenge the podling to see if there's a way to simplify their
>>> LICENSE by instead using npm or some other javascript packaging tool to
>>> build a distribution, rather than shipping the dependencies in the source
>>> release, makes it much easier to use.
>>> 
>>> As the podling matures, would be good to see information about the author
>>> switch from an individual to a community (in setup.cfg, its already in
>>> setup.py so may have been a miss)
>>> 
>>> It would be great to see a binary distribution in the next vote to see how
>>> that may work, its not clear how to build it from this.  Likewise, don't
>>> hesitate to clean up your old release artifacts, I downloaded the wrong
>>> artifact at first.
>>> 
>>> John
>>> 
>>> On Fri, May 5, 2017 at 4:44 PM Chris Riccomini <criccom...@apache.org>
>>> wrote:
>>> 
>>>> Hello Incubator PMC’ers,
>>>> 
>>>> The Apache Airflow community has voted and approved the proposal to
>>> release
>>>> Apache Airflow 1.8.1 (incubating) based on 1.8.1 Release Candidate 2. We
>>>> now kindly request the Incubator PMC members to review and vote on this
>>>> incubator release. If the vote is successful we will rename release
>>>> candidate 2 to final.
>>>> 
>>>> Airflow is a platform to programmatically author, schedule and monitor
>>>> workflows. Use airflow to author workflows as directed acyclic graphs
>>>> (DAGs) of tasks. The airflow scheduler executes your tasks on an array of
>>>> workers while following the specified dependencies. Rich command line
>>>> utilities make performing complex surgeries on DAGs a snap. The rich user
>>>> interface makes it easy to visualize pipelines running in production,
>>>> monitor progress, and troubleshoot issues when needed. When workflows are
>>>> defined as code, they become more maintainable, versionable, testable,
>>> and
>>>> collaborative.
>>>> 
>>>> The Apache Airflow-1.8.1-incubating release candidate is now available
>>> with
>>>> the following artifacts for a project vote:
>>>> 
>>>> * [VOTE] Thread:*
>>>> 
>>>> https://mail-archives.apache.org/mod_mbox/incubator-
>>> airflow-dev/201705.mbox/%3CCABYbY7eZk2SYHs3ni31h94uwwRd
>>> cn4dkJwumYtUMsfFLq-gwjg%40mail.gmail.com%3E
>>>> 
>>>> *[RESULT] [VOTE] Thread:*
>>>> 
>>>> https://mail-archives.apache.org/mod_mbox/incubator-
>>> airflow-dev/201705.mbox/%3CCABYbY7dBAnjcvb-w_
>>> 4Hdy3ZUM3CGn6Y3eUvZctuFCfdAfPGAXQ%40m

Re: [RESULT] [VOTE] Release Apache Airflow 1.8.1 (incubating)

[P. Taylor Goetz]

Hi Chris,

Unless I’m missing something, you’re one vote shy of the requirement of having 
3 IPMC +1 votes [1].

Were there mentor +1 votes on the dev@ vote thread that can be carried over?

-Taylor

[1] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases



> On May 9, 2017, at 12:52 PM, Chris Riccomini  wrote:
> 
> Hey all,
> 
> The vote has passed after 72+ hours.
> 
> There were two +1 votes:
> 
>  Josh Elser, John D. Ament
> 
> No 0/-1 votes. I'm going to wrap up the release.
> 
> @John, thanks for the feedback. We'll take this into account on the next
> release. Some items have actually already been fixed, just not
> cherry-picked into the 1.8.1 branch.
> 
> Cheers,
> Chris
> 
> On Sun, May 7, 2017 at 2:08 PM, John D. Ament  wrote:
> 
>> +1, however there's a few issues with the LICENSE file:
>> 
>> - Would be good to list out the locations of each file (or path to a group
>> of files) (some have this, and others do not so its hard to follow)
>> - There's errant /* .. */ around each license declaration, which should be
>> removed.
>> - Missing license bodies for FooTable v2, jQuery Clock Plugin,
>> 
>> Likewise, your NOTICE has copyright 2011-2017, however Airflow hasn't been
>> incubating that long.  If you like, you can give origination notices to the
>> original creators here to specify the original copyright dates.
>> 
>> I would challenge the podling to see if there's a way to simplify their
>> LICENSE by instead using npm or some other javascript packaging tool to
>> build a distribution, rather than shipping the dependencies in the source
>> release, makes it much easier to use.
>> 
>> As the podling matures, would be good to see information about the author
>> switch from an individual to a community (in setup.cfg, its already in
>> setup.py so may have been a miss)
>> 
>> It would be great to see a binary distribution in the next vote to see how
>> that may work, its not clear how to build it from this.  Likewise, don't
>> hesitate to clean up your old release artifacts, I downloaded the wrong
>> artifact at first.
>> 
>> John
>> 
>> On Fri, May 5, 2017 at 4:44 PM Chris Riccomini 
>> wrote:
>> 
>>> Hello Incubator PMC’ers,
>>> 
>>> The Apache Airflow community has voted and approved the proposal to
>> release
>>> Apache Airflow 1.8.1 (incubating) based on 1.8.1 Release Candidate 2. We
>>> now kindly request the Incubator PMC members to review and vote on this
>>> incubator release. If the vote is successful we will rename release
>>> candidate 2 to final.
>>> 
>>> Airflow is a platform to programmatically author, schedule and monitor
>>> workflows. Use airflow to author workflows as directed acyclic graphs
>>> (DAGs) of tasks. The airflow scheduler executes your tasks on an array of
>>> workers while following the specified dependencies. Rich command line
>>> utilities make performing complex surgeries on DAGs a snap. The rich user
>>> interface makes it easy to visualize pipelines running in production,
>>> monitor progress, and troubleshoot issues when needed. When workflows are
>>> defined as code, they become more maintainable, versionable, testable,
>> and
>>> collaborative.
>>> 
>>> The Apache Airflow-1.8.1-incubating release candidate is now available
>> with
>>> the following artifacts for a project vote:
>>> 
>>> * [VOTE] Thread:*
>>> 
>>> https://mail-archives.apache.org/mod_mbox/incubator-
>> airflow-dev/201705.mbox/%3CCABYbY7eZk2SYHs3ni31h94uwwRd
>> cn4dkJwumYtUMsfFLq-gwjg%40mail.gmail.com%3E
>>> 
>>> *[RESULT] [VOTE] Thread:*
>>> 
>>> https://mail-archives.apache.org/mod_mbox/incubator-
>> airflow-dev/201705.mbox/%3CCABYbY7dBAnjcvb-w_
>> 4Hdy3ZUM3CGn6Y3eUvZctuFCfdAfPGAXQ%40mail.gmail.com%3E
>>> 
>>> *The release candidate(s) to be voted on is available at:*
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/ or
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> apache-airflow-1.8.1rc2+incubating.tar.gz
>>> 
>>> *Git branch*
>>> https://github.com/apache/incubator-airflow/tree/v1-8-test or
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
>> git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-test
>>> 
>>> *Git tag*
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
>> git;a=shortlog;h=af2d0b4b5cb1ef30a065b1af66f90a01a953e2be
>>> 
>>> *PGP signature*
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> apache-airflow-1.8.1rc2+incubating.tar.gz.asc
>>> 
>>> *MD5/SHA Hashes*
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> apache-airflow-1.8.1rc2+incubating.tar.gz.md5
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/airflow/
>> apache-airflow-1.8.1rc2+incubating.tar.gz.sha
>>> 
>>> *Keys to verify the signature of the release artifacts are available at:*
>>> https://dist.apache.org/repos/dist/release/incubator/airflow/
>>> 
>>> * RAT License checks*
>>> 
>>> RAT is executed as 

Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC3

[P. Taylor Goetz]

Apologies for the auto correct.

Please sub "Niclas" for "Nicolas".

-Taylor

> On May 4, 2017, at 8:43 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> Nicolas,
> 
> I understand and appreciate your passion, but would respectfully ask that you 
> step down your tone a little bit. Craig and John have both taken time to 
> review the release candidate (which you should be appreciative of -- getting 
> IPMC members to review a release can be difficult). In my opinion their 
> reviews bring up some valid points that need to be considered.
> 
> Weex, by its nature, has a complicated codebase with respect to licensing and 
> building from source. It is a far cry from a java project with a Pom and a a 
> "src" directory. It pulls in a lot of different code that needs to be 
> considered and evaluated. Going forward the (P)PMC will need to understand 
> that and as a TLP will need to be able to address issues accordingly.
> 
> What may seem like "Incubator hazing" right now, I would argue, is an 
> exercise in making sure the podling has what it takes to operate as a fully 
> functional TLP. No two podlings are the same, and some face certain burdens 
> that others do not.
> 
> For now can we try to turn the thread toward a more constructive path that 
> benefits both the podling and the Incubator?
> 
> For what it's worth, I agree with some (not all) of the objections that have 
> been raised. So I would be a -1 as well.
> 
> -Taylor
> 
> 
> 
>> On May 4, 2017, at 3:02 AM, Niclas Hedhman <nic...@hedhman.org> wrote:
>> 
>> Sorry, but if you don't know the background on that file, then perhaps you
>> think I am "not civil"... The fact is that NOTICE file doesn't require any
>> inclusion of what the project depends on, since they are not bundled, but
>> will be downloaded during build. In a previous round, we were told to take
>> it out of NOTICE for that reason (not bundled) and I argued that we should
>> keep it in to make it more reasonable for downstreams to get an idea of
>> what a binary distro will actually contain. This file was the compromise of
>> providing such details to downstream.
>> 
>> Now you say, "Uhhh, it is unclear..." when in reality it would be even more
>> unclear if we left it out, as some people on this very list pushed for on a
>> previous RC.
>> 
>> So, yes, I get pissed off as well. The incubator over time is getting more
>> and more intolerant at podling's first release, and I think it is the wrong
>> way to go. It is disheartening... truly...
>> 
>> 
>> Niclas
>> 
>>> On Thu, May 4, 2017 at 1:57 PM, Craig Russell <apache@gmail.com> wrote:
>>> 
>>> I'm going to call foul on this one.
>>> 
>>> If you cannot be civil, then leave the discussion to others.
>>> 
>>> Craig
>>> 
>>>> On May 3, 2017, at 7:24 PM, Niclas Hedhman <nic...@hedhman.org> wrote:
>>>> 
>>>> BUT ALSO figuring out what to start looking for. For fak sake,
>>>> man Get a grip on reality!
>>> 
>>> 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
>>> 
>>> 
>> 
>> 
>> -- 
>> Niclas Hedhman, Software Developer
>> http://polygene.apache.org - New Energy for Java

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

Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC3

[P. Taylor Goetz]

Nicolas,

I understand and appreciate your passion, but would respectfully ask that you 
step down your tone a little bit. Craig and John have both taken time to review 
the release candidate (which you should be appreciative of -- getting IPMC 
members to review a release can be difficult). In my opinion their reviews 
bring up some valid points that need to be considered.

Weex, by its nature, has a complicated codebase with respect to licensing and 
building from source. It is a far cry from a java project with a Pom and a a 
"src" directory. It pulls in a lot of different code that needs to be 
considered and evaluated. Going forward the (P)PMC will need to understand that 
and as a TLP will need to be able to address issues accordingly.

What may seem like "Incubator hazing" right now, I would argue, is an exercise 
in making sure the podling has what it takes to operate as a fully functional 
TLP. No two podlings are the same, and some face certain burdens that others do 
not.

For now can we try to turn the thread toward a more constructive path that 
benefits both the podling and the Incubator?

For what it's worth, I agree with some (not all) of the objections that have 
been raised. So I would be a -1 as well.

-Taylor



> On May 4, 2017, at 3:02 AM, Niclas Hedhman  wrote:
> 
> Sorry, but if you don't know the background on that file, then perhaps you
> think I am "not civil"... The fact is that NOTICE file doesn't require any
> inclusion of what the project depends on, since they are not bundled, but
> will be downloaded during build. In a previous round, we were told to take
> it out of NOTICE for that reason (not bundled) and I argued that we should
> keep it in to make it more reasonable for downstreams to get an idea of
> what a binary distro will actually contain. This file was the compromise of
> providing such details to downstream.
> 
> Now you say, "Uhhh, it is unclear..." when in reality it would be even more
> unclear if we left it out, as some people on this very list pushed for on a
> previous RC.
> 
> So, yes, I get pissed off as well. The incubator over time is getting more
> and more intolerant at podling's first release, and I think it is the wrong
> way to go. It is disheartening... truly...
> 
> 
> Niclas
> 
>> On Thu, May 4, 2017 at 1:57 PM, Craig Russell  wrote:
>> 
>> I'm going to call foul on this one.
>> 
>> If you cannot be civil, then leave the discussion to others.
>> 
>> Craig
>> 
>>> On May 3, 2017, at 7:24 PM, Niclas Hedhman  wrote:
>>> 
>>> BUT ALSO figuring out what to start looking for. For fak sake,
>>> man Get a grip on reality!
>> 
>> 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
>> 
>> 
> 
> 
> -- 
> Niclas Hedhman, Software Developer
> http://polygene.apache.org - New Energy for Java

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

Re: Don't forget to un-incubate

[P. Taylor Goetz]

general@ moved to BCC.

Casey,

If you need any help with the graduation steps let me know, I'd be happy to 
help.

-Taylor

> On Apr 28, 2017, at 4:11 PM, Greg Stein  wrote:
> 
> Apache Metron,
> 
> You need to move to a TLP. It has been over a week since the Board meeting,
> and Infrastructure has not seen any tickets filed to perform your move.
> 
> I'd suggest stopping your 0.4.0 release and deal with moving to TLP status.
> 
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
> 
> 
> On Wed, Apr 19, 2017 at 8:48 PM, John D. Ament 
> wrote:
> 
>> Dear Fineract, Metron and CarbonData PMCs
>> 
>> First of all, congratulations on your graduations today.
>> 
>> I want to put out an early reminder that you should complete your
>> un-incubation steps.  Some of the infra steps require a director to hit a
>> button, which may not have happened yet.  However from the foundation's
>> point of view you are graduated.  You may be working on some publicity of
>> the event with Sally, or expecting some follow up discussion, but that's
>> it, you're done in the incubator.  I would like to ask you (specifically
>> the new chairs, but anyone on the new PMCs could as well) to complete your
>> post-incubation steps found at [1].
>> 
>> Regards,
>> 
>> John
>> 
>> [1]: http://incubator.apache.org/guides/graduation.html#unincubate
>> 

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

Re: [VOTE] Apache Trafodion (incubating) release 2.1.0 RC 3

[P. Taylor Goetz]

+1 (binding)

- L look good and DISCLAIMER exists
- signature is good
- spot checked license headers
- verified no binaries included

I noticed the same “installer” vs. “install” issue John pointed out, but that’s 
very minor.

-Taylor

> On Apr 17, 2017, at 2:24 PM, Sandhya Sundaresan 
>  wrote:
> 
> 
> Hello ,
> 
> This is a call to vote on  Apache Trafodion (incubating)  release 2.1.0 RC3 
> (Release Candidate 3)
> 
> Apache Trafodion is a webscale SQL-on-Hadoop solution enabling transactional 
> or operational workloads on Hadoop. Trafodion builds on the scalability,
> elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide 
> guaranteed transactional integrity, enabling new kinds of big data 
> applications to run on Hadoop.
> 
> The Trafodion community has  voted and approved this release. Original email 
> thread :
> https://lists.apache.org/thread.html/6f000a0386492d9c48649a7f7278ec3b008146c896cfdf16e0b6511e@%3Cdev.trafodion.apache.org%3E
> 
> 
> This is a major release and includes over 300 fixes and some important 
> features.
> 
> The highlights are all documented here in the Release Notes : Trafodion 2.1 
> Release 
> Notes
> 
> They include :
> 
>  *   The new python installer
>  *   Ambari integration and much easier  install option for use on HDP 
> platform
>  *   New features, SQL functions and syntax extensions
>  *   Performance enhancements
>  *   300+ Bug fixes resolved
> 
> JIRA Release Notes :
> Trafodion 2.1 JIRA Release Notes Notes>
> 
> GIT info:
> The tag for this candidate is "2.1.0rc3". Git repository: git:// 
> git.apache.org/incubator-trafodion.git
> 
> Release artifacts :
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.1.0-RC3
> Artifacts are signed with my key :  85F0776A  which is in 
> https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
> 
> Instructions :
> 
> Setting up build environment and building from source :
> * 
> https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment
> * https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source
> 
> Installing Trafodion using convenience binaries:
> * Follow requirements in Section 4 : 
> http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#requirements
> * Download Trafodion Binaries : 
> http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#_download_binaries
> 
> * Ambari Install on HDP platform : 
> http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#install-ambari
> * Python Installer : 
> http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#install
> 
> 
> 
> [ ] +1 approve
> 
> [ ] +0 no opinion
> 
> [ ] -1 disapprove (and reason why)
> 
> Vote will be open for atleast 72 hours unless cancelled.
> 
> 


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

Re: Guidance needed ( Apache Trafodion (incubating) release 2.1.0 )

[P. Taylor Goetz]

Hi Sandhya,

I’ll review your rc now and will respond today.

In the meantime I would suggest asking on general@ to see if anyone is 
available to help mentor Trafodion (which you mostly have here). You may also 
want to privately touch base privately with inactive mentors to see if the wish 
to continue in that role.

-Taylor


> On Apr 27, 2017, at 2:24 PM, Sandhya Sundaresan 
>  wrote:
> 
> Hello again,
> 
> The Trafodion podling needs some help and guidance from the IPMC on moving 
> forward with its current release (Trafodion R2.1).  A Vote has been pending 
> since April 17th.  I've been following the other thread on the "Incubator 
> Governance Change" as well and the last message from Roman about hollering on 
> this list  if we aren't getting the mentorship needed.  
> 
> So the situation now  is that of 3 mentors for the Trafodion project, 2 have 
> been inactive. Our third is on vacation and has been occupied/busy with other 
> stuff. He has been helpful with the past releases. We are pursuing a search 
> for new mentors  on the side. 
> 
> But for this immediate release, we are in the tail end of the voting process 
> and lacking one IPMC vote. I understand it does not have to be a mentor 
> necessarily (although preferable).  
> 
> We have the following  votes from :
> 
> Jean-Baptiste Onofré (binding)
> John D Ament (binding)
> Ivam Firestone
> 
> Original full thread
> https://lists.apache.org/thread.html/8eca13e52620d16c3f974bc5054d59af29fa98d30763d646829a3850@%3Cgeneral.incubator.apache.org%3E
> 
> 
> Seeking the advice and help  of the experts here on the best way forward for 
> the  release  at this point. Looks like the mentor search or governance 
> change( if any) may take a while. Maintaining the master branch as well as 
> the current release branch is expensive. There's are some prospects  awaiting 
> the 2.1 release which contains several features and 300+ bugfixes.  
> 
> We hope to be able to speed this up and move forward with some help from the 
> community . 
> 
> Thank you !
> Sandhya
> 
> 
> 
> 
> -Original Message-
> From: Sandhya Sundaresan [mailto:sandhya.sundare...@esgyn.com] 
> Sent: Monday, April 24, 2017 8:53 AM
> To: general@incubator.apache.org
> Subject: RE: [VOTE] Apache Trafodion (incubating) release 2.1.0 RC 3
> 
> Hi,
>   No not yet. I sent them a private reminder message as well. 
> 
> Devaraj Das 
> Enis Söztutar 
> Michael Stack 
> 
> Thanks !
> Sandhya
> 
> -Original Message-
> From: bdelacre...@gmail.com [mailto:bdelacre...@gmail.com] On Behalf Of 
> Bertrand Delacretaz
> Sent: Sunday, April 23, 2017 11:22 PM
> To: Incubator General 
> Subject: Re: [VOTE] Apache Trafodion (incubating) release 2.1.0 RC 3
> 
> Hi,
> 
> On Mon, Apr 24, 2017 at 7:31 AM, Sandhya Sundaresan 
>  wrote:
>> ...The Trafodion 2.1.0 release is awaiting just one more binding vote before 
>> we can move forward with this release
> 
> Did your mentors review the release and vote?
> I don't see any of the names listed at [1] as having voted in this thread or 
> the podling vote thread, but maybe I missed something.
> 
> -Bertrand
> 
> [1] http://incubator.apache.org/projects/trafodion.html
> 
> -
> 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] Superset Proposal for Apache Incubator

[P. Taylor Goetz]

There was a minor change to the proposal in the Incubator wiki, so technically 
what were voting on and the wiki don't match.

I'm okay with that and don't think it should disrupt the vote. Highlighting the 
change in this thread should be enough.

+1 (binding)

I would recommend asking for/finding additional mentors to bring the count to 
>= 3.

-Taylor

> On Apr 23, 2017, at 10:53 AM, Jeff Feng  wrote:
> 
> Dear Apache Incubator Community,
> 
> We have updated the Superset proposal
>  (copied below) for
> Apache Incubation with an additional mentor (Luke Han - luke@apache.org),
> and would like to start a vote thread for acceptance into the incubator.
> 
> Our team is excited to share Superset with the Apache community and we hope
> for the your continued support!
> 
> Cheers,
> Jeff & the Superset Team
> 
> 
> 
> 
> = Superset =
> 
> == Abstract ==
> Superset is an enterprise-ready web application for data exploration, data
> visualization and dashboarding.
> 
> == Proposal ==
> Superset is business intelligence (BI) software that helps modern
> organizations visualize and interact with their data. Superset enables
> users explore data from a variety of databases, assemble beautiful
> dashboards and share their findings.  Superset works neatly with all modern
> SQL-speaking databases, and integrates with Druid.io to provide real-time,
> interactive, blazing fast data access to large datasets.
> 
> == Background ==
> Data is mission critical. To succeed in this era, organizations need to
> provide low-friction, intuitive and interactive access to data. It is
> paramount for knowledge workers to be capable of answering their own
> questions by querying, exploring and visualizing data.
> 
> The entire business intelligence industry has pivoted from a model of
> centralized top-down platforms driven by IT organizations to self-service
> analytics and agile workflows by any user.  This shift unblocks centralized
> service bottlenecks for creating data visualizations while also creating an
> environment that is iterative and fast-moving.  This means that business
> intelligence software must also be easy and delightful to use.
> Self-service analytics doesn’t mean that admin and governance features are
> not needed.
> Modern BI tools provide fine-grain access controls and auditing
> capabilities to understand how data is being used.  Superset is a solution
> that delivers on all of these vectors.
> 
> The technology stack is also constantly morphing - vendors are struggling
> to provide cheap, quick and easy solutions to access data.  Business
> intelligence users are finding existing solutions lacking as these software
> products either disregard or react slowly to recent game-changing
> technologies like Druid.io, PrestoDB, Apache Drill, Apache Kylin, d3.js,
> React.js and iPython’s Jupyter for instance.
> 
> == Rationale ==
> Business intelligence is more relevant today than at any other point in
> history.  Organizations are currently very limited in options for open
> source data visualization solutions, especially solutions that are both
> self-service and enterprise-ready.  Every company informing their decisions
> with data needs a BI tool.
> 
> We believe that Superset will be a strong compliment to existing Apache
> Software Foundation technologies by offering scalable user interactions to
> distributed storage and computation solutions.  Users will often find that
> Superset can act as a catalyst for tooling that can visualize the byproduct
> of data and computation infrastructure.
> 
> Superset has many key design elements that help fill a gap in current
> solutions for organizations:
> * Easy, low friction access to data through a simple, web-based data
> exploration interface.  Composing charts and dashboards are intuitive.
> Eliminating the need to write code or SQL empowers anyone to use it.
> * Access to a wide array of rich, interactive data visualization types.
> * Enterprise-ready: Integration with different authentication mechanisms
> and granular permissions centered around actions and data access.
> * Realtime & fast: Superset provides realtime analytics at the speed of
> thought on very large datasets when integrated with Druid.io.
> * Broad data access: Consume data out of any SQL-speaking relational
> database.
> * Extensible: Can be extended to talk to many noSQL databases like Apache
> Drill, Elastic Search, and other popular database engines.
> * Fast loading dashboards with configurable web-scale caching.
> * Plug-in framework that enables organizations to build custom analytical
> applications with new UI/UX interfaces.
> * SQL Lab, a state-of-the-art SQL IDE that empowers SQL-speaking users
> with more flexibility.  SQL Lab integrates with the visualization engine
> seamlessly.
> 
> == Initial Goals ==
> The initial goals of the Superset project are several-fold:
> * Move the existing codebase to 

Re: Incubator Governance Change

[P. Taylor Goetz]

> On Apr 25, 2017, at 9:06 PM, Roman Shaposhnik  wrote:
> 
> I honestly think its time for us to consider being more board like
> around here at
> IPMC. May be not exactly as strict as the board, but moving in that direction.
> 
> After all, being a podling means being TLP-on-training-wheels. That's the 
> whole
> idea. If your PMC shrinks -- you have to know what it means. Same here. If 
> your
> mentors are not active -- you've got to raise hell around here on general@
> before its too late.

I mostly agree, but would hesitate with the idea that a podling be responsible 
for raising a red flag when mentors are inactive. If the IPMC isn’t doing it’s 
job, that’s on us, not the projects we incubate.

-Taylor

Re: [PROPOSAL] Superset Proposal for Apache Incubator

[P. Taylor Goetz]

Hi Jeff,

With the change to the proposal on the wiki, it now differs from the proposal 
text in the VOTE email. The reason we include the proposal text in the VOTE 
thread is because it represents the state of the proposal (which being a wiki 
page, is inherently mutable) at the time of the VOTE.

It's largely technical/procedural, but I would recommend cancelling the current 
vote and let the DISCUSS thread play out a little longer.

Not that calling a VOTE was wrong or premature, the thread had died down. But 
oftentimes the actual VOTE thread is what kicks IPMC members toward taking a 
closer look at a proposal. (We, the IPMC, are an imperfect group of volunteers. 
:) )

-Taylor



> On Apr 25, 2017, at 3:17 AM, Jeff Feng  wrote:
> 
> Thanks John and Max - I have updated the proposal wiki to reflect this
> update.  It now reads:
> 
> Source and Intellectual Property Submission Plan
> 
> Airbnb will submit a Software Grant Agreement (SGA) as Superset joins the
> incubator. We do not expect any complications for the submission of the
> Superset code base. Our code is already in Github and there is only a
> single code base.
> 
> 
> On Mon, Apr 24, 2017 at 11:32 PM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> 
>> "Airbnb will submit a Software Grant Agreement (SGA) as Superset joins the
>> incubator."
>> 
>> Should I add this sentence in the proposal?
>> 
>> Max
>> 
>> On Mon, Apr 24, 2017 at 5:48 AM, John D. Ament 
>> wrote:
>> 
>>> I missed this discussion.  In your IP section, you list out:
>>> 
>>> == Source and Intellectual Property Submission Plan ==
>>> We do not expect any complications for the submission of the Superset
>> code
>>> base.  Our code is already in Github and there is only a single code
>> base.
>>> 
>>> This IMHO not clear.  Does Airbnb plan to submit a SGA for Superset, or
>>> expect that no SGA is required because its Apache licensed?
>>> 
>>> John
>>> 
>>> On Sun, Apr 2, 2017 at 4:09 PM Jeff Feng 
>>> wrote:
>>> 
 Dear Apache Incubator Community,
 
 We are excited to share our proposal for discussion and feedback for
 entering Apache Incubation.  Superset is an enterprise-ready web
 application for data exploration, data visualization and dashboarding.
 
 Our Incubation proposal is at the following Wiki as well as copied in
>> the
 email below:
 
 https://wiki.apache.org/incubator/SupersetProposal
 
 We have an active Superset community including 400+ members and nearly
>>> 200
 topics.  The Google Group can be found below.  We plan to move the
 discussion to the ASF:
 
 https://groups.google.com/forum/#!forum/airbnb_superset
 
 Thank you and look forward to the discussion!
 
 Jeff, Max & Alanna
 
 
 
 
 = Superset =
 
 == Abstract ==
 
 Superset is an enterprise-ready web application for data exploration,
>>> data
 visualization and dashboarding.
 
 == Proposal ==
 
 Superset is business intelligence (BI) software that helps modern
 organizations visualize and interact with their data. Superset enables
 users explore data from a variety of databases, assemble beautiful
 dashboards and share their findings.  Superset works neatly with all
>>> modern
 SQL-speaking databases, and integrates with Druid.io to provide
>>> real-time,
 interactive, blazing fast data access to large datasets.
 
 == Background ==
 
 Data is mission critical. To succeed in this era, organizations need to
 provide low-friction, intuitive and interactive access to data. It is
 paramount for knowledge workers to be capable of answering their own
 questions by querying, exploring and visualizing data.
 
 The entire business intelligence industry has pivoted from a model of
 centralized top-down platforms driven by IT organizations to
>> self-service
 analytics and agile workflows by any user.  This shift unblocks
>>> centralized
 service bottlenecks for creating data visualizations while also
>> creating
>>> an
 environment that is iterative and fast-moving.  This means that
>> business
 intelligence software must also be easy and delightful to use.
 Self-service analytics doesn’t mean that admin and governance features
>>> are
 not needed.
 
 Modern BI tools provide fine-grain access controls and auditing
 capabilities to understand how data is being used.  Superset is a
>>> solution
 that delivers on all of these vectors.
 
 The technology stack is also constantly morphing - vendors are
>> struggling
 to provide cheap, quick and easy solutions to access data.  Business
 intelligence users are finding existing solutions lacking as these
>>> software
 products either disregard or react slowly to recent game-changing
 technologies like Druid.io, PrestoDB, Apache 

Re: Incubator Governance Change

[P. Taylor Goetz]

> On Apr 23, 2017, at 11:09 AM, Shane Curcuru  wrote:
> 
> Pat Ferrel wrote on 4/22/17 11:46 AM:
>> Probably the wrong place for this but…
>> 
>> What do people think about a governance change for approving releases
>> through the IPMC to wit:
>> 
>> A week of no vote activity over the release proposal of a podling
>> should be considered a passing vote. In other words the IPMC is to
>> become a vetoing group.
> 
> No, because as noted in this thread the board and Legal Affairs
> Committee already have a policy for Apache software releases:
> 
>  https://www.apache.org/legal/release-policy.html#policy
> 
> This is the spot where all the little legal bits of having a corporation
> intersects with the Incubator's ability to mentor new podlings in how to
> effectively run projects in the Apache Way.  However that legal policy
> in particular is not going to change IMO.
> 
> Personally, I support any proposals that help ensure podling mentors are
> more actively engaged, and can better serve as the formal IPMC votes for
> podling releases.  Great to see some serious discussion about that in
> this thread and the upcoming IPMC chair election.  The incubator has
> been getting better organized as a whole over the past few years, and
> keeps improving, which is great to see.
> 
>> I propose this for 2 reasons: 1) lack of votes or attention from the
>> IPMC seems all too prevalent and puts an undo drag on the energy and
>> velocity of community involvement. 2) the release has already been
>> voted on and checked by at least 3 PMC members of the podling (which
>> has ASF mentors in most all cases) so a veto role by the IPMC seems
>> to have minimum danger to the ASF system of checks and balances.>
> 
> Yes, but the whole point of Incubation is that a podling is not yet a
> project.  Only Apache PMCs have the authority to make a release, thus
> only IPMC votes count.  On one hand this must feel incredibly annoying.
> On the other hand, it is the #1 reason we have the ASF as a corporation
> - to prevent the individual release manager from potentially getting
> sued *personally* for problems with the release.
> 
> The fact that we have these documented policies, and that the board and
> IPMC enforces them means that legally, releases are acts of the
> Foundation.  Thus if anyone ever were to sue, they'd sue the Foundation
> (which has insurance and legal counsel) and not individual committers.
> 
> -- 
> 
> - Shane, IPMC Member
>  https://www.apache.org/foundation/marks/resources
> 

I completely agree with Shane. To put it another way, podlings don’t make 
releases, the IPMC makes releases.

In the past I’ve seen others advocate that one active mentor is enough for a 
podling. I do not share that opinion and think release voting is another reason 
a podling should aim (notice I’m not saying “must” here) to have at least three 
mentors. Mentors, by virtue of being more intimately involved with a podling, 
are much more likely to vote on a release than non-mentor IPMC members.

To address the low level of IPMC members voting on podling releases, we need to 
understand why it happens. Is it just a lack of individuals’ time? Is it that 
IPMC members expect a podling’s mentors to review and vote on a release?

Historically I’ve tended toward the latter, but my thinking has changed over 
time. While podlings have an explicit set of mentors, the IPMC as a whole can 
be thought of as an informal set of mentors. Reviewing and voting on podling 
release candidates is one way for any IPMC member to help a podling whether a 
mentor or not.

-Taylor





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

Re: The state of Sirona

[P. Taylor Goetz]

+1 for retirement.

There's absolutely nothing wrong with a podling returning to the place from 
whence it came. I'm encouraged that that sentiment seems to be proliferating 
among the IPMC.

-Taylor







> On Apr 16, 2017, at 11:33 AM, Ted Dunning  wrote:
> 
> Sounds like consensus is coming together, then. Sound right?
> 
> 
>> On Apr 16, 2017 06:03, "larry mccay"  wrote:
>> 
>> H - interesting points about incubator vs github and overhead.
>> I do think my statement was unclear though.
>> 
>> I was saying exactly the same thing about struggling podlings.
>> Much better to find out in the incubator than as a TLP that the apache way
>> isn't really going to work for them at the moment.
>> 
>> 
>> On Sun, Apr 16, 2017 at 7:21 AM, John D. Ament 
>> wrote:
>> 
 On Sat, Apr 15, 2017 at 3:04 PM larry mccay  wrote:
 
 Well said.
 It is healthy to not have a podling graduate and subsequently struggle
>>> as a
 TLP.
 This is actually a success of sorts.
 
 At least until a majority of podlings have trouble. :)
 
 
>>> I may be reading Ted's email differently.  Or I might be reading your
>>> response wrong.
>>> 
>>> Retirement isn't a failure.  Podlings are meant to be experiments in some
>>> cases.  Can I build a strong enough community, can we follow the apache
>>> way.
>>> 
>>> There's a notion that the incubator adds over head to smaller projects.
>> If
>>> you're a one-or-two developer group, who can commit one small change and
>>> cut a release in an afternoon, coming to apache with our 3 day voting
>>> periods seems crazy.
>>> 
>>> For small projects like Sirona, they may benefit from rapid iterate,
>>> release, feedback cycles. This is where tooling like GitHub becomes much
>>> more useful.  Once you get wikis, websites going, you can iterate and
>> seem
>>> like a strong community.  Until you become a community of 100's of users.
>>> 
>>> We don't want to see struggling podlings graduate.  This is why the
>>> incubator has no time limit.  We do get worried when a podling's been
>> here
>>> for too long.
>>> 
>>> Basically, Sirona may see some success retiring from Apache, moving
>>> development to github, until they've been able to build a bigger
>> community.
>>> 
>>> 
 On Sat, Apr 15, 2017 at 2:55 PM, Ted Dunning 
 wrote:
 
> I think that we need to get over thinking of this state of affairs
>> is a
> "failure".
> 
> It is just one of the many different possible outcomes for
>> incubation.
>>> To
> my mind, having multiple possible outcomes is a *feature*, not a bug.
> 
> Obviously, we should not admit podlings that we aren't committed to
 helping
> become TLP's and we should help those podlings become TLP's. But
>> there
 are
> lots of different possible outcomes and only the podling can really
> determine which outcome it will have.
> 
> It is a fact of nature that we cannot always know whether a new
>> podling
> really has the right intent and contributor mix to become a good TLP.
> Sometimes it is apparent that the project will be a great fit and
 sometimes
> it is apparent that it won't be, but many times we won't exactly
>> know.
> There will be cases where a community will melt away and there will
>> be
> cases where a community really didn't get the point of the Apache
 license.
> In many cases, the world just changes and by the time it is time to
> graduate, the project just isn't the right thing to do any more.
> 
> As such, I think we need to (somewhat) over-admit podlings when there
>>> is
> doubt. That doesn't mean admit projects that just won't ever succeed,
>>> but
> it does mean we should be a little generous in terms of admission. We
> should vote to admit in cases of some doubt.
> 
> If that is true, then we have to expect that there will be a variety
>> of
> outcomes and we have to take that as a consequence of our initial
> generosity. This is not a cause for tears. Frankly, every project
>> that
> becomes an obvious candidate for retirement means that there is
>> another
> successful project that we admitted even though there was doubt.
> 
> IF it is time to retire Sirona, let's just do it.
> 
> 
> 
> On Sat, Apr 15, 2017 at 10:09 AM, Pierre Smits <
>> pierre.sm...@gmail.com
 
> wrote:
> 
>> It is very sad to see a project failing at growing a community.
>>> Looking
> at
>> the various public sources, I see:
>> 
>>   - just 2 pull request since its start in incubation
>>   - no postings on the user ml since December 2015
>>   - only 3 committing contributors since start in incubation
>>   - No description (readme) in github
>>   - No mission statement/goal description of the project on the
> project's
>>   

Re: Draft - Incubator PMC Board Report - April 2017

[P. Taylor Goetz]

ramework that simplifies common
> aspects of big data integration such as data ingestion, replication,
> organization and lifecycle management for both streaming and batch data
> ecosystems.
> 
> Gobblin has been incubating since 2017-02-23.
> 
> Few first steps has been made:
> 
> * mailing list setup
> * jira setup
> * few Apache account creation for new committers.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. Code import. Still need agreement from LinkedIn/Microsoft
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
>  None
> 
> How has the community developed since the last report?
> 
>  We are very first steps of the project
> 
> How has the project developed since the last report?
> 
>  First report :-)
> 
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
> 
>  [X] Initial setup
>  [ ] Working towards first release
>  [ ] Community building
>  [ ] Nearing graduation
>  [ ] Other:
> 
> Date of last release:
> 
>  N/A
> 
> When were the last committers or PPMC members elected?
> 
>  N/A
> 
> Signed-off-by:
> 
>  [X](gobblin) Olivier Lamy
>  [X](gobblin) Jean-Baptiste Onofre
> Comments:
>  [X](gobblin) Jim Jagielski
> Comments:
> 
> IPMC/Shepherd notes:
> 
> 
> 
> 
> Gossip
> 
> Gossip is an implementation of the Gossip Protocol.
> 
> Gossip has been incubating since 2016-04-28.
> 
> Three most important issues to address in the move towards graduation:
> 
>  1. A project leveraging Apache Gossip such as
> https://issues.apache.org/jira/browse/IGNITE-4837
>  2. Two additional active committers to handle management tasks like code
> review
>  3. Continued releases
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
> 
>  Two students are submitting proposals for Google Summer of Code. Both have
>  already contributed features which were committed to the project. We are
>  hopefully they both proposals will be accepted.
> 
> How has the community developed since the last report?
> 
>  The mailing list has been active with several people who were drawn to the
>  project by GSOC 17 labels placed on our tickets. Two of them have
>  contributed features that have been committed, and a third person (who
> will
>  not be doing GSOC) has asked to be assigned a ticket. Our last release had
>  roughly 5 different contributors, The mailing list is fairly active as we
>  review GSOC proposals. We have more than 50 stars on github which shows
>  that visibility is making a steady climb.
> 
> How has the project developed since the last report?
> 
>  A release 0.1.1 was completed right before our last report. We made an
>  aggressive list of features for 0.1.2. We de-prioritized some of the
> items,
>  but we completed far more than we expected. We had improvements in
>  performance, testing, and features. CRDT support seemed to be the biggest
>  'splash' feature.
> 
> How would you assess the podling's maturity?
> 
>  I am happy with the continued feature development and code/test
>  improvement. We are attracting interest of some new developers who seem
>  likely to stay involved and potentially be committers in the future. While
>  the majority of management and reviews is done by a few, others are
>  beginning to help with tasks like code reviews. As pointed out in the
> "move
>  towards graduation" section, having a couple other highly active
>  reviewers/committers would be a positive next step.
> 
> Please feel free to add your own commentary.
> 
>  [ ] Initial setup
>  [ ] Working towards first release
>  [x] Community building
>  [ ] Nearing graduation
>  [ ] Other:
> 
> Date of last release:
> 
>  2017-04-02 (April 02)
> 
> When were the last committers or PPMC members elected?
> 
>  Chandresh Pancholi added as a committer in February 2017
> 
> Signed-off-by:
> 
>  [ ](gossip) P. Taylor Goetz
> Comments:
>  [x](gossip) Josh Elser
> Comments:
>The podling is still working to attract new members, but those
>involved so far are doing well.
>  [x](gossip) Drew Farris
> Comments:
>It is great to see the interest driven by GSOC participation.
>Kudos to the team for engaging with GSOC.
> 
> IPMC/Shepherd notes:
> 
> 
> 
> 
> Griffin
> 
> Griffin is a open source Data Quality solution for distributed data systems
> at
> any scale in both streaming or batch data context
> 
> Griffin has been incubating since 

Re: Creating a podli...@incubator.apache.org mailing list

[P. Taylor Goetz]

+1 for moderation.

-Taylor

> On Apr 6, 2017, at 5:21 AM, John D. Ament  wrote:
> 
> I agree to both points.  I've already started on the script, based on the
> existing python scripts we use to generate our reports.
> 
> How do others feel about the moderation?  Its only for "official"
> communication so..
> 
> John
> 
>> On Wed, Apr 5, 2017 at 11:03 PM Greg Stein  wrote:
>> 
>> Hi John, et al,
>> 
>> From an Infrastructure position, I have several points w.r.t to this
>> request, and its associated Jira ticket [1] :
>> 
>> * The spam potential is large for this, so I suggest it gets treated like
>> announce@apache, which requires sending from @apache and forced moderation
>> of *all* messages. I hope we can have a mailing list to use those features
>> (a simple fan-out alias won't do it), with subscribers being other lists.
>> We'll note in the ticket if a problem arises.
>> 
>> * As I've raised elsewhere, Infrastructure work/costs have a direct
>> correlation to podling entry, and podling graduation. Adjusting the
>> podlings@ fan-out at entry/graduation is heaping on. more work. I've
>> spoken
>> with John on HipChat, and asked that the IPMC provide a script to fetch and
>> print the desired set of target dev@ lists (I don't want Infra to guess;
>> y'all need a script to define the set). We'll incorporate that into a daily
>> cron job. Whether the script uses LDAP or pulls podling.xml ... *shrug*
>> 
>> If there are any questions/concerns, then please continue here or in the
>> ticket.
>> 
>> Cheers,
>> Greg Stein
>> Infrastructure Administrator, ASF
>> 
>> [1] https://issues.apache.org/jira/browse/INFRA-13823
>> 
>> 
>> On Mon, Mar 20, 2017 at 1:52 PM, John D. Ament 
>> wrote:
>> 
>>> All,
>>> 
>>> Before I go ahead with it, wanted to see if others had any opinions.  I'm
>>> planning to ask infra to create a podlings@i.a.o mailing list, which
>> would
>>> go to all podlings dev@ list.  There may be some scenarios where we need
>>> to
>>> communicate out to all podlings.  For instance, the logo change and how
>> it
>>> impacts the podlings.
>>> 
>>> John
>>> 
>> 

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

Re: [VOTE] Apache Metron podling Graduation

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Mar 29, 2017, at 10:39 AM, Casey Stella <ceste...@gmail.com> wrote:
> 
> Hi Everyone,
> 
> I propose that we graduate Apache Metron (incubating) from the incubator.
> The full text of the proposal is below, with requisite modifications
> applied from the discussion thread.
> 
> The discuss thread can be found at
> https://lists.apache.org/thread.html/e5d106456b28562bdc947624c6f33e3281297dfd3803aab3d171bbad@%3Cgeneral.incubator.apache.org%3E
> 
> 
> Best,
> 
> Casey
> 
> Resolution:
> 
> Establish the Apache Metron 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 security analytics platform for big data use cases.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Metron Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
> 
> RESOLVED, that the Apache Metron Project be and hereby is
> responsible for the creation and maintenance of software
> related to:
> (a) A mechanism to capture, store, and normalize any type of security
> telemetry at extremely high rates.
> (b) Real time processing and application of enrichments
> (c) Efficient information storage
> (d) An interface that gives a security investigator a centralized view
> of data and alerts passed through the system.
> 
> RESOLVED, that the office of "Vice President, Apache Metron" 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 Metron Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Metron 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 Metron Project:
> 
> 
> PPMC by Affiliation:
> 
> Hortonworks:
>  Sheetal Dolas (sheetal_dolas)
>  Ryan Merriman (rmerriman)
>  Larry McCay (lmccay)
>  P. Taylor Goetz (ptgoetz)
>  Nick Allen (nickallen)
>  David Lyle (lyle)
>  George Vetticaden (gvetticaden)
>  James Sirota (jsirota)
>  Casey Stella (cstella)
>  Michael Perez (mperez)
>  Kiran Komaravolu (kirankom)
>  Vinod Kumar Vavilapalli (vinodkv)
> 
> Cisco:
>  Debo Dutta (ddutta)
>  Discovery Gerdes (discovery)
> 
> Rackspace:
>  Oskar Zabik (smogg)
>  Andrew Hartnett (dev_warlord)
>  Paul Kehrer (reaperhulk)
>  Sean Schulte (sirsean)
> 
> B23:
>  Mark Bittmann (mbittmann)
>  Dave Hirko (dbhirko)
>  Brad Kolarov (bjkolly)
> 
> Mantech:
>  Charles Porter (cporter)
>  Ray Urciuoli (rurcioli)
> 
> Fogbeam Labs:
>  Phillip Rhodes (prhodes)
> 
> 
> 
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella
> be appointed to the office of Vice President, Apache Metron, 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 Metron PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Metron Project; and be it further
> 
> RESOLVED, that the Apache Metron Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Metron podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Metron podling encumbered upon the Apache Incubator
> Project are hereafter discharged.


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

Re: [DISCUSS] Apache Metron podling Graduation

[P. Taylor Goetz]

To be honest, I don't know, but I don't see it as a problem.

I will admit upfront that I am a Hortonworks employee, so there is potential 
for bias. But I always try to wear the right hat, even when my position may not 
please my employer.

As a mentor (to this and other podlings), I try to instill that ethic during 
incubation and thereafter.

In the Metron community I see some that share that ethic. They selected a PMC 
Chair that gets it and I trust will serve the project well in that role.

Yes, the project is Hortonworks-heavy. But I think they are doing things right 
in terms of the Apache Way. I also intend to participate in the PMC to help 
ensure it remains that way.

-Taylor


> On Mar 24, 2017, at 8:15 PM, Dave Fisher <dave2w...@comcast.net> wrote:
> 
> This is a list of 24 of which 12 are Hortonworks.
> 
> Can we assume that the other 12 of which 6 are PPMC are unaffiliated?
> 
> What percentage of the commits are coming from Hortonworks affiliated 
> contributors?
> 
> Thanks,
> Dave
> 
>> On Mar 23, 2017, at 8:39 PM, Casey Stella <ceste...@gmail.com> wrote:
>> 
>> Of course, very fair question.  Also, yes, the we have 36 committers as all
>> PPMC members are committers.
>> 
>> The affiliations are as follows:
>> 
>> Hortonworks:
>> * Sheetal Dolas (sheetal_dolas)
>> * Larry McCay (lmccay)
>> * P. Taylor Goetz (ptgoetz)
>> * Ryan Merriman (rmerriman)
>> * James Sirota (jsirota)
>> * Casey Stella (cstella)
>> * David Lyle (lyle)
>> * Nick Allen (nickallen)
>> * George Vetticaden (gvetticaden)
>> * Vinod Kumar Vavilapalli (vinodkv)
>> * Kiran Komaravolu (kirankom)
>> * Michael Perez (mperez)
>> 
>> Cisco:
>> * Debo Dutta (ddutta)
>> * Discovery Gerdes (discovery)
>> 
>> Rackspace:
>> * Oskar Zabik (smogg)
>> * Andrew Hartnett (dev_warlord)
>> * Paul Kehrer (reaperhulk)
>> * Sean Schulte (sirsean)
>> 
>> B23:
>> * Mark Bittmann (mbittmann)
>> * Dave Hirko (dbhirko)
>> * Brad Kolarov (bjkolly)
>> 
>> Mantech:
>> * Charles Porter (cporter)
>> * Ray Urciuoli (rurcioli)
>> 
>> Fogbeam Labs:
>> * Phillip Rhodes (prhodes)
>> 
>> 
>> 
>> 
>> 
>>> On Thu, Mar 23, 2017 at 9:34 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>>> 
>>> 
>>> 
>>>> On Mar 23, 2017, at 7:38 PM, John D. Ament <johndam...@apache.org>
>>> wrote:
>>>> 
>>>>> On Thu, Mar 23, 2017 at 3:10 PM P. Taylor Goetz <ptgo...@gmail.com>
>>> wrote:
>>>>> 
>>>>> As a mentor, I fully support Metron's graduation. The community has
>>> come a
>>>>> long way, learned to make solid releases, build a sustainable community,
>>>>> and follow the Apache Way.
>>>>> 
>>>>> One minor nit: The paddling status page is missing a few Apache IDs,
>>> but I
>>>>> see them in the resolution, so it's an easy fix.
>>>>> 
>>>>> 
>>>> Paddlings are always out of sync :-P
>>>> 
>>>> One other nit - I'm not sure why you only have 6 committers.  I think you
>>>> mean 30 committers (all PMC members are committers).  Can you provide the
>>>> associations of PMC members and employers?
>>> 
>>> Metron PPMC,
>>> 
>>> Can you respond? I feel this is a valid question.
>>> 
>>> -Taylor
>>> 
>>> -
>>> 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] Apache Metron podling Graduation

[P. Taylor Goetz]

> On Mar 23, 2017, at 7:38 PM, John D. Ament <johndam...@apache.org> wrote:
> 
>> On Thu, Mar 23, 2017 at 3:10 PM P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>> As a mentor, I fully support Metron's graduation. The community has come a
>> long way, learned to make solid releases, build a sustainable community,
>> and follow the Apache Way.
>> 
>> One minor nit: The paddling status page is missing a few Apache IDs, but I
>> see them in the resolution, so it's an easy fix.
>> 
>> 
> Paddlings are always out of sync :-P
> 
> One other nit - I'm not sure why you only have 6 committers.  I think you
> mean 30 committers (all PMC members are committers).  Can you provide the
> associations of PMC members and employers?

Metron PPMC,

Can you respond? I feel this is a valid question.

-Taylor

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

Re: [DISCUSS] Apache Metron podling Graduation

[P. Taylor Goetz]

As a mentor, I fully support Metron's graduation. The community has come a long 
way, learned to make solid releases, build a sustainable community, and follow 
the Apache Way.

One minor nit: The paddling status page is missing a few Apache IDs, but I see 
them in the resolution, so it's an easy fix.

-Taylor

> On Mar 23, 2017, at 5:53 PM, Julian Hyde <jh...@apache.org> wrote:
> 
> I reviewed the last few months on the dev and private lists and the project 
> is healthy, growing, increasing in diversity and making regular releases. In 
> my opinion it is ready to graduate. Good luck!
> 
> Julian
> 
> 
>> On Mar 23, 2017, at 11:32 AM, Casey Stella <ceste...@gmail.com> wrote:
>> 
>> Hi Everyone,
>> 
>> The incubating Apache Metron community believes it is time to graduate
>> to TLP.
>> 
>> Apache Metron entered incubation in December of 2015. Since then, we've
>> overcome technical challenges to remove Category X dependencies, and
>> made 3 releases. Our most recent release contains binary convenience
>> artifacts. We are a very helpful and engaged community, ready to answer
>> all questions and feedback directed to us via the user list. Through our
>> time in incubation we've added a number of committers and promoted some
>> of them to PPMC membership. We are actively pursuing others. While we do
>> still have issues to address raised by means of the maturity model, all
>> projects are ongoing processes, and we believe we no longer need the
>> incubator to continue addressing these issues.
>> 
>> To inform the discussion, here is some basic project information:
>> 
>> Project status:
>> http://incubator.apache.org/projects/metron.html
>> 
>> Project website:
>> https://metron.incubator.apache.org/
>> 
>> Project documentation:
>>  https://cwiki.apache.org/confluence/display/METRON/Documentation
>> 
>> Maturity assessment:
>> 
>> https://cwiki.apache.org/confluence/display/METRON/Apache+Project+Maturity+Model
>> 
>> Community Vote to Graduate:
>> 
>> https://lists.apache.org/thread.html/540378e2773b1b2ce2af498e56a6435e547c04948a6b496b9a4ffc71@%3Cdev.metron.apache.org%3E
>> 
>> DRAFT of the board resolution is at the bottom of this email
>> 
>> Proposed PMC size: 24 members
>> 
>> Total number of committers: 6 members
>> 
>> 
>> 516 commits on develop
>> 34 contributors across all branches
>> 
>> dev list averaged ~650 msgs/month for the last 3 months
>> 
>> 
>> Resolution:
>> 
>> Establish the Apache Metron 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 security analytics platform for big data use cases.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Metron Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>> 
>> RESOLVED, that the Apache Metron Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to:
>> (a) A mechanism to capture, store, and normalize any type of security
>> telemetry at extremely high rates.
>> (b) Real time processing and application of enrichments
>> (c) Efficient information storage
>> (d) An interface that gives a security investigator a centralized view
>> of data and alerts passed through the system.
>> 
>> RESOLVED, that the office of "Vice President, Apache Metron" 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 Metron Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Metron 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 Metron Project:
>> 
>> 
>> PPMC:
>> Mark Bittmann (mbittmann)
>> Sheetal Dolas (sheetal_dolas)
>> Debo Dutta (ddutta)
>> Discovery Gerdes (discovery)
>> Andrew Hartnett (dev_warlord)
>> Dave Hirko (dbhirko)
>> Paul Kehrer (reaperhulk)
>> Brad Kolarov (bjkolly)
>> Kiran Komaravolu (kirankom)
>

Re: [VOTE] Release Gossip (Incubating) version gossip-0.1.2-incubating (RC1)

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Mar 13, 2017, at 4:03 PM, Edward Capriolo  wrote:
> 
> I am pleased to call an IPMC vote for gossip-0.1.2-incubating.
> 
> The PPMC vote thread is here:
> 
> https://lists.apache.org/thread.html/5571d2996633f3a7ed10f3b0de3366702027db3b2f7870403c390141@%3Cdev.gossip.apache.org%3E
> 
> Additionally a description of the new features in the release is here:
> 
> https://lists.apache.org/thread.html/d244f03eba775c0de96bf527c67dce80e393c7ed614d43650cb23793@%3Cdev.gossip.apache.org%3E
> 
> Release this package?
> [ ] +1 yes
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
> 
> Thank you,
> Edward


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

Re: Creating a podli...@incubator.apache.org mailing list

[P. Taylor Goetz]

+1 for both.

-Taylor

> On Mar 20, 2017, at 4:17 PM, John D. Ament  wrote:
> 
> On Mon, Mar 20, 2017 at 12:55 PM Luciano Resende  >
> wrote:
> 
>> On Mon, Mar 20, 2017 at 12:00 PM John D. Ament 
>> wrote:
>> 
>>> All,
>>> 
>>> Before I go ahead with it, wanted to see if others had any opinions.  I'm
>>> planning to ask infra to create a podlings@i.a.o mailing list, which
>> would
>>> go to all podlings dev@ list.  There may be some scenarios where we need
>>> to
>>> communicate out to all podlings.  For instance, the logo change and how
>> it
>>> impacts the podlings.
>>> 
>>> John
>>> 
>> 
>> This would be more like an alias, similar to @PMCs right ? Also, in the
>> past, some of these communications would go to podling private (e.g. Gsoc
>> info) where there was a request for the podling pmc to discuss this
>> appropriately in their dev lists? That might still be a viable approach.
>> 
>> 
> Yes, I believe that's how infra would implement it.  It isn't meant to
> replace general@ but instead allow us a convenient way to email blast all
> podlings.
> 
> As I was typing the email, I thought about private lists.  I wouldn't mind
> a podlings-private@i.a.o  as well.
> 
> 
>> BTW, podlings, particular podling mentors should (MUST) be following all
>> pertinent general@ discussions.
>> --
>> Sent from my Mobile device

Re: [VOTE] Releasing Apache Metron (incubating) 0.3.1-RC5

[P. Taylor Goetz]

+1 (binding)

- signature checks out
- DISCLAIMER exists
- L look good
- “incubating” in package name
- can build from source (had to skip tests)

-Taylor

> On Feb 27, 2017, at 1:53 PM, Casey Stella  wrote:
> 
> This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating
> 
> Full list of changes in this release:
> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
> -incubating/CHANGES
> 
> The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.
> git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc5-incubating
> 
> The source archive being voted upon can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
> -incubating/apache-metron-0.3.1-rc5-incubating.tar.gz
> 
> Other release files, signatures and digests can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
> -incubating/
> 
> The release artifacts are signed with the following key:
> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.
> git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/
> apache-metron-0.3.1-rc5-incubating
> 
> The book associated with this RC is located at
> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5
> -incubating/book-site/index.html
> 
> Please vote on releasing this package as Apache Metron 0.3.1-RC5 incubating
> 
> When voting, please list the actions taken to verify the release.
> 
> Recommended build validation and verification instructions are posted here:
> https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds
> 
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Metron 0.3.1-RC5 incubating
> 
> [ ]  0 No opinion
> 
> [ ] -1 Do not release this package because...


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

Re: Forming of a Selection Committee for New Incubator Logo

[P. Taylor Goetz]

> On Feb 17, 2017, at 12:22 PM, Marvin Humphrey  wrote:
> 
> (FWIW, I used to work in graphic design and prepress.)

Me too. ;)

I’d also be interested in participating.

-Taylor

Re: Podling Graduation Rally

[P. Taylor Goetz]

I can help with pushing Metron forward. They have been discussing graduation 
for a while now.

-Taylor


> On Feb 13, 2017, at 7:28 AM, John D. Ament  wrote:
> 
> All,
> 
> As mentioned in this month's report, there are 63 active podlings.  While
> I've been chasing retiring podlings, I think it would be good for the
> community as a whole to look closely as podlings and see what we can do to
> graduate podlings that seem to be doing well.
> 
> Take a look at the last two reports:
> 
> https://wiki.apache.org/incubator/February2017
> https://wiki.apache.org/incubator/January2017
> 
> Last month, I listed 4 podlings that appear to have completed all
> graduation requirements, but remain in the incubator (Airflow, BatchEE,
> Freemarker, Metron).  I didn't include that in February, but if I had to
> list the names, it would be: CarbonData, Edgent, Fineract, Guacamole,
> PredictionIO, SystemML, Tamaya, Unomi (but that's entirely my POV/opinion
> unless others want to chime in).
> 
> So I'm curious, what can others do to help these 12 podlings get past the
> finish line?
> 
> John


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

Re: [DISCUSS] Podling report format changes

[P. Taylor Goetz]

+1

-Taylor

> On Jan 25, 2017, at 10:43 AM, John D. Ament <johndam...@apache.org> wrote:
> 
> Just to provide, here's the proposed patch I have for the website
> 
> Index: content/guides/ppmc.xml
> ===
> --- content/guides/ppmc.xml (revision 1780221)
> +++ content/guides/ppmc.xml (working copy)
> @@ -43,7 +43,7 @@
> 
>   Private Mail List
> 
> -A private mail list, named project-private, lets
> +A private mail list, named private@project, lets
> the PPMC discuss confidential topics.
> Most communication should be on the Podling's dev list!
> The private list is used only for confidential discussions that
> @@ -107,8 +107,12 @@
>  Project name and one-line summary.
>  Date of entry to the Incubator.
>  Top three items to resolve before graduation.
> + Internal issues that may require IPMC or Board input
> + How has the community changed
> + How has the project changed
> + How mature the project feels they are
>   
> -
> +
>   Here are the points to be addressed:
>   
> Is there anything that the Incubator PMC or ASF Board
> 
> On Wed, Jan 25, 2017 at 6:41 AM John D. Ament <johndam...@apache.org> wrote:
> 
>> On Wed, Jan 25, 2017 at 12:40 AM P. Taylor Goetz <ptgo...@gmail.com>
>> wrote:
>> 
>> I'm fine with 1 and 3, but 2 gives me pause. I like the idea of the
>> maturity model, but is it yet another burden on mentors?
>> 
>> 
>> I would hope not.  How often are mentors writing the reports for podlings,
>> vs pushing that the podlings write the reports themselves?  I guess its a
>> factor of how embedded within the podling that mentor is.  And granted, I'm
>> not pushing that its the ComDev Apache Project Maturity Model [1] being
>> followed
>> 
>> [1]:
>> http://community.apache.org/apache-way/apache-project-maturity-model.html
>> 
>> 
>> 
>> If we are trying to increase mentor engagement, we probably don't want to
>> set too high  a bar.
>> 
>> -Taylor
>> 
>>> On Jan 24, 2017, at 8:15 PM, John D. Ament <john.d.am...@gmail.com>
>> wrote:
>>> 
>>> All,
>>> 
>>> The Incubator PMC has received feedback from the board that changes may
>>> need to be made to the structure of our report.  Specifically, there is
>>> confusion from the board members over how podlings get classified.  There
>>> is also a request to increase and improve mentor feedback on podling
>>> reports.  Based on this input, I would like to propose the following
>>> changes to our report format.  I would like to try to implement this for
>>> the March report, if not before then.
>>> 
>>> 1. Eliminate the podling summary section of the report.  It shouldn't be
>> on
>>> the report manager to classify each podling.  We have begun leveraging a
>>> maturity model for podlings, while its not required to fulfill it serves
>> as
>>> an equivalent to this section.  The list of podlings who failed to report
>>> shall remain.
>>> 
>>> 2. Add a "Podling Maturity Assessment" to the individual podling reports.
>>> This would give a clear opportunity for each podling to describe how they
>>> are doing, perhaps compared to the maturity model or our classic
>> categories.
>>> 
>>> 3. Change the mentor sign off section to include a per-mentor comment.
>>> E.g. instead of the current:
>>> 
>>> [ ](podling) mentor1
>>> [ ](podling) mentor2
>>> [ ](podling) mentor3
>>> 
>>> It would be:
>>> 
>>> [ ](podling) mentor1
>>> Comments:
>>> [ ](podling) mentor2
>>> Comments:
>>> [ ](podling) mentor3
>>> Comments:
>>> 
>>> And rename Shepherd/Mentor notes: to just "Shepherd notes:"
>>> 
>>> Thoughts?
>>> 
>>> John
>> 
>> -
>> 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] Podling report format changes

[P. Taylor Goetz]

I'm fine with 1 and 3, but 2 gives me pause. I like the idea of the maturity 
model, but is it yet another burden on mentors?

If we are trying to increase mentor engagement, we probably don't want to set 
too high  a bar.

-Taylor

> On Jan 24, 2017, at 8:15 PM, John D. Ament  wrote:
> 
> All,
> 
> The Incubator PMC has received feedback from the board that changes may
> need to be made to the structure of our report.  Specifically, there is
> confusion from the board members over how podlings get classified.  There
> is also a request to increase and improve mentor feedback on podling
> reports.  Based on this input, I would like to propose the following
> changes to our report format.  I would like to try to implement this for
> the March report, if not before then.
> 
> 1. Eliminate the podling summary section of the report.  It shouldn't be on
> the report manager to classify each podling.  We have begun leveraging a
> maturity model for podlings, while its not required to fulfill it serves as
> an equivalent to this section.  The list of podlings who failed to report
> shall remain.
> 
> 2. Add a "Podling Maturity Assessment" to the individual podling reports.
> This would give a clear opportunity for each podling to describe how they
> are doing, perhaps compared to the maturity model or our classic categories.
> 
> 3. Change the mentor sign off section to include a per-mentor comment.
> E.g. instead of the current:
> 
>  [ ](podling) mentor1
>  [ ](podling) mentor2
>  [ ](podling) mentor3
> 
> It would be:
> 
>  [ ](podling) mentor1
>  Comments:
>  [ ](podling) mentor2
>  Comments:
>  [ ](podling) mentor3
>  Comments:
> 
> And rename Shepherd/Mentor notes: to just "Shepherd notes:"
> 
> Thoughts?
> 
> John

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

Re: [VOTE] Release Gossip version gossip-0.1.1-incubating (RC2)

[P. Taylor Goetz]

Forwarding my vote from Devi list. +1 (binding)

-Taylor

> On Jan 11, 2017, at 3:06 PM, Josh Elser <els...@apache.org> wrote:
> 
> Forwarding my +1 (binding)
> 
> Edward Capriolo wrote:
>> I am pleased to call an IPMC vote for gossip-0.1.1-incubating.
>> 
>> The PPMC vote thread is here:
>> The vote thread is here:
>> https://lists.apache.org/thread.html/86bf41b491a575c4751c1191f8f9d8ee2d17bedeac4bdef582ba5f03@%3Cdev.gossip.apache.org%3E
>> 
>> Release this package?
>> [ ] +1 yes
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>> 
>> Thank you,
>> Edward
>> 
>> Below is a copy of the [RESULT] for voting:
>> -
>> The vote for gossip-0.1.1-incubating (RC2) has passed.
>> 
>> Josh Elser +1
>> P. Taylor Goetz +1
>> Gary Dusbabek +1
>> Chandresh Pancholi +1
>> Edward Capriolo +1
>> 
>> The vote thread is here:
>> https://lists.apache.org/thread.html/86bf41b491a575c4751c1191f8f9d8ee2d17bedeac4bdef582ba5f03@%3Cdev.gossip.apache.org%3E
>> 
>> I am pleased to be calling this vote for the source release of Apache Gossip
>> 
>> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>> https://repository.apache.org/content/repositories/orgapachegossip-1002/
>> 
>> The Git commit ID is:
>> 6720f35beb8718ae39018211f33bbff2ac782fb6
>> https://github.com/apache/incubator-gossip/commit/6720f35beb8718ae39018211f33bbff2ac782fb6
>> 
>> The tag is:
>> https://github.com/apache/incubator-gossip/tree/gossip-0.1.1-incubating-rc2
>> 
>> Checksums of:
>> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip
>> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip.md5
>> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip.sha1
>> SHA1: 66dfe09a925fe2650fd3d85c97fdc10b049a9776
>> MD5: 2695f11e714edb1364a4105b970039b8
>> 
>> Are confirmed:
>> [edward@jackintosh tmp]$ wget
>> https://repository.apache.org/content/repositories/orgapachegossip-1002/org/apache/gossip/gossip/0.1.1-incubating/gossip-0.1.1-incubating-source-release.zip
>> [edward@jackintosh tmp]$ md5sum gossip-0.1.1-incubating-source-release.zip
>> 2695f11e714edb1364a4105b970039b8  gossip-0.1.1-incubating-source-release.zip
>> [edward@jackintosh tmp]$ sha1sum gossip-0.1.1-incubating-source-release.zip
>> 66dfe09a925fe2650fd3d85c97fdc10b049a9776
>>  gossip-0.1.1-incubating-source-release.zip
>> 
>> Release artifacts are signed with the following key:
>> http://people.apache.org/~ecapriolo/
>> http://people.apache.org/~ecapriolo/ecapriolo_asf.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/incubator/gossip/KEYS
>> 
>> Please download the release candidate and evaluate the necessary items
>> including checking hashes, signatures, build from source, and test.
>> 
>> Note: The end-to-end tests (ShutdownDeadtimeTest) tend to be flakey.
>> https://issues.apache.org/jira/browse/GOSSIP-22 will address this feature
>> in next release.
>> 
>> Release this package?
>> [ ] +1 yes
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because because...
>> 
> 
> -
> 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] Drop incubating requirement of Maven artifacts

[P. Taylor Goetz]

-1 (binding)

I look at the “-incubating” tag in the same way I do the DISCLAIMER file and 
the podling website disclaimer — As an indicator and reminder that a release 
may not be completely clean from a licensing/policy perspective.

-Taylor

> On Jan 3, 2017, at 4:20 PM, Josh Elser  wrote:
> 
> (late to the party)
> 
> -1 (binding) as an ask to table the VOTE and try to reach some better 
> consensus.
> 
> I have to agree with Julian that some more discussion may be prudent here. 
> There are definitely two divided camps, both of which bring good points to 
> the table.
> 
> * Differing policies for the languages/tools of products that podlings create 
> (maven projects vs. python/ruby projects). Julian states this very well.
> 
> * A clear definition of what the IPMC thinks "x.y.z-incubating" should mean 
> and some better public-facing docs on what "incubating releases" actually 
> mean.
>  - Groovy is a great, recent example. They were a very "mature" software 
> project, but still were "immature" in the terms of an ASF community (purely 
> speaking of them as being a podling, not a TLP). Personally, if I see the 
> -incubating suffix on a version, I can recognize that the *community* is the 
> thing at risk. However, I can also see how those less affiliated with the 
> incubator could interpret it as "software quality". John states this very 
> well in the VOTE text itself -- it leaves me wondering if we couldn't just be 
> more clear out of the gates.
> 
> I also need to re-read the original thread from freemarker (no [DISCUSS] in 
> the subject and the holidays kept me from reading it closely) to think about 
> the original stated problem some more.
> 
> - Josh
> 
> Julian Hyde wrote:
>> John,
>> 
>> I see your points, and hopefully you see mine. I think we can agree on one 
>> thing: we have not reached consensus. :)
>> 
>> The inconsistency among build tools is a red herring. If we want consistency 
>> across build tools (and more importantly across package formats, regardless 
>> of the tool used to build them), let’s first figure out what we want, and 
>> apply this to all build tools.
>> 
>> Julian
>> 
>> 
>>> On Jan 3, 2017, at 3:34 AM, John D. Ament  wrote:
>>> 
>>> Carsten, Julian,
>>> 
>>> I want to reiterate my notes from a prior message [1] in case there is any
>>> confusion over the ask.  There is a "best practice" around maven specific
>>> releases that has been treated as policy,  [2].  This best practice for
>>> some reason is only applied if you are using the maven build tool.  E.g.
>>> published python packages, ruby gems do not have this requirement.  The
>>> purpose of this thread is to realign maven specific releases with the other
>>> convenience binaries published by podlings.
>>> 
>>> This is not intended to drop the -incubator/-incubating tag applied to
>>> source releases.  It was however established in 2008 [3] that releases
>>> published by the incubator were endorsed, the -incubator/incubating tag was
>>> to imply that the project itself was not considered stable and could go
>>> away.
>>> 
>>> John
>>> 
>>> [1]:
>>> https://lists.apache.org/thread.html/c6daddf2d564685acdcd14a876bebf392b25c268905b353e36b3cac5@%3Cgeneral.incubator.apache.org%3E
>>> [2]:
>>> http://incubator.apache.org/guides/release-java.html#best-practice-maven
>>> [3]:
>>> https://lists.apache.org/thread.html/0b6c065a908c5f9ec39fa78c31b39c83a6fea29eb34fada0ee070413@1222432864@%3Cgeneral.incubator.apache.org%3E
>>> 
>>> 
>>> On Tue, Jan 3, 2017 at 1:47 AM Carsten Ziegeler
>>> wrote:
>>> 
 -1
 
 I followed the "other thread" but it's still unclear to me what real
 problem this tries to solve.
 As others noted, there should be an indicator whether this is already an
 official Apache project or in the incubator and adding it to the version
 information is the solution with causes the least amount of pain for
 users. It's a simple marker, clearly visible for any user.
 And once the project is out of the incubator, users simply need to
 update to a new version - something which they would do anyway.
 
 Carsten
 
 John D. Ament wrote
> All,
> 
> I'm calling to vote on a proposed policy change.  Current guide at [1]
> indicates that maven artifacts should include incubator (or incubating)
 in
> the version string of maven artifacts.  Its labeled as a best practice,
 not
> a requirement and is not a policy followed on other repository management
> tools (e.g. PyPi).
> 
> I therefore push forward that the incubator will cease expecting
 java-based
> projects to publish artifacts with "-incubating" in the version string,
> with the understanding that:
> 
> - Incubating is a term used to refer to a project's stability, not a
> release's stability.  It is generally understood that incubating projects
> are not necessarily 

Re: [FINAL] Incubator PMC Board Report - November 2016

[P. Taylor Goetz]

Yeah, they pulled their report, but their still listed in the “Summary of 
podling reports” section.

-Taylor

> On Nov 11, 2016, at 3:34 PM, John D. Ament <johndam...@apache.org> wrote:
> 
> I believe they already removed themselves.
> 
> On Nov 11, 2016 15:24, "P. Taylor Goetz" <ptgo...@gmail.com> wrote:
> 
>> Hi John,
>> 
>> Sorry for the late change request, but is it okay to remove Metron from
>> the report front matter since they aren’t due to report this month?
>> 
>> -Taylor
>> 
>>> On Nov 11, 2016, at 8:12 AM, John D. Ament <johndam...@apache.org>
>> wrote:
>>> 
>>> All,
>>> 
>>> I'll be submitting this report in a couple of hours, on behalf of the
>>> IPMC.  I don't see any changes, but I will grab the current copy from
>>> https://wiki.apache.org/incubator/November2016 .
>>> 
>>> John
>>> 
>>> On Wed, Nov 9, 2016 at 9:12 PM John D. Ament <johndam...@apache.org>
>> wrote:
>>> 
>>>> All,
>>>> 
>>>> Below is the final draft of this month's report.
>>>> 
>>>> John
>>>> 
>>>> Incubator PMC report for November 2016
>>>> 
>>>> The Apache Incubator is the entry path into the ASF for projects and
>>>> codebases wishing to become part of the Foundation's efforts.
>>>> 
>>>> There are currently 63 podlings incubating - no change from last month.
>>>> The Geode podling has begun discussions around graduation.  There were
>> two
>>>> new IPMC members added this past month.  The IPMC approved 17 releases
>> this
>>>> month as well.
>>>> 
>>>> * Community
>>>> 
>>>> New IPMC members:
>>>> 
>>>> - Felix Meschberger
>>>> - Stephan Ewen
>>>> 
>>>> People who left the IPMC:
>>>> 
>>>> - None
>>>> 
>>>> * New Podlings
>>>> 
>>>> - None
>>>> 
>>>> * Graduations
>>>> 
>>>> The board has motions for the following:
>>>> 
>>>> - Geode
>>>> 
>>>> * Releases
>>>> 
>>>> The following releases entered distribution during the month of
>>>> October:
>>>> 
>>>> - Apache Unomi1.1.0-incubating 2016-10-03
>>>> - Apache Impala   2.7.0-incubating 2016-10-04
>>>> - Apache Fluo 1.0.0-incubating 2016-10-05
>>>> - Apache Htrace   4.2.0-incubating 2016-10-07
>>>> - Apache PredictionIO 0.10.0-incubating2016-10-07
>>>> - Apache Pirk 0.2.0-incubating 2016-10-09
>>>> - Apache HAWQ 2.0.0.0-incubating   2016-10-10
>>>> - Apache CarbonData   0.1.1-incubating 2016-10-11
>>>> - Apache Metron   0.2.1BETA-incubating 2016-10-13
>>>> - Apache Geode1.0.0-incubating 2016-10-15
>>>> - Apache Mnemonic 0.3.0-incubating 2016-10-21
>>>> - Apache Juneau   6.0.0-incubating 2016-10-24
>>>> - Apache Fineract 0.4.0-incubating 2016-10-25
>>>> - Apache Fluo Recipes 1.0.0-incubating 2016-10-27
>>>> - Apache Rya  3.2.10-incubating2016-10-28
>>>> - Apache S2Graph  0.1.0-incubating 2016-10-30
>>>> - Apache Beam 0.3.0-incubating 2016-10-31
>>>> 
>>>> 
>>>> * IP Clearance
>>>> 
>>>> - None
>>>> 
>>>> * Legal / Trademarks
>>>> 
>>>> - Incoming podlings are pushing more for GitHub as master approaches.
>>>> - In addition, the usage of GitHub Issues continues to be asked.
>>>> - Better alignment between all impacted parties is needed for both of
>>>> these.
>>>> 
>>>> * Infrastructure
>>>> 
>>>> - While the loss of a server is never convenient, the report manager
>>>> gives huge kudos to the infra team for replacing the moin-moin wiki
>> server
>>>> quickly, avoiding much impact on this months report.
>>>> 
>>>> * Miscellaneous
>>>> 
>>>> - None
>>>> 
>>>> * Credits
>>>> 
>>>> - Report Manager: John D. Ament
>>>> 
>>>>  Summary of podling reports 
>

Re: [FINAL] Incubator PMC Board Report - November 2016

[P. Taylor Goetz]

.1.  Now using ASF-associated signing key.  Feedback from
>> previous release addressed.
>>  * Website updated alongside 1.3.1 release.
>>  * Cleaned up release instructions.
>> 
>> Date of last release:
>> 
>>  2016-08-10
>> 
>> When were the last committers or PMC members elected?
>> 
>>  July 2016 (Eyal Allweil)
>> 
>> Signed-off-by:
>> 
>>  [ ](datafu) Ashutosh Chauhan
>>  [X](datafu) Roman Shaposhnik
>>  [ ](datafu) Ted Dunning
>> 
>> Shepherd/Mentor notes:
>> 
>> (rvs) pushing this community towards graduation is pretty high on my TODO
>> list. I think they are as ready as they are ever going to be.
>> 
>> 
>> 
>> DistributedLog
>> 
>> DistributedLog is a high-performance replicated log service. It offers
>> durability, replication and strong consistency, which provides a
>> fundamental
>> building block for building reliable distributed systems.
>> 
>> DistributedLog has been incubating since 2016-06-24.
>> 
>> Three most important issues to address in the move towards graduation:
>> 
>>  1.Continue to grow the community, and increase diversity of community.
>>  2.Improve documentation, including documentation of project and
>> processes.
>>  3.Successful releases.
>> 
>> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>> 
>> None
>> 
>> 
>> How has the community developed since the last report?
>> 
>> 1. Increase in contributions from community.
>>   - 8 created and 4 resolved issues in community JIRA in October.
>> 2. Lots of engagement on documentation.
>>   - Enhance existing documents,
>>   - Setup guides for developers and committers.
>> 3. Increased traffic on the mailing list, in particular, due to committers
>> engaging more actively with contributors.
>>   - we have 35 people subscribed mail list.
>>   - 125 messages to distributedlog mail list in October.
>> 
>> 
>> How has the project developed since the last report?
>> 
>> 1. Documentation has improved for project build and project deployment.
>> Added more information on  community page.
>>New added pages:
>>https://cwiki.apache.org/confluence/display/DL/Developer+Guide
>>https://cwiki.apache.org/confluence/display/DL/Committer+Guide
>> 2. Involved more discussion of new ideas and bring in new features.
>> Include major discussions like 'transaction support', 'batch commit',
>> "EventStore" . etc.
>> 3. First release expected on November, and repackaging of the project
>> under apache namespace are being discussed.
>> - Pull requests for repackaging.
>> - The major blocker is https://issues.apache.org/jira/browse/DL-2. We
>> were expecting to let DL depends on an official bk version.
>> 
>> 
>> Date of last release:
>> NA
>> 
>> 
>> When were the last committers or PMC members elected?
>> NA
>> 
>> Signed-off-by:
>> 
>>  [ ](distributedlog) Flavio Junqueira
>>  [ ](distributedlog) Chris Nauroth
>>  [X](distributedlog) Henry Saputra
>> 
>> 
>> 
>> Eagle
>> 
>> Eagle is a Monitoring solution for Hadoop to instantly identify access to
>> sensitive data, recognize attacks, malicious activities and take actions in
>> real time.
>> 
>> Eagle has been incubating since 2015-10-26.
>> 
>> Three most important issues to address in the move towards graduation:
>> 
>>  1.  Jira, PR are all populated with good description so that people can
>> reference in the future.
>>  2.  Massive improvement on unit test, now it becomes stable and build
>> status is closed monitored in README
>>  3.  Community has one more discussion about graduation and all are with
>> positive feedback, and we are going through the graduation steps.
>> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>> 
>>  Nil
>> 
>> How has the community developed since the last report?
>> 
>>  - Presented in conference: QCon Shanghai
>>  - More active contributors from YHD.com participate in large feature
>> development
>> 
>> How has the project developed since the last report?
>> 
>>  - 0.5 version is being in active development. This version will include
>> big improvement in application management and alert engine.
>>  - Job monitoring feature is ready including map/reduce and spark job
>>  - Standalon

Re: [VOTE] Accept RocketMQ into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On Nov 10, 2016, at 11:41 AM, Bruce Snyder  wrote:
> 
> Subsequent to the discussion on RocketMQ, I would like to call a vote on
> accepting RocketMQ into the Apache Incubator.
> 
> [ ] +1 Accept RocketMQ into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept RocketMQ into the Apache Incubator because...
> 
> The proposal is pasted below and also available in the wiki here:

[RESULT] [IP CLEARANCE] Apache Storm JMS Integration

[P. Taylor Goetz]

With 72 hours having elapsed with no objections, this vote passes.

-Taylor

> On Sep 29, 2016, at 2:43 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> 
> Apache Storm has received a code donation for Storm JMS Integration:
> 
> http://incubator.apache.org/ip-clearance/storm-jms.html 
> <http://incubator.apache.org/ip-clearance/storm-jms.html>
> 
> The source code can be found at https://github.com/ptgoetz/storm-jms 
> <https://github.com/ptgoetz/storm-jms> with the following git commit SHA: 
> aab6acdf316c48bf566e37776790116f2794199b
> 
> Please vote to approve this contribution. Lazy consensus applies. If no -1
> votes are cast within the next 72 hours, the vote passes.
> 
> Regards,
> 
> -Taylor



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [DISCUSS] Olympian Incubation Proposal

[P. Taylor Goetz]

> On Oct 2, 2016, at 11:55 AM, Roman Shaposhnik  wrote:
> 
> 
> ultimately
> decided that expecting a bit more up-front community action was a
> prudent choice.
> 
> What I'd like to see is a proof that ASF or no ASF the community wants to take
> matters into its own hands and fork away. For now it isn't actually
> obvious to me.
> 
> Thanks,
> Roman.

Now that a move to the ASF is (currently) off the table, the community is 
regrouping to host the project elsewhere. Once basic infrastructure is in place 
there will likely be some sort of announcement. Proof will come.

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

Re: [DISCUSS] Olympian Incubation Proposal

[P. Taylor Goetz]

I think the community behind this proposal is ready to accept defeat at this 
point. With DataStax' objection, the project simply can't be brought under the 
auspices of the ASF unless DataStax reverses its stance.

Personally, I'm somewhat discouraged to see a company I once held in high 
regard in  terms of supporting OSS and the ASF take this action. This 
represents a further erosion of that respect. It is what it is. I can't fault 
DataStax for trying to protect their bottom line. They are well within their 
rights here. It could be considered a stain on their relationship with the ASF, 
or not.

The community seems committed to moving forward with a fork, whether it is 
considered hostile or friendly. From discussions I've been privy to, if 
DataStax were to reverse their stance, this community would come back to the 
ASF in a heartbeat. There's a community behind this code, and they deserve the 
right to move forward.

I think they will, unfortunately not at the ASF. At least for now. Nothing 
would please me more than to see this community be able to come to Apache.

-Taylor

> On Sep 30, 2016, at 4:15 AM, Tom Barber <tom.bar...@meteorite.bi> wrote:
> 
> I like the re-licensing threat get it forked on github and prove to
> them there is a willing community out there!
> 
> Tom
> 
>> On Fri, Sep 30, 2016 at 4:17 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
>> 
>> I'd leave it open for now. I imagine/hope there are enough people aware of
>> this thread that the sentiments expressed here might affect a change.
>> 
>> -Taylor
>> 
>>>> On Sep 29, 2016, at 10:57 PM, Henry Saputra <henry.sapu...@gmail.com>
>>> wrote:
>>> 
>>> With obvious block due to Datastax response, shall I CLOSE this DISCUSS
>>> thread until further updates, if any?
>>> 
>>>> On Thursday, September 29, 2016, P. Taylor Goetz <ptgo...@gmail.com>
>> wrote:
>>>> 
>>>> For the record I'd be -1 as well unless DataStax chose to support it.
>>>> 
>>>> I would like to give them time to change their mind though.
>>>> 
>>>> -Taylor
>>>> 
>>>>>> On Sep 29, 2016, at 10:37 PM, Greg Stein <gst...@gmail.com
>>>>> <javascript:;>> wrote:
>>>>> 
>>>>>> On Sep 29, 2016 19:22, "P. Taylor Goetz" <ptgo...@gmail.com
>>>> <javascript:;>> wrote:
>>>>>> ...
>>>>>> They can block a move to the ASF, but they can’t block a fork of the
>>>>> project moving elsewhere. Strong communities will regroup and live on.
>>>>> DataStax' reluctance to allow it could very easily be interpreted as a
>>>>> rejection of the ASF governance model or the Foundation itself.
>>>>> 
>>>>> Yes, the community could certainly launch their fork at GitHub or some
>>>>> such. DataStax provided them with that ability via the ALv2 license.
>> The
>>>>> ASF is not a necessary step for that community.
>>>>> 
>>>>>> ...
>>>>>> Can we wait and see if DataStax is willing to do the right thing
>> before
>>>>> shooting down the proposal as a hostile fork?
>>>>> 
>>>>> My vote remains -1. That can change, based on their choices.
>>>>> 
>>>>> Cheers,
>>>>> -g
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>>> <javascript:;>
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>> <javascript:;>
>> 
>> -
>> 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