Re: [IP CLEARANCE] Apache Maven - Mvndaemon
paperwork updated with the last hash On Mon, 6 Dec 2021 at 15:52, Olivier Lamy wrote: > The mentioned issue has been fixed. > We are moving the GitHub repo under asf org. > I don’t understand your question > > On Mon, 6 Dec 2021 at 1:51 pm, Justin Mclean > wrote: > >> Hi, >> >> > AFAIK, Guillaume fixed the issue as described in >> > https://issues.apache.org/jira/browse/LEGAL-586 < >> https://issues.apache.org/jira/browse/LEGAL-586> >> > >> > Nothing blocks now, isn't it? >> >> I’m nt aware of anything. >> >> > Do we consider the clearance ok as a conclusion, or should we restart a >> new >> > thread? >> >> Is what you donating the same or has it changed and has a different VC >> hash? If it’s changed I would start a new thread. >> >> Kind Regards, >> Justin > >
Re: [IP CLEARANCE] Apache Maven - Mvndaemon
The mentioned issue has been fixed. We are moving the GitHub repo under asf org. I don’t understand your question On Mon, 6 Dec 2021 at 1:51 pm, Justin Mclean wrote: > Hi, > > > AFAIK, Guillaume fixed the issue as described in > > https://issues.apache.org/jira/browse/LEGAL-586 < > https://issues.apache.org/jira/browse/LEGAL-586> > > > > Nothing blocks now, isn't it? > > I’m nt aware of anything. > > > Do we consider the clearance ok as a conclusion, or should we restart a > new > > thread? > > Is what you donating the same or has it changed and has a different VC > hash? If it’s changed I would start a new thread. > > Kind Regards, > Justin
Re: [IP CLEARANCE] Apache Maven - Mvndaemon
FYI legal JIRA raise https://issues.apache.org/jira/browse/LEGAL-586 cheers Olivier On Tue, 7 Sept 2021 at 19:26, Justin Mclean wrote: > Hi, > > > Can we replace the header with the following one instead: > > > > > https://github.com/openjdk/jdk/blob/master/src/java.base/share/native/include/jni.h > < > https://github.com/openjdk/jdk/blob/master/src/java.base/share/native/include/jni.h > > > > It is more clearly GPLv2 w/ CPE, so it should be allowed, as my > > understanding is that it is an exception to category X. > > AFAIK it is not. It is listed as Category X here [1]. > > Form memory there might some cases where GPL + CPE might be OK as a > dependancy but it’s not OK in a release. Probably best to discuss on legal > discuss list or raise a legal JIRA. > > Kind Regards, > Justin > > 1. https://www.apache.org/legal/resolved.html#category-x -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [IP CLEARANCE] Apache Maven - Mvndaemon
On Mon, 6 Sept 2021 at 12:13, Daniel Widdis wrote: > Code size is not the only measure of significance. > > Without any specialty knowledge of the domain, I would consider this > security fix probably significant. > https://github.com/mvndaemon/mvnd/pull/391 fixing > https://github.com/mvndaemon/mvnd/issues/390 I don't understand your concern? every project can have security issues but if it's fixed what is the problem? At least the first release under ASF will contain the fix because it's already fixed. > > > However, the AL2.0 license states: > > Unless You explicitly state otherwise, any Contribution intentionally > submitted for inclusion in the Work by You to the Licensor shall be under > the terms and conditions of this License, without any additional terms or > conditions. > > Given the project was AL2.0 licensed at the time of the contribution, > submitting a PR to the repository should constitute a "Contribution > intentionally submitted for inclusion in the Work" and should require no > additional terms. > > Also see > https://issues.apache.org/jira/browse/LEGAL-156?focusedCommentId=13554864=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13554864 > > Any contribution - in any form (patch to the mailing list, blog post, > JIRA attchment, git pull request, Bugzilla attachment, scrawled on the back > of a napkin) - may be included as long as two conditions are met: > > > > 1. As per section 5 of AL2 the person providing the patch does not > explicitly state that the patch provided is not licensed under ALv2 > > > > 2. The project's PMC is happy that the person providing the contribution > has the necessary rights to do so. > > > > On 9/5/21, 6:46 PM, "Olivier Lamy" wrote: > looking at this https://github.com/mvndaemon/mvnd/graphs/contributors > except the 2 main contributors we can't really qualify other > contributions > as really significant in terms of code size :) > > > > > > ----- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [IP CLEARANCE] Apache Maven - Mvndaemon
On Mon, 6 Sept 2021 at 12:03, Justin Mclean wrote: > Hi, > > > looking at this https://github.com/mvndaemon/mvnd/graphs/contributors < > https://github.com/mvndaemon/mvnd/graphs/contributors> except the 2 main > contributors we can't really qualify other contributions as really > significant in terms of code size :) > > You might want to look at each contribution and see if they are > significant, I would look at those > 50 lines or so rather than using a > comparison to the largest committers. > Is there any rule written somewhere? Because frankly "significant" contribution is very subjective Do we consider 50 lines of pom.xml as a significant contribution? I have seen larger contributions in some projects without any CLA. Again the project is already Apache license from the start so any contribution will be de facto ASF compliant > > Thanks, > Justin -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [IP CLEARANCE] Apache Maven - Mvndaemon
On Mon, 6 Sept 2021 at 11:08, Justin Mclean wrote: > Hi, > > > ?? You mean we need CLAs for every person who contributed a Pull Request > to > > an Apache License project? > > No we don’t, but it’s best to have them from everyone who has made a > significant contribution. > looking at this https://github.com/mvndaemon/mvnd/graphs/contributors except the 2 main contributors we can't really qualify other contributions as really significant in terms of code size :) > > > we need to address the native part. Not sure how ATM > > You probably need to work this out before merging the code into the ASF > repo. > yup definitely! > > Kind Regards, > Justin -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [IP CLEARANCE] Apache Maven - Mvndaemon
Hi Thanks for looking into this. On Mon, 6 Sept 2021 at 09:15, Justin Mclean wrote: > Hi, > > I have a couple of questions: > I see we have ICLAs for the two main contributors, do we have ICLAs for > any for the the other contributors? > ?? You mean we need CLAs for every person who contributed a Pull Request to an Apache License project? ( https://github.com/mvndaemon/mvnd/graphs/contributors) I don't understand the point. If folks have contributed to Apache license project I do not think a CLA is needed. We are not even doing that here @ ASF > The repro includes GPL licensed code how is this going to be handled? (GPL > is category X and not compatible with the Apache license). > we need to address the native part. Not sure how ATM > There also seems to be other non open source code? (e.g. "Copyright 2004 > Sun Microsystems, Inc. All rights reserved. SUN PROPRIETARY/CONFIDENTIAL. > Use is subject to license terms.”) How will this be handled? > yup the native part has some problems which need to be addressed. > > There is Apache licensed code from 3rd parties included the donations, do > take care when updating the headers after donation, and don’t replace these > headers. > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
[IP CLEARANCE] Apache Maven - Mvndaemon
Hi The Apache Maven project has voted [1] the donation of the mvndaemon project [2]. Following the IP clearance process [3] this is a lazy consensus majority vote, open for at least 72 hours. Please vote to accept this contribution. Thanks, -- Olivier [1] https://www.mail-archive.com/dev@maven.apache.org/msg124559.html [2] https://incubator.apache.org/ip-clearance/maven-daemon.html [3] https://incubator.apache.org/ip-clearance/
Re: [VOTE] Graduate Apache Gobblin (Incubating) as a TLP
+1 On Thu, 17 Dec 2020 at 18:55, Abhishek Tiwari wrote: > Hi all, > > After a discussion with the community [1], a positive vote > result [2], and a discussion with the IPMC [7], we believe > Apache Gobblin (Incubating) is ready for graduation to a TLP, > and we'd like to call for a Vote. > > Please vote on the resolution pasted below to graduate > Apache Gobblin (Incubating) from the incubator to a TLP: > > [ ] +1, Graduate Apache Gobblin from the Incubator. > [ ] +0, Don't care. > [ ] -1, Don't graduate Apache Gobblin from the Incubator (provide details) > > To list a few of the community's achievements: > > - 1700+ contributions from 149 contributors > - 4 releases under 3 different release managers > - 5 new committers invited, including 2 new PPMC members (all accepted) > - Diverse committers and PPMCs (from 9 companies/institutes) > - New Apache website setup [3] > - Issue tracking migrated to Jira [4] > - Dev conversations moved to d...@gobblin.incubator.org > - Apache Gobblin name search has been approved [5] > - Assessed ourselves against the Apache Project maturity matrix [6] > - We have built a meritocratic and open collaborative process (the Apache > way) > > [1] https://s.apache.org/le17y > [2] https://s.apache.org/q4ug6 > [3] https://gobblin.incubator.apache.org/ > [4] https://issues.apache.org/jira/projects/GOBBLIN/issues/ > [5] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-131 > [6] > https://cwiki.apache.org/confluence/display/GOBBLIN/ASF+Maturity+Evaluation > [7] https://s.apache.org/1gt3s > > The vote will remain open for at least 72 hours. > > If approved by the Apache Incubator PMC members, the proposed > resolution will be submitted to the Board of Directors for their > consideration. > > Thanks, > Abhishek > > --- > > Establish the Apache Gobblin 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 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. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > (PMC), to be known as the "Apache Gobblin Project", be and hereby is > established pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache Gobblin Project be and hereby is responsible > for the creation and maintenance of software related to 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; and > be it further > > RESOLVED, that the office of "Vice President, Apache Gobblin" 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 Gobblin > Project, and to have primary responsibility for management of the > projects within the scope of responsibility of the Apache Gobblin > 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 Gobblin Project: > > * Abhishek Tiwari > * Hung Tran > * Issac Buenrostro > * Jean-Baptiste Onofré > * Kishore G > * Lorand Bendig > * Olivier Lamy > * Owen O'Malley > * Sahil Takiar > * Shirshanka Das > * Sudarshan Vasudevan > * Tamás Németh > * Yinan Li > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Abhishek Tiwari be > appointed to the office of Vice President, Apache Gobblin, to serve in > accordance with and subject to the direction of the Board of Directors > and the Bylaws of the Foundation until death, resignation, retirement, > removal or disqualification, or until a successor is appointed; and be > it further > > RESOLVED, that the Apache Gobblin Project be and hereby is tasked with > the migration and rationalization of the Apache Incubator Gobblin > podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > Gobblin podling encumbered upon the Apache Incubator PMC are hereafter > discharged. > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.15.0 release RC2
+1 On Tue, 8 Dec 2020 at 07:35, Sudarshan Vasudevan wrote: > Hi, > I'd like to call a vote to release Apache Gobblin 0.15.0 (Incubating). > > The source release candidate RC2 can be downloaded here: > > > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin-incubating-0.15.0-rc2/ > > The artifacts (i.e. JARs) corresponding to this release candidate can be > found here: > > https://repository.apache.org/content/repositories/orgapachegobblin-1014/ > > This has been signed with PGP key 7F4FC4D0, corresponding to > suvas...@apache.org, which is included in the repository's KEYS file. > This > key can be found on keyservers, such as: > > > > > https://keyserver.ubuntu.com/pks/lookup?search=suvasude%40apache.org=on=index > > > It is also listed here: > https://people.apache.org/keys/committer/suvasude.asc > > The release candidate has been tagged with release-0.15.0-rc2. > I've also created a branch 0.15.0-rc2. > > For reference, here is a list of all closed JIRAs tagged with 0.15.0: > > > https://issues.apache.org/jira/browse/GOBBLIN-1324?jql=project%20%3D%20Gobblin%20AND%20fixVersion%20%3D%200.15.0%20AND%20status%20in%20(Closed%2CResolved) > > For a summary of the changes in this release, see: > > https://github.com/apache/incubator-gobblin/blob/0.15.0/CHANGELOG.md > > Please review and vote. The vote will be open for 72 hours starting > Monday (ends on > Thursday, 10 December 2020, 5pm PST). > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > My vote: +1 > > Thanks, > Sudarshan > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Pinot (incubating) 0.6.0 RC1
+1 On Thu, 12 Nov 2020 at 12:09, Felix Cheung wrote: > It was discussed several times in private@pinot, we can take it from > there. > > It will probably best if one of you simply edit that line right now in the > git repo so we don’t get into this again in 0.7 release. > > > On Wed, Nov 11, 2020 at 10:58 AM Jialiang Li wrote: > > > Hi Felix, > > > > Thanks for the feedback! Sorry I don't have the context on including > > thirdeye into the pinot open source release. Could you share the related > > email thread? If it's not urgent, maybe we can add some notes in pinot > > release page (https://github.com/apache/incubator-pinot/releases), so > > that the next POC will pick it up. > > > > Thanks, > > Jack > > > > On 2020/11/11 04:05:49, Felix Cheung wrote: > > > +1 but > > > > > > it was discussed before, but thirdeye is not included in the source > > release > > > > > > https://github.com/apache/incubator-pinot/blob/master/pinot-distribution/pinot-source-assembly.xml#L39 > > > > > > - incubating in name > > > - signature and hash fine > > > - DISCLAIMER is fine > > > - LICENSE and NOTICE are fine > > > - No unexpected binary files > > > Event for testing, ideally you want to build the test tarball from > > > source paddingPercent.tar.gz, paddingOld.tar.gz, paddingNull.tar.gz, > > > fake_stream_avro_data.tar.gz > > > - All source files have ASF headers > > > > > > On Tue, Nov 10, 2020 at 5:29 PM Jialiang Li wrote: > > > > > > > Hi all, > > > > > > > > This is a call for vote to the release Apache Pinot (incubating) > > version > > > > 0.6.0. > > > > > > > > Apache Pinot (incubating) is a distributed columnar storage engine > > that can > > > > ingest > > > > data in realtime and serve analytical queries at low latency. > > > > > > > > Pinot community has voted and approved this release. > > > > > > > > Vote thread: > > > > > > > > > > > https://lists.apache.org/thread.html/r9c715527f12e425ee15024cdbae7b597c04942a8901711f521f53a34%40%3Cdev.pinot.apache.org%3E > > > > > > > > Result thread: > > > > > > > > > > > https://lists.apache.org/thread.html/r646618892a671155fe810c945c7e16f2ad1de7d7c92bc9e24c0a3290%40%3Cdev.pinot.apache.org%3E > > > > > > > > The release candidate: > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.6.0-rc1 > > > > > > > > Git tag for this release: > > > > https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc1 > > > > > > > > Git hash for this release: > > > > bb646baceafcd9b849a1ecdec7a11203c7027e21 > > > > > > > > The artifacts have been signed with key: FC4005F4DCB8B2F4, which can > be > > > > found in the following KEYS file. > > > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > > > > > Release notes: > > > > > > https://github.com/apache/incubator-pinot/releases/tag/release-0.6.0-rc1 > > > > > > > > Staging repository: > > > > > https://repository.apache.org/content/repositories/orgapachepinot-1022 > > > > > > > > Documentation on verifying a release candidate: > > > > > > > > > > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > > > > > > > > > > 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, > > > > Apache Pinot (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 > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Pinot (incubating) 0.5.0 RC2
+1
On Sat, 5 Sep 2020 at 05:06, Ting Chen wrote:
> Hi all,
>
> This is a call for a vote to release Apache Pinot (incubating) version
> 0.5.0.
>
> Apache Pinot (incubating) is a distributed columnar storage engine that can
> ingest data in realtime and serve analytical queries at low latency.
>
> The Pinot community has voted and approved this release.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/rd12f8915647996cc027299181b0665fd422021bb20cd1a308f467045%40%3Cdev.pinot.apache.org%3E
>
> Result thread:
>
> https://lists.apache.org/thread.html/rd12f8915647996cc027299181b0665fd422021bb20cd1a308f467045%40%3Cdev.pinot.apache.org%3E
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.5.0-rc2
>
> Diff with apache-pinot-incubating-0.5.0-rc1
> https://github.com/apache/incubator-pinot/commit/d902c1a (Remove the
> node_modules codes from the src package)
>
> Git tag for this release:
> https://github.com/apache/incubator-pinot/tree/release-0.5.0-rc2
>
> Git hash for this release:
> d87bbc9032c6efe626eb5f9ef1db4de7aa067179
>
> The artifacts have been signed with a key: C650A5210408F8F4, which can be
> found in the following KEYS file.
> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
>
> Release notes:
> https://github.com/apache/incubator-pinot/releases/tag/release-0.5.0-rc2
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachepinot-1016
>
> Documentation on verifying a release candidate:
>
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
>
>
> *Special notes for verification: During this step "diff -r
> apache-pinot-incubating-${VERSION}-src pinot-git-src", due to Cluster
> Manager UI & Query Console UI revamp (#5684), you might see the extra lines
> below. It is fine because they are generated code for the revamped
> controller UI.*
>
> *Only in
> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
> dist*
> *Only in
> apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
> package-lock.json*
>
>
> The vote will be open for at least 72 hours or until a necessary number of
> votes are reached.
>
> Please vote accordingly,
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache Pinot (incubating) team
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Pinot (incubating) 0.3.0 RC2
+1 On Fri, 20 Mar 2020 at 02:53, Fu Xiang wrote: > Hi all, > > This is a call for vote to the release Apache Pinot (incubating) version > 0.3.0. > > Apache Pinot (incubating) is a distributed columnar storage engine that can > ingest data in realtime and serve analytical queries at low latency. > > Pinot community has voted and approved this release. > > Vote threads: > > https://lists.apache.org/thread.html/r2b9a26398aa529c13a9f871499a116547819be20129cf91f2be16d07%40%3Cdev.pinot.apache.org%3E > > Result thread: > > https://lists.apache.org/thread.html/r4c3c9e4025e5a69bd19317d1a123c3f8a55039b4712aeb019ad015e0%40%3Cdev.pinot.apache.org%3E > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.3.0-rc2 > > Git tag for this release: > https://github.com/apache/incubator-pinot/tree/release-0.3.0-rc2 > > Git hash for this release: > 9b2dc20c07dec6cf33df08cd996e8202c3ba > > The artifacts have been signed with key: CDEDB21B862F6C66, which can be > found in the following KEYS file. > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > Release notes: > GitHub: > https://github.com/apache/incubator-pinot/releases/tag/release-0.3.0-rc2 > GitBook: > https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachepinot-1010 > > Documentation on verifying a release candidate: > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > 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, > > Xiang Fu > (On behalf of Apache Pinot (incubating) team) > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Pinot (incubating) 0.2.0 RC0
+1 On Tue, 19 Nov 2019 at 05:35, Subbu Subramaniam wrote: > Hi all, > > This is a call for vote to the release Apache Pinot (incubating) version > 0.2.0. > > Apache Pinot (incubating) is a distributed columnar storage engine that can > ingest data in realtime and serve analytical queries at low latency. > > Pinot community has voted and approved this release. > > Vote threads: > > https://lists.apache.org/thread.html/302ea5dd91e731eaaf9ce3881e027613ebc76a8c01472c0517b56e89@%3Cdev.pinot.apache.org%3E > > https://lists.apache.org/thread.html/3d785c502905b23f1d4d1da8718501a7cb4ef8245dd665fe99bf6daf@%3Cdev.pinot.apache.org%3E > > Result thread: > > https://lists.apache.org/thread.html/c425825f7d9da198adfbc5c5633dd0300f77f0ce3f9b88dba92dbe60@%3Cdev.pinot.apache.org%3E > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.2.0-rc0 > > Git tag for this release: > https://github.com/apache/incubator-pinot/tree/release-0.2.0-rc0 > > Git hash for this release: > f8e1980c4160ac7fd2686d9edefab9ac0a825c5b > > The artifacts have been signed with key: B530034C, which can be > found in the following KEYS file. > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > Release notes: > https://github.com/apache/incubator-pinot/releases/tag/release-0.2.0-rc0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachepinot-1003 > > Documentation on verifying a release candidate: > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > 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, > > -Subbu Subramaniam > (on behalf of Apache Pinot (incubating) team) > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)
Good effort Bertrand that's definitely some discussions we should have and ease incubation! To be honest I'm mentoring some projects but sometimes I'm out of motivation due to the huge number of nitpicking tasks/requests. I perfectly understand people reactions when they try to go trough the incubation process.. (disclaimer it's an email from the peanut gallery) So yes let's make Apache incubation great again.. On Thu, 20 Jun 2019 at 03:28, Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > On Wed, Jun 19, 2019 at 7:14 PM Ted Dunning wrote: > > ...This vote is *confirming* that > > nobody has objections (of any form) to Zipkin leaving and control of the > > git repos being transferred... > > I agree and this means that in this case a [LAZY] vote would have been > sufficient. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Recommend 'Apache NetBeans graduation to Top Level Project' resolution to board
+1 (binding) Good job!! On Tue, 9 Apr 2019 at 20:41, Geertjan Wielenga wrote: > Hi all, > > The Apache NetBeans podling community brings the resolution, after > discussion[1], to become a top level Apache project up for the IPMC vote. > The PPMC community vote[2] resulted in 64 +1 votes and no 0 or -1 votes, > further details about the project and what has been done is found in the > related discussion thread[1]. > > We have had a long and eventful incubation period and are looking forward > to graduating and continuing our development and community work with and > around Apache NetBeans. > > The vote is open for 72 hours, assuming that at that stage there are at > least 3 +1 votes and nothing left open for discussion. > > Thanks, > > Geertjan > on behalf of Apache NetBeans PPMC > > 1. > > https://lists.apache.org/thread.html/648834cdb10ce55aff2c6c8dd3c32454a74711c6289f385e456b74d8@%3Cgeneral.incubator.apache.org%3E > 2. > > https://lists.apache.org/thread.html/72e59c722580fef2cbaa637735691a549756aeaa72c4cbf52265fbe0@%3Cdev.netbeans.apache.org%3E > > - > > Establish the Apache NetBeans 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 providing a development environment, tooling platform, and application > framework. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), > to be known as the "Apache NetBeans Project", be and hereby is established > pursuant to Bylaws of the Foundation; and be it further > > RESOLVED, that the Apache NetBeans Project be and hereby is responsible for > the creation and maintenance of software related to providing a development > environment, tooling platform, and application framework; and be it further > > RESOLVED, that the office of "Vice President, Apache NetBeans" 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 NetBeans Project, and > to have primary responsibility for management of the projects within the > scope of responsibility of the Apache NetBeans 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 NetBeans Project: > > * Anton Epple > * Antonio Vieiro > * Aristides Villarreal > * Arunava Sinha > * Ate Douma > * Attila Kelemen > * Bertrand Delacretaz > * Bruno Flávio > * Bruno Souza > * Christian Lenz > * Constantin Drabo > * David Heffelfinger > * Daniel Gruno > * Dusan Balek > * Eirik Bakke > * Emilian Bold > * Emmanuel Hugonnet > * Eric Barboni > * Florian Vogler > * Geertjan Wielenga > * Glenn Holmer > * Ivar Grimstad > * James Gosling > * Jan Lahoda > * Jan Pirek > * Jaroslav Tulach > * Jean-Marc Borer > * Jiří Kovalský > * Joerg Michelberger > * Johan Vos > * John Kostaras > * John McDonnell > * Josh Juneau > * José Pereda > * Junichi Yamamoto > * Kirk Pepperdine > * Lars Bruun-Hansen > * Laszlo Kishalmi > * Leonardo Zanivan > * Mark Stephens > * Mark Struberg > * Martin Entlicher > * Martin Klähn > * Matthias Bläsing > * Michael Müller > * Michael Nascimento > * Michel Graciano > * Neil C Smith > * Ralph Benjamin Ruijs > * Reema Taneja > * Shai Almog > * Simon Phipps > * Svatopluk Dedic > * Sven Reimers > * Thilina Ranathunga > * Timon Veenstra > * Tomas Mysik > * Tomas Zezula > * Tushar Joshi > * Vladimir Voskresensky > * Wade Chandler > * Zoran Sevarac > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Geertjan Wielenga be appointed > to the office of Vice President, Apache NetBeans, to serve in accordance > with and subject to the direction of the Board of Directors and the Bylaws > of the Foundation until death, resignation, retirement, removal or > disqualification, or until a successor is appointed; and be it further > > RESOLVED, that the Apache NetBeans Project be and hereby is tasked with the > migration and rationalization of the Apache Incubator NetBeans podling; and > be it further > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > NetBeans podling encumbered upon the Apache Incubator PMC are hereafter > discharged. > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Zipkin Brave (incubating) for Apache Cassandra version 0.10.2
+1 On Fri, 22 Mar 2019 at 01:29, Adrian Cole wrote: > The Apache Zipkin community has voted on and approved a proposal to > release Apache Zipkin Brave (incubating) for Apache Cassandra version > 0.10.2. The voting thread can be found here: > > https://lists.apache.org/thread.html/c2c55a0e347f90bcb07032b4fa79e34a6832742e7284d7f327583b23@%3Cdev.zipkin.apache.org%3E > > Three binding +1 vote from mentors Andriy Redko, Willem Ning Jiang and > Mick Semb Wever carry over from the dev list thread. > > We now kindly request the Incubator PMC members review and vote on > this incubator release. > > Apache Zipkin Brave (incubating) for Apache Cassandra allows you to > trace activities started by Datastax Java Driver for Apache Cassandra > all the way to inside Apache Cassandra itself. It was originally > created by Mick at The Last Pickle and also championed by Lance at > Smart Things. > > The release candidates: > > https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave-cassandra/0.10.2/ > > Git tag for the release: > https://github.com/apache/incubator-zipkin-brave-cassandra/tree/v0.10.2 > > Hash for the release tag: > b8e379f33eb9f52f0742d3187252de330163cbf7 > > Release Notes: > > https://github.com/apache/incubator-zipkin-brave-cassandra/releases/tag/v0.10.2 > > The artifacts have been signed with Key : BB67A050, which can be found > in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS > > Verification Hints: > For your convenience, the below includes detailed how-to on verifying > a source release. Please note that this document is a work-in-progress > > https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release > > 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 Zipkin (Incubating) Team > > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Pinot (incubating) 0.1.0 RC0
+1 On Fri, 1 Mar 2019 at 04:45, Seunghyun Lee wrote: > Hi all, > > This is a call for vote to the release Apache Pinot (incubating) version > 0.1.0. > > Apache Pinot (incubating) is a distributed columnar storage engine that can > ingest > data in realtime and serve analytical queries at low latency. > > Pinot community has voted and approved this release. > > Vote thread: > > https://lists.apache.org/thread.html/f136d3eaa9dfbab6e17b262a5542813099f2b128465d9d17ef69defd@%3Cdev.pinot.apache.org%3E > > Result thread: > > https://lists.apache.org/thread.html/ce58034678349f82afc5f8ed2edd435875301183554f964778dffb7a@%3Cdev.pinot.apache.org%3E > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.1.0-rc0 > > Git tag for this release: > https://github.com/apache/incubator-pinot/tree/release-0.1.0-rc0 > > Git hash for this release: > bbf29dc6e0f23383948f0db66565ebbdf383dd0d > > The artifacts have been signed with key: 44BA03AD164D961B, which can be > found in the following KEYS file. > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > Release notes: > https://github.com/apache/incubator-pinot/releases/tag/release-0.1.0-rc0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachepinot-1002 > > Documentation on verifying a release candidate: > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > 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, > Apache Pinot (incubating) team > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Zipkin Brave (incubating) for Apache Karaf version 0.1.2
+1 On Sat, 23 Feb 2019 at 10:54, Adrian Cole wrote: > Hello All, > > This is a call for vote to release Apache Zipkin Brave (incubating) > for Apache Karaf version 0.1.2 > > The Apache Zipkin community has voted on and approved a proposal to > release Apache Zipkin Brave (incubating) for Apache Karaf version > 0.1.2. > > We now kindly request the Incubator PMC members review and vote on > this incubator release. > > Apache Zipkin Brave (incubating) for Apache Karaf sets up tracing > components such that tools built Karaf needn't configure these > explicitly. > > Zipkin community vote and result thread: > > https://lists.apache.org/thread.html/32baf4b4b65644dd1dd8e2bf0cb360c94f8f939d61c5444b8f4ef45b@%3Cdev.zipkin.apache.org%3E > > The release candidates: > https://dist.apache.org/repos/dist/dev/incubator/zipkin/brave-karaf/0.1.2/ > > Git tag for the release: > https://github.com/apache/incubator-zipkin-brave-karaf/tree/v0.1.2 > > Hash for the release tag: > 3cf4ac6577eb0d4775d20f24814e7a0852fa1635 > > Release Notes: > https://github.com/apache/incubator-zipkin-brave-karaf/releases/tag/v0.1.2 > > The artifacts have been signed with Key : BB67A050, which can be found > in the keys file: > https://dist.apache.org/repos/dist/dev/incubator/zipkin/KEYS > > Verification Hints: > For your convenience, the below includes detailed how-to on verifying > a source release. Please note that this document is a work-in-progress > > https://cwiki.apache.org/confluence/display/ZIPKIN/Verifying+a+Source+Release > > 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 Zipkin (Incubating) Team > > --------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.14.0 release RC0
+1 On Wed, 5 Dec 2018 at 09:13, Abhishek Tiwari wrote: > The Apache Gobblin community has voted on and approved the release of > Apache Gobblin 0.14.0 (incubating): > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02386.html > > Results: > 3 binding +1 votes > No 0 votes > No -1 votes > > I'd like to call a vote in general to approve the release. > > The source release candidate RC0 can be downloaded here: > > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin-incubating-0.14.0-rc0/ > > > The artifacts (i.e. JARs) corresponding to this release candidate can be > found here: > https://repository.apache.org/content/repositories/orgapachegobblin-1008/ > > This has been signed with PGP key 234E3FE3, corresponding to > a...@apache.org, which is included in the repository's KEYS file. This > key can be found on keyservers, such as: > http://pgp.mit.edu/pks/lookup?op=get=0x234E3FE3 > > It is also listed here: > https://people.apache.org/keys/committer/abti.asc > > The release candidate has been tagged with release-0.14.0-rc0 > I've also created a branch 0.14.0 > > For reference, here is a list of all closed JIRAs tagged with 0.14.0: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GOBBLIN%20AND%20fixVersion%20%3D%200.14.0%20AND%20status%20in%20(Closed%2C%20Resolved)%20ORDER%20BY%20updatedDate%20DESC%2C%20createdDate%20DESC%2C%20status%20DESC%2C%20priority%20DESC > > > For a summary of the changes in this release, please see: > https://github.com/apache/incubator-gobblin/blob/0.14.0/CHANGELOG.md > > Please review and vote. The vote will be open for atleast 72 hours (ends on > Friday, December 7, 2018 at 3:30 pm PT). > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Thanks, > Abhishek, on behalf of the Apache Gobblin (incubating) PPMC > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept the Iceberg project for incubation
; Iceberg utilizes other Apache projects such as Avro, Hadoop, Hive, ORC, > Parquet, Pig, and Spark. We anticipate integration with additional Apache > projects as the Iceberg community and interest in the project grows. > Known Risks Orphaned Products > > Netflix is committed to the future development of Iceberg and understands > that graduation to a TLP, while preferable, is not the only positive > outcome of incubation. > > Should the Iceberg project be accepted by the Incubator, the prospective > PPMC would be willing to agree to a target incubation period of 2 years or > less, knowing that every Incubator project incurs a certain cost in terms > of ASF infrastructure and volunteer time. > Inexperience with Open Source > > Three of the initial committers are Apache members and Incubator PMC > members. They will work with the other community members to teach them the > Apache Way. > Homogenous Developers > > The majority of the committers work at Netflix, though we are committed to > recruiting and developing additional committers from a wide spectrum of > industries and backgrounds. > Reliance on Salaried Developers > > It is expected that Iceberg development will occur on both salaried time > and on volunteer time, after hours. Most of the initial committers are paid > by Netflix to contribute to this project. However, they are all passionate > about the project, and we are both confident and hopeful that the project > will continue even if no salaried developers contribute to the project. > Relationships with Other Apache Products > > As mentioned in the Rationale section, Iceberg utilizes a number of > existing Apache projects (Avro, Hadoop, Hive, ORC, Parquet, Pig, & Spark), > and we expect that list to expand as the community grows and diversifies. > Any Apache project in the big data space that needs to store or process > tabular data would be potentially relevant. > An Excessive Fascination with the Apache Brand > > We are applying to the Incubator process because we think it is the next > logical step for the Iceberg project after open-sourcing the code. This > proposal is not for the purpose of generating publicity. Rather, we want to > make sure to create a very inclusive and meritocratic community, outside > the umbrella of a single company. Netflix has a long history of > contributing to Apache projects and the Iceberg developers and contributors > understand the implication of making it an Apache project. > Required Resources Mailing lists > >- d...@iceberg.incubator.apache.org >- comm...@iceberg.incubator.apache.org >- priv...@iceberg.incubator.apache.org > > The podling may also create a user mailing list, if needed. > Source Control and Issue Tracking > > The Iceberg podling would use Apache’s gitbox integration to sync between > github and Apache infrastructure. The podling would use github issues and > pull requests for community engagement. > Current Resources > >- Initial source: https://github.com/Netflix/iceberg >- Java documentation: > > https://netflix.github.io/iceberg/current/javadoc/index.html?com/netflix/iceberg/package-summary.html >- Table specification: > > https://docs.google.com/document/d/1Q-zL5lSCle6NEEdyfiYsXYzX_Q8Qf0ctMyGBKslOswA/edit > > Source and Intellectual Property Submission Plan > > The Iceberg source code in Github is currently licensed under Apache > License v2.0 and the copyright is assigned to Netflix. If Iceberg becomes > an Incubator project at the ASF, Netflix will transfer the source code and > trademark ownership to the Apache Software Foundation via a Software Grant > Agreement. > External Dependencies > > External dependencies licensed under Apache License 2.0 > >- Guava https://github.com/google/guava >- Jackson https://github.com/FasterXML/jackson-core >- Joda-Time http://www.joda.org/joda-time/ > > External dependencies licensed under the MIT License > >- SLF4J https://www.slf4j.org/ >- Mockito https://github.com/mockito/mockito > > ASF Projects > >- Apache Avro >- Apache Hadoop >- Apache Hive >- Apache ORC >- Apache Parquet >- Apache Pig >- Apache Spark > > Cryptography > > We do not expect Iceberg to be a controlled export item due to the use of > encryption. > Initial Committers and Affiliations > >- Ryan Blue b...@apache.org (Netflix) >- Parth Brahmbhatt pa...@apache.org (Netflix) >- Julien Le Dem jul...@apache.org (WeWork) >- Owen O’Malley omal...@apache.org (Hortonworks) >- Daniel Weeks dwe...@apache.org (Netflix) > > Sponsors and Nominated Mentors > >- Champion and mentor: Owen O’Malley omal...@apache.org >- Mentor: Ryan Blue b...@apache.org >- Mentor: Julien Le Dem jul...@apache.org > > Sponsoring Entity > > The Apache Incubator > -- > Ryan Blue > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.13.0 release RC2
+1 On Tue, 18 Sep 2018 at 22:27, Jim Jagielski wrote: > Sorry for the delay... > > +1 for the source release (binding) but I agree w/ removing the binary > > > On Sep 17, 2018, at 6:27 PM, Abhishek Tiwari wrote: > > > > Ping. > > > > Can someone help us review and vote :) > > > > Regards > > Abhishek > > > > On Tue, Sep 11, 2018 at 2:59 PM Abhishek Tiwari wrote: > > > >> +1 > >> > >> Abhishek > >> > >> On Tue, Sep 11, 2018 at 2:51 PM Hung Tran wrote: > >> > >>> Adding some CCs since the message was not received. > >>> > >>> Hung. > >>> -- > >>> *From:* Hung Tran > >>> *Sent:* Monday, September 10, 2018 9:51:31 PM > >>> *To:* general@incubator.apache.org > >>> *Subject:* [VOTE] Apache Gobblin 0.13.0 release RC2 > >>> > >>> The Apache Gobblin community has voted on and approved the release of > >>> Apache Gobblin 0.13.0 (incubating): > >>> > >>> > >>> > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02175.html > >>> > >>> Results: > >>> 3 binding +1 votes > >>> No 0 votes > >>> No -1 votes > >>> > >>> The feedback from previous release candidates has been addressed: > >>> > >>> RC1 thread: > >>> > https://www.mail-archive.com/general@incubator.apache.org/msg64403.html > >>> Resolution: > >>> Removed the binary release tar from the source release tar. > >>> > >>> I'd like to call a vote in general to approve the release. > >>> > >>> The source release candidate RC2 with convenience binaries can be > >>> downloaded here: > >>> > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin > >>> -incubating-0.13.0-rc2/ > >>> > >>> The artifacts (i.e. JARs) corresponding to this release candidate can > be > >>> found here: > >>> > https://repository.apache.org/content/repositories/orgapachegobblin-1007 > >>> > >>> This has been signed with PGP key 0x9BB772F1,corresponding to > >>> hut...@apache.org, which is included in the repository's KEYS file ( > >>> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS). > This > >>> key can be found on keyservers, such as: > >>> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1 > >>> > >>> > >>> The release candidate has been tagged with release-0.13.0-rc2. > >>> I've also created a branch 0.13.0. > >>> > >>> > >>> For reference, here is a list of all closed JIRAs tagged with 0.13.0: > >>> https://issues.apache.org/jira/issues/?filter=12343492 > >>> > >>> For a summary of the changes in this release, see: > >>> https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md > >>> > >>> Please review and vote. The vote will be open for at least 72 hours. > >>> > >>> [ ] +1 approve > >>> [ ] +0 no opinion > >>> [ ] -1 disapprove (and reason why) > >>> > >>> Thanks, > >>> Hung, on behalf of the Apache Gobblin PPMC > >>> > >>> > >>> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.13.0 release RC1
nope not all. But nice to see someone is reading the thread and may be able to help :P Honestly if we have process in place they shouldn't be here only to slow progress Anyway someone else for a review? On Wed, 22 Aug 2018 at 11:24, Justin Mclean wrote: > Hi, > > Only if those people are IPMC members. > > Justin > > On Wed., 22 Aug. 2018, 11:23 am Olivier Lamy, wrote: > > > Hi > > We got 4 +1 on dev@ so we might be good for a release. > > > > Cheers > > Olivier > > > > On Wed, 22 Aug 2018 at 05:03, Abhishek Tiwari wrote: > > > > > Sorry for spam. But, bump again to get some attention. > > > > > > Abhishek > > > > > > On Fri, Aug 17, 2018 at 5:34 PM Abhishek Tiwari > wrote: > > > > > > > Bumping up to get traction :) > > > > > > > > Abhishek > > > > > > > > On Wed, Aug 15, 2018 at 8:01 AM Abhishek Tiwari > > wrote: > > > > > > > >> +1 (non-binding) > > > >> > > > >> Abhishek > > > >> > > > >> On Tue, Aug 14, 2018 at 5:59 PM Hung Tran > > wrote: > > > >> > > > >>> The Apache Gobblin community has voted on and approved the release > of > > > Apache > > > >>> Gobblin 0.13.0 (incubating): > > > >>> > > > >>> > > > >>> < > > > > > > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02091.html > > > > > > > >>> > > > > > > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02110.html > > > >>> > > > >>> Results: > > > >>> 4 binding +1 votes > > > >>> No 0 votes > > > >>> No -1 votes > > > >>> > > > >>> I'd like to call a vote in general to approve the release. > > > >>> > > > >>> The source release candidate RC1 can be downloaded here: > > > >>> > > > > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin > > > >>> -incubating-0.13.0-rc1/ > > > >>> > > > >>> The artifacts (i.e. JARs) corresponding to this release candidate > can > > > be > > > >>> found here: > > > >>> > > > > https://repository.apache.org/content/repositories/orgapachegobblin-1006 > > > >>> > > > >>> This has been signed with PGP key 0x9BB772F1, corresponding to > > > >>> hut...@apache.org, which is included in the repository's KEYS > file ( > > > >>> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS > ). > > > >>> This key can be found on keyservers, such as: > > > >>> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1 > > > >>> > > > >>> The release candidate has been tagged with release-0.13.0-rc1. > > > >>> I've also created a branch 0.13.0. > > > >>> > > > >>> For reference, here is a list of all closed JIRAs tagged with > 0.13.0: > > > https://issues.apache.org/jira/issues/?filter=12343492 > > > >>> > > > >>> For a summary of the changes in this release, see: > > > https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md < > > > https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md> > < > > > https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md> > > > >>> > > > >>> > > > >>> Please review and vote. The vote will be open for at least 72 > hours. > > > >>> > > > >>> [ ] +1 approve > > > >>> [ ] +0 no opinion > > > >>> [ ] -1 disapprove (and reason why) > > > >>> > > > >>> > > > >>> Thanks, > > > >>> Hung, on behalf of the Apache Gobblin PPMC > > > >>> > > > >>> > > > > > > > > > -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.13.0 release RC1
Hi We got 4 +1 on dev@ so we might be good for a release. Cheers Olivier On Wed, 22 Aug 2018 at 05:03, Abhishek Tiwari wrote: > Sorry for spam. But, bump again to get some attention. > > Abhishek > > On Fri, Aug 17, 2018 at 5:34 PM Abhishek Tiwari wrote: > > > Bumping up to get traction :) > > > > Abhishek > > > > On Wed, Aug 15, 2018 at 8:01 AM Abhishek Tiwari wrote: > > > >> +1 (non-binding) > >> > >> Abhishek > >> > >> On Tue, Aug 14, 2018 at 5:59 PM Hung Tran wrote: > >> > >>> The Apache Gobblin community has voted on and approved the release of > Apache > >>> Gobblin 0.13.0 (incubating): > >>> > >>> > >>> < > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02091.html > > > >>> > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02110.html > >>> > >>> Results: > >>> 4 binding +1 votes > >>> No 0 votes > >>> No -1 votes > >>> > >>> I'd like to call a vote in general to approve the release. > >>> > >>> The source release candidate RC1 can be downloaded here: > >>> > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin > >>> -incubating-0.13.0-rc1/ > >>> > >>> The artifacts (i.e. JARs) corresponding to this release candidate can > be > >>> found here: > >>> > https://repository.apache.org/content/repositories/orgapachegobblin-1006 > >>> > >>> This has been signed with PGP key 0x9BB772F1, corresponding to > >>> hut...@apache.org, which is included in the repository's KEYS file ( > >>> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS). > >>> This key can be found on keyservers, such as: > >>> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1 > >>> > >>> The release candidate has been tagged with release-0.13.0-rc1. > >>> I've also created a branch 0.13.0. > >>> > >>> For reference, here is a list of all closed JIRAs tagged with 0.13.0: > https://issues.apache.org/jira/issues/?filter=12343492 > >>> > >>> For a summary of the changes in this release, see: > https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md < > https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md> < > https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md> > >>> > >>> > >>> Please review and vote. The vote will be open for at least 72 hours. > >>> > >>> [ ] +1 approve > >>> [ ] +0 no opinion > >>> [ ] -1 disapprove (and reason why) > >>> > >>> > >>> Thanks, > >>> Hung, on behalf of the Apache Gobblin PPMC > >>> > >>> > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.12.0 release RC3
+1 On Thu, 28 Jun 2018 at 3:05 am, Abhishek Tiwari wrote: > [bump up to get traction] > > Abhishek > > On Sat, Jun 23, 2018 at 1:57 PM Abhishek Tiwari wrote: > > > The Apache Gobblin community has voted on and approved the release of > > Apache Gobblin 0.12.0 (incubating): > > > > > https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg01981.html > > > > Results: > > 5 binding +1 votes > > 1 non-binding +1 vote > > No 0 votes > > No -1 votes > > > > The feedback from previous release candidates has been addressed: > > RC0 thread: https://www.mail-archive.com/general@incubator.apache > > .org/msg62151.html > > RC0 resolution: LICENSE and NOTICE files have been updated (tracked by > > GOBBLIN-431 <https://issues.apache.org/jira/browse/GOBBLIN-431>) > > RC1 thread: https://www.mail-archive.com/dev@gobblin.incubator.apache > > .org/msg01733.html > > RC1 resolution: gradlew scripts have been included in the source > > distribution, and the steps for building the distribution has been added > to > > README (including the way to obtain gradlew jar) > > RC 2 thread: https://mail-archives.apache > > > .org/mod_mbox/incubator-general/201804.mbox/%3CCAD+38UAE+Cpv3syCYH1RHGLbdHNqZHPfVh3YS6g= > qxhhb8n...@mail.gmail.com%3E > > RC 2 resolution: This release candidate (RC3) has been cut with Justin's > > changes to NOTICE file to make it Apache compliant > > > > I'd like to call a vote in general to approve the release. > > > > The source release candidate RC3 can be downloaded here: > > https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin > > -incubating-0.12.0-rc3/ > > > > The artifacts (i.e. JARs) corresponding to this release candidate can be > > found here: > > https://repository.apache.org/content/repositories/orgapachegobblin-1003 > > > > This has been signed with PGP key 234E3FE3, corresponding to > > a...@apache.org, which is included in the repository's KEYS file ( > > https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS). > This > > key can be found on keyservers, such as: > > > > *http://pgp.mit.edu/pks/lookup?op=get=0x234E3FE3 > > <http://pgp.mit.edu/pks/lookup?op=get=0x234E3FE3>* > > > > It is also listed here: > > https://people.apache.org/keys/committer/abti.asc > > > > The release candidate has been tagged with release-0.12.0-rc3. > > I've also created a branch 0.12.0. > > > > For reference, here is a list of all closed JIRAs tagged with 0.12.0: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20GOBBLIN%20AND%20fixVersion%20%3D%200.12.0%20AND%20status%20in%20(Closed%2C%20Resolved)%20ORDER%20BY%20updatedDate%20DESC%2C%20createdDate%20DESC%2C%20status%20DESC%2C%20priority%20DESC > > > > > > For a summary of the changes in this release, see: > > https://github.com/apache/incubator-gobblin/blob/0.12.0/CHANGELOG.md > > > > Please review and vote. The vote will be open for 72 hours. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > Thanks, > > Abhishek, on behalf of the Apache Gobblin PPMC > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.12.0 release RC2
I reckon I'm a bit confused as well now as I'm not sure what is the correct fix to apply Is there any of the folks who voted -1 to propose some fixes? via pull request or a patch? the git repo is available here: https://github.com/apache/incubator-gobblin This will definitely helps a lot as even with few years of experience here, I'm really confused about what and how to fix the issue. Thanks a lot Olivier On Mon, 2 Apr 2018 at 09:19, Abhishek Tiwari <a...@apache.org> wrote: > Although the vote is over and successful, at this point I think I will just > update the NOTICE file and bring in another RC for vote. > > However, I am puzzled that this improvement (not blocker) is attracting -1 > votes. I would have expected +1 or 0 with improvement suggestion, > specifically because I see that this is a very common pattern in many if > not most of the major Apache TLP projects. > The two entries in our NOTICE file is for: bootstrap and Glyphicon icons. > And, for exactly the same included bits, here are the NOTICE files for a > few other major TLPs: > Apache Hadoop: https://github.com/apache/hadoop/blob/trunk/NOTICE.txt > < > https://www.google.com/url?q=https://github.com/apache/hadoop/blob/trunk/NOTICE.txt=D=hangouts=1522643463206000=AFQjCNGI8Ip-PaJG9FI1khGSq5ErPtu6eQ > > > > Apache HBase: https://github.com/apache/hbase/blob/master/NOTICE.txt > < > https://www.google.com/url?q=https://github.com/apache/hbase/blob/master/NOTICE.txt=D=hangouts=1522643463206000=AFQjCNGuWUiULf55KJuDhruPujU8zDiLhg > > > > Apache Ambari: https://github.com/apache/ambari/blob/trunk/ > ambari-web/app/assets/licenses/NOTICE.txt > < > https://www.google.com/url?q=https://github.com/apache/ambari/blob/trunk/ambari-web/app/assets/licenses/NOTICE.txt=D=hangouts=1522643463206000=AFQjCNHhiS9lcjtDZJi0LCRVKBBkiFslmw > > > > Apache Spark: https://github.com/apache/spark/blob/master/NOTICE > < > https://www.google.com/url?q=https://github.com/apache/spark/blob/master/NOTICE=D=hangouts=1522643463206000=AFQjCNEyNwgI9q--GLEqJJXMLE9gPxD9VQ > > > > .. there are many more, but I stopped at these. > > So, isn't enforcing improvements on podling not harsh when it does not > attracts -1 or blocks releases for other Apache TLP releases? > > Abhishek > > On Sun, Apr 1, 2018 at 3:12 PM, Justin Mclean <jus...@classsoftware.com> > wrote: > > > Hi, > > > > It's hard to come up with a single simple sentence that applies in all > > cases. So when I said "if something is bundled then it's license and > > copyright needs to be in LICENSE not NOTICE.” I’m wrong as it's not going > > to all cover all cases. > > > > For bundling Apache licensed (v2) bits of software the copyright isn’t in > > the license. If the software has a NOTICE file then that is very likely > > going to effect your NOTICE file - which I think what Sebb was getting at > > and this is certainly the most common situation. > > > > In general other permissive licenses (like MIT and BSD) include a > > copyright line in the license text and theres’s no need to include > anything > > in NOTICE. > > > > Then we come to required notices which are going to be uncommon. The > > licenses with required notices (ignoring ALv2) that I know of are the BSD > > with advertising clause (Category X), CDDL (list of modifications and how > > to get source) and MPL (info how to get source code) which are both > > Category B. None of these would be bundled in a source release (but may > > affect a binary one). I can’t think of any category A license which has a > > required notices. Does anyone know of one? > > > > Thanks, > > Justin > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.12.0 release RC2
Well not a big drama, we can fix that with the next release. ATM 2 mentors have voted +1: Jean-Baptiste and myself. 1 * IPMC with Matt. On Sun, 1 Apr 2018 at 18:36, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > PS by my count you only need one more +1 vote and only one of your project > mentors have voted. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Gobblin 0.12.0 release RC2
Hi the content is simply. " Apache Gobblin Copyright 2017-2018 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). This product includes Bootstrap Copyright (c) 2011-2015 Twitter, Inc. This product includes the Glyphicons Halflings icon set Copyright (c) Jan Kovařík (http://glyphicons.com) Licensed under The MIT License (MIT) as a part of the Bootstrap project. This product includes normalize.css Copyright (c) Nicolas Gallagher and Jonathan Neal " Can you please explain what is the legal problem with such content? TBH I can see so many similar content in a lot of TLP projects. So why we should be more rude here than for other projects? On Sun, 1 Apr 2018 at 09:08, Justin Mclean <justinmcl...@me.com> wrote: > Hi, > > -1 binding as NOTICE should not contain copyrights of bundled 3rd party > software. The NOTICE file needs to only contain what is required (and not > already in LICENSE) and needs to be as small as possible as it affects > downstream projects. [2] > > I checked: > - incubating in name > - signatures and hashes good > - DISCLAIMER exists > - LICENSE is missing info for fonts [1] > - NOTICE is incorrect > - Some .sh files are missing ASF headers > - Can compile from source > > Thanks, > Justin > > 1. > apache-gobblin-incubating-sources-0.12.0/gobblin-admin/src/main/resources/static/fonts/* > 2. http://www.apache.org/dev/licensing-howto.html#mod-notice > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept Pinot into Apache Incubator
-codec:1.6 > > * commons-configuration:commons-configuration:1.6 > > * commons-fileupload:commons-fileupload:1.2.2 > > * commons-httpclient:commons-httpclient:3.1 > > * commons-io:commons-io:2.1 > > * commons-validator:commons-validator:1.4.0 > > * io.netty:netty-all:4.1.4.Final > > * io.swagger:swagger-jaxrs:1.5.10 > > * io.swagger:swagger-jersey2-jaxrs:1.5.10 > > * it.unimi.dsi:fastutil:6.5.16 > > * joda-time:joda-time:2 > > * log4j:log4j:1.2.17 > > * me.lemire.integercompression:JavaFastPFOR:0.0.13 > > * nl.jqno.equalsverifier:equalsverifier:1.7.2 > > * org.apache.avro:avro:1.7.6 > > * org.apache.commons:commons-compress:1.9 > > * org.apache.commons:commons-lang3:3.5 > > * org.apache.commons:commons-math:2.1 > > * org.apache.hadoop:hadoop-client:2.7.0 > > * org.apache.hadoop:hadoop-common:2.7.0 > > * org.apache.helix:helix-core:0.6.8 > > * org.apache.httpcomponents:httpclient:4.1.3 > > * org.apache.httpcomponents:httpclient:4.2.5 > > * org.apache.httpcomponents:httpcore:4.2.5 > > * org.apache.httpcomponents:httpmime:4.2.5 > > * org.apache.kafka:kafka_2.10:0.9.0.1 > > * org.apache.thrift:libthrift:0.9.1 > > * org.apache.zookeeper:zookeeper:3.4.9 > > * org.codehaus.jackson:jackson-core-asl:1.9.6 > > * org.codehaus.jackson:jackson-mapper-asl:1.9.6 > > * org.json:json:20080701 > > * org.roaringbitmap:RoaringBitmap:0.5.10 > > * org.testng:testng:6.0.1 > > * org.twitter4j:twitter4j-core:4.0.3 > > * org.webjars:swagger-ui:2.2.2 > > * org.xerial.larray:larray:0.2.1 > > * org.yaml:snakeyaml:1.16 > > * xml-apis:xml-apis:1.0.b2 > > === Dual license (Apache License 2.0 + LGPL 2.1), using under the Apache > > License === > > * org.codehaus.jackson:jackson-jaxrs:1.9.6 > > * org.codehaus.jackson:jackson-xc:1.9.6 > > === BSD === > > * com.jcabi:jcabi-log:0.17.1 > > * org.antlr:antlr4-annotations:4.3 > > * org.antlr:antlr4-runtime:4.3 > > === MIT === > > * com.github.nkzawa:socket.io-client:0.5.1 > > * org.mockito:mockito-core:2.10.0 > > * org.slf4j:slf4j-api:1.7.7 > > * org.slf4j:slf4j-log4j12:1.7.7 > > > > === Dependencies from the ASF Category B === > > Dual license (CDDL 1.1 + GPL 2 w/ CPE), using under the CDDL > > * com.sun.jersey:jersey-client:1.19.2 > > * javax.servlet:javax.servlet-api:3.0.1 > > * org.glassfish.jersey.containers:jersey-container-grizzly2-http:2.23 > > * org.glassfish.jersey.core:jersey-common:2.23 > > * org.glassfish.jersey.core:jersey-server:2.23 > > * org.glassfish.jersey.media:jersey-media-json-jackson:2.24 > > * org.glassfish.jersey.media:jersey-media-multipart:2.23 > > > > === Dependencies from the ASF Category X === > > JSON License > > * org.json:json:20080701 (to be removed before Apache incubation) > > > > > > == Cryptography == > > > > None > > > > == Required Resources == > > > > === Mailing lists === > > > > * pinot-private (with moderated subscriptions) > > * pinot-user > > * pinot-dev > > * pinot-commits > > > > === Git repository === > > > > * git://git.apache.org/pinot > > * https://git-wip-us.apache.org/repos/asf/incubator-pinot.git > > > > === Issue Tracking === > > > > A JIRA Issue tracker (PINOT) > > > > === Other Resources === > > > > The existing code already has unit and integration tests and we use > travis > > to test the patch before committing it to master. We would like to have > an > > instance of Jenkins to achieve similar functionality. > > > > == Initial Committers == > > > > * Kishore Gopalakrishna > > * Ravi Aringunram > > * Jean-François Im > > * Mayank Shrivastava > > * Subbu Subramaniam > > * Adwait Tumbde > > * Xiaotian Jiang > > * Jennifer Dai > > * Seunghyun Lee > > * Xiang Fu > > * Dhaval Patel > > * Neha Pawar > > * Alex Pucher > > * Yen-Jung Chang > > > > > > > > == Affiliations == > > > > * Kishore Gopalakrishna (LinkedIn) > > * Ravi Aringunram (LinkedIn) > > * Jean-François Im (LinkedIn) > > * Mayank Shrivastava (LinkedIn) > > * Subbu Subramaniam (LinkedIn) > > * Adwait Tumbde (LinkedIn) > > * Xiaotian Jiang (LinkedIn) > > * Jennifer Dai (LinkedIn) > > * Seunghyun Lee (LinkedIn) > > * Xiang Fu (Uber) > > * Dhaval Patel (Uber) > > * Neha Pawar (LinkedIn) > > * Alex Pucher (LinkedIn) > > * Yen-Jung Chang (LinkedIn) > > * Marcel Siegrist > > > > == Sponsors == > > > > === Champion === > > > > * Olivier Lamy < olamy at apache dot org> > > > > === Nominated Mentors === > > > > * Olivier Lamy > > * Kishore Gopalakrishna < kishoreg at apache dot org> > > * > > > > === Sponsoring Entity === > > > > The Apache Incubator > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept Pinot into Apache Incubator
9.6 > * org.json:json:20080701 > * org.roaringbitmap:RoaringBitmap:0.5.10 > * org.testng:testng:6.0.1 > * org.twitter4j:twitter4j-core:4.0.3 > * org.webjars:swagger-ui:2.2.2 > * org.xerial.larray:larray:0.2.1 > * org.yaml:snakeyaml:1.16 > * xml-apis:xml-apis:1.0.b2 > === Dual license (Apache License 2.0 + LGPL 2.1), using under the Apache > License === > * org.codehaus.jackson:jackson-jaxrs:1.9.6 > * org.codehaus.jackson:jackson-xc:1.9.6 > === BSD === > * com.jcabi:jcabi-log:0.17.1 > * org.antlr:antlr4-annotations:4.3 > * org.antlr:antlr4-runtime:4.3 > === MIT === > * com.github.nkzawa:socket.io-client:0.5.1 > * org.mockito:mockito-core:2.10.0 > * org.slf4j:slf4j-api:1.7.7 > * org.slf4j:slf4j-log4j12:1.7.7 > > === Dependencies from the ASF Category B === > Dual license (CDDL 1.1 + GPL 2 w/ CPE), using under the CDDL > * com.sun.jersey:jersey-client:1.19.2 > * javax.servlet:javax.servlet-api:3.0.1 > * org.glassfish.jersey.containers:jersey-container-grizzly2-http:2.23 > * org.glassfish.jersey.core:jersey-common:2.23 > * org.glassfish.jersey.core:jersey-server:2.23 > * org.glassfish.jersey.media:jersey-media-json-jackson:2.24 > * org.glassfish.jersey.media:jersey-media-multipart:2.23 > > === Dependencies from the ASF Category X === > JSON License > * org.json:json:20080701 (to be removed before Apache incubation) > > > == Cryptography == > > None > > == Required Resources == > > === Mailing lists === > > * pinot-private (with moderated subscriptions) > * pinot-user > * pinot-dev > * pinot-commits > > === Git repository === > > * git://git.apache.org/pinot > * https://git-wip-us.apache.org/repos/asf/incubator-pinot.git > > === Issue Tracking === > > A JIRA Issue tracker (PINOT) > > === Other Resources === > > The existing code already has unit and integration tests and we use travis > to test the patch before committing it to master. We would like to have an > instance of Jenkins to achieve similar functionality. > > == Initial Committers == > > * Kishore Gopalakrishna > * Ravi Aringunram > * Jean-François Im > * Mayank Shrivastava > * Subbu Subramaniam > * Adwait Tumbde > * Xiaotian Jiang > * Jennifer Dai > * Seunghyun Lee > * Xiang Fu > * Dhaval Patel > * Neha Pawar > * Alex Pucher > * Yen-Jung Chang > > > > == Affiliations == > > * Kishore Gopalakrishna (LinkedIn) > * Ravi Aringunram (LinkedIn) > * Jean-François Im (LinkedIn) > * Mayank Shrivastava (LinkedIn) > * Subbu Subramaniam (LinkedIn) > * Adwait Tumbde (LinkedIn) > * Xiaotian Jiang (LinkedIn) > * Jennifer Dai (LinkedIn) > * Seunghyun Lee (LinkedIn) > * Xiang Fu (Uber) > * Dhaval Patel (Uber) > * Neha Pawar (LinkedIn) > * Alex Pucher (LinkedIn) > * Yen-Jung Chang (LinkedIn) > * Marcel Siegrist > > == Sponsors == > > === Champion === > > * Olivier Lamy < olamy at apache dot org> > > === Nominated Mentors === > > * Olivier Lamy > * Kishore Gopalakrishna < kishoreg at apache dot org> > * > > === Sponsoring Entity === > > The Apache Incubator > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Resolution to graduate Apache FreeMarker to TLP
+1 (binding) On 19 February 2018 at 20:45, Jacopo Cappellato <jaco...@apache.org> wrote: > Hi all, > > The FreeMarker community has discussed [1] and voted [2] positively on > graduating to a top level project (TLP). The resolution for the graduation > has been proposed and discussed in this list [3]. > Information about FreeMarker can be found in the status page [4], > in the project maturity model [5] and in the website [6]. > > I am now calling a VOTE to ask the IPMC to recommend the resolution to the > ASF Board: > the proposed resolution can be found at the bottom of this email. > The vote will be open for 72 hours. > > [ ] +1 recommend to the Board the resolution to graduate Apache FreeMarker > to a TLP > [ ] +0 no opinion > [ ] -1 don't graduate Apache FreeMarker to a TLP (please specify a reason) > > Thanks, > Jacopo Cappellato > > References: > [1] Community graduation discussion: https://s.apache.org/gYMw > [2] Community graduation vote: https://s.apache.org/MNdd > [3] Incubator resolution discussion: https://s.apache.org/xdI3 > [4] Project status page: > http://incubator.apache.org/projects/freemarker.html > [5] Project maturity model: https://s.apache.org/ixlR > [6] Freemarker website: https://freemarker.apache.org/ > > The proposed Resolution of the Apache FreeMarker project: > > -- > > Establish the Apache FreeMarker 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 template engine. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache FreeMarker Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that the Apache FreeMarker Project be and hereby is > responsible for the creation and maintenance of software > related to a template engine, and be it further > > RESOLVED, that the office of "Vice President, Apache FreeMarker" 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 FreeMarker Project, and to have primary responsibility > for management of the projects within the scope of > responsibility of the Apache FreeMarker 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 FreeMarker Project: > > * Dániel Dékány <ddek...@apache.org> > * David E. Jones<jone...@apache.org> > * Jacopo Cappellato <jaco...@apache.org> > * Jacques Le Roux <jler...@apache.org> > * Nan Lei <nan...@apache.org> > * Sergio Fernández<wik...@apache.org> > * Woonsan Ko <woon...@apache.org> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dániel Dékány > be appointed to the office of Vice President, Apache FreeMarker, > to serve in accordance with and subject to the direction of the > Board of Directors and the Bylaws of the Foundation until > death, resignation, retirement, removal or disqualification, > or until a successor is appointed; and be it further > > RESOLVED, that the Apache FreeMarker Project be and hereby > is tasked with the migration and rationalization of the Apache > Incubator FreeMarker podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator FreeMarker podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > -- > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [DISCUSS] Apache Pinot Incubator Proposal
org.apache.hadoop:hadoop-common:2.7.0 > > >>> * org.apache.helix:helix-core:0.6.8 > > >>> * org.apache.httpcomponents:httpclient:4.1.3 > > >>> * org.apache.httpcomponents:httpclient:4.2.5 > > >>> * org.apache.httpcomponents:httpcore:4.2.5 > > >>> * org.apache.httpcomponents:httpmime:4.2.5 > > >>> * org.apache.kafka:kafka_2.10:0.9.0.1 > > >>> * org.apache.thrift:libthrift:0.9.1 > > >>> * org.apache.zookeeper:zookeeper:3.4.9 > > >>> * org.codehaus.jackson:jackson-core-asl:1.9.6 > > >>> * org.codehaus.jackson:jackson-mapper-asl:1.9.6 > > >>> * org.json:json:20080701 > > >>> * org.roaringbitmap:RoaringBitmap:0.5.10 > > >>> * org.testng:testng:6.0.1 > > >>> * org.twitter4j:twitter4j-core:4.0.3 > > >>> * org.webjars:swagger-ui:2.2.2 > > >>> * org.xerial.larray:larray:0.2.1 > > >>> * org.yaml:snakeyaml:1.16 > > >>> * xml-apis:xml-apis:1.0.b2 > > >>> === Dual license (Apache License 2.0 + LGPL 2.1), using under the > > Apache > > >>> License === > > >>> * org.codehaus.jackson:jackson-jaxrs:1.9.6 > > >>> * org.codehaus.jackson:jackson-xc:1.9.6 > > >>> === BSD === > > >>> * com.jcabi:jcabi-log:0.17.1 > > >>> * org.antlr:antlr4-annotations:4.3 > > >>> * org.antlr:antlr4-runtime:4.3 > > >>> === MIT === > > >>> * com.github.nkzawa:socket.io-client:0.5.1 > > >>> * org.mockito:mockito-core:2.10.0 > > >>> * org.slf4j:slf4j-api:1.7.7 > > >>> * org.slf4j:slf4j-log4j12:1.7.7 > > >>> > > >>> === Dependencies from the ASF Category B === > > >>> Dual license (CDDL 1.1 + GPL 2 w/ CPE), using under the CDDL > > >>> * com.sun.jersey:jersey-client:1.19.2 > > >>> * javax.servlet:javax.servlet-api:3.0.1 > > >>> * org.glassfish.jersey.containers:jersey-container- > grizzly2-http:2.23 > > >>> * org.glassfish.jersey.core:jersey-common:2.23 > > >>> * org.glassfish.jersey.core:jersey-server:2.23 > > >>> * org.glassfish.jersey.media:jersey-media-json-jackson:2.24 > > >>> * org.glassfish.jersey.media:jersey-media-multipart:2.23 > > >>> > > >>> === Dependencies from the ASF Category X === > > >>> JSON License > > >>> * org.json:json:20080701 (to be removed before Apache incubation) > > >>> > > >>> > > >>> == Cryptography == > > >>> > > >>> None > > >>> > > >>> == Required Resources == > > >>> > > >>> === Mailing lists === > > >>> > > >>> * pinot-private (with moderated subscriptions) > > >>> * pinot-user > > >>> * pinot-dev > > >>> * pinot-commits > > >>> > > >>> === Git repository === > > >>> > > >>> * git://git.apache.org/pinot > > >>> * https://git-wip-us.apache.org/repos/asf/incubator-pinot.git > > >>> > > >>> === Issue Tracking === > > >>> > > >>> A JIRA Issue tracker (PINOT) > > >>> > > >>> === Other Resources === > > >>> > > >>> The existing code already has unit and integration tests and we use > > >>> travis > > >>> to test the patch before committing it to master. We would like to > have > > >>> an > > >>> instance of Jenkins to achieve similar functionality. > > >>> > > >>> == Initial Committers == > > >>> > > >>> * Kishore Gopalakrishna > > >>> * Ravi Aringunram > > >>> * Jean-François Im > > >>> * Mayank Shrivastava > > >>> * Subbu Subramaniam > > >>> * Adwait Tumbde > > >>> * Xiaotian Jiang > > >>> * Jennifer Dai > > >>> * Seunghyun Lee > > >>> * Xiang Fu > > >>> * Dhaval Patel > > >>> * Neha Pawar > > >>> * Alex Pucher > > >>> * Yen-Jung Chang > > >>> > > >>> > > >>> > > >>> == Affiliations == > > >>> > > >>> * Kishore Gopalakrishna (LinkedIn) > > >>> * Ravi Aringunram (LinkedIn) > > >>> * Jean-François Im (LinkedIn) > > >>> * Mayank Shrivastava (LinkedIn) > > >>> * Subbu Subramaniam (LinkedIn) > > >>> * Adwait Tumbde (LinkedIn) > > >>> * Xiaotian Jiang (LinkedIn) > > >>> * Jennifer Dai (LinkedIn) > > >>> * Seunghyun Lee (LinkedIn) > > >>> * Xiang Fu (Uber) > > >>> * Dhaval Patel (Uber) > > >>> * Neha Pawar (LinkedIn) > > >>> * Alex Pucher (LinkedIn) > > >>> * Yen-Jung Chang (LinkedIn) > > >>> > > >>> == Sponsors == > > >>> > > >>> === Champion === > > >>> > > >>> * Olivier Lamy < olamy at apache dot org> > > >>> > > >>> === Nominated Mentors === > > >>> > > >>> * Olivier Lamy > > >>> > > >>> === Sponsoring Entity === > > >>> > > >>> The Apache Incubator > > >> > > >> > > >> - > > >> 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 > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Guacamole 0.9.13-incubating (RC1)
+1 On 29 July 2017 at 09:52, Mike Jumper <mike.jum...@guac-dev.org> wrote: > On Sun, Jul 23, 2017 at 10:32 PM, Mike Jumper <mike.jum...@guac-dev.org> > wrote: > > > Hello Incubator PMC, > > > > The Apache Guacamole community has voted on and approved a proposal to > > release Apache Guacamole 0.9.13-incubating. > > > > We now kindly request that the Incubator PMC members review and vote on > > this incubator release. > > > > The VOTE RESULT is here: > > > > http://mail-archives.apache.org/mod_mbox/incubator-guacamole > > -dev/201707.mbox/%3CCALKeL-Oc-xjbeKr_RiLqp_m4_7sYdF5ZoK9T4q% > > 3DN%2B0J7q-Hk9g%40mail.gmail.com%3E > > > > The draft release notes (along with links to artifacts, > > signatures/checksums, and updated documentation) can be found here: > > > > http://guacamole.incubator.apache.org/releases/0.9.13-incubating/ > > > > The git tag for all relevant repositories is "0.9.13-incubating-RC1": > > > > https://github.com/apache/incubator-guacamole-client/tree/0. > > 9.13-incubating-RC1 (commit de12b683d746129ddc8b34425ed6e40b618c91d6) > > https://github.com/apache/incubator-guacamole-server/tree/0. > > 9.13-incubating-RC1 (commit ca3563a38e6416a6cde7f208dc9827c512227888) > > https://github.com/apache/incubator-guacamole-manual/tree/0. > > 9.13-incubating-RC1 (commit a1a4ee64dd00217905288ac1d902713b0298c03b) > > > > Build instructions are included in the manual, which is part of the > > updated documentation referenced above. For convenience: > > > > http://guacamole.incubator.apache.org/doc/0.9.13-incubating/ > > gug/installing-guacamole.html > > > > Maven artifacts for guacamole-common, guacamole-common-js, and > > guacamole-ext can be found in the following staging repository: > > > > https://repository.apache.org/content/repositories/ > orgapacheguacamole-1007 > > > > Source and binary distributions (also linked within the release notes): > > > > https://dist.apache.org/repos/dist/dev/incubator/guacamole/0 > > .9.13-incubating-RC1/ > > > > Artifacts have been signed with the "mjum...@apache.org" key listed in: > > > > https://dist.apache.org/repos/dist/dev/incubator/guacamole/KEYS > > > > Please review and vote: > > > > [ ] +1 Approve the release > > [ ] -1 Don't approve the release (please provide specific comments) > > > > This vote will be open for at least 72 hours. > > > > Thanks, > > > > - Mike > > > > > Friendly bump. > > Many thanks, > > - Mike > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Gobblin Incubator Meetup/Video Conference
Hi, So moving forward on Gobblin, (yeah finally software grant bottleneck unlock!!). This community used to have a monthly online conference (such announced https://www.meetup.com/Big-Data-Meetup-LinkedIn/events/239739875/ ) The idea is to keep doing with report/links/etc... posted on both user@ and the wiki. I wonder if someone see any issue with that? Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Git repo creation request no incubator in PMC list
Thanks! On 20 July 2017 at 12:19, John D. Ament <johndam...@apache.org> wrote: > Olivier, > > Looks like a bug with reporeq. I also do not see incubator in the drop > down. I have submitted https://issues.apache.org/jira/browse/INFRA-14658 > to > address. Hopefully infra can fix soon. > > John > > On Wed, Jul 19, 2017 at 9:56 PM Olivier Lamy <ol...@apache.org> wrote: > > > Hi, > > I'd like to create a git repo for Gobblin website. > > So I follow the documentation and the documentation to create a git repo > > says to go to https://reporeq.apache.org/ > > But here I don't have any option to choose incubator as a PMC so the no > > writable field Generated name says: "Your PMCs-incubator-gobblin-site. > git" > > (see attache screenshot). which is a bit weird. > > > > So I wonder how to fix that or is there any other tool to use for > > incubator? > > > > Thanks > > -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > [1} > > https://incubator.apache.org/guides/podling_sourcecontrol. > html#set_up_git_repository > > > > --------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Git repo creation request no incubator in PMC list
Hi, I'd like to create a git repo for Gobblin website. So I follow the documentation and the documentation to create a git repo says to go to https://reporeq.apache.org/ But here I don't have any option to choose incubator as a PMC so the no writable field Generated name says: "Your PMCs-incubator-gobblin-site.git" (see attache screenshot). which is a bit weird. So I wonder how to fix that or is there any other tool to use for incubator? Thanks -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy [1} https://incubator.apache.org/guides/podling_sourcecontrol.html#set_up_git_repository - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Amaterasu into the Apache Incubator
ate but provide a large set of features. We plan to > stabilize and head to a first production ready release during the > incubation process. The current license is already Apache 2.0. > > === Meritocracy === > > We intend to radically expand the initial developer and user community by > running the project in accordance with the "Apache Way". Users and new > contributors will be treated with respect and welcomed. By participating in > the community and providing quality patches/support that move the project > forward, they will earn merit. They also will be encouraged to provide > non-code contributions (documentation, events, community management, etc.) > and will gain merit for doing so. Those with a proven support and quality > track record will be encouraged to become committers. > > === Community === > > As a relatively new project, Amaterasu has a small, but growing community. > Amaterasu is an open project, not just with it’s source code but also with > our discussions which are held openly in our slack > https://shintoio.slack.com which contains channels for design, tech and > future directions discussions. > > If Amaterasu is accepted for incubation, the primary initial goal is to > build a large and strong community. We are confident that Amaterasu can > become a key project for big data operations, which hopefully will create a > large community of users and developers. > > === Known Risks === > > Development has been sponsored mostly by a one company. For the project to > fully transition to the Apache Way governance model, development must shift > towards the meritocracy-centric model of growing a community of > contributors balanced with the needs for extreme stability and core > implementation coherency. > > === Orphaned products === > > We are fully committed on Amaterasu. A few organizations have expressed > their interest in using Amaterasu. > > === Inexperience with Open Source === > > We have been developing and using open source software for a long time. > Additionally, several ASF veterans have agreed to mentor the project and > they are listed in this proposal. The project will rely on their guidance > and collective wisdom to quickly transition the entire team of initial > committers towards practicing the Apache Way. > > === Reliance on Salaried Developers === > > Most of the current contributors are employed in the Big Data space. While > they might wander from their current employers, they are unlikely to > venture far from their core expertises and thus will continue to be engaged > with the project regardless of their current employers. > > === An Excessive Fascination with the Apache Brand === > > While we intend to leverage the Apache ‘branding’ when talking to other > projects as testament of our project’s ‘neutrality’, we have no plans for > making use of Apache brand in press releases nor posting billboards > advertising acceptance of Amaterasu into Apache Incubator. > > The main purpose in applying for Apache incubation is due to the fact that > Amaterasu is built with integration already in mind for many tools which > are Apache projects, and we see Amaterasu as an extension of these > projects. We hope that by being an Apache project, we can integrate better, > and collaborate more effectively with the relevant projects. As Amaterasu > matures, we see mutual benefits for all involved. > > === Initial Source === > > https://github.com/shintoio/amaterasu > > === External Dependencies === > > All external dependencies are licensed under an Apache 2.0 license or > Apache-compatible license. As we grow the Amaterasu community we will > configure our build process to require and validate all contributions and > dependencies are licensed under the Apache 2.0 license or are under an > Apache-compatible license. > > * Apache Spark > * Apache Hadoop > * Apache Maven (maven-core) > * Apache Commons > * Apache Log4j > * Apache Mesos > * Apache Zookeeper > * Apache Curator > * Scala > * Junit > * Py4j > > Future versions are planned to integrate with: > > * Apache YARN > * Apache Hive > * Apache Drill > > === Required Resources === > > Mailing lists > > * priv...@amaterasu.incubator.apache.org (moderated subscriptions) > * comm...@amaterasu.incubator.apache.org > * d...@amaterasu.incubator.apache.org > * iss...@amaterasu.incubator.apache.org > > Git Repository > > * https://git-wip-us.apache.org/repos/asf/incubator-amaterasu.git > > Issue Tracking > > * JIRA Project Amaterasu > > Initial Committers > > * Yaniv Rodenski > * Jean-Baptiste Onofré > * Eyal Ben Ivri > * Karel Alfonso > * Kirupagaran (Kirupa) Devarajan > * Nadav Har Tzvi > > Affiliations > > * Yaniv Rodenski - Shinto > * Jean-Baptiste Onofré - Talend > * Olivier Lamy - Webtide > > Sponsors > > Champion > > * Jean-Baptiste Onofré > > Mentors > > * Jean-Baptiste Onofré > * Olivier Lamy > > Sponsoring Entity > > The Apache Incubator > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [RESULT][VOTE] Gobblin to enter Apache Incubator
Hi, My first task was to create the podling file in incubator svn the ask mailing lists. So now that's done then we will be able to exchange on mailing list when they will have been created. Cheers Olivier On 24 February 2017 at 00:06, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Great ! > > Here we are ;) > > @Olivier, can we sync together to create the resources ? > > Thanks ! > Regards > JB > > On 02/23/2017 01:00 AM, Olivier Lamy wrote: > >> Hi, >> The vote has passed with the following result: >> +1 (binding): Jean-Baptiste, Ross, Colm, Jim, Raphael, Carl, Craig >> +1 (non binding): Lian, Abhishek, Naresh >> >> Vote thread: https://s.apache.org/GOBBLIN_INCUBATION_VOTE >> I will start all the process in the coming days. >> Thanks to all the voters! >> >> Cheers >> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
[RESULT][VOTE] Gobblin to enter Apache Incubator
Hi, The vote has passed with the following result: +1 (binding): Jean-Baptiste, Ross, Colm, Jim, Raphael, Carl, Craig +1 (non binding): Lian, Abhishek, Naresh Vote thread: https://s.apache.org/GOBBLIN_INCUBATION_VOTE I will start all the process in the coming days. Thanks to all the voters! Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Gobblin to enter Apache Incubator
Hi Craig On 20 February 2017 at 00:23, Craig Russell <craig.russ...@oracle.com> wrote: > Hi Olivier, > > Can you also post the link to this proposal on https://wiki.apache.org/ > incubator/ProjectProposals ? > Sure. done. Olivier > > Thanks, > > Craig > > > On Feb 16, 2017, at 9:33 PM, Olivier Lamy <ol...@apache.org> wrote: > > > > Hello Everyone, > > I would like to call a vote for accepting "Gobblin" for incubation in the > > Apache Incubator. > > The full proposal is available below, and is also available in the wiki: > > https://wiki.apache.org/incubator/GobblinProposal > > > > 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 > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
[VOTE] Gobblin to enter Apache Incubator
Hello Everyone, I would like to call a vote for accepting "Gobblin" for incubation in the Apache Incubator. The full proposal is available below, and is also available in the wiki: https://wiki.apache.org/incubator/GobblinProposal Please cast your vote: [ ] +1, bring Gobblin into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Gobblin into Incubator, because... The vote will open at least for 72 hours and only votes from the Incubator PMC are binding. I start with my vote: +1 (binding) Cheers -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy = Apache Gobblin Proposal = == Abstract == 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. == Proposal == Gobblin is a universal data integration framework. The framework has been used to build a variety of big data applications such as ingestion, replication, and data retention. The fundamental constructs provided by the Gobblin framework are: 1. An expandable set of connectors that allow data to be integrated from a variety of sources and sinks. The range of connectors already available in Gobblin are quite diverse and are an ever expanding set. To highlight just a few examples, connectors exist for databases (e.g., MySQL, Oracle Teradata, Couchbase etc.), web based technologies (REST APIs, FTP/SFTP servers, Filers), scalable storage (HDFS, S3, Ambry etc,), streaming data (Kafka, EventHubs etc.), and a variety of proprietary data sources and sinks (e.g.Salesforce, Google Analytics, Google Webmaster etc.). Similarly, Gobblin has a rich library of converters that allow for conversion of data from one format to another as data moves across system boundaries (e.g. AVRO in HDFS to JSON in another system). 2. Gobblin has a well defined and customizable state management layer that allows writing stateful applications. These are particularly useful when solving problems like bulk incremental ingest and keeping several clusters replicated in sync. The ability to record work that has been completed and what remains in a scalable manner is critical to writing such diverse applications successfully. 3. Gobblin is agnostic to the underlying execution engine. It can be tailored to run ontop of a variety of execution frameworks ranging from multiple processes on a single node, to open source execution engines like MapReduce, Spark or Samza, natively on top of raw containers like Yarn or Mesos, and the public cloud like Amazon AWS or Microsoft Azure. We are extending Gobblin to run on top of a self managed cluster when security is vital. This allows different applications that require different degrees of scalability, latency or security to be customized to for their specific needs. For example, highly latency sensitive applications can be executed in a streaming environment while batch based execution might benefit applications where the priority might be geared towards optimal container utilization. 4.Gobblin comes out of the box with several diagnosability features like Gobblin metrics and error handling. Collectively, these features allow Gobblin to operate at the scale of petabytes of data. To give just one example, the ability to quarantine a few bad records from an isolated Kafka topic without stopping the entire flow from continued execution is vital when the number of Kafka topics range in the thousands and the collective data handled is in the petabytes. Gobblin thus provides crisply defined software constructs that can be used to build a vast array of data integration applications customizable for varied user needs. It has become a preferred technology for data integration use-cases by many organizations worldwide (see a partial list here). == Background == Over the last decade, data integration has evolved use case by use case in most companies. For example, at LinkedIn, when Kafka became a significant part of the data ecosystem, a system called Camus was built to ingest this data for analytics processing on Hadoop. Similarly, we had custom pipelines to ingest data from Salesforce, Oracle and myriad other sources. This pattern became the norm rather than the exception and one point, LinkedIn was running at least fifteen different types of ingestion pipelines. This fragmentation has several unfortunate implications. Operational costs scale with the number of pipelines even if the myriad pipelines share a vasty array of common features. Bug fixes and performance optimizations cannot be shared across the pipelines. A common set of practices around debugging and deployment does not emerge. Each pipeline operator will continue to invest in his little silo of the data integration world completely oblivious to the challenges of his fellow operator sitting five tables down. These experiences were the genesis behind
Re: [discuss] Apache Gobblin Incubator Proposal
Hi Thanks for the proposal Jim! I will add you as a mentor then start the vote Cheers Olivier On 16 February 2017 at 02:35, Jim Jagielski <j...@jagunet.com> wrote: > If you need/want another mentor, I volunteer > > > On Feb 14, 2017, at 3:53 PM, Olivier Lamy <ol...@apache.org> wrote: > > > > Hi > > Well I don't see issues as no one discuss the proposal. > > So I will start the official vote tomorrow. > > Cheers > > Olivier > > > > On 6 February 2017 at 14:08, Olivier Lamy <ol...@apache.org> wrote: > > > >> Hello everyone, > >> I would like to submit to you a proposal to bring Gooblin to the Apache > >> Software Foundation. > >> The text of the proposal is included below and available as a draft here > >> in the Wiki: https://wiki.apache.org/incubator/GobblinProposal > >> > >> We will appreciate any feedback and input. > >> > >> Olivier on behalf of the Gobblin community > >> > >> > >> = Apache Gobblin Proposal = > >> == Abstract == > >> 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. > >> > >> == Proposal == > >> > >> Gobblin is a universal data integration framework. The framework has > been > >> used to build a variety of big data applications such as ingestion, > >> replication, and data retention. The fundamental constructs provided by > the > >> Gobblin framework are: > >> > >> 1. An expandable set of connectors that allow data to be integrated from > >> a variety of sources and sinks. The range of connectors already > available > >> in Gobblin are quite diverse and are an ever expanding set. To highlight > >> just a few examples, connectors exist for databases (e.g., MySQL, Oracle > >> Teradata, Couchbase etc.), web based technologies (REST APIs, FTP/SFTP > >> servers, Filers), scalable storage (HDFS, S3, Ambry etc,), streaming > data > >> (Kafka, EventHubs etc.), and a variety of proprietary data sources and > >> sinks (e.g.Salesforce, Google Analytics, Google Webmaster etc.). > Similarly, > >> Gobblin has a rich library of converters that allow for conversion of > data > >> from one format to another as data moves across system boundaries (e.g. > >> AVRO in HDFS to JSON in another system). > >> > >> > >> 2. Gobblin has a well defined and customizable state management layer > >> that allows writing stateful applications. These are particularly useful > >> when solving problems like bulk incremental ingest and keeping several > >> clusters replicated in sync. The ability to record work that has been > >> completed and what remains in a scalable manner is critical to writing > such > >> diverse applications successfully. > >> > >> > >> 3. Gobblin is agnostic to the underlying execution engine. It can be > >> tailored to run ontop of a variety of execution frameworks ranging from > >> multiple processes on a single node, to open source execution engines > like > >> MapReduce, Spark or Samza, natively on top of raw containers like Yarn > or > >> Mesos, and the public cloud like Amazon AWS or Microsoft Azure. We are > >> extending Gobblin to run on top of a self managed cluster when security > is > >> vital. This allows different applications that require different > degrees > >> of scalability, latency or security to be customized to for their > specific > >> needs. For example, highly latency sensitive applications can be > executed > >> in a streaming environment while batch based execution might benefit > >> applications where the priority might be geared towards optimal > container > >> utilization. > >> > >> 4.Gobblin comes out of the box with several diagnosability features like > >> Gobblin metrics and error handling. Collectively, these features allow > >> Gobblin to operate at the scale of petabytes of data. To give just one > >> example, the ability to quarantine a few bad records from an isolated > Kafka > >> topic without stopping the entire flow from continued execution is vital > >> when the number of Kafka topics range in the thousands and the > collective > >> data handled is in the petabytes. > >> > >> Gobblin thus provides crisply defined softwar
Re: [discuss] Apache Gobblin Incubator Proposal
Hi Well I don't see issues as no one discuss the proposal. So I will start the official vote tomorrow. Cheers Olivier On 6 February 2017 at 14:08, Olivier Lamy <ol...@apache.org> wrote: > Hello everyone, > I would like to submit to you a proposal to bring Gooblin to the Apache > Software Foundation. > The text of the proposal is included below and available as a draft here > in the Wiki: https://wiki.apache.org/incubator/GobblinProposal > > We will appreciate any feedback and input. > > Olivier on behalf of the Gobblin community > > > = Apache Gobblin Proposal = > == Abstract == > 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. > > == Proposal == > > Gobblin is a universal data integration framework. The framework has been > used to build a variety of big data applications such as ingestion, > replication, and data retention. The fundamental constructs provided by the > Gobblin framework are: > > 1. An expandable set of connectors that allow data to be integrated from > a variety of sources and sinks. The range of connectors already available > in Gobblin are quite diverse and are an ever expanding set. To highlight > just a few examples, connectors exist for databases (e.g., MySQL, Oracle > Teradata, Couchbase etc.), web based technologies (REST APIs, FTP/SFTP > servers, Filers), scalable storage (HDFS, S3, Ambry etc,), streaming data > (Kafka, EventHubs etc.), and a variety of proprietary data sources and > sinks (e.g.Salesforce, Google Analytics, Google Webmaster etc.). Similarly, > Gobblin has a rich library of converters that allow for conversion of data > from one format to another as data moves across system boundaries (e.g. > AVRO in HDFS to JSON in another system). > > > 2. Gobblin has a well defined and customizable state management layer > that allows writing stateful applications. These are particularly useful > when solving problems like bulk incremental ingest and keeping several > clusters replicated in sync. The ability to record work that has been > completed and what remains in a scalable manner is critical to writing such > diverse applications successfully. > > > 3. Gobblin is agnostic to the underlying execution engine. It can be > tailored to run ontop of a variety of execution frameworks ranging from > multiple processes on a single node, to open source execution engines like > MapReduce, Spark or Samza, natively on top of raw containers like Yarn or > Mesos, and the public cloud like Amazon AWS or Microsoft Azure. We are > extending Gobblin to run on top of a self managed cluster when security is > vital. This allows different applications that require different degrees > of scalability, latency or security to be customized to for their specific > needs. For example, highly latency sensitive applications can be executed > in a streaming environment while batch based execution might benefit > applications where the priority might be geared towards optimal container > utilization. > > 4.Gobblin comes out of the box with several diagnosability features like > Gobblin metrics and error handling. Collectively, these features allow > Gobblin to operate at the scale of petabytes of data. To give just one > example, the ability to quarantine a few bad records from an isolated Kafka > topic without stopping the entire flow from continued execution is vital > when the number of Kafka topics range in the thousands and the collective > data handled is in the petabytes. > > Gobblin thus provides crisply defined software constructs that can be used > to build a vast array of data integration applications customizable for > varied user needs. It has become a preferred technology for data > integration use-cases by many organizations worldwide (see a partial list > here). > > == Background == > > Over the last decade, data integration has evolved use case by use case in > most companies. For example, at LinkedIn, when Kafka became a significant > part of the data ecosystem, a system called Camus was built to ingest this > data for analytics processing on Hadoop. Similarly, we had custom pipelines > to ingest data from Salesforce, Oracle and myriad other sources. This > pattern became the norm rather than the exception and one point, LinkedIn > was running at least fifteen different types of ingestion pipelines. This > fragmentation has several unfortunate implications. Operational costs scale > with the number of pipelines even if the myriad pipelines share a vasty > array of common features. Bug fixes and performance optimizations cannot be > sha
[discuss] Apache Gobblin Incubator Proposal
). == Cryptography == We do not expect Gobblin to be a controlled export item due to the use of encryption. == Required Resources == === Mailing lists === * gobblin-user * gobblin-dev * gobblin-commits * gobblin-private for private PMC discussions (with moderated subscriptions) === Subversion Directory === Git is the preferred source control system: git://git.apache.org/gobblin === Issue Tracking === JIRA Gobblin (GOBBLIN) === Other Resources === The existing code already has unit and integration tests, so we would like a Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committers == * Abhishek Tiwari * Shirshanka Das * Chavdar Botev * Sahil Takiar * Yinan Li * Ziyang Liu <> * Lorand Bendig * Issac Buenrostro * Hung Tran * Olivier Lamy * Jean-Baptiste Onofré <jbono...@apache.org> == Affiliations == * Abhishek Tiwari - LinkedIn * Shirshanka Das - LinkedIn * Chavdar Botev - Stealth Startup * Sahil Takiar - Cloudera * Yinan Li - Google * Ziyang Liu - Facebook * Lorand Bendig - Swisscom * Issac Buenrostro - LinkedIn * Hung Tran - LinkedIn * Olivier Lamy - Webtide * Jean-Baptiste Onofre - Talend == Sponsors == === Champion === Olivier Lamy < olamy at apache dot org> === Nominated Mentors === * Olivier Lamy * Jean-Baptiste Onofre * ? * ? == Sponsoring Entity == The Apache Incubator
Re: [IP CLEARANCE] Aether, renamed to Maven Artifact Resolver
+1 On 29 September 2016 at 01:25, Hervé Boutemy <hbout...@apache.org> wrote: > Apache Maven received a code donation for Aether, that we renamed to Maven > Artifact Resolver to fix a trademark issue: > > http://incubator.apache.org/ip-clearance/maven-aether.html > > The import plan is more detailed at http://maven.apache.org/aether.html > > Please vote to approve this contribution. Lazy consensus applies. If no -1 > votes are cast within the next 72 hours, the vote passes. > > Regards, > > Hervé > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept Mnemonic into the Apache Incubator
t; > > interests in starting this project is based on the factors mentioned > > > in the Rationale section. > > > > > > We would like Mnemonic to become an Apache project to further foster > > > a healthy community of contributors and consumers in BigData > > > technology R areas. Since Mnemonic can directly benefit many > > > Apache projects and solves major performance problems, we expect the > > > Apache Software Foundation to increase interaction with the larger > community as well. > > > > > > === Documentation === > > > The documentation is currently available at Intel and will be posted > > > under: https://mnemonic.incubator.apache.org/docs > > > > > > === Initial Source === > > > Initial source code is temporary hosted Github for general viewing: > > > https://github.com/NonVolatileComputing/Mnemonic.git > > > It will be moved to Apache http://git.apache.org/ after podling. > > > > > > The initial Source is written in Java code (88%) and mixed with JNI > > > C code (11%) and shell script (1%) for underlying native allocation > > > libraries. > > > > > > === Source and Intellectual Property Submission Plan === As soon as > > > Mnemonic is approved to join the Incubator, the source code will be > > > transitioned via the Software Grant Agreement onto ASF > > > infrastructure and in turn made available under the Apache License, > > > version 2.0. > > > > > > === External Dependencies === > > > The required external dependencies are all Apache licenses or other > > > compatible Licenses > > > Note: The runtime dependent licenses of Mnemonic are all declared as > > > Apache 2.0, the GNU licensed components are used for Mnemonic build > > > and deployment. The Mnemonic JNI libraries are built using the GNU > > > tools. > > > > > > maven and its plugins (http://maven.apache.org/ ) [Apache 2.0] > > > JDK8 or OpenJDK 8 (http://java.com/) [Oracle or Openjdk JDK License] > > > Nvml (http://pmem.io ) [optional] [Open Source] PMalloc > > > (https://github.com/bigdata-memory/pmalloc ) [optional] [Apache > > 2.0] > > > > > > Build and test dependencies: > > > org.testng.testng v6.8.17 (http://testng.org) [Apache 2.0] > > > org.flowcomputing.commons.commons-resgc v0.8.7 [Apache 2.0] > > > org.flowcomputing.commons.commons-primitives v.0.6.0 [Apache 2.0] > > > com.squareup.javapoet v1.3.1-SNAPSHOT [Apache 2.0] > > > JDK8 or OpenJDK 8 (http://java.com/) [Oracle or Openjdk JDK License] > > > > > > === Cryptography === > > > Project Mnemonic does not use cryptography itself, however, Hadoop > > > projects use standard APIs and tools for SSH and SSL communication > > > where necessary. > > > > > > === Required Resources === > > > We request that following resources be created for the project to > > > use > > > > > > Mailing lists > > > priv...@mnemonic.incubator.apache.org (moderated subscriptions) > > > comm...@mnemonic.incubator.apache.org > > > d...@mnemonic.incubator.apache.org > > > > > > Git repository > > > https://github.com/apache/incubator-mnemonic > > > > > > Documentation > > > https://mnemonic.incubator.apache.org/docs/ > > > > > > JIRA instance > > > https://issues.apache.org/jira/browse/mnemonic > > > > > > === Initial Committers === > > > * Gang (Gary) Wang (gang1 dot wang at intel dot com) > > > > > > * Yanping Wang (yanping dot wang at intel dot com) > > > > > > * Uma Maheswara Rao G (umamahesh at apache dot org) > > > > > > * Kai Zheng (drankye at apache dot org) > > > > > > * Rakesh Radhakrishnan Potty (rakeshr at apache dot org) > > > > > > * Sean Zhong (seanzhong at apache dot org) > > > > > > * Henry Saputra (hsaputra at apache dot org) > > > > > > * Hao Cheng (hao dot cheng at intel dot com) > > > > > > === Additional Interested Contributors === > > > * Debo Dutta (dedutta at cisco dot com) > > > > > > * Liang Chen (chenliang613 at Huawei dot com) > > > > > > === Affiliations === > > > * Gang (Gary) Wang, Intel > > > > > > * Yanping Wang, Intel > > > > > > * Uma Maheswara Rao G, Intel > > > > > > * Kai Zheng, Intel > > > > > > * Rakesh Radhakrishnan Potty, Intel > > > > > > * Sean Zhong, Intel > > > > > > * Henry Saputra, Independent > > > > > > * Hao Cheng, Intel > > > > > > === Sponsors === > > > Champion > > > Patrick Hunt > > > > > > Nominated Mentors > > > * Patrick Hunt - Apache IPMC member > > > > > > * Andrew Purtell - Apache IPMC member > > > > > > * James Taylor - Apache IPMC member > > > > > > * Henry Saputra - Apache IPMC member > > > > > > Sponsoring Entity > > > Apache Incubator PMC > > > > > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept Guacamole into the Apache incubator
quality patches/support that move the project > forward, they will earn merit. The community will also be encouraged to > provide non-code contributions (documentation, events, community > management, etc.) and will gain merit for doing so. Those with a proven > support and quality track record will be encouraged to become committers. > > == Community == > > If Guacamole is accepted for incubation, its primary initial goal will be > to build a large community of users and developers. We trust that Guacamole > will become a key project for cloud platforms, and thus expect its > community to grow as word of the project continues to spread. > > == Known Risks == > > Development has been sponsored mostly by one company. For the project to > fully transition to the Apache Way governance model, development must shift > towards the meritocracy-centric model of growing a balanced community of > contributors. > > == Orphaned products == > > Glyptodon, Nanocloud Software, and other companies are fully committed to > Guacamole and have a vested interest in making Guacamole succeed by driving > its close integration with sister ASF projects. Commercial reliance on > Guacamole by third-party companies, as well as widespread public interest > in cloud-based access as a whole, reduces the risk of the product being > orphaned. > > == Inexperience with Open Source == > > Glyptodon has been developing and using open source software since its > inception in 2013. Additionally, several ASF veterans agreed to mentor the > project and are listed in this proposal. The Guacamole project will rely on > their guidance and collective wisdom to quickly transition the entire team > of initial committers towards practicing the Apache Way. > > == Reliance on Salaried Developers == > > Most of the contributors are paid to work in cloud space. While they might > wander from their current employers, they are unlikely to venture far from > their core expertises and thus will continue to be engaged with the project > regardless of their current employers. > > == An Excessive Fascination with the Apache Brand == > > Our primary interest in bringing Guacamole to Apache is to foster growth > within the project and its community of developers and users. We have no > plans to make use of the Apache brand in press releases, nor to advertise > acceptance of Guacamole into Apache Incubator. > > == Required Resources == > > === Mailing Lists === > > * priv...@guacamole.incubator.apache.org (moderated subscriptions) > * comm...@guacamole.incubator.apache.org > * d...@guacamole.incubator.apache.org > * iss...@guacamole.incubator.apache.org > > === Git Repository === > > * https://git-wip-us.apache.org/repos/asf/incubator-guacamole.git > > === Issue Tracking === > > * JIRA Project Guacamole (GUAC) > > === Other Resources === > > * Means of setting up regular builds for Guacamole on builds.apache.org > > == Initial Committers == > > * Mike Jumper > * James Muehlner > > == Additional Interested Contributors == > > * Jim Jagielski > * Greg Trasuk > > == Affiliations == > > * Glyptodon : Mike Jumper, James Muehlner > > == Champion == > > * Jean-Baptiste Onofré (jbono...@apache.org) - Apache Member > > == Mentors == > > * Jean-Baptiste Onofré (jbono...@apache.org) - Apache Member > * Daniel Gruno (humbed...@apache.org) - Apache Member > * Olivier Lamy (ol...@apache.org) - Apache Member > * Jim Jagielski (j...@apache.org) - Apache Member > * Greg Trasuk (gtra...@apache.org) - Apache Member > > == Sponsoring Entity == > > We would like to propose Apache incubator to sponsor this project. > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > - > 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 > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept Beam into the Apache Incubator
t; * Davor Bonaci[da...@google.com] > * Frances Perry [f...@google.com] > * James Malone[jamesmal...@google.com] > * Jean-Baptiste Onofré[jbono...@apache.org] > * Josh Wills [jwi...@apache.org] > * Kostas Tzoumas [kos...@data-artisans.com] > * Kenneth Knowles [k...@google.com] > * Luke Cwik [lc...@google.com] > * Maximilian Michels [m...@apache.org] > * Stephan Ewen[step...@data-artisans.com] > * Tom White [t...@cloudera.com] > * Tyler Akidau[taki...@google.com] > * Robert Bradshaw [rober...@google.com] > > == Additional Interested Contributors == > > * Debo Dutta [dedu...@cisco.com] > * Henry Saputra [hsapu...@apache.org] > * Taylor Goetz[ptgo...@gmail.com] > * James Carman[ja...@carmanconsulting.com] > * Joe Witt[joew...@apache.org] > * Vaibhav Gumashta[vgumas...@hortonworks.com] > * Prasanth Jayachandran [pjayachand...@hortonworks.com] > * Johan Edstrom [seij...@gmail.com] > * Hugo Louro [hmclo...@gmail.com] > * Krzysztof Sobkowiak [krzys.sobkow...@gmail.com] > * Jeff Genender [jgenen...@apache.org] > * Edward J. Yoon [edward.y...@samsung.com] > * Hao Chen[h...@apache.org] > * Byung-Gon Chun [bgc...@gmail.com] > * Charitha Elvitigala [charit...@apache.org] > * Alexander Bezzubov [b...@apache.org] > * Tsuyoshi Ozawa [oz...@apache.org] > * Mayank Bansal [maban...@gmail.com] > * Supun Kamburugamuve [su...@apache.org] > * Matthias Wessendorf [mat...@apache.org] > * Felix Cheung[felixche...@apache.org] > * Ajay Yadava [ajay.ya...@inmobi.com] > * Liang Chen [chenliang...@huawei.com] > * Renaud Richardet[renaud (at) apache (dot) org] > * Bakey Pan [bakey1...@gmail.com] > * Andreas Neumann [a...@apache.org] > * Suresh Marru[sma...@apache.org] > * Hadrian Zbarcea [hzbar...@gmail.com] > > == Affiliations == > > The initial committers are from six organizations. Google developed > Dataflow and the Dataflow SDK, data Artisans developed the Flink runner, > and Cloudera (Labs) developed the Spark runner. > > * Cloudera > * Tom White > * Data Artisans > * Aljoscha Krettek > * Kostas Tzoumas > * Maximilian Michels > * Stephan Ewen > * Google > * Ben Chambers > * Dan Halperin > * Davor Bonaci > * Frances Perry > * James Malone > * Kenneth Knowles > * Luke Cwik > * Tyler Akidau > * Robert Bradshaw > * PayPal > * Amit Sela > * Slack > * Josh Wills > * Talend > * Jean-Baptiste Onofré > > == Sponsors == > > === Champion === > > * Jean-Baptiste Onofre [jbono...@apache.org] > > === Nominated Mentors === > > * Jean-Baptiste Onofre [jbono...@apache.org] > * Jim Jagielski [j...@apache.org] > * Venkatesh Seetharam[venkat...@apache.org] > * Bertrand Delacretaz[bdelacre...@apache.org] > * Ted Dunning[tdunn...@apache.org] > > === Sponsoring Entity === > > The Apache Incubator > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [DISCUSS] Apache Guacamole Incubator Proposal
welcomed. By > participating in the community and providing quality patches/support > that move the project forward, they will earn merit. The community will > also be encouraged to provide non-code contributions (documentation, > events, community management, etc.) and will gain merit for doing so. > Those with a proven support and quality track record will be encouraged > to become committers. > > == Community == > > If Guacamole is accepted for incubation, its primary initial goal will > be to build a large community of users and developers. We trust that > Guacamole will become a key project for cloud platforms, and thus expect > its community to grow as word of the project continues to spread. > > == Known Risks == > > Development has been sponsored mostly by one company. For the project to > fully transition to the Apache Way governance model, development must > shift towards the meritocracy-centric model of growing a balanced > community of contributors. > > == Orphaned products == > > Glyptodon, Nanocloud Software, and other companies are fully committed > to Guacamole and have a vested interest in making Guacamole succeed by > driving its close integration with sister ASF projects. Commercial > reliance on Guacamole by third-party companies, as well as widespread > public interest in cloud-based access as a whole, reduces the risk of > the product being orphaned. > > == Inexperience with Open Source == > > Glyptodon has been developing and using open source software since its > inception in 2013. Additionally, several ASF veterans agreed to mentor > the project and are listed in this proposal. The Guacamole project will > rely on their guidance and collective wisdom to quickly transition the > entire team of initial committers towards practicing the Apache Way. > > == Reliance on Salaried Developers == > > Most of the contributors are paid to work in cloud space. While they > might wander from their current employers, they are unlikely to venture > far from their core expertises and thus will continue to be engaged with > the project regardless of their current employers. > > == An Excessive Fascination with the Apache Brand == > > Our primary interest in bringing Guacamole to Apache is to foster growth > within the project and its community of developers and users. We have no > plans to make use of the Apache brand in press releases, nor to > advertise acceptance of Guacamole into Apache Incubator. > > == Required Resources == > > === Mailing Lists === > > * priv...@guacamole.incubator.apache.org (moderated subscriptions) > * comm...@guacamole.incubator.apache.org > * d...@guacamole.incubator.apache.org > * iss...@guacamole.incubator.apache.org > > === Git Repository === > > * https://git-wip-us.apache.org/repos/asf/incubator-guacamole.git > > === Issue Tracking === > > * JIRA Project Guacamole (GUAC) > > === Other Resources === > > * Means of setting up regular builds for Guacamole on builds.apache.org > > == Initial Committers == > > * Mike Jumper > * James Muehlner > > == Additional Interested Contributors == > > == Affiliations == > > * Glyptodon : Mike Jumper, James Muehlner > > == Mentors == > > * Jean-Baptiste Onofré (jbono...@apache.org) - Apache Member > > == Sponsoring Entity == > > We would like to propose Apache incubator to sponsor this project. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > <general-h...@incubator.apache.org>
Re: [DISCUSS] Apache Guacamole Incubator Proposal
welcomed. By > participating in the community and providing quality patches/support > that move the project forward, they will earn merit. The community will > also be encouraged to provide non-code contributions (documentation, > events, community management, etc.) and will gain merit for doing so. > Those with a proven support and quality track record will be encouraged > to become committers. > > == Community == > > If Guacamole is accepted for incubation, its primary initial goal will > be to build a large community of users and developers. We trust that > Guacamole will become a key project for cloud platforms, and thus expect > its community to grow as word of the project continues to spread. > > == Known Risks == > > Development has been sponsored mostly by one company. For the project to > fully transition to the Apache Way governance model, development must > shift towards the meritocracy-centric model of growing a balanced > community of contributors. > > == Orphaned products == > > Glyptodon, Nanocloud Software, and other companies are fully committed > to Guacamole and have a vested interest in making Guacamole succeed by > driving its close integration with sister ASF projects. Commercial > reliance on Guacamole by third-party companies, as well as widespread > public interest in cloud-based access as a whole, reduces the risk of > the product being orphaned. > > == Inexperience with Open Source == > > Glyptodon has been developing and using open source software since its > inception in 2013. Additionally, several ASF veterans agreed to mentor > the project and are listed in this proposal. The Guacamole project will > rely on their guidance and collective wisdom to quickly transition the > entire team of initial committers towards practicing the Apache Way. > > == Reliance on Salaried Developers == > > Most of the contributors are paid to work in cloud space. While they > might wander from their current employers, they are unlikely to venture > far from their core expertises and thus will continue to be engaged with > the project regardless of their current employers. > > == An Excessive Fascination with the Apache Brand == > > Our primary interest in bringing Guacamole to Apache is to foster growth > within the project and its community of developers and users. We have no > plans to make use of the Apache brand in press releases, nor to > advertise acceptance of Guacamole into Apache Incubator. > > == Required Resources == > > === Mailing Lists === > > * priv...@guacamole.incubator.apache.org (moderated subscriptions) > * comm...@guacamole.incubator.apache.org > * d...@guacamole.incubator.apache.org > * iss...@guacamole.incubator.apache.org > > === Git Repository === > > * https://git-wip-us.apache.org/repos/asf/incubator-guacamole.git > > === Issue Tracking === > > * JIRA Project Guacamole (GUAC) > > === Other Resources === > > * Means of setting up regular builds for Guacamole on builds.apache.org > > == Initial Committers == > > * Mike Jumper > * James Muehlner > > == Additional Interested Contributors == > > == Affiliations == > > * Glyptodon : Mike Jumper, James Muehlner > > == Mentors == > > * Jean-Baptiste Onofré (jbono...@apache.org) - Apache Member > > == Sponsoring Entity == > > We would like to propose Apache incubator to sponsor this project. > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Graduate Apache Brooklyn from incubator
+1 (binding) I'd like to remain on PMC and try to help in the future. Olivier On 29 September 2015 at 00:06, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > This is the Incubator vote to decide if Apache Brooklyn should graduate > from the Incubator. Please see the proposed resolution below. > > See also discuss thread [1]. Mentors were invited to join the future TLP > PMC on request. Invitation is open until this vote is closed. > > This vote is open for at least 72 hours. > > [ ] +1 Graduate Apache Brooklyn from the Incubator. > [ ] +0 Don't care. > [ ] -1 Don't graduate Apache Brooklyn from the Incubator because ... > > Thanks, > Hadrian > > [1] > http://mail-archives.apache.org/mod_mbox/incubator-general/201509.mbox/%3C5604323C.1010207%40gmail.com%3E > > > > X. Establish the Apache Brooklyn 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 tools that help automate various > administrative tasks or information lookup activities. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Brooklyn Project", > be and hereby is established pursuant to Bylaws of the > Foundation; and be it further > > RESOLVED, that the Apache Brooklyn Project be and hereby is > responsible for the creation and maintenance of a software > framework for modeling, monitoring, and managing cloud > applications through autonomic blueprints; and be it further > > RESOLVED, that the office of "Vice President, Apache Brooklyn" > 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 Brooklyn Project, and to have primary > responsibility for management of the projects within the scope > of responsibility of the Apache Brooklyn 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 Brooklyn Project Management Committee: > > * Aled Sage <aleds...@apache.org> > * Alex Heneveld <henev...@apache.org> > * Andrea Turli <andreatu...@apache.org> > * Andrew Kennedy <grk...@apache.org> > * Ciprian Ciubotariu <c...@apache.org> > * Hadrian Zbarcea <hadr...@apache.org> > * Richard Downer <rich...@apache.org> > * Sam Corbett <sjcorb...@apache.org> > * Svetoslav Neykov <s...@apache.org> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Richard Downer be > appointed to the office of Vice President, Apache Brooklyn, 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 Brooklyn Project be and hereby > is tasked with the creation of a set of bylaws intended to > encourage open development and increased participation in the > Apache Brooklyn Project. > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Groovy 2.4.5-incubating
+1 (ipmc binding) On 20 September 2015 at 20:20, Cédric Champeau <cchamp...@apache.org> wrote: > Hi all! > > The Apache Groovy PPMC has successfully voted the release of Apache Groovy > 2.4.5-incubating [1], with 4 "+1" binding votes, one "+1" non binding and > no 0/-1 votes. We are now asking the IPMC to vote it too. > > This release was done in a particular context, at the SpringOne2GX > conference. Following a very successful BOF session, we followed up with a > release initiation party to share the knowledge about how to perform a > release! We anticipate this will make it easier for more of us to be > involved with releases in the future. It's worth noting that the release > was performed with the presence of Baruch Sadogursky from JFrog > (Artifactory/Bintray) that we use, and he could already suggest some nice > improvements in our release process that we're going to improve for the > upcoming releases. > > Vote on dev list: > > http://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201509.mbox/%3CCADQzvmkCoEUFXfmSR%2B71K%2BEmSYHAjkFWa1HH76LEcPDLMNSYZQ%40mail.gmail.com%3E > Result of vote on dev list: > > http://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201509.mbox/%3CCADQzvm%3DDzF-6T46crzuOBizG2wq0xPArfuz%3DQio_OwgQxEHEcw%40mail.gmail.com%3E > > This release fixes documentation issues, a potential memory leak when > loading the Groovy runtime from different classloaders, some JSON fixes and > improvements and numerous small bug fixes. > > The changelog for this release can be found here: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12332749 > > Tag: > > https://git1-us-west.apache.org/repos/asf?p=incubator-groovy.git;a=commit;h=13934972b400d40600c994377308b26978fcc325 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/incubator/groovy/ > > Release artifacts are signed with the following key: > https://dist.apache.org/repos/dist/dev/incubator/groovy/KEYS > Vote is open for at least 72 hours. Artifacts will be moved to dist as soon > as the vote passes. > > [ ] +1, release Apache Groovy 2.4.5-incubating > [ ] 0, I don't care > [ ] -1, because... > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Apache Johnzon 0.9-incubating release
+1 (binding) On 16 August 2015 at 21:59, John D. Ament johndam...@apache.org wrote: +1 (binding) On Thu, Aug 13, 2015 at 2:53 PM Hendrik Dev hendrikde...@gmail.com wrote: The Apache Johnzon PPMC has voted to release Apache Johnzon 0.9-incubating based on the second release candidate described below. Now it is the IPMC's turn to vote. Git commit for the release is https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=ab542d7208c2b60aa6fdab1b11fa01a1e9ad8241 Maven staging repo: https://repository.apache.org/content/repositories/orgapachejohnzon-1007 Source releases (zip/tar.gz): https://repository.apache.org/content/repositories/orgapachejohnzon-1007/org/apache/johnzon/apache-johnzon/0.9-incubating/apache-johnzon-0.9-incubating-src.zip SHA-1:51ab45e8fb5f315c482593923c9d85af6d1bc18b https://repository.apache.org/content/repositories/orgapachejohnzon-1007/org/apache/johnzon/apache-johnzon/0.9-incubating/apache-johnzon-0.9-incubating-src.tar.gz SHA-1:f80bfce2717d632e38eb12930e1f6a5f30f0180a https://repository.apache.org/content/repositories/orgapachejohnzon-1007/org/apache/johnzon/apache-johnzon/0.9-incubating/apache-johnzon-0.9-incubating-src.tar.gzSHA-1:f80bfce2717d632e38eb12930e1f6a5f30f0180a The files are also here https://dist.apache.org/repos/dist/dev/incubator/johnzon/ PGP release keys (signed using 90910A83): https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS This release is mainly a bugfixing release. The mapper also introduced basic map support for nested converter. Snapshot deps. removed. The vote will be open for at least 72 hours. Project vote passes with 3 binding +1 votes and no -1 votes: http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201508.mbox/%3C8173EB96-FC9B-433A-B659-06A5D83E4A14%40apache.org%3E The vote will be open for at least 72 hours. [ ] +1 approve [ ] -1 disapprove (and reason why) Thanks -- Hendrik Saly (salyh, hendrikdev22) @hendrikdev22 PGP: 0x22D7F6EC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Graduate Ignite from the Incubator
: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Release Apache Commons RDF 0.1.0-incubating RC2
+1 (binding) On 11 May 2015 at 03:45, Sergio Fernández wik...@apache.org wrote: Hello, I am pleased to be calling this vote for the source release of Apache Commons RDF 0.1.0-incubating, composed by: * commons-rdf-api 0.1.0-incubating * commons-rdf-simple 0.1.0-incubating A candidate for the Commons RDF 0.1.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/commonsrdf/0.1.0-incubating/ The release candidate is based on the sources from commit 454ebc1ff457bcdb34f4671565bc984e6fbbcb77, tagged as 0.1.0-incubating, at: https://git-wip-us.apache.org/repos/asf/incubator-commonsrdf.git Release artifacts are signed with the keys available at: https://dist.apache.org/repos/dist/release/incubator/commonsrdf/KEYS A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecommons-1095 The changelog for this version is available from JIRA: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316620version=12332056 The current release has got 3 +1 votes (2 of them binding IPMC), with no 0 or -1 votes; the voting thread can be found at: http://s.apache.org/G2S This would represent the first incubating release of the podling, so we kindly ask you the Incubator PMC to carefully look to the release. Please vote on releasing this package as Apache Commons RDF 0.1.0-incubating. The vote is open for at least 72 hours and passes if a majority of at least three +1 IPMC votes are cast. [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernan...@redlink.co w: http://redlink.co -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [VOTE] Accept Groovy into the Apache Incubator
go far from the Java family tree. === Relationships with Other Apache Products === Groovy currently has a few ASF projects as optional dependencies but otherwise doesn't depend on any ASF projects. A few ASF projects already depend on Groovy. === An Excessive Fascination with the Apache Brand === While we intend to leverage the Apache ‘branding’ when talking to other projects as testament of our project’s ‘neutrality’, we have no plans for making use of Apache brand in press releases nor posting billboards advertising acceptance of Groovy into Apache Incubator. == Documentation == See [[http://www.groovy-lang.org/documentation.html|documentation]] for the current state of the Groovy documentation. A mature project website is also available at [[http://www.groovy-lang.org/|groovy-lang.org]]. == Initial Source == Initial source is available on GitHub under the ALv2 [[https://github.com/groovy/groovy-core|groovy-core]] == Source and Intellectual Property Submission Plan == We know of no legal encumberments in the way of transfer of source to Apache. In fact, given the series of corporate due diligence procedures performed on the source code during two of the acquisitions we expect the code base to be squeaky clean from an IP perspective. == External Dependencies == Embedded dependencies (relocated): * Antlr 2, ANTLR 2 License (development branch includes Antlr4 using BSD license) * ASM, BSD * Openbeans (ALv2) * Apache Commons CLI (ALv2) Module or optional dependencies: * Apache Ant (ALv2) * Apache Commons BSF (ALv2) * Apache Commons Logging (ALv2) * Apache Ivy (ALv2) * Apache Log4j (ALv2) * Apache Log4j 2 (ALv2) * JAnsi (ALv2) * JCommander (ALv2) * JLine 2 (BSD) * JUnit (EPL 1.0) * Logback (EPL 1.0) * QDox (ALv2) * SLF4J (MIT) * TestNG (ALv2) Build only dependencies: * bnd (ALv2) * jarjar (ALv2) * Checkstyle (LGPL) * Cobertura (GPL) * Gradle (ALv2) * Asciidoctor (MIT) * Simian (http://www.harukizaemon.com/simian/get_it_now.html) Test only dependencies: * Apache Commons HTTP Client (ALv2) * Apache Lucene (ALv2) * Eclipse OSGi (EPL 1.0) * GPars (ALv2) * HSQLDB (BSD) * JMock (jMock Project License) * OpenEJB (ALv2) * Spock (ALv2) * XMLUnit 1 (BSD) * XStream (BSD) Cryptography N/A == Required Resources == === Mailing lists === * priv...@groovy.incubator.apache.org (moderated subscriptions) * comm...@groovy.incubator.apache.org * d...@groovy.incubator.apache.org * iss...@groovy.incubator.apache.org * u...@groovy.incubator.apache.org === Git Repository === https://git-wip-us.apache.org/repos/asf/incubator-groovy.git === Issue Tracking === JIRA Groovy (GROOVY) === Other Resources === A build server is currently sponsored by Jetbrains (TeamCity): http://ci.groovy-lang.org?guest=1 The CI server has a number of build plans including multiple JDKs (5 to 9), 3rd party joint builds and integration with the Groovy website (automatic deployment upon push). Means of setting up regular builds for Groovy on builds.apache.org == Initial Committers == * Cédric Champeau * Guillaume Laforge * Jochen Theodorou * Paul King * Pascal Schumacher == Affiliations == * Pivotal: Cédric Champeau, Jochen Theodorou * Restlet: Guillaume Laforge * ASERT: Paul King * Pascal Schumacher == Sponsors == === Champion === Roman Shaposhnik === Nominated Mentors === * Bertrand Delacretaz - Apache Member * Emmanuel Lecharny - Apache Member * Jim Jagielski - Apache Member * Roman Shaposhnik - Apache Member * Andrew Bayer - Apache Member * Konstantin Boudnik - IPMC Member Six mentors is plenty, we are not looking for more mentors at this time. === Sponsoring Entity === We would like to propose Apache incubator to sponsor this project. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Should Sirona be monthly?
I don't see any comments here: http://wiki.apache.org/incubator/February2015 So I wonder what sort of administrative stuff is missing?... Thanks Olivier On 22 February 2015 at 04:01, John D. Ament johndam...@apache.org wrote: All, In the last incubator report, Sirona was marked as having an incomplete report. I didn't see anything marked in the board report summary, so are we thinking the report should be expected again or accepted as is? Does the incubator have the concept of not accepting a podling's report? John -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Should Sirona be monthly?
On 23 February 2015 at 03:07, John D. Ament johndam...@apache.org wrote: On Sun Feb 22 2015 at 10:38:23 AM Marvin Humphrey mar...@rectangular.com wrote: On Sun, Feb 22, 2015 at 3:44 AM, Olivier Lamy ol...@apache.org wrote: I don't see any comments here: http://wiki.apache.org/ incubator/February2015 I'm the one who categorized Sirona under Report incomplete in the Summary of podling reports section: * Report incomplete Sirona I honestly thought Sirona's report was a work in progress when I did that because several sections had been left blank. So I wonder what sort of administrative stuff is missing?... It's not administrative stuff that's missing. The problem is that until Matt filed his Shepherd review, there was literally nothing in the report describing the state of the Sirona community. The following sections were left empty: * `Three most important issues to address in the move towards graduation:` * `How has the community developed since the last report?` * `When were the last committers or PMC members elected?` (The full report is pasted below my sig for reference.) The Board consistently follows up after TLPs who neglect to answer that last question. If the Incubator teaches that such reports are acceptable, I don't think it's doing a very good job because such reports are unlikely to be acceptable to the Board. That's actually why I raised my question. I had assumed the board would have flagged Sirona as not having a complete report and expected it again next month, yet I saw nothing mentioned in the board report (probably because there was a high volume of missing reports, this one skirted by?) about Sirona's not being accepted. However, when I flagged Sirona in the draft report review thread, nobody responded. In the absence of IPMC consensus that Sirona's report was unacceptable, I opted to defer to the Sirona Mentors who signed off and did not pursue the matter further. And that's where I think we leave things regarding the subject of this thread, Should Sirona be monthly?: Sirona should not be required to report next month, in deference to its Mentors. And that's where I'm struggling a bit with Sirona. Olivier's the active guy on the project, PPMC and Mentor. OpenHub and GitHub agree https://github.com/apache/sirona/graphs/contributors https://www.openhub.net/p/sirona/contributors You can even see in Olivier's email to the dev alias that he considered the report to be incomplete (only started). http://mail-archives.apache.org/mod_mbox/sirona-dev/201502.mbox/%3CCAPoyBqSRbOv6Y3pkQMqkCjzz3wOhqrV0yHrEyX4aNaP_FsvfEw%40mail.gmail.com%3E Thoughts? I missed to answer to my own email saying that's finished. Sorry I reckon I'm really bad on administrative papers things Olivier John Marvin Humphrey Sirona Monitoring Solution. Sirona has been incubating since 2013-10-15. Three most important issues to address in the move towards graduation: 1. 2. 3. 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? How has the project developed since the last report? Some refactoring of the UI. A contributor made some development to have some features still working with java 1.5 Date of last release: 2014-06-26 When were the last committers or PMC members elected? Signed-off-by: [x](sirona) Olivier Lamy [ ](sirona) Henri Gomez [x](sirona) Jean-Baptiste Onofre [ ](sirona) Tammo van Lessen [ ](sirona) Mark Struberg Shepherd/Mentor notes: Matthew B. Franklin (mfranklin): Lot's of code is being committed to the project, but mostly by a couple of developers. There also does not appear to be much discussion on the list in last period, likely due to the low number of developers. I recommend the podling focus on increasing the size and participation of the community as one of the issues to address prior to graduation. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
[ANN] Apache Sirona 0.2-incubating
The Apache Sirona Team is pleased to announce the first release 0.2-incubating of Apache Sirona project. Apache Sirona provide a simple but extensible monitoring solution for Java applications. It's an incubating project and a technology preview release. So some APIs can be change in the future. The full release notes is available here: http://sirona.incubator.apache.org/docs/0.2-incubating/jira-report.html You can download the releases sources/binaries: http://sirona.incubator.apache.org/download.cgi We hope you will enjoy using Apache Sirona! If you have any questions, please consult: * the web site: http://sirona.incubator.apache.org/ * the sirona mailing lists: http://sirona.incubator.apache.org/mail-lists.html Have Fun, -- The Apache Sirona Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
so it looks this project doesn't have any interest here A shame!! I can maybe propose to nominate some shepherd to watch IPMC members who doesn't help starting project to make a release :-) Yup not all project are part of the big data buzz and do not make enough lobbying Really funny when I read the other thread which use the word weight for project which cannot release. I reckon it's really hard sometimes to have fun here. Cheers Olivier On 3 June 2014 22:32, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Sirona 0.2-incubating We fixed 20 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325648styleName=TextprojectId=12314925Create=Create Staging Maven repository: https://repository.apache.org/content/repositories/orgapachesirona-1000/ Staging release: https://dist.apache.org/repos/dist/dev/incubator/sirona/0.2-incubating/ Documentation: http://sirona.incubator.apache.org/docs/0.2-incubating/ KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/sirona/KEYS Vote thread from dev@ project: http://mail-archives.apache.org/mod_mbox/incubator-sirona-dev/201405.mbox/browser Vote open for 72H +1 0 -1 Thanks! -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache MRQL 0.9.2 incubating (RC2)
+1 -- Olivier On Jun 20, 2014 4:55 PM, Leonidas Fegaras fega...@cse.uta.edu wrote: Hello, This is a call for a vote on Apache MRQL 0.9.2 incubating. Apache MRQL is a query processing and optimization system for large-scale, distributed data analysis, built on top of Apache Hadoop, Apache Hama, and Apache Spark. This is our second release. A vote was held on the MRQL developer mailing list and it passed with four +1 PPMC votes, no -1 votes, and no 0 votes (see the vote thread [1] and result thread [2]), and now requires a vote on this list. The vote will be open for at least 72 hours and passes if a majority of at least three +1 IPMC votes are cast. [ ] +1 Release this package as Apache MRQL 0.9.2-incubating [ ] -1 Do not release this package because ... The release tarballs, including signatures, digests, etc can be found at: https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.2- incubating-RC2/ The release candidate consists of the following source distribution archives: - mrql-dist-0.9.2-incubating-src.[tar.gz|zip] SHA1 of TGZ: 9209 735B CAE2 D431 71BE EB6F 985B 07F7 B0A3 E4A6 SHA1 of ZIP: 180F 0CE1 D09E 9B21 A08F 1BED 495E 8BB2 6486 CAF9 You can compile the sources using 'mvn clean install'. In addition, the following supplementary binary distributions are provided for user convenience at the same location: - mrql-dist-0.9.2-incubating-bin.[tar.gz|zip] SHA1 of TGZ: AC77 F97F 0C3C FACA C312 8C68 50B5 5474 DBFE 93C1 SHA1 of ZIP: F552 021C 2FF0 7343 5098 C16B 18B8 1AF8 9820 9675 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemrql-1001/ The release candidate has been signed through the key 798764F1 in: http://www.apache.org/dist/incubator/mrql/KEYS The release candidate is based on the sources tagged with MRQL-0.9.2-incubating-RC2 at: https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h= f80a1e6fcb1e2a31063e568508ada3d9ef3466e3 The list of fixed issues: https://git-wip-us.apache.org/repos/asf?p=incubator-mrql. git;a=blob_plain;f=RELEASE_NOTES;hb=f80a1e6fcb1e2a31063e568508ada3 d9ef3466e3 To learn more about Apache MRQL, please visit: http://wiki.apache.org/mrql/ Thanks, Leonidas Fegaras [1] http://markmail.org/message/eiqz44qovjy6f6sl [2] http://markmail.org/message/eo3d64jx24v6oir2 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
On 25 June 2014 17:25, Justin Mclean jus...@classsoftware.com wrote: Hi, Sorry I been a bit busy with travel and other releases over the last few weeks. -1 binding due to vote issues, NOTICE and binaries in source release. vote details below binaries in source release?? (you mean from https://dist.apache.org/repos/dist/dev/incubator/sirona/0.2-incubating/src/sirona-0.2-incubating-src.zip ) what are the binaries??? I checked: - missing VOTE RESULT and can't tell if there are 3 +1 binding votes or not. There are 4 +1 votes on of which one is not binding but unsure re the others. Only one of the +1 votes is listed as a PMC member here [1] and the project is not listed here [2]. There are currently 2 IPMC votes from: jbonofre and olamy http://people.apache.org/committer-index.html#jbonofre http://people.apache.org/committer-index.html#olamy - artefact name includes incubating - signatures and md5 hash all good - DISCLAIMER present - LICENSE correct - NOTICE file includes too many things (see below) - binary files in source release (see bleow) - can compile from source - test failed (JavaAgent) - up to you if you think this is an issue or not In the NOTICE file you have: SB Admin Theme (Apache) Twitter bootstrap (MIT) Bootstrap datetimepicker (Apache) Table sorter (MIT) JQuery (MIT) JQuery Flot (MIT) As per [3] there is not need to modify the NOTICE file when bundling permissive licenses. Why is it blocker?? Binary file in source release. - Font files in resources/fonts. It is unclear how there are these licensed and where are they from. Some minor thing you may want to fix in future releases. - Add a KEY file to the incubating release ares Already here: https://dist.apache.org/repos/dist/release/incubator/sirona/ - add apache to the release artefact name - not sure that DEPENDANCIES is needed - probably no need for LICENSE and LICENSE.txt - Is year 2008-2013 correct in NOTICE file? - No README (how to compile) or RELEASE_NOTES (changes form last version) - init-git-svn.sh and siteDeploy.sh scripts are missing license header - sb-admin.css missing license header The test failed with this error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.1:shade (default) on project sirona-javaagent: Error creating shaded jar: /Users/justinmclean/Documents/Sirona0.2/apache-sirona-0.2-incubating/agent/performance/aop/target/classes (Is a directory) - [Help 1] maybe you are using maven 2.x Thanks, Justin 1. http://sirona.incubator.apache.org/team-list.html 2. http://people.apache.org/committers-by-project.html 3. http://www.apache.org/dev/licensing-howto.html#permissive-deps - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
On 26 June 2014 05:29, Mark Struberg strub...@yahoo.de wrote: wow, txs for that review. I personally think sirona can be something which is really interesting. But the code is pretty hardcore and thus we do hard in reaching 'starters'. Not sure how to improve this... Even if I really agree :-), honestly that's definitely to discuss before a release vote on the dev list. Yes I know it's a sort of grumbling email but It's already hard to release something here especially when you are volunteer and doing the coding part on your spare time and without the support of all paid folks who join IPMC just to have a binding vote on some projects!! So please start such discussion before on the dev list. LieGrue, strub On Wednesday, 25 June 2014, 9:25, Justin Mclean jus...@classsoftware.com wrote: Hi, Sorry I been a bit busy with travel and other releases over the last few weeks. -1 binding due to vote issues, NOTICE and binaries in source release. I checked: - missing VOTE RESULT and can't tell if there are 3 +1 binding votes or not. There are 4 +1 votes on of which one is not binding but unsure re the others. Only one of the +1 votes is listed as a PMC member here [1] and the project is not listed here [2]. - artefact name includes incubating - signatures and md5 hash all good - DISCLAIMER present - LICENSE correct - NOTICE file includes too many things (see below) - binary files in source release (see bleow) - can compile from source - test failed (JavaAgent) - up to you if you think this is an issue or not In the NOTICE file you have: SB Admin Theme (Apache) Twitter bootstrap (MIT) Bootstrap datetimepicker (Apache) Table sorter (MIT) JQuery (MIT) JQuery Flot (MIT) As per [3] there is not need to modify the NOTICE file when bundling permissive licenses. Binary file in source release. - Font files in resources/fonts. It is unclear how there are these licensed and where are they from. Some minor thing you may want to fix in future releases. - Add a KEY file to the incubating release ares - add apache to the release artefact name - not sure that DEPENDANCIES is needed - probably no need for LICENSE and LICENSE.txt - Is year 2008-2013 correct in NOTICE file? - No README (how to compile) or RELEASE_NOTES (changes form last version) - init-git-svn.sh and siteDeploy.sh scripts are missing license header - sb-admin.css missing license header The test failed with this error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.1:shade (default) on project sirona-javaagent: Error creating shaded jar: /Users/justinmclean/Documents/Sirona0.2/apache-sirona-0.2-incubating/agent/performance/aop/target/classes (Is a directory) - [Help 1] Thanks, Justin 1. http://sirona.incubator.apache.org/team-list.html 2. http://people.apache.org/committers-by-project.html 3. http://www.apache.org/dev/licensing-howto.html#permissive-deps - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
On 25 June 2014 17:25, Justin Mclean jus...@classsoftware.com wrote: Hi, Sorry I been a bit busy with travel and other releases over the last few weeks. -1 binding due to vote issues, NOTICE and binaries in source release. I checked: - missing VOTE RESULT and can't tell if there are 3 +1 binding votes or not. There are 4 +1 votes on of which one is not binding but unsure re the others. Only one of the +1 votes is listed as a PMC member here [1] and the project is not listed here [2]. And honestly I have no idea how to get the project listed here http://people.apache.org/committers-by-project.html - artefact name includes incubating - signatures and md5 hash all good - DISCLAIMER present - LICENSE correct - NOTICE file includes too many things (see below) - binary files in source release (see bleow) - can compile from source - test failed (JavaAgent) - up to you if you think this is an issue or not In the NOTICE file you have: SB Admin Theme (Apache) Twitter bootstrap (MIT) Bootstrap datetimepicker (Apache) Table sorter (MIT) JQuery (MIT) JQuery Flot (MIT) As per [3] there is not need to modify the NOTICE file when bundling permissive licenses. Binary file in source release. - Font files in resources/fonts. It is unclear how there are these licensed and where are they from. Some minor thing you may want to fix in future releases. - Add a KEY file to the incubating release ares - add apache to the release artefact name - not sure that DEPENDANCIES is needed - probably no need for LICENSE and LICENSE.txt - Is year 2008-2013 correct in NOTICE file? - No README (how to compile) or RELEASE_NOTES (changes form last version) - init-git-svn.sh and siteDeploy.sh scripts are missing license header - sb-admin.css missing license header The test failed with this error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.1:shade (default) on project sirona-javaagent: Error creating shaded jar: /Users/justinmclean/Documents/Sirona0.2/apache-sirona-0.2-incubating/agent/performance/aop/target/classes (Is a directory) - [Help 1] Thanks, Justin 1. http://sirona.incubator.apache.org/team-list.html 2. http://people.apache.org/committers-by-project.html 3. http://www.apache.org/dev/licensing-howto.html#permissive-deps - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
On 26 June 2014 11:01, Justin Mclean jus...@classsoftware.com wrote: Hi, what are the binaries??? The font files in resources/fonts. Any idea where they come from or how they are licensed? If they are ALv2 or similar then there is no issue. coming from boostrap which is MIT There are currently 2 IPMC votes from: jbonofre and olamy http://people.apache.org/committer-index.html#jbonofre http://people.apache.org/committer-index.html#olamy Thanks. A tally of VOTES and/or votes noted as binding would of made this clearer. As per [3] there is not need to modify the NOTICE file when bundling permissive licenses. Why is it blocker?? It important to get the NOTICE right, but if you raise a JIRA and fix it in the next release that good enough for me. Already here: https://dist.apache.org/repos/dist/release/incubator/sirona/ But not here: https://dist.apache.org/repos/dist/dev/incubator/sirona/ My key is already available in plenty of places here. https://dist.apache.org/repos/dist/release/archiva/KEYS https://dist.apache.org/repos/dist/release/tomcat/maven-plugin/KEYS.txt https://dist.apache.org/repos/dist/release/maven/KEYS https://dist.apache.org/repos/dist/release/directmemory/KEYS etc... I don't get the point to duplicate my key again here :-) Just a suggestion for make voting easier btw - non required. maybe you are using maven 2.x I'm using 3.2.1 and Java 1.7.0_10. so are you using: mvn clean install (or something else?) Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
On 26 June 2014 11:05, Justin Mclean jus...@classsoftware.com wrote: Hi, Yes I know it's a sort of grumbling email but It's already hard to release something here especially when you are volunteer and doing the coding part on your spare time and without the support of all paid folks who join IPMC just to have a binding vote on some projects!! So please start such discussion before on the dev list. Not that it really matters but I'm am also a volunteer and not one of those paid folk. :-) My response was for Mark :-) Justin -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Sirona 0.2-incubating
On 26 June 2014 12:37, Justin Mclean jus...@classsoftware.com wrote: Hi, The font files in resources/fonts. Any idea where they come from or how they are licensed? If they are ALv2 or similar then there is no issue. coming from boostrap which is MIT Looking at the font metadata I don't see a MIT license only a URL [1] and a copyright - Copyright © 2013 by Jan Kovarik. All rights reserved. Checking the URL it look like the halflings regular font isn't normally free or redistributable. However it is packaged with bootstrap. [2] Note that you it does ask for a link back to the glyphicons URL. It doesn't say anything about redistribution rights which may or may not be an issue - probably not. Anyone with actually legal knowledge have an opinion? See http://glyphicons.com/license/ which says Creative Commons Attribution 3.0 Unported (CC BY 3.0) I hope we can use that. If not so many projects here @apache have illegal distributions :-) I don't get the point to duplicate my key again here :-) Just to make it easier for peopel with limited time to test - but as I said it is not required. so are you using: mvn clean install (or something else?) mvn clean compile actually and today it seems to be working. mvn clean install hangs on a test for me. It might be good to add this info to the README. Not a blocker to release but other users may run into similar issues. make sense, I will As you asked for changelog, that's here: http://sirona.incubator.apache.org/docs/0.2-incubating/jira-report.html Thanks, Justin 1. http://www.glyphicons.com 2. http://getbootstrap.com/components/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Sirona 0.2-incubating
On 26 June 2014 11:31, Marvin Humphrey mar...@rectangular.com wrote: On Wed, Jun 25, 2014 at 5:39 PM, Olivier Lamy ol...@apache.org wrote: Yes I know it's a sort of grumbling email but It's already hard to release something here especially when you are volunteer and doing the coding part on your spare time and without the support of all paid folks who join IPMC just to have a binding vote on some projects!! So please start such discussion before on the dev list. The scarcity of IPMC release votes is an inherent, structural problem of the Incubator, arising because podling contributors are generally more invested in their projects than IPMC members. Sending grumbling email is at best a temporary fix. Thanks. It looks to work :-) ( hopefully I come from a grumbling country so I'm used to that :P ) Fortunately, as of last December we finally have a structural fix: the 2013 Alternate Release Voting Process. http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Podlings who would like to avoid blocking on IPMC members to cast binding votes should consider this option. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Apache Sirona 0.2-incubating
Hi, So the vote has passed. +1 (binding IPMC): Jean-Baptiste Onofre, Justin Mclean, Olivier Lamy +1 (non binding): Romain Manni-Bucau, Jean-Louis Monteiro, Ashish I will finish the release process. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire the S4 podling
+1 On 14 June 2014 04:36, Joe Brockmeier j...@zonker.net wrote: Hi all, Per recent discussions on general@[1] and s4-dev@ [2], I went ahead and called for a VOTE on the S4 dev@ mailing list [3] about retiring the podling. That VOTE has passed with no -1s and 4 (binding) +1s from the podling PMC/committers. (S4 only has committers, and doesn't distinguish between PPMC/committer.) We didn't get a weigh-in from all mentors/PPMC on the retirement VOTE, so I'm going ahead and asking for a vote here. This VOTE will be open for at least 72 hours. Please indicate (binding) or (non-binding) when casting your VOTE. +1 [ ] Yes, I am in favor of retiring S4 from the Apache Incubator. +0 [ ] -1 [ ] No, I am not in favor of retiring S4 because... Note that we have one IPMC vote from Patrick already. [1] http://s.apache.org/7Gz [2] http://s.apache.org/ig [3] http://s.apache.org/OAU -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Sirona 0.2-incubating
Hi, I'd like to release Apache Sirona 0.2-incubating We fixed 20 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325648styleName=TextprojectId=12314925Create=Create Staging Maven repository: https://repository.apache.org/content/repositories/orgapachesirona-1000/ Staging release: https://dist.apache.org/repos/dist/dev/incubator/sirona/0.2-incubating/ Documentation: http://sirona.incubator.apache.org/docs/0.2-incubating/ KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/sirona/KEYS Vote thread from dev@ project: http://mail-archives.apache.org/mod_mbox/incubator-sirona-dev/201405.mbox/browser Vote open for 72H +1 0 -1 Thanks! -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Parquet into the incubator
Mattmann * Jake Farrell * Roman Shaposhnik === Sponsoring Entity === The Apache Incubator -- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719 -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Brooklyn into the Incubator
+1 On 28 April 2014 23:49, Chip Childers chipchild...@apache.org wrote: Based on the previous discussion of accepting Brooklyn into the Apache Incubator as a podling, I'd like to call a vote for this now. [ ] +1 Accept Brooklyn into the Incubator [ ] +/-0 Indifferent to the acceptance of Brooklyn [ ] -1 Do not accept Brooklyn because... The proposal can be found here: https://wiki.apache.org/incubator/BrooklynProposal (For the IPMC members, I believe we typically lock the proposal page making it read-only during the voting. I'm not sure how to do this, or if I'm remembering correctly. Can someone clarify? I'll watch that page to be sure there are no changes during the voting process.) -chip - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Brooklyn
, such as its domain name, Twitter account, and IRC channel. During incubation the PPMC will identify all these assets, and arrange the transfer, replacement, or deprecation of these assets as appropriate. == External Dependencies == The vast majority of Brooklyn's direct and indirect dependencies are licensed (or dual-licensed) under The Apache License, Category A or B licenses, or are dedicated to the public domain. A small number dependencies give cause for concern; there are two cases of LGPL dependencies, and a number of dependencies where the license is either unknown, or compatibility with Apache is unknown. The PPMC must therefore: * determine the license for all code where it is not currently known; * determine ASL compatibility where this is not currently known; * replace all dependencies that do not have an ASL compatible license. == Cryptography == Brooklyn does not directly implement cryptography code. It may rely on other projects to perform certain cryptographic tasks (e.g. calculating signatures for requests to cloud providers.) == Required Resources == === Mailing lists === We seek dev and user lists to replace the lists currently in use. In alignment with Apache's standard practices, we would also have a private list for the PMC members, and a commits list. === Source Control === We would require a Git repository named brooklyn to hold the Brooklyn source code, and brooklyn-site to hold the web site source code. We would like these to be mirrored to GitHub repositories, where we intend to follow the same model currently used by Apache jclouds. === Issue Tracking === Jira, with a project name of BROOKLYN. === Other Resources === No other resources are required at this time. == Initial Committers == * Alex Heneveld * Aled Sage * Andrew Kennedy grk...@apache.org * Richard Downer == Affiliations == The majority of the commits to the project so far have been made by people who were employees of Cloudsoft Corporation Ltd at the time of the contribution, and the vast majority of those commits were in the line of their employment. All named initial committers are employees of Cloudsoft. As stated in the Known Risks section, we appreciate that this cannot continue long term, and a key goal of the podling will be to encourage people not affiliated with Cloudsoft to join the project as committers and PMC members. == Sponsors == Champion * Chip Childers chipchild...@apache.org Nominated Mentors * Matt Hogstrom hogst...@apache.org * Alex Karasulu akaras...@apache.org We appreciate that 3-5 Mentors greatly assists the incubation process, so welcome more Mentors. Sponsoring Entity We are asking that the Incubator sponsors the Brooklyn podling. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Jenkins Access for Storm
done Have fun!! On 20 December 2013 01:23, P. Taylor Goetz ptgo...@gmail.com wrote: I'd like to set up a Jenkins build for Storm. If someone could add me (username: ptgoetz) to the hudson-jobadmin group I would greatly appreciate it. Thanks in advance, Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Apache Sirona 0.1-incubating
FYI we got the last missing IPMC binding vote. http://mail-archives.apache.org/mod_mbox/incubator-sirona-dev/201312.mbox/%3CCAN%3DtixmOspWgDXwVTfRiKvMK3kwBwRpiVrmzJ5xwKGiWDk3xfg%40mail.gmail.com%3E So the vote now passed the requirement of 3 IPMC binding vote SO the vote has passed. On 2 December 2013 11:37, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Sirona 0.1-incubating. Release notes: http://sirona.incubator.apache.org/releases/release-notes-0.1-incubating.html Vote result from dev@sirona: http://mail-archives.apache.org/mod_mbox/incubator-sirona-dev/201312.mbox/browser Maven staged release repository: https://repository.apache.org/content/repositories/orgapachesirona-003/ Distribution: * binaries: https://dist.apache.org/repos/dist/dev/incubator/sirona/0.1-incubating/binaries/ * sources: https://dist.apache.org/repos/dist/dev/incubator/sirona/0.1-incubating/src/ KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/sirona/KEYS Vote open for 72H [+1] [0] [-1] Thanks -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANN] Apache Sirona 0.1-incubating
The Apache Sirona Team is pleased to announce the first release 0.1-incubating of Apache Sirona project. Apache Sirona provide a simple but extensible monitoring solution for Java applications. It's an incubating project and a technology preview release. So some APIs can be change in the future. The full release notes is available here: http://sirona.incubator.apache.org/releases/release-notes-0.1-incubating.html You can download the releases sources/binaries: http://sirona.incubator.apache.org/download.cgi We hope you will enjoy using Apache Sirona! If you have any questions, please consult: * the web site: http://sirona.incubator.apache.org/ * the sirona mailing lists: http://sirona.incubator.apache.org/mail-lists.html Have Fun, -- The Apache Sirona Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Verification Checklist
On 9 December 2013 22:04, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Mon, Dec 9, 2013 at 11:34 AM, ant elder ant.el...@gmail.com wrote: ...2) Podlings should normally graduate after the first release (and we should more proactively do that) not stay to do more... I wouldn't set this as a goal. It's nice when it happens, but as you say the goal is for a podling to be generally healthy and to have understood the Apache invariants before graduating. It's not the number of releases. ...If we could find a way to have Incubator PMC members accept a lower bar for doing podling releases it would make a massive improvement to everyones experience of the Incubator Define lower bar. Do you see any of the review items http://incubator.apache.org/guides/release_manifest.txt as optional? Good sounds so light compared to http://incubator.apache.org/guides/releasemanagement.html Definitely great to have a small, simple and human readable document! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Phoenix for incubator project
type system that has been introduced in the current major release of HBase. By all these products adopting this new serialization format, interoperability between them will take a big step forward. In addition, we plan to explore providing lower level APIs for other products such as Apache Drill to plug into when querying HBase data so that they get the performance benefits of using Phoenix. A Excessive Fascination with the Apache Brand Phoenix is already a healthy and relatively well known open source project. This proposal is not for the purpose of generating publicity. Rather, the primary benefits to joining Apache are those outlined in the Rationale section. Documentation Additional documentation on Phoenix may be found on its github website: Phoenix overview: https://github.com/forcedotcom/phoenix/blob/master/README.md Phoenix wiki: https://github.com/forcedotcom/phoenix/wiki Phoenix road map: https://github.com/forcedotcom/phoenix/wiki#roadmap Phoenix issue tracking: https://github.com/forcedotcom/phoenix/issues?direction=descsort=updatedstate=open Phoenix codebase: https://github.com/forcedotcom/phoenix Phoenix SQL language reference: http://forcedotcom.github.io/phoenix/ Phoenix performance: https://github.com/forcedotcom/phoenix/wiki/Performance#phoenix-vs-related-products User group: https://groups.google.com/group/phoenix-hbase-user Initial Source The Phoenix codebase is currently hosted on Github: https://github.com/forcedotcom/phoenix. Source and Intellectual Property Submission Plan Currently, the Phoenix codebase is distributed under a BSD license. Upon entering Apache, the Phoenix license will be migrated to the Apache 2.0 License. External Dependencies Beyond relying on Apache HBase, Phoenix has the following external dependencies: ANTLR 3.5 (BSD license: http://www.antlr3.org/license.html) Sqlline 1.1.2 (BSD license: https://github.com/julianhyde/sqlline/blob/master/LICENSE) Open CSV 2.3 (Apache 2.0 license) Upon acceptance to the incubator, we would begin a thorough analysis of all transitive dependencies to verify this information and introduce license checking into the build and release process by integrating with Apache Rat. Required Resources Mailing list We will migrate the existing Phoenix mailing lists as follows: phoenix-hbase-u...@googlegroups.com -- us...@phoenix.incubator.apache.org phoenix-hbase-...@googlegroups.com -- d...@phoenix.incubator.apache.org priv...@phoenix.incubator.apache.org for IPMC members comm...@phoenix.incubator.apache.org The latter is to be consistent with the new PIAO naming scheme for podlings. Source control The Phoenix team would like to use Git for source control, due to our current use of Git. We request a writeable Git repo for Phoenix, and mirroring to be set up to Github through INFRA. Issue Tracking Phoenix currently uses the github issue tracking system associated with its github repo: https://github.com/forcedotcom/phoenix/issues?direction=descsort=updatedstate=open . We will migrate to the Apache JIRA: http://issues.apache.org/jira/browse/PHOENIX Other Resources Jenkins/Hudson for builds and test running. Wiki for documentation purposes Blog to improve project dissemination Initial Committers James Taylor jtaylor at salesforce dot com Mujtaba Chohan mchohan at salesforce dot com Jesse Yates jyates at apache dot org Eli Levine elevine at salesforce dot com Simon Toens stoens at salesforce dot com Maryann Xue wei.xue at intel dot com Anoop Sam John anoopsamjohn at apache dot org Ramkrishna S Vasudevan ramkrishna at apache dot org Jeffrey Zhong jeffreyz at apache dot org Nick Dimiduk ndimiduk at apache dot org Affiliations The initial committers are from three organizations: Salesforce.com, Intel, and Hortonworks. James Taylor (Salesforce.com) Mujtaba Chohan (Salesforce.com) Jesse Yates (Salesforce.com) Eli Levine (Salesforce.com) Simon Toens (Salesforce.com) Maryann Xue (Intel) Anoop Sam John (Intel) Ramkrishna S Vasudevan (Intel) Jeffrey Zhong (Hortonworks) Nick Dimiduk (Hortonworks) Sponsors Champion Michael Stack Nominated Mentors Michael Stack Lars Hofhansl Andrew Purtell Devaraj Das Enis Soztutar Steven Noels Sponsoring Entity The Apache Incubator -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Verification Checklist
On 6 December 2013 20:55, ant elder ant.el...@gmail.com wrote: On Fri, Dec 6, 2013 at 1:40 AM, Marvin Humphrey mar...@rectangular.comwrote: On Thu, Dec 5, 2013 at 8:38 AM, sebb seb...@gmail.com wrote: On 5 December 2013 10:37, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Dec 3, 2013 at 11:39 PM, Marvin Humphrey mar...@rectangular.com wrote: ... Second, I'm amused that the commits list item was quietly dropped, but new checklist items have been inserted regarding the dev and private lists... Pure oversight on my part, sorry...but what would we do if no reviewer follows the commit lists? I don't think that's a reason to kill a release. Oversight of the commit list is vital; that is how we ensure that SCM only contains material that is permitted. The source release is then checked against SCM to ensure we are only published vetted material. If there is no review of the commit list, then the whole system breaks down. I certainly agree that following the commits list is essential (and sought to emphasize as much in the post at the top of the thread). I'd barely even considered the possibility that *none* of the reviewers might be following the commits list. However, I think that Bertrand's provenance checklist item largely achieves what I'd been grasping for with the commits list item, and fits much better into the context of approving the release. If nobody's following the commits list, that's an issue with serious implications for the project, but it's not a direct release blocker. If provenance is unsettled, though, that clearly blocks the release. Personally, I wouldn't feel confident checking the provenance item if I wasn't watching the commits list. It's true that the person making the commit affirms that they have the right to their contribution, but still, I feel like you need to at least be aware of what contributions have gone into the product. Maybe there ought to be a note to such effect on the explanations page. But in any case, I'm OK with the commits list item disappearing, so long as the provenance item stays. As of revision 14 (removing the dev list and private list items) I'm now generally satisfied with the content of the checklist items and hope to move on to refining the workflow and surrounding documentation. All the stuff required to be checked when voting on a release should be documented in the ASF doc about releases. That its not in that doc suggests its not required. If someone thinks something is required then they should go get consensus around that with the wider ASF and get the ASF doc updated. Podling releases are not quite the same as TLP releases, thats why they have the DISCLAIMER and incubating naming. I think we should be making it easier for podlings to do releases, if its really necessary then make an audit of the last release a requirement of graduation. ...ant +1 I don't see why releasing in incubator must be more complicated than in TLPs and have more rules. We have a lot of pending votes and I see you guys discussing about rules why not spend your times on having a look at those votes... And with such discussion we don't look very attractive. Isn't the goal of the ASF to have a lot of project developed here? Sorry personally I don't have time to read/participate the whole thread as I prefer to spend my time on writing softwares. But my participation could be: is it possible to add something in the verification checklist as Build great/usable software for our lovely users Cheers -- /me tired reading all of this over complicated administrative threads... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Sirona 0.1-incubating
So please instead of discussing again about procedures. Just discuss about the release :-) /me trying to rock the boat On 7 December 2013 12:05, Marvin Humphrey mar...@rectangular.com wrote: On Fri, Dec 6, 2013 at 3:23 PM, John D. Ament john.d.am...@gmail.com wrote: I just wanted to clarify with you. What you're saying is that a podling must have three PPMC votes. Once that is done, they must then send the release to the incubator to vote. Once 3 IPMC's approve it, it's ready to go, right? Here's the official answer, from the Incubator's policy page: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Our release management guide, as is often the case, duplicates information better described elsewhere, adding inaccuracies and misleading rephrasings. http://incubator.apache.org/guides/releasemanagement.html#glossary-release-manager Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Apache Helix as TLP Resolution
So no comments (neither complains :-) ). I believe I can the resolution for next board meeting. On 27 November 2013 09:22, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Nov 26, 2013 at 1:48 PM, Olivier Lamy ol...@apache.org wrote: So we now have +1 (IPMC binding): Patrick Hunt, Olivier Lamy, Suresh Marru That's 3 +1 but I have no idea if we reach the quorum for graduation vote. Let me know. There's no official quorum for IPMC graduation votes as far as I know. Personally, I'm satisfied that two out of the four Helix Mentors have voted in favor of graduation. You know much more about what is going on with the podling than the rest of the IPMC. In any case, an Incubator PMC VOTE on graduation only serves as a recommendation to the Board; it is the Board voting to approve a resolution which actually establishes the project. They can theoretically disregard the IPMC's recommendation; it is hard to imagine circumstances where the Board would oppose the spirit of the recommendation, but they occasionally tinker with the resolution text (which we frequently mess up). Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Sirona 0.1-incubating
Hi, I'd like to release Apache Sirona 0.1-incubating. Release notes: http://sirona.incubator.apache.org/releases/release-notes-0.1-incubating.html Vote result from dev@sirona: http://mail-archives.apache.org/mod_mbox/incubator-sirona-dev/201312.mbox/browser Maven staged release repository: https://repository.apache.org/content/repositories/orgapachesirona-003/ Distribution: * binaries: https://dist.apache.org/repos/dist/dev/incubator/sirona/0.1-incubating/binaries/ * sources: https://dist.apache.org/repos/dist/dev/incubator/sirona/0.1-incubating/src/ KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/sirona/KEYS Vote open for 72H [+1] [0] [-1] Thanks -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Tez-0.2.0-incubating RC0
+1 On 26 November 2013 11:33, Hitesh Shah hit...@apache.org wrote: Hello folks, I have created a tez-0.2.0-incubating release candidate (rc0). This is the first release for Tez. Therefore, please do not be gentle. GIT source tag: https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.2.0-rc0 Staging site: http://people.apache.org/~hitesh/tez-release-rc/tez-0.2.0-incubating-rc0/ Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetez-002/ PGP release keys: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xA9510905F0B000F0 KEYS file also available at https://dist.apache.org/repos/dist/release/incubator/tez/KEYS One can look into the issues fixed in this release at: https://issues.apache.org/jira/browse/TEZ/fixforversion/12324349 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) thanks -- Hitesh - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Helix as TLP Resolution
So we now have +1 (IPMC binding): Patrick Hunt, Olivier Lamy, Suresh Marru That's 3 +1 but I have no idea if we reach the quorum for graduation vote. Let me know. On 26 November 2013 11:24, Suresh Marru sma...@apache.org wrote: + 1 (binding). Good to see Helix hatch out of incubation. Suresh On Nov 20, 2013, at 8:07 PM, Olivier Lamy ol...@apache.org wrote: Hi, Here the vote for Apache Helix as TLP graduation. The vote result for dev@helix.i.a.o is available here: http://markmail.org/message/22orwjy2v3d4af67 Vote open for 72H [+1] [0] [-1] X. Resolution to establish the Apache Helix 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 related to cluster management system for managing partitioned and replicated resources in distributed data systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Helix Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Helix Project be and hereby is responsible for the creation and maintenance of a software project related to cluster management system for managing partitioned and replicated resources in distributed data systems; and be it further RESOLVED, that the office of Vice President, Helix 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 Helix Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Helix 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 Helix Project: * Olivier Lamy olamy * Patrick Hunt phunt * Mahadev Konar mahadev * Owen O'Malley omalley * Kishore Gopalakrishna kishoreg * Zhen Zhang zzhang * Shi Lu slu * Kapil Surlaker ksurlaker * Bob Schulman rms * Swaroop Jagadish swaroop-aj * Rahul Aggarwal rahula * Terence Yim chtyim * Santiago Perez santip * Vinayak Borkar vinayakb * Shirshanka Das sdas * Kanak Biscuitwala kanak NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be and hereby is appointed to the office of Vice President, Helix, 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 Helix Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Helix podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Helix podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - 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 -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Helix as TLP Resolution
ping. How many votes does it need? On 21 November 2013 12:07, Olivier Lamy ol...@apache.org wrote: Hi, Here the vote for Apache Helix as TLP graduation. The vote result for dev@helix.i.a.o is available here: http://markmail.org/message/22orwjy2v3d4af67 Vote open for 72H [+1] [0] [-1] X. Resolution to establish the Apache Helix 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 related to cluster management system for managing partitioned and replicated resources in distributed data systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Helix Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Helix Project be and hereby is responsible for the creation and maintenance of a software project related to cluster management system for managing partitioned and replicated resources in distributed data systems; and be it further RESOLVED, that the office of Vice President, Helix 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 Helix Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Helix 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 Helix Project: * Olivier Lamy olamy * Patrick Hunt phunt * Mahadev Konar mahadev * Owen O'Malley omalley * Kishore Gopalakrishna kishoreg * Zhen Zhang zzhang * Shi Lu slu * Kapil Surlaker ksurlaker * Bob Schulman rms * Swaroop Jagadish swaroop-aj * Rahul Aggarwal rahula * Terence Yim chtyim * Santiago Perez santip * Vinayak Borkar vinayakb * Shirshanka Das sdas * Kanak Biscuitwala kanak NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be and hereby is appointed to the office of Vice President, Helix, 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 Helix Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Helix podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Helix podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] helix-0.7.0-incubating
mb-olamy:tmp olamy$ wget http://mirror.ventraip.net.au/apache/incubator/helix/0.7.0-incubating/src/helix-0.7.0-incubating-src.zip --2013-11-25 09:24:51-- http://mirror.ventraip.net.au/apache/incubator/helix/0.7.0-incubating/src/helix-0.7.0-incubating-src.zip Resolving mirror.ventraip.net.au... 112.140.180.131, 2400:b800:1:1::15 Connecting to mirror.ventraip.net.au|112.140.180.131|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3321232 (3.2M) [application/zip] Saving to: ‘helix-0.7.0-incubating-src.zip’ 100%[=] 3,321,232 2.06MB/s in 1.5s 2013-11-25 09:24:53 (2.06 MB/s) - ‘helix-0.7.0-incubating-src.zip’ saved [3321232/3321232] mb-olamy:tmp olamy$ unzip -l helix-0.7.0-incubating-src.zip|grep NOTICE 801 11-14-13 15:58 helix-0.7.0-incubating/helix-agent/NOTICE 801 11-14-13 15:58 helix-0.7.0-incubating/helix-examples/NOTICE 801 11-14-13 15:58 helix-0.7.0-incubating/helix-core/NOTICE 801 11-14-13 15:58 helix-0.7.0-incubating/helix-admin-webapp/NOTICE 164 11-14-13 15:58 helix-0.7.0-incubating/NOTICE So AFICS the NOTICE is in the source release (it's generated by maven) Cheers On 24 November 2013 08:29, sebb seb...@gmail.com wrote: On 23 November 2013 20:00, Kanak Biscuitwala kana...@hotmail.com wrote: sebb, I fixed the tag to include NOTICE here: https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=37c20e79d0e132710f0fa0e5e8dbdb95b2e639ff The parent project doesn't produce any binary artifacts that we release. Do we need to go through the entire release process again? Again, does the release include the correct NOTICE and LICENSE files? Date: Mon, 18 Nov 2013 23:48:56 -0800 Subject: [VOTE] helix-0.7.0-incubating From: zzh...@apache.org To: general@incubator.apache.org Hi, This is to call for a vote on releasing the following candidate as Apache Helix 0.7.0-incubating. This is the first release candidate of our fourth release at Apache. Apache Helix is a generic cluster management framework that makes it easy to build partitioned and replicated, fault tolerant and scalable distributed systems. Release notes: http://helix.incubator.apache.org/site-releases/0.7.0-incubating-site/releasenotes/release-0.7.0-incubating.html Our vote thread on helix-dev: http://markmail.org/message/jevvd7e3v6e75vgg The following IPMC members have voted +1 Patrick Hunt Olivier Lamy Release artifacts: https://repository.apache.org/content/repositories/orgapachehelix-139 Distribution: *binaries: https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/binaries/ *sources: https://dist.apache.org/repos/dist/dev/incubator/helix/0.7.0-incubating/src/ The 0.7.0-incubating release tag https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=575a02b463c3482cefd164578214da7d478da27f KEYS file available here: https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS Please vote on the release. The vote will be open for 72 hours. [+1] [0] [-1] Thanks, The Apache Helix 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 -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] helix-0.6.2-incubating
On 25 November 2013 11:09, David Nalley da...@gnsa.us wrote: On Sat, Nov 23, 2013 at 8:51 PM, Kanak Biscuitwala kana...@hotmail.com wrote: Date: Sun, 24 Nov 2013 00:53:13 + Subject: Re: [VOTE] helix-0.6.2-incubating From: seb...@gmail.com To: general@incubator.apache.org On 23 November 2013 23:47, Kanak Biscuitwala kana...@hotmail.com wrote: Oh, interesting. I believe it generates this automatically with the license-maven-plugin in the build/package stage. In that case, is this an acceptable solution, or is an explicit NOTICE file still required? Every ASF distribution must have LICENSE and NOTICE files (and DISCLAIMER for podlings) This includes releases and SCM. Given this requirement, which of the following is the correct course of action? 1. Update master with a NOTICE file which is a copy of the generated NOTICE file (it looks correct) and take no further action with the releases since the released packages contain NOTICE files. 2. Update master and both tags with NOTICE files. Take no further action since the distributed packages have 1:1 correspondence with all files in source control. 3. Update master and both tags with NOTICE files, skip the vote, and just update the already-pushed packages. 4. Update master and both tags with NOTICE files, go through the entire voting process again, re-release. Really what I want to get out of all this is what is required to bring current and future Helix releases to full compliance with ASF standards. You really should be asking this of your mentors. But you asked general@, so I'll wade in - IMO the release doesn't comply with policy, but what's done tis done; you can't unrelease it now that it's published. If I were in your shoes I'd probably publish a new version that is in compliance. (and incidentally you don't seem to be moving older versions (0.6.0, 0.6.1, etc) to the archive when promoting a new release. - see http://www.apache.org/dev/release.html#when-to-archive for more) The NOTICE file must not contain any unnecessary content - in particular it must only contain references to bits that are actually included in the distribution. I'm not sure whether the plugin handles this properly yet (early versions were not good in this regard). It seems to do it correctly. The top level project is just the website for this project, which has no dependencies other than ASF projects, and this is reflected in the generated NOTICE file. Or does the top level NOTICE file need to be the union of all of its subprojects' NOTICE files? You are only releasing one artifact - the source artifact. (in this case this file: https://dist.apache.org/repos/dist/release/incubator/helix/0.6.2-incubating/src/helix-0.6.2-incubating-src.zip IF that release artifact contains the software that needs to be noted in the NOTICE file it should be done at the top level. The binaries you produce are not Apache releases. (If this confuses you please ask your mentors, or come back here and ask) Your SCM tree and the artifacts you release should have NOTICE, LICENSE, and DISCLAIMER at the top level, of the release artifact that is correctly populated. (e.g. the NOTICE file in your subdirectories appear to be incorrectly populated) mb-olamy:tmp olamy$ wget https://dist.apache.org/repos/dist/release/incubator/helix/0.6.2-incubating/src/helix-0.6.2-incubating-src.zip --2013-11-25 12:15:22-- https://dist.apache.org/repos/dist/release/incubator/helix/0.6.2-incubating/src/helix-0.6.2-incubating-src.zip Resolving dist.apache.org... 140.211.11.22 Connecting to dist.apache.org|140.211.11.22|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 2268555 (2.2M) [application/octet-stream] Saving to: ‘helix-0.6.2-incubating-src.zip’ 100%[=] 2,268,555650KB/s in 3.4s 2013-11-25 12:15:28 (650 KB/s) - ‘helix-0.6.2-incubating-src.zip’ saved [2268555/2268555] mb-olamy:tmp olamy$ unzip -l helix-0.6.2-incubating-src.zip|grep NOTICE 801 11-14-13 15:31 helix-0.6.2-incubating/helix-agent/NOTICE 801 11-14-13 15:31 helix-0.6.2-incubating/helix-admin-webapp/NOTICE 801 11-14-13 15:31 helix-0.6.2-incubating/helix-core/NOTICE 164 11-14-13 15:31 helix-0.6.2-incubating/NOTICE So NOTICE is here in the top. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Helix as TLP Resolution
Hi, Here the vote for Apache Helix as TLP graduation. The vote result for dev@helix.i.a.o is available here: http://markmail.org/message/22orwjy2v3d4af67 Vote open for 72H [+1] [0] [-1] X. Resolution to establish the Apache Helix 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 related to cluster management system for managing partitioned and replicated resources in distributed data systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Helix Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Helix Project be and hereby is responsible for the creation and maintenance of a software project related to cluster management system for managing partitioned and replicated resources in distributed data systems; and be it further RESOLVED, that the office of Vice President, Helix 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 Helix Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Helix 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 Helix Project: * Olivier Lamy olamy * Patrick Hunt phunt * Mahadev Konar mahadev * Owen O'Malley omalley * Kishore Gopalakrishna kishoreg * Zhen Zhang zzhang * Shi Lu slu * Kapil Surlaker ksurlaker * Bob Schulman rms * Swaroop Jagadish swaroop-aj * Rahul Aggarwal rahula * Terence Yim chtyim * Santiago Perez santip * Vinayak Borkar vinayakb * Shirshanka Das sdas * Kanak Biscuitwala kanak NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be and hereby is appointed to the office of Vice President, Helix, 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 Helix Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Helix podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Helix podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Tajo-0.2-incubating RC3
+1 (binding) On 14 November 2013 03:23, Jakob Homan jgho...@gmail.com wrote: +1 (binding). Verified MD5. License, disclaimer and notice all look good. On Tue, Nov 12, 2013 at 8:07 PM, Hyunsik Choi hyun...@apache.org wrote: Ping - just a friendly reminder that we're seeking votes on our first release here. - hyunsik On Sun, Nov 10, 2013 at 2:46 PM, Hyunsik Choi hyun...@apache.org wrote: Dear IPMC members, If there are some reasons why you do not vote, please leave reasons here. I would like to proceed or cancel this vote. Best regards, Hyunsik Choi On Thu, Nov 7, 2013 at 11:59 AM, Hyunsik Choi hyun...@apache.org wrote: Are there other IPMC members who are willing to review this release? We need two more votes! - hyunsik 2013년 11월 4일 월요일에 Hyunsik Choi님이 작성: Hi folks This is the fourth candidate for Apache Tajo-0.2-incubating, and it is also the first official release for Tajo. The PPMC vote [1][2][3] was passed with 3 binding +4s and no -1. Release git tag is at: https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git;a=shortlog;h=refs/tags/release-0.2.0-rc3 Release notes is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/RELEASE_NOTES.html Release artifacts, signatures, md5, and sha1 are at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/ and the KEYS file containing the PGP keys used to sign the release can currently be found at: http://people.apache.org/keys/group/tajo.asc The RAT report is at: http://people.apache.org/~hyunsik/tajo-0.2.0-incubating-rc3/rat.txt Please vote [ ] +1 release this package as apache-tajo-0.2-incubating [ ] -1 do not release this package because ... Thanks, Hyunsik Choi [1] http://markmail.org/message/cvwzgdfkq2zfmmbo [2] http://markmail.org/message/crhbpagwo3pvm4et [3] http://markmail.org/message/kofx3nfjzcr7chqu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: missing dev mail list for BatchEE and Sirona
https://issues.apache.org/jira/browse/INFRA-6977 On 8 November 2013 08:20, David Crossley cross...@apache.org wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Twill for Incubation
+1 (binding) On 8 November 2013 11:16, Edward J. Yoon edwardy...@apache.org wrote: +1 (non-binding) On Fri, Nov 8, 2013 at 7:37 AM, Alejandro Abdelnur t...@cloudera.com wrote: +1 On Thu, Nov 7, 2013 at 2:19 PM, Roman Shaposhnik r...@apache.org wrote: On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote: The discussion about the Weave proposal has calmed. As the outcome of the discussion, we have chosen a new name for the project, Twill. I would like to call a vote for Twill to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/TwillProposal Let's keep this vote open for three business days, closing the voting on Tuesday 11/12. [ ] +1 Accept Twill into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Twill because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Apache Sirona as an incubated project
Hi, The vote has passed with the following result: +1: Bertrand, Romain, Christian, Andrei, Sergio, Mark, Enrico, Tammo, Henry, Szabolcs, Hadrian, Christian Vote thread: http://markmail.org/message/dzlqknkg5yw752hv So I will continue the process. Thanks to all voters, -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache Sirona as an incubated project
Hi, Since discussion about the Sirona seems done, I'd like to call a vote for Sirona to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/SironaProposal Let's keep this vote open for three business days. [ ] +1 Accept Sirona into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Sirona because... ## page was renamed from MonitoringProposal = Apache Sirona = == Abstract == Apache Sirona aims to provide a simple but extensible monitoring solution for Java applications. Apache Sirona provides two kind of components : * Apache Sirona Core to provide a base framework for monitoring/recording a Java application. * Default based plugins * Apache Sirona base reporting web application (provide a basic reporting on recorded figures). == Background == Currently, Apache Sirona source is hosted in Apache Commons Sandbox scm. The development has begun few years ago but goes to dormant statut. == Rationale == Currently users who need some monitoring need to use some non Open Source solutions or GPL solutions. The goal is to provide a solution based on the Apache License. == Initial Goals == Apache Sirona doesn't have any release currently. The initial goal of this project will be to build community in the spirit of the Apache Way, and to address new features and bug-fixes of the first releases. === Current Status === Intent of the proposal is to build a diverse community of developers around Sirona. Sirona started in the Apache Commons Sandbox, driven in the spirit of open source and we would like to continue in this spirit by, for example, encouraging contributors from a variety of organizations. === Community === Apache Sirona stakeholders desire to expand the user and developer base of Apache Sirona further in the future == Known Risks == === Orphaned Products === Sirona is a new product. So without community adoption the risks of it being orphaned exist. === Inexperience with Open Source === The code has been developed in Apache Commons Sandbox mostly by Romain Manni-Bucau and Olivier Lamy who intimately familiar with the Apache model for open-source development and is experienced with working with new contributors. === Homogeneous Developers === The initial set of committers is from a small set of organizations. However, we expect that once approved for incubation, the project will attract new contributors from diverse organizations and will thus grow organically. The participation of developers from several different organizations in the mailing list is a strong indication for this assertion. === Reliance on Salaried Developers === It is expected that Apache Sirona will be developed on salaried and volunteer time. === Relationships with Other Apache Products === Apache Sirona depends upon other Apache Projects: Velocity and various Apache Commons components and build systems like Maven. === A Fascination with the Apache Brand === The reason for joining Apache is to foster a healthy community of contributors and consumers around the project. This is facilitated by ASF and that is the primary reason we would like Apache Sirona to become an Apache project. == Documentation == Docs: http://commons.apache.org/sandbox/commons-monitoring/ == Initial Source == https://svn.apache.org/repos/asf/commons/sandbox/monitoring/trunk == Source and Intellectual Property Submission Plan == The initial source is already Apache 2.0 licensed. == External Dependencies == The required external dependencies are all Apache License or compatible licenses. Following components with non-Apache licenses are enumerated : == Cryptography == Apache Sirona does not depend upon any cryptography tools or libraries. == Required Resources == === Mailing lists === * sirona-private (with moderated subscriptions) * sirona-dev * sirona-commits * sirona-user == Subversion Directory == https://svn.apache.org/repos/asf/incubator/sirona == Issue Tracking == JIRA Sirona (key: SIRONA) == Other Resources == The existing code already has unit and integration tests so we would like to use Jenkins instance to run them whenever a new patch is submitted. This can be added after project creation. == Initial Committer == * Romain Manni-Bucau (rmannibu...@apache.org) * Jean-Louis Monteiro (jlmonte...@apache.org) * Fred Zhang (no ASF account) * Fabrice Bacchella (no ASF account) * Christian Grobmeier (grobme...@apache.org) == Affiliations == * Olivier Lamy, Ecetera * Fred Zhang, Ecetera == Sponsors == === Champion === * Olivier Lamy (ol...@apache.org) === Nominated Mentors === * Olivier Lamy (ol...@apache.org) * Henri Gomez (hgo...@apache.org) * Jean-Baptiste Onofré (jbono...@apache.org) * Tammo van Lessen (va...@apache.org) * Mark Struberg (strub...@apache.org) Thanks -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
No worries. I got few kids so I know how it can be hard and long to find the good name and have all agree on it :-) On 7 October 2013 22:26, Christian Grobmeier grobme...@gmail.com wrote: Thanks a lot Olivier On 7 Oct 2013, at 1:26, Olivier Lamy wrote: Page renamed: https://wiki.apache.org/incubator/SironaProposal I will wait until tomorrow if no more objections then start the vote. On 7 October 2013 09:59, Tammo van Lessen tvanles...@gmail.com wrote: +1 for Sirona On Fri, Oct 4, 2013 at 4:44 PM, Ashish paliwalash...@gmail.com wrote: +1, sounds good On Wed, Oct 2, 2013 at 4:31 AM, Olivier Lamy ol...@apache.org wrote: So Apache Merlin sounds good to me. Any objections? On 25 September 2013 23:47, Christian Grobmeier grobme...@gmail.com wrote: Nechtan sounds cool also. Please note, in the german wikipedia its translated with The tremendousness. This is not noted on the english wikipedia. After reading wikipedia I am still not sure what Nechtan stands for. But I like its sound. I just found Sirona, goddess of healing. Because monitoring is identifying the sickness before its getting worse. However, Sirona is used by companies related to healing (aka dental works). What I found interesting is this page claims Merlin being a god: http://wicca.com/celtic/wicca/celtic.htm of protecting, counseling, crystal reading and so. A few projects use Merlin, but all are very small ant not related to monitoring. There is a project management software called marlin: http://www.projectwizards.net/de/merlin/ I believe we currently have: Apache Leitstand Apache Nechtan Apache Merlin Apache Sirona Apache Heimdall Apache Dagr Cheers On 25 Sep 2013, at 15:03, Stephen Connolly wrote: Why not try Celtic mythology I was thinking Apache Nechtan due to the association with access to knowledge and floods... but heck I am not good on my Irish mythology and the Norse ones always sounded way cooler On 25 September 2013 13:23, Christian Grobmeier grobme...@gmail.com wrote: I also see thor is being used by infra: status.apache.org (mentioning, because it has been proposed as name too). However, it's not so bad. I actually mixed up Baldur with Heimdall, who is the actual protector of Bifröst. Baldur was more known because he was able to return from Hel (sounds like a good name for a server ;-) A quick crosscheck told me Heimdall is not used that often. For those who were concerned about using nordic godnames: Heimdall was named as the father of all humans. He was also known for his horn Gjallarhorn which he blew when danger appeared. Most notable he blew that horn when Ragnarökr (the end of our time and the fall of the gods) starts. I imagine the sound of a horn when critical notification of the tool happens ;-) Another idea i just had was Dagr. It old norsk for Day. In old myths Dagr is the son of night and he rides his horse Skinfaxi through heaven. The crest of the horse lights the earth with golden shimmer. I imagine Apache Dagr to shed light on the dark corners of our applications. Heck, when I was young i read a lot about northern mythology. Its so poetic. I should spend some time to read again. On 25 Sep 2013, at 10:19, Daniel Gruno wrote: On 09/25/2013 09:21 AM, Tammo van Lessen wrote: Baldr is fine with me, my only concern is the similarity to Apache Buildr. Just a heads up from infra; baldr.apache.org is already very much a thing, and has been for more than five years. If it can be avoided, we'd really appreciate it if we can keep the name Baldr for our infrastructure. With regards, Daniel. Tammo Am 25.09.2013 01:18 schrieb Olivier Lamy ol...@apache.org: So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/**foundation/marks/naming.html http://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
Page renamed: https://wiki.apache.org/incubator/SironaProposal I will wait until tomorrow if no more objections then start the vote. On 7 October 2013 09:59, Tammo van Lessen tvanles...@gmail.com wrote: +1 for Sirona On Fri, Oct 4, 2013 at 4:44 PM, Ashish paliwalash...@gmail.com wrote: +1, sounds good On Wed, Oct 2, 2013 at 4:31 AM, Olivier Lamy ol...@apache.org wrote: So Apache Merlin sounds good to me. Any objections? On 25 September 2013 23:47, Christian Grobmeier grobme...@gmail.com wrote: Nechtan sounds cool also. Please note, in the german wikipedia its translated with The tremendousness. This is not noted on the english wikipedia. After reading wikipedia I am still not sure what Nechtan stands for. But I like its sound. I just found Sirona, goddess of healing. Because monitoring is identifying the sickness before its getting worse. However, Sirona is used by companies related to healing (aka dental works). What I found interesting is this page claims Merlin being a god: http://wicca.com/celtic/wicca/celtic.htm of protecting, counseling, crystal reading and so. A few projects use Merlin, but all are very small ant not related to monitoring. There is a project management software called marlin: http://www.projectwizards.net/de/merlin/ I believe we currently have: Apache Leitstand Apache Nechtan Apache Merlin Apache Sirona Apache Heimdall Apache Dagr Cheers On 25 Sep 2013, at 15:03, Stephen Connolly wrote: Why not try Celtic mythology I was thinking Apache Nechtan due to the association with access to knowledge and floods... but heck I am not good on my Irish mythology and the Norse ones always sounded way cooler On 25 September 2013 13:23, Christian Grobmeier grobme...@gmail.com wrote: I also see thor is being used by infra: status.apache.org (mentioning, because it has been proposed as name too). However, it's not so bad. I actually mixed up Baldur with Heimdall, who is the actual protector of Bifröst. Baldur was more known because he was able to return from Hel (sounds like a good name for a server ;-) A quick crosscheck told me Heimdall is not used that often. For those who were concerned about using nordic godnames: Heimdall was named as the father of all humans. He was also known for his horn Gjallarhorn which he blew when danger appeared. Most notable he blew that horn when Ragnarökr (the end of our time and the fall of the gods) starts. I imagine the sound of a horn when critical notification of the tool happens ;-) Another idea i just had was Dagr. It old norsk for Day. In old myths Dagr is the son of night and he rides his horse Skinfaxi through heaven. The crest of the horse lights the earth with golden shimmer. I imagine Apache Dagr to shed light on the dark corners of our applications. Heck, when I was young i read a lot about northern mythology. Its so poetic. I should spend some time to read again. On 25 Sep 2013, at 10:19, Daniel Gruno wrote: On 09/25/2013 09:21 AM, Tammo van Lessen wrote: Baldr is fine with me, my only concern is the similarity to Apache Buildr. Just a heads up from infra; baldr.apache.org is already very much a thing, and has been for more than five years. If it can be avoided, we'd really appreciate it if we can keep the name Baldr for our infrastructure. With regards, Daniel. Tammo Am 25.09.2013 01:18 schrieb Olivier Lamy ol...@apache.org: So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/**foundation/marks/naming.html http://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would be the best
Re: [VOTE] Retire the Tashi podling
+1 On 3 October 2013 09:45, Marvin Humphrey mar...@rectangular.com wrote: Greets, As discussed previously on general@incubator[1], the Tashi community has voted to retire from the Incubator. Following the retirement guide[2], it is now time for an IPMC vote ratifying their decision. [ ] +1 Retire the Tashi podling [ ] +0 Neither here nor there [ ] -1 Do not retire the podling because ... This vote will remain open for at least the next 72 hours. Here is my +1. Marvin Humphrey [1] http://s.apache.org/G1S [2] http://incubator.apache.org/guides/retirement.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
Sounds good for me too. On 2 October 2013 18:19, Mark Struberg strub...@yahoo.de wrote: -1 for Merlin. Just too widely used :( There are 10++ pages of trademarks in all fields in trademarkia, many of them in the software area +1 for Sirona as it has a nice meaning and it seems to not be used for any software related product so far. LieGrue, strub - Original Message - From: Jean-Baptiste Onofré j...@nanthrax.net To: general@incubator.apache.org Cc: Sent: Wednesday, 2 October 2013, 8:46 Subject: Re: [DISCUSS] [PROPOSAL] Apache Monitoring +1 Regards JB On 10/02/2013 01:01 AM, Olivier Lamy wrote: So Apache Merlin sounds good to me. Any objections? On 25 September 2013 23:47, Christian Grobmeier grobme...@gmail.com wrote: Nechtan sounds cool also. Please note, in the german wikipedia its translated with The tremendousness. This is not noted on the english wikipedia. After reading wikipedia I am still not sure what Nechtan stands for. But I like its sound. I just found Sirona, goddess of healing. Because monitoring is identifying the sickness before its getting worse. However, Sirona is used by companies related to healing (aka dental works). What I found interesting is this page claims Merlin being a god: http://wicca.com/celtic/wicca/celtic.htm of protecting, counseling, crystal reading and so. A few projects use Merlin, but all are very small ant not related to monitoring. There is a project management software called marlin: http://www.projectwizards.net/de/merlin/ I believe we currently have: Apache Leitstand Apache Nechtan Apache Merlin Apache Sirona Apache Heimdall Apache Dagr Cheers On 25 Sep 2013, at 15:03, Stephen Connolly wrote: Why not try Celtic mythology I was thinking Apache Nechtan due to the association with access to knowledge and floods... but heck I am not good on my Irish mythology and the Norse ones always sounded way cooler On 25 September 2013 13:23, Christian Grobmeier grobme...@gmail.com wrote: I also see thor is being used by infra: status.apache.org (mentioning, because it has been proposed as name too). However, it's not so bad. I actually mixed up Baldur with Heimdall, who is the actual protector of Bifröst. Baldur was more known because he was able to return from Hel (sounds like a good name for a server ;-) A quick crosscheck told me Heimdall is not used that often. For those who were concerned about using nordic godnames: Heimdall was named as the father of all humans. He was also known for his horn Gjallarhorn which he blew when danger appeared. Most notable he blew that horn when Ragnarökr (the end of our time and the fall of the gods) starts. I imagine the sound of a horn when critical notification of the tool happens ;-) Another idea i just had was Dagr. It old norsk for Day. In old myths Dagr is the son of night and he rides his horse Skinfaxi through heaven. The crest of the horse lights the earth with golden shimmer. I imagine Apache Dagr to shed light on the dark corners of our applications. Heck, when I was young i read a lot about northern mythology. Its so poetic. I should spend some time to read again. On 25 Sep 2013, at 10:19, Daniel Gruno wrote: On 09/25/2013 09:21 AM, Tammo van Lessen wrote: Baldr is fine with me, my only concern is the similarity to Apache Buildr. Just a heads up from infra; baldr.apache.org is already very much a thing, and has been for more than five years. If it can be avoided, we'd really appreciate it if we can keep the name Baldr for our infrastructure. With regards, Daniel. Tammo Am 25.09.2013 01:18 schrieb Olivier Lamy ol...@apache.org: So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail
Re: [VOTE] Release Apache Marmotta 3.1.0-incubating
+1 sources build fine. -- Olivier On Sep 30, 2013 8:17 PM, Sebastian Schaffert sschaff...@apache.org wrote: Dear all, After several months of work since the last incubating release (3.0.0-incubating) in April, we are now ready to release version 3.1.0-incubating. We fixed all the remaining issues that have been discussed in April (see thread [1]) plus many more technical issues. We have already held a vote that was open for more than 72 hours on the Apache Marmotta developer mailinglist [2]. The vote concluded [3] with 7 positive votes, of which 2 have been binding from IPMC members (Andy and Nandana) and the remaining 5 from the Apache Marmotta developers. I'd therefore like to ask the general incubator to check our release candidate. The release notes are available at the Jira Issue Tracker [4]. The vote form is included at the bottom of this mail. Greetings, Sebastian [1] http://apache.markmail.org/message/5tieelmeevi2j6xb [2] http://apache.markmail.org/message/lk3hc3jutoaxp6dr [3] http://apache.markmail.org/message/fvytzho2pnhasw2c [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12324026 === A candidate for the Marmotta 3.1.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/ The release candidate is based on the sources tagged with 3.1.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git The release candidate consists of the following source distribution archives: - apache-marmotta-3.1.0- incubating-src.[zip|tar.gz] SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527 SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729 In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617 - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75 - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142 SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-092/ Please vote on releasing this package as Apache Marmotta 3.1.0-incubating. The vote is open for the next 72 hours and passes if a majority of at least three +1 Marmotta PMC votes are cast. [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... === Release Notes - Marmotta - Version 3.1-incubating ** Sub-task * [MARMOTTA-216] - Implement JOIN improvements * [MARMOTTA-217] - Implement FILTER improvements * [MARMOTTA-218] - Integrate in marmotta-sparql ** Bug * [MARMOTTA-28] - Implement tests for core that take into account triple store changes * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently not working properly * [MARMOTTA-66] - Rework sesame-commons ResourceUtils * [MARMOTTA-143] - unable to import big files * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords * [MARMOTTA-155] - 3-char lang-tags are not accepted * [MARMOTTA-156] - Add Logback configuration to all tests to enable/disable debug logging * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file contains wrong comments * [MARMOTTA-171] - remove legacy subdirs from src/main/webapp in marmotta-webapp * [MARMOTTA-186] - LDPath parser fails on local names that contain '.' * [MARMOTTA-187] - ldpath extension for CM does not recognize local names with '.' or '-' * [MARMOTTA-191] - SPARQL graph results fails under some circunstances * [MARMOTTA-197] - ldpath is loosing brackets on re-serialisation * [MARMOTTA-204] - Update to Sesame 2.7.1 * [MARMOTTA-205] - Turtle-Exports do not contain any language tags * [MARMOTTA-206] - Strictly follow the standard formatting on the NOTICE * [MARMOTTA-208] - Meta Put Webservice Deleting Tuples Incorrectly * [MARMOTTA-213] - Address the issues on our NOTICE files * [MARMOTTA-214] - Memento timestamp does not use the right template * [MARMOTTA-221] - ldpath is loosing quotes for StringConstants on re-serialisation * [MARMOTTA-225] - Serializing ldpath field mappings with URIs as fieldname does not work correctly * [MARMOTTA-227] - Snorql uses different set of prefixes in the query evaluation than the showed at the user interface
Re: [DISCUSS] [PROPOSAL] Apache Monitoring
So Apache Merlin sounds good to me. Any objections? On 25 September 2013 23:47, Christian Grobmeier grobme...@gmail.com wrote: Nechtan sounds cool also. Please note, in the german wikipedia its translated with The tremendousness. This is not noted on the english wikipedia. After reading wikipedia I am still not sure what Nechtan stands for. But I like its sound. I just found Sirona, goddess of healing. Because monitoring is identifying the sickness before its getting worse. However, Sirona is used by companies related to healing (aka dental works). What I found interesting is this page claims Merlin being a god: http://wicca.com/celtic/wicca/celtic.htm of protecting, counseling, crystal reading and so. A few projects use Merlin, but all are very small ant not related to monitoring. There is a project management software called marlin: http://www.projectwizards.net/de/merlin/ I believe we currently have: Apache Leitstand Apache Nechtan Apache Merlin Apache Sirona Apache Heimdall Apache Dagr Cheers On 25 Sep 2013, at 15:03, Stephen Connolly wrote: Why not try Celtic mythology I was thinking Apache Nechtan due to the association with access to knowledge and floods... but heck I am not good on my Irish mythology and the Norse ones always sounded way cooler On 25 September 2013 13:23, Christian Grobmeier grobme...@gmail.com wrote: I also see thor is being used by infra: status.apache.org (mentioning, because it has been proposed as name too). However, it's not so bad. I actually mixed up Baldur with Heimdall, who is the actual protector of Bifröst. Baldur was more known because he was able to return from Hel (sounds like a good name for a server ;-) A quick crosscheck told me Heimdall is not used that often. For those who were concerned about using nordic godnames: Heimdall was named as the father of all humans. He was also known for his horn Gjallarhorn which he blew when danger appeared. Most notable he blew that horn when Ragnarökr (the end of our time and the fall of the gods) starts. I imagine the sound of a horn when critical notification of the tool happens ;-) Another idea i just had was Dagr. It old norsk for Day. In old myths Dagr is the son of night and he rides his horse Skinfaxi through heaven. The crest of the horse lights the earth with golden shimmer. I imagine Apache Dagr to shed light on the dark corners of our applications. Heck, when I was young i read a lot about northern mythology. Its so poetic. I should spend some time to read again. On 25 Sep 2013, at 10:19, Daniel Gruno wrote: On 09/25/2013 09:21 AM, Tammo van Lessen wrote: Baldr is fine with me, my only concern is the similarity to Apache Buildr. Just a heads up from infra; baldr.apache.org is already very much a thing, and has been for more than five years. If it can be avoided, we'd really appreciate it if we can keep the name Baldr for our infrastructure. With regards, Daniel. Tammo Am 25.09.2013 01:18 schrieb Olivier Lamy ol...@apache.org: So what about Baldr? BTW we can start incubation using Monitoring then change the name for TLP? WDYT? On 21 September 2013 06:30, Christian Grobmeier grobme...@gmail.com wrote: I would like to throw in this document: http://www.apache.org/**foundation/marks/naming.htmlhttp://www.apache.org/foundation/marks/naming.html We should make a few tests already before we start the process officially. here is the current list, i felt so free to add a few comments already. - CoMon There is Common Software, a company. We might have a trademarks problem because of similarity. - Leitstand Not sure if I like the sound :-), but did not find any repositories at github. From the meaning, a Leitstand is usually something were you can adjust things (more power, less steam and so on). Monitoring would be only a part of it. But on the other hand, it expresses things well and it is a unused word so far. - Thor Great name, great god, but unfortunately a lot of people use that name for their code :-( - Balder / Baldur, also possible: Baldr I haven't see a lot with that name, but we need to check this more in detail. From that perspective, Leitstand would be the best catch from a unique point of view. I like Baldr very much from that meaning. Lets see if there are more names the next days. Romain Manni-Bucau schrieb: Why not CoMon? Remind commons monitoring, that's fun and closer to english so easier to propagate IMO. Le 20 sept. 2013 12:59, Jean-Baptiste Onofré j...@nanthrax.net a écrit : I like the Apache Leitstand name. Regards JB On 09/20/2013 09:51 AM, Tammo van Lessen wrote: So if German is en vogue already, I'd propose Apache Leitstand [1], which means control room. I think it would make also a nice name when pronounced in English. This of course only works if the GUI is an important piece of the project, which is the case if I
