Re: [VOTE] Release apache-calcite-1.1.0-incubating
Forwarding my +1 from dev@calcite: +1. I checked the signatures, DISCLAIMER, NOTICE, and LICENSE files, built the code and ran the tests, and checked to make sure there were no jars or class files in the distribution. Alan. Julian Hyde mailto:jh...@apache.org March 16, 2015 at 23:30 Hi all, The Calcite community has voted on and approved a proposal to release Apache Calcite 1.1.0-incubating. Proposal: http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3ccamctmekcqb3bezn0q-1ug6tzxm1p6jzjvbun9jupsfnjc3r...@mail.gmail.com%3E Vote result: 3 binding +1 votes 1 non-binding +1 votes No -1 votes http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3CCAMCtmeJ4uRMbZRc8yFUw8JjH_P-geG749%3D-6m%3D2K3tYuutSthQ%40mail.gmail.com%3E The commit to be voted upon: http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/f10ea367ff1cc25497f50f149ef0c91b3ae03031 Its hash is f10ea367ff1cc25497f50f149ef0c91b3ae03031. The artifacts to be voted on are located here: http://people.apache.org/~jhyde/apache-calcite-1.1.0-incubating-rc1/ The hashes of the artifacts are as follows: src.tar.gz.md5 805f8a1ec7f7dec0b4cd096a7f2b24c3 src.tar.gz.sha1 bc0e718ce3e75c1975bc1825fca2e0dcb22da3d2 src.zip.md5 41732e764ba9557c2dbf269d7904c61b src.zip.sha1 d401cf6a1fd539a3167201d5ed2c6dfe31417349 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecalcite-1006 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/jhyde.asc Pursuant to the Releases section of the Incubation Policy and with the endorsement of 1 of our mentors we would now like to request the permission of the Incubator PMC to publish the release. The vote is open for 72 hours, or until the necessary number of votes (3 +1) is reached. [ ] +1 Release this package as Apache Calcite 1.1.0-incubating [ ] -1 Do not release this package because... Julian Hyde, on behalf of Apache Calcite PPMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release apache-calcite-1.1.0-incubating
Hi all, The Calcite community has voted on and approved a proposal to release Apache Calcite 1.1.0-incubating. Proposal: http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3ccamctmekcqb3bezn0q-1ug6tzxm1p6jzjvbun9jupsfnjc3r...@mail.gmail.com%3E Vote result: 3 binding +1 votes 1 non-binding +1 votes No -1 votes http://mail-archives.apache.org/mod_mbox/calcite-dev/201503.mbox/%3CCAMCtmeJ4uRMbZRc8yFUw8JjH_P-geG749%3D-6m%3D2K3tYuutSthQ%40mail.gmail.com%3E The commit to be voted upon: http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/f10ea367ff1cc25497f50f149ef0c91b3ae03031 Its hash is f10ea367ff1cc25497f50f149ef0c91b3ae03031. The artifacts to be voted on are located here: http://people.apache.org/~jhyde/apache-calcite-1.1.0-incubating-rc1/ The hashes of the artifacts are as follows: src.tar.gz.md5 805f8a1ec7f7dec0b4cd096a7f2b24c3 src.tar.gz.sha1 bc0e718ce3e75c1975bc1825fca2e0dcb22da3d2 src.zip.md5 41732e764ba9557c2dbf269d7904c61b src.zip.sha1 d401cf6a1fd539a3167201d5ed2c6dfe31417349 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachecalcite-1006 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/jhyde.asc Pursuant to the Releases section of the Incubation Policy and with the endorsement of 1 of our mentors we would now like to request the permission of the Incubator PMC to publish the release. The vote is open for 72 hours, or until the necessary number of votes (3 +1) is reached. [ ] +1 Release this package as Apache Calcite 1.1.0-incubating [ ] -1 Do not release this package because... Julian Hyde, on behalf of Apache Calcite PPMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
This should also be done for the logo as well... I don't know the provenance of it, but I am sure that the Groovy team does not want to abandon its logo. On Mar 17, 2015, at 4:55 PM, Shane Curcuru a...@shanecurcuru.org wrote: On 3/17/15 12:41 PM, Roman Shaposhnik wrote: On Wed, Mar 11, 2015 at 3:23 PM, Shane Curcuru a...@shanecurcuru.org wrote: On 3/11/15 4:20 PM, Martijn Dashorst wrote: Great initiative! Just one question: I don't see anything related to the groovy name and possible trademark in the proposal. Does Pivotal have any claims to the name groovy, and if so are those claims transferred to the ASF? Good point. Just from the Apache *policy* side, the ASF must have trademark rights to a podling's name before the board will approve a graduation vote. With such a long history, we would need a clear statement of some sort from whoever was previously hosting Groovy software product releases, which would seem to be Pivotal. Or, the podling would have to choose a new name that we did have rights to. 8-) If the PPMC requests it, we can then register the project's name as a trademark in the US *after* graduation. If this podling joins the incubator, please coordinate some Groovy PPMC and Pivotal contacts with trademarks@. Presuming Pivotal is willing (and I can't imagine why they wouldn't be), trademarks@ can ensure the right stuff gets done. Turns out it is not up to Pivotal. In fact, the statement I've just got goes like this: Pivotal does not have, nor will it make, any claims to the GROOVY trademark Can you ensure that whoever actually wrote that from the Pivotal side communicates it to trademarks@, or at least to vp-brand@? If we do have questions later, counsel will need to email someone directly about it. Basically, Pivotal was happy to sponsor the project (just like it sponsors RabbitMQ or Redis) but wasn't involved in sorting out the situation around the Groovy project name and its legal status. Shane, please let me know if this bit of information is sufficient for you. It appears as though ASF will have to do the usual PODDLINGNAMESEARCH and determine the status of Groovy trademark on its own. I plan to start a [VOTE] thread sometime on Wed, unless you tell me otherwise. No need to gate a podling acceptance vote on branding issues. The only hard requirement is before graduation. - Shane Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release apache-calcite-1.1.0-incubating
Hi, +1 binding - signatures and hashes correct - artefact has incubating in it's name - DISCLAIMER exists - LICENSE and NOTICE correct - All source files have Apache header - No unexpected binary files - Can compile from source - Tests pass Minor issue is that the RC was not placed in the correct place [1] Can this be done with the next release candidate? Thanks, Justin 1. http://incubator.apache.org/guides/releasemanagement.html#glossary-incubator-dist - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
On 3/17/15 12:41 PM, Roman Shaposhnik wrote: On Wed, Mar 11, 2015 at 3:23 PM, Shane Curcuru a...@shanecurcuru.org wrote: On 3/11/15 4:20 PM, Martijn Dashorst wrote: Great initiative! Just one question: I don't see anything related to the groovy name and possible trademark in the proposal. Does Pivotal have any claims to the name groovy, and if so are those claims transferred to the ASF? Good point. Just from the Apache *policy* side, the ASF must have trademark rights to a podling's name before the board will approve a graduation vote. With such a long history, we would need a clear statement of some sort from whoever was previously hosting Groovy software product releases, which would seem to be Pivotal. Or, the podling would have to choose a new name that we did have rights to. 8-) If the PPMC requests it, we can then register the project's name as a trademark in the US *after* graduation. If this podling joins the incubator, please coordinate some Groovy PPMC and Pivotal contacts with trademarks@. Presuming Pivotal is willing (and I can't imagine why they wouldn't be), trademarks@ can ensure the right stuff gets done. Turns out it is not up to Pivotal. In fact, the statement I've just got goes like this: Pivotal does not have, nor will it make, any claims to the GROOVY trademark Can you ensure that whoever actually wrote that from the Pivotal side communicates it to trademarks@, or at least to vp-brand@? If we do have questions later, counsel will need to email someone directly about it. Basically, Pivotal was happy to sponsor the project (just like it sponsors RabbitMQ or Redis) but wasn't involved in sorting out the situation around the Groovy project name and its legal status. Shane, please let me know if this bit of information is sufficient for you. It appears as though ASF will have to do the usual PODDLINGNAMESEARCH and determine the status of Groovy trademark on its own. I plan to start a [VOTE] thread sometime on Wed, unless you tell me otherwise. No need to gate a podling acceptance vote on branding issues. The only hard requirement is before graduation. - Shane Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
Hi everybody, when will the voting start? Or if it did start already when will there be decision? Thanks and kind regards, Pascal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
Hi Hervé, It would be very nice, if it fits the general schedule (Groovy is not yet voted). Best regards, On 16/03/2015 23:00, Hervé Boutemy wrote: Hi, We're scheduling the Jira migration for Maven projects on the week-end of 4/5/6 april. If this schedule is fine for Groovy, I suppose it would be ok to add Groovy Jira project to the actual list [1] Just tell, and I'll avoid to remove Groovy from the full dump we'll have during the migration. Regards, Hervé Notice: please CC me if necessary, since I'm not subscribed to general@incubator [1] https://issues.apache.org/jira/browse/INFRA-9116 Le lundi 16 mars 2015 09:53:00 Stephen Connolly a écrit : Arg! hit send too soon. You should really check in with Hervé to confirm that Groovy was in the export. I am 99% confident that your issues and comments are in the XML dump, but you really should check with Hervé to be certain. Also you may want to ask Mark Thomas what exactly is involved in preparing and doing such an import. Our own timelines for Maven's switch may not align with the Groovy incubation timelines... (mind you we are all at the grace of Ben for getting our timeline for the second export he committed to the Maven project) On 16 March 2015 at 09:49, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 16 March 2015 at 09:19, Cédric Champeau cedric.champ...@gmail.com wrote: Thanks Stephen, sounds like a good news. For us the attachments do not matter much, there are not so many. However, keeping track of comments is very important, because some issues have a lot of discussions. 2015-03-16 10:08 GMT+01:00 Stephen Connolly stephen.alan.conno...@gmail.com On 16 March 2015 at 08:55, Jochen Theodorou blackd...@gmx.org wrote: Am 16.03.2015 09:25, schrieb Upayavira: When Stephen Connolly says ”We @ Maven will have a full dump of the Codehaus JIRA and we have a VM set up to test migration…” isn’t he implying that the Groovy issues are *included* in that? I.e. there’s not so much for you to worry about here? Even if Stephen gets a full dump, this does not mean we will get the Groovy part out of it. Ben was so far telling us he cannot give it out like that, because of private and internal data in there. Instead he suggested a json export (which most likely will not contain everything) Well we are getting the full XML dump because that's all you can get via the XML dump, but whether we get *all* attachments or only those for Maven is a different question. So unless Stephy has this clear with his employee I stand on the part, that we don't have that. Clarification: Ben and I are co-workers. bye Jochen -- Jochen blackdrag Theodorou - Groovy Project Tech Lead blog: http://blackdragsview.blogspot.com/ german groovy discussion newsgroup: de.comp.lang.misc For Groovy programming sources visit http://groovy-lang.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 -- Cédric Champeau Groovy language developer http://twitter.com/CedricChampeau http://melix.github.io/blog - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
Hi Russel! thanks for following up here. I've seen that others have commented on the points you raised, but I also wanted to chime in before this thread goes into a VOTE phase. On Fri, Mar 13, 2015 at 3:50 AM, Russel Winder rus...@winder.org.uk wrote: On Fri, 2015-03-13 at 08:55 +0100, Bertrand Delacretaz wrote: On Thu, Mar 12, 2015 at 6:07 PM, Cédric Champeau cedric.champ...@gmail.com wrote: ...I see no point in wanting to reach a target number of committers. Having a large number of quality contributions, more contributors is IMHO more important than people having write access to the repo Once again, there's no set number that you have to reach to graduate - it is not about numbers. I think something has gone very wrong with this point about committer count, see below… I could see where you're coming from, but my personal experience around incubator suggests that this could only be a problem if the folks who may have a stake in the project are not recognized during the incubation phase. See bellow for more details: As I said before, being a committer does not necessarily means commit code - if someone's a project evangelist for example and you'd like them to be recognized as a core team member the only way in an Apache project is to make them a committer (and maybe PMC member). As in committed to the project, even if they don't write code. I think this is a fundamentally wrong metric. I have been associated with the Groovy programming language since 2004. Do I have commit privileges, no. Am I part of the Groovy community? Well I would say yes, and if you ask people at Groovy-related, DevoxxUK-related, ACCU-related conferences Is Russel Winder a part of the Groovy community, I think those that knew my name would say definitely. Likewise Is Russel Winder a strong Groovy advocate with a history of converting people to Groovy/Gradle/Spock/GroovyFX/GPars? would get a lot of yes answers. Am I a committer to the Groovy project, no. Do I feel I have to gain status as a committer to validate my position in the Groovy community? No. This is where ASF starts being a really special kind of foundation. While the committership status most definitely allows you to push bits into source code repository, what it really signifies is your commitment (no pun intended) to the project. This is a very subtle, but a very important distinction that Incubator folks are trying to emphasize with every poddling. Poddling's community is NOT only developers, but all the other folks who make the community vibrant as well. Now, given that a formal recognition of a committer could be somewhat time consuming, I've seen a few cases in the past where a PMC approached a prolific contributor to invite him or her to join a project in a more official status and received a polite decline. To me this shows a great degree of maturity and responsibility, but the fact that the offer was made in first place shows that the project is functioning as a true ASF project. Now, I don't have a benefit of following Groovy development history for as long as you have (I've started my journey somewhere around '09). That said, from what I've seen -- you're definitely one of the 'Groovy folks'. Thus, as a mentor, I am going to make sure that Groovy podling does the right things and reaches out to the folks like you. More on the process here: https://community.apache.org/newcommitter.html With The Groovy Project seeking to become a TLP of the Apache Organization, I have been taking a peek at some of the writing on The Apache Way. The phrase that springs immediately to my mind is Community over Code. Most of the discussion in this thread though is about the number of committers, as though only committers are part of the community. Forgive me presuming to say this but this seems a contradiction with The Apache Way as written about. Also it is very CVCS/Subversion focussed. You're absolutely correct. The community is way bigger than PMC and also bigger than formally recognized committers. That said, making sure that merit is recognized with invitations is one of the things we feels helps us run great communities as smoothly as possible. So I would say that status within the community is unrelated to status as a committer, and health of the project is likewise unrelated to the number of committers. If The Apache Way requires a person to be a committer to be considered a recognized person in a community, then I say the metric is wrong and Apache should reconsider its metrics. Having ways and means to ensure releases, that pull requests come in, that mailing lists are vibrant and constructive, that Groovy evolves to the needs of mankind (not just the current users) is almost, but not quite, totally unrelated to the number of committers. Personally, I think we are completely on the same page. Please let me know if you have any suggestions wrt. wording of the proposal. We're planning to move to a
Re: [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 4:38 PM, Benson Margulies bimargul...@gmail.com wrote: ...You may think that the discussion has died down, but perhaps recall the lesson of NiFi. Or not, it might not strike you as applicable... I wasn't involved (or maybe I think I wasn't ;-) so I don't - archive URLs welcome. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Accept Apache Singa as incubator project
After a week-long voting period, the VOTE for accepting Singa into the Apache Incubator has passed with 7 binding +1s and 1 binding +0 . +1 (binding) Konstantin I Boudnik Ted Dunning Alan Gates Thejas Nair Konstantin I Boudnik Alan Cabrera Daniel Dai +0 (binding) Jan I Thanks for voting! I will work on getting the infra JIRAs created. Thanks, Thejas -- Forwarded message -- From: Thejas Nair thejas.n...@gmail.com Date: Tue, Mar 10, 2015 at 7:30 AM Subject: [VOTE] Accept Apache Singa as incubator project To: Cc: oo...@comp.nus.edu.sg The Singa Incubator Proposal document has been updated based on feedback in the proposal thread. This vote is proposing the inclusion of Apache Singa as incubator project. The vote will run for at least 72 hours. [ ] +1 Accept Apache Singa into the Incubator [ ] +0 Don’t care. [ ] -1 Don’t accept Apache Singa into the Incubator because.. Please vote ! Here is my +1 . Link to version of proposal being voted on : https://wiki.apache.org/incubator/SingaProposal?action=recallrev=10 The text is below -- = Singa Incubator Proposal = == Abstract == SINGA is a distributed deep learning platform. == Proposal == SINGA is an efficient, scalable and easy-to-use distributed platform for training deep learning models, e.g., Deep Convolutional Neural Network and Deep Belief Network. It parallelizes the computation (i.e., training) onto a cluster of nodes by distributing the training data and model automatically to speed up the training. Built-in training algorithms like Back-Propagation and Contrastive Divergence are implemented based on common abstractions of deep learning models. Users can train their own deep learning models by simply customizing these abstractions like implementing the Mapper and Reducer in Hadoop. == Background == Deep learning refers to a set of feature (or representation) learning models that consist of multiple (non-linear) layers, where different layers learn different levels of abstractions (representations) of the raw input data. Larger (in terms of model parameters) and deeper (in terms of number of layers) models have shown better performance, e.g., lower image classification error in Large Scale Visual Recognition Challenge. However, a larger model requires more memory and larger training data to reduce over-fitting. Complex numeric operations make the training computation intensive. In practice, training large deep learning models takes weeks or months on a single node (even with GPU). == Rational == Deep learning has gained a lot of attraction in both academia and industry due to its success in a wide range of areas such as computer vision and speech recognition. However, training of such models is computationally expensive, especially for large and deep models (e.g., with billions of parameters and more than 10 layers). Both Google and Microsoft have developed distributed deep learning systems to make the training more efficient by distributing the computations within a cluster of nodes. However, these systems are closed source softwares. Our goal is to leverage the community of open source developers to make SINGA efficient, scalable and easy to use. SINGA is a full fledged distributed platform, that could benefit the community and also benefit from the community in their involvement in contributing to the further work in this area. We believe the nature of SINGA and our visions for the system fit naturally to Apache's philosophy and development framework. == Initial Goals == We have developed a system for SINGA running on a commodity computer cluster. The initial goals include, * improving the system in terms of scalability and efficiency, e.g., using Infiniband for network communication and multi-threading for one node computation. We would consider extending SINGA to GPU clusters later. * benchmarking with larger datasets (hundreds of millions of training instances) and models (billions of parameters). * adding more built-in deep learning models. Users can train the built-in models on their datasets directly. == Current Status == === Meritocracy === We would like to follow ASF meritocratic principles to encourage more developers to contribute in this project. We know that only active and excellent developers can make SINGA a successful project. The committer list and PMC will be updated based on developers' performance and commitment. We are also improving the documentation and code to help new developers get started quickly. === Community === SINGA is currently being developed in the Database System Research Lab at the National University of Singapore (NUS) in collaboration with Zhejiang University in China. Our lab has extensive experience in building database related systems, including distributed systems. Six PhD students and research assistants (Jinyang Gao, Kaiping Zheng, Sheng Wang, Wei Wang, Zhaojing Luo and Zhongle Xie) , a research fellow (Anh Dinh) and three
Re: [DISCUSS] Groovy Incubation proposal
Roman is saying he will start the vote tomorrow. You will see a thread on this list with [VOTE] in the subject. As to what the vote is about - this is the Apache Incubator PMC (Project Management Committee) voting as to whether to accept Groovy into the Incubator. Votes from others, who aren’t on the Incubator PMC are welcome as they inform the process, but for this particular purpose, won’t be binding. Personally, it seems a pretty straight-forward thing to me, but then, we won’t know that for sure until the vote has actually happened. I’d expect Roman’s vote email to explain how long the vote will run for. Upayavira On Tue, Mar 17, 2015, at 06:27 PM, Pascal Schumacher wrote: Hi everybody, when will the voting start? Or if it did start already when will there be decision? Thanks and kind regards, Pascal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 1:09 PM Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Mar 17, 2015 at 5:09 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: ...having seen some of the issues that came from prior proposals rushing a vote, I'd like to see [VOTE] thread to exist for at least a week I don't think letting the vote drag on purpose is useful - after almost a week of discussions it seems like all the (minor) issues that have not come to closure need to be discussed once the podling is established. A longer vote would be counterproductive w.r.t these issues. +1. That is the purpose of the discussion phase. We should all have enough context to vote one way or another. So unless new issues come up once the vote starts (which would be bad - that's why we have a DISCUSS phase) I would very much like to close the vote after the standard 72 hours. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
On Fri, Mar 13, 2015 at 2:39 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ... Starting the vote on the proposal is Roman's job anyway, as the Groovy champion, so let's wait for him... Is there any reason to wait more? IMO the discussion on the proposal has died down so we can move forward. Roman, WDYT? -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache NiFi 0.0.2-incubating release
Hello The Apache NiFi team is excited to announce the release of Apache NiFi 0.0.2-incubating. Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi was made for dataflow. It supports highly configurable directed graphs of data routing, transformation, and system mediation logic. More details on Apache NiFi can be found here: http://nifi.incubator.apache.org/ The release artifacts can be downloaded from here: http://nifi.incubator.apache.org/downloads/ Maven artifacts have been made available here: https://repository.apache.org/content/repositories/releases/org/apache/nifi/ Release notes available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020version=12329373 Thank you The Apache NiFi team DISCLAIMER Apache NiFi is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 3:19 PM, Emmanuel Lécharny elecha...@gmail.com wrote: ...We already have demonstrated our ability to raises various points on various subjects, time to demonstrate The ASF in action !.. +1 - as I said elsethread it's in theory Roman's job to start the vote, as the Groovy champion. But I guess if any of the mentors feel impatient we can do that as well...going once... ;-) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Vote ? was [DISCUSS] Groovy Incubation proposal
Hi guys, we can discuss for 3 more months, but at some point, isn't it time to start a vote ? We already have demonstrated our ability to raises various points on various subjects, time to demonstrate The ASF in action ! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
On 17/03/2015 15:34, Bertrand Delacretaz wrote: On Tue, Mar 17, 2015 at 3:19 PM, Emmanuel Lécharny elecha...@gmail.com wrote: ...We already have demonstrated our ability to raises various points on various subjects, time to demonstrate The ASF in action !.. +1 - as I said elsethread it's in theory Roman's job to start the vote, as the Groovy champion. But I guess if any of the mentors feel impatient we can do that as well...going once... ;-) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org I wouldn't mind starting a vote early, given the time constraints that we have :) -- Cédric Champeau Groovy language developer http://twitter.com/CedricChampeau http://melix.github.io/blog - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 3:38 PM, Cédric Champeau cedric.champ...@gmail.com wrote: ...I wouldn't mind starting a vote early, given the time constraints that we have :)... Ok, I'll start the vote Wednesday morning CET unless we hear from Roman until then. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 8:38 AM, Benson Margulies bimargul...@gmail.com wrote: You may think that the discussion has died down, but perhaps recall the lesson of NiFi. Or not, it might not strike you as applicable. exactly! Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
On Wed, Mar 11, 2015 at 3:23 PM, Shane Curcuru a...@shanecurcuru.org wrote: On 3/11/15 4:20 PM, Martijn Dashorst wrote: Great initiative! Just one question: I don't see anything related to the groovy name and possible trademark in the proposal. Does Pivotal have any claims to the name groovy, and if so are those claims transferred to the ASF? Good point. Just from the Apache *policy* side, the ASF must have trademark rights to a podling's name before the board will approve a graduation vote. With such a long history, we would need a clear statement of some sort from whoever was previously hosting Groovy software product releases, which would seem to be Pivotal. Or, the podling would have to choose a new name that we did have rights to. 8-) If the PPMC requests it, we can then register the project's name as a trademark in the US *after* graduation. If this podling joins the incubator, please coordinate some Groovy PPMC and Pivotal contacts with trademarks@. Presuming Pivotal is willing (and I can't imagine why they wouldn't be), trademarks@ can ensure the right stuff gets done. Turns out it is not up to Pivotal. In fact, the statement I've just got goes like this: Pivotal does not have, nor will it make, any claims to the GROOVY trademark Basically, Pivotal was happy to sponsor the project (just like it sponsors RabbitMQ or Redis) but wasn't involved in sorting out the situation around the Groovy project name and its legal status. Shane, please let me know if this bit of information is sufficient for you. It appears as though ASF will have to do the usual PODDLINGNAMESEARCH and determine the status of Groovy trademark on its own. I plan to start a [VOTE] thread sometime on Wed, unless you tell me otherwise. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Groovy Incubation proposal
You may think that the discussion has died down, but perhaps recall the lesson of NiFi. Or not, it might not strike you as applicable. On Tue, Mar 17, 2015 at 7:33 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Fri, Mar 13, 2015 at 2:39 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ... Starting the vote on the proposal is Roman's job anyway, as the Groovy champion, so let's wait for him... Is there any reason to wait more? IMO the discussion on the proposal has died down so we can move forward. Roman, WDYT? -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 7:19 AM, Emmanuel Lécharny elecha...@gmail.com wrote: Hi guys, we can discuss for 3 more months, but at some point, isn't it time to start a vote ? Sure. But at least a week for something like Groovy should be expected. Besides, I still owe IPMC an answer about status of the Groovy trademark. I'm trying to research this on my end with Pivotal team. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
Hi! having seen some of the issues that came from prior proposals rushing a vote, I'd like to see [VOTE] thread to exist for at least a week. I am going to start a vote tomorrow once a full week of [DISCUSS] elapses. Thanks, Roman. On Tue, Mar 17, 2015 at 8:04 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Mar 17, 2015 at 3:38 PM, Cédric Champeau cedric.champ...@gmail.com wrote: ...I wouldn't mind starting a vote early, given the time constraints that we have :)... Ok, I'll start the vote Wednesday morning CET unless we hear from Roman until then. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
On Tue, Mar 17, 2015 at 5:11 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: ...I still owe IPMC an answer about status of the Groovy trademark. I'm trying to research this on my end with Pivotal team... Sure, it's good to find out but I don't think that's a blocker for entering incubation. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote ? was [DISCUSS] Groovy Incubation proposal
Hi, On Tue, Mar 17, 2015 at 5:09 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: ...having seen some of the issues that came from prior proposals rushing a vote, I'd like to see [VOTE] thread to exist for at least a week I don't think letting the vote drag on purpose is useful - after almost a week of discussions it seems like all the (minor) issues that have not come to closure need to be discussed once the podling is established. A longer vote would be counterproductive w.r.t these issues. So unless new issues come up once the vote starts (which would be bad - that's why we have a DISCUSS phase) I would very much like to close the vote after the standard 72 hours. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
