Re: Github pull request hooks
Very cool, guys! On 08/02/14 23:42, Matei Zaharia wrote: Thanks for the very quick action on this, Daniel and Jake! Matei On Feb 8, 2014, at 3:51 AM, Daniel Gruno wrote: Let me just get some information across to podlings wondering about this new GitHub stuff we've added, and what is supported so far: - It is now possible to relay new GitHub PRs, comments on PRs and closing/reopening of PRs to your mailing list. - It is also possible for all committers in a project to close PRs with a commit message to the master/trunk branch of a project saying, for instance, "this closes #1234 on GitHub" in the commit message. - This GitHub feature is currently only supported for projects/podlings that have their primary source repository in Git. If you have an SVN mirror instead, we are not fully able to support GitHub PR relaying at the time being, but will support it in the near future. - You have to request PR comments to be enabled for your project, preferably via a JIRA ticket (at https://issues.apache.org/jira/browse/INFRA ). By default, hooks have been set up so that only PR opening/closing gets passed on. New setups will include relaying of comments, but if your project has been set up for a web hook in the past, you must request it be set up with comment notification. This is a new default setting, and all projects that now request PR notifications will automatically receive comments on PRs in their respective mailing list as well. If you are unsure whether your project is set up for relaying GitHub messages (and you want this), make a new JIRA ticket to have it set up, rather one ticket too many than one too few. - Comments _should_ now be nested, so that each new comment has an email reference to the original PR issue, meaning they will nest in mod_mbox and your email client if you have nesting/threading enabled. - We may, in the future, add the possibility to filter out certain comments from being relayed to the ML (such as jenkins workflows etc), but this will all depend on how this initial phase goes along. With regards, Daniel. On 02/07/2014 10:02 PM, Daniel Gruno wrote: We had a bit of a snafu on adding PR titles to the subject lines, but it's been taken care of now. With regards, Daniel. On 02/07/2014 09:57 PM, Henry Saputra wrote: Ah looks like the missing PR title only happen for the emails describing comments from the Github pull requests. - Henry On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra wrote: Hi Jake, Looks like all the emails from the PR has the same subject: "[GitHub] incubator-spark pull request:" Is there a way to get the Title of the pull request included in the Subject line? Thanks, Henry On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell wrote: I just wanted to follow up on my previous comments about the Github webhooks not posting comments, Daniel Gruno and I have been debugging the Github webhooks we had in place to send pull request notifications and we have fixed it so comments for issues and pull requests will now go to the dev@ lists. If anyone replies to this mail it will stay on the dev@ list. -Jake NOTE: This still remains a project/PMC responsibility to ensure communication is recorded as this is coming from a 3rd party we do not control. Communications should be encouraged to occur on our mailing lists. We (infra) are working to make things easier and allow for better integrations and are always open to anyone wanting to help contribute to these efforts. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release of Apache Olingo 1.1.0 incubating (RC03)
No progress on Olingo's release vote. Still one binding vote is missing. What else can we do to get it done? Regards, Stephan On 06.02.14 23:01, "Marvin Humphrey" wrote: >On Thu, Feb 6, 2014 at 7:43 AM, Amend, Christian >wrote: >> Hi IPMC members, >> >> Olingo is waiting to get a third vote for our current release >>candidate. We >> would really appreciate if someone could have a look at this. > >Is it time to enroll Olingo as in our release voting experiment? Or if >anyone >is opposed, how about some votes? > >Marvin Humphrey > >- >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 of Apache Olingo 1.1.0 incubating (RC03)
+1 Looks ok to me ...ant On Mon, Feb 10, 2014 at 8:52 AM, Klevenz, Stephan wrote: > No progress on Olingo's release vote. Still one binding vote is missing. > What else can we do to get it done? > > Regards, > Stephan > > On 06.02.14 23:01, "Marvin Humphrey" wrote: > > >On Thu, Feb 6, 2014 at 7:43 AM, Amend, Christian > > >wrote: > >> Hi IPMC members, > >> > >> Olingo is waiting to get a third vote for our current release > >>candidate. We > >> would really appreciate if someone could have a look at this. > > > >Is it time to enroll Olingo as in our release voting experiment? Or if > >anyone > >is opposed, how about some votes? > > > >Marvin Humphrey > > > >- > >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 of Apache Olingo 1.1.0 incubating (RC03)
Also, why doesn't Olingo go for graduation? I had a little look around the project and don't see anything holding it up. ...ant On Mon, Feb 10, 2014 at 9:35 AM, ant elder wrote: > +1 > > Looks ok to me > >...ant > > > On Mon, Feb 10, 2014 at 8:52 AM, Klevenz, Stephan > wrote: > >> No progress on Olingo's release vote. Still one binding vote is missing. >> What else can we do to get it done? >> >> Regards, >> Stephan >> >> On 06.02.14 23:01, "Marvin Humphrey" wrote: >> >> >On Thu, Feb 6, 2014 at 7:43 AM, Amend, Christian < >> christian.am...@sap.com> >> >wrote: >> >> Hi IPMC members, >> >> >> >> Olingo is waiting to get a third vote for our current release >> >>candidate. We >> >> would really appreciate if someone could have a look at this. >> > >> >Is it time to enroll Olingo as in our release voting experiment? Or if >> >anyone >> >is opposed, how about some votes? >> > >> >Marvin Humphrey >> > >> >- >> >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 of Apache Olingo 1.1.0 incubating (RC03)
Thanks :-) Discussion about graduation will start soon... Stephan On 10.02.14 10:36, "ant elder" wrote: >Also, why doesn't Olingo go for graduation? I had a little look around the >project and don't see anything holding it up. > > ...ant > > >On Mon, Feb 10, 2014 at 9:35 AM, ant elder wrote: > >> +1 >> >> Looks ok to me >> >>...ant >> >> >> On Mon, Feb 10, 2014 at 8:52 AM, Klevenz, Stephan >>> > wrote: >> >>> No progress on Olingo's release vote. Still one binding vote is >>>missing. >>> What else can we do to get it done? >>> >>> Regards, >>> Stephan >>> >>> On 06.02.14 23:01, "Marvin Humphrey" wrote: >>> >>> >On Thu, Feb 6, 2014 at 7:43 AM, Amend, Christian < >>> christian.am...@sap.com> >>> >wrote: >>> >> Hi IPMC members, >>> >> >>> >> Olingo is waiting to get a third vote for our current release >>> >>candidate. We >>> >> would really appreciate if someone could have a look at this. >>> > >>> >Is it time to enroll Olingo as in our release voting experiment? Or >>>if >>> >anyone >>> >is opposed, how about some votes? >>> > >>> >Marvin Humphrey >>> > >>> >- >>> >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
[RESULT] [VOTE] Release of Apache Olingo 1.1.0 incubating (RC03)
Dear all, Thanks for your support! The 72 hours have passed and we have 9 positive votes, of which 3 are binding and 6 are non-binding. We now have the required number of positive binding votes and will therefore proceed with the release. Binding Votes: +1 Ant Elder +1 Florian Mueller +1 Alan D. Cabrera Non-Binding Votes: +1 Jens Huesken +1 Kobler-Morris Sven +1 Michael Bolz +1 Francesco Chicchiriccò +1 Stephan Klevenz +1 Christian Amend Incubator-List Votes: [1] http://incubator.markmail.org/message/eucahz3yegxnuezc Dev-List votes: [2] http://markmail.org/message/ugfeqpzjxrnedpqn [3] http://markmail.org/message/uiklgm25o7upks3t
Re: Github pull request hooks
Daniel & Jake, This is simply nice, appreciate your efforts in integrating this on a quick turn around. Can I become more greedy and ask a follow on question/request? In addition to (or arguably in place of) dev list emails, is it possible to have ASF JIRA tickets updated with github PR’s? I mean similar to git and svn commits if a pull request is created with a title including issue number (like PROJECT-), then it might be useful to have a comment added to the JIRA. This of course raises another question of duplicate emails to the dev list for these PR's. I am looking to address this scenario: A contributor would like to provide a patch to an issue created in a project JIRA; creates a github PR; all discussion of PR is recorded on the JIRA; once a consensus (direct or assumed lazy) is reached, a committer/pmc member will merge the PR closing both github PR and resolving JIRA. Comments on usefulness of this? I am sure I am missing something here. Thanks, Suresh On Feb 8, 2014, at 6:51 AM, Daniel Gruno wrote: > Let me just get some information across to podlings wondering about this > new GitHub stuff we've added, and what is supported so far: > > - It is now possible to relay new GitHub PRs, comments on PRs and > closing/reopening of PRs to your mailing list. > > - It is also possible for all committers in a project to close PRs with > a commit message to the master/trunk branch of a project saying, for > instance, "this closes #1234 on GitHub" in the commit message. > > - This GitHub feature is currently only supported for projects/podlings > that have their primary source repository in Git. If you have an SVN > mirror instead, we are not fully able to support GitHub PR relaying at > the time being, but will support it in the near future. > > - You have to request PR comments to be enabled for your project, > preferably via a JIRA ticket (at > https://issues.apache.org/jira/browse/INFRA ). By default, hooks have > been set up so that only PR opening/closing gets passed on. New setups > will include relaying of comments, but if your project has been set up > for a web hook in the past, you must request it be set up with comment > notification. This is a new default setting, and all projects that now > request PR notifications will automatically receive comments on PRs in > their respective mailing list as well. If you are unsure whether your > project is set up for relaying GitHub messages (and you want this), make > a new JIRA ticket to have it set up, rather one ticket too many than one > too few. > > - Comments _should_ now be nested, so that each new comment has an email > reference to the original PR issue, meaning they will nest in mod_mbox > and your email client if you have nesting/threading enabled. > > - We may, in the future, add the possibility to filter out certain > comments from being relayed to the ML (such as jenkins workflows etc), > but this will all depend on how this initial phase goes along. > > With regards, > Daniel. > > On 02/07/2014 10:02 PM, Daniel Gruno wrote: >> We had a bit of a snafu on adding PR titles to the subject lines, but >> it's been taken care of now. >> >> With regards, >> Daniel. >> >> On 02/07/2014 09:57 PM, Henry Saputra wrote: >>> Ah looks like the missing PR title only happen for the emails >>> describing comments from the Github pull requests. >>> >>> - Henry >>> >>> On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra >>> wrote: Hi Jake, Looks like all the emails from the PR has the same subject: "[GitHub] incubator-spark pull request:" Is there a way to get the Title of the pull request included in the Subject line? Thanks, Henry On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell wrote: > I just wanted to follow up on my previous comments about the Github > webhooks not posting comments, Daniel Gruno and I have been debugging the > Github webhooks we had in place to send pull request notifications and we > have fixed it so comments for issues and pull requests will now go to the > dev@ lists. If anyone replies to this mail it will stay on the dev@ list. > > -Jake > > > NOTE: This still remains a project/PMC responsibility to ensure > communication is recorded as this is coming from a 3rd party we do not > control. Communications should be encouraged to occur on our mailing > lists. > We (infra) are working to make things easier and allow for better > integrations and are always open to anyone wanting to help contribute to > these efforts. >>> >>> - >>> 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.apa
Re: Github pull request hooks
cc'ing infra, as this is really an infra topic. Yes, it is possible - anything is possible, but it will require quite a lot of work from Infra to make this possible. I would suggest you create a new JIRA ticket with this _wish_ and label is as Git+Wilderness, and I'll try to figure out whether we can support this or not. With regards, Daniel. On 02/10/2014 02:44 PM, Suresh Marru wrote: > Daniel & Jake, > > This is simply nice, appreciate your efforts in integrating this on a quick > turn around. Can I become more greedy and ask a follow on question/request? > > In addition to (or arguably in place of) dev list emails, is it possible to > have ASF JIRA tickets updated with github PR’s? I mean similar to git and svn > commits if a pull request is created with a title including issue number > (like PROJECT-), then it might be useful to have a comment added to the > JIRA. This of course raises another question of duplicate emails to the dev > list for these PR's. > > I am looking to address this scenario: A contributor would like to provide a > patch to an issue created in a project JIRA; creates a github PR; all > discussion of PR is recorded on the JIRA; once a consensus (direct or assumed > lazy) is reached, a committer/pmc member will merge the PR closing both > github PR and resolving JIRA. > > Comments on usefulness of this? I am sure I am missing something here. > > Thanks, > Suresh > > On Feb 8, 2014, at 6:51 AM, Daniel Gruno wrote: > >> Let me just get some information across to podlings wondering about this >> new GitHub stuff we've added, and what is supported so far: >> >> - It is now possible to relay new GitHub PRs, comments on PRs and >> closing/reopening of PRs to your mailing list. >> >> - It is also possible for all committers in a project to close PRs with >> a commit message to the master/trunk branch of a project saying, for >> instance, "this closes #1234 on GitHub" in the commit message. >> >> - This GitHub feature is currently only supported for projects/podlings >> that have their primary source repository in Git. If you have an SVN >> mirror instead, we are not fully able to support GitHub PR relaying at >> the time being, but will support it in the near future. >> >> - You have to request PR comments to be enabled for your project, >> preferably via a JIRA ticket (at >> https://issues.apache.org/jira/browse/INFRA ). By default, hooks have >> been set up so that only PR opening/closing gets passed on. New setups >> will include relaying of comments, but if your project has been set up >> for a web hook in the past, you must request it be set up with comment >> notification. This is a new default setting, and all projects that now >> request PR notifications will automatically receive comments on PRs in >> their respective mailing list as well. If you are unsure whether your >> project is set up for relaying GitHub messages (and you want this), make >> a new JIRA ticket to have it set up, rather one ticket too many than one >> too few. >> >> - Comments _should_ now be nested, so that each new comment has an email >> reference to the original PR issue, meaning they will nest in mod_mbox >> and your email client if you have nesting/threading enabled. >> >> - We may, in the future, add the possibility to filter out certain >> comments from being relayed to the ML (such as jenkins workflows etc), >> but this will all depend on how this initial phase goes along. >> >> With regards, >> Daniel. >> >> On 02/07/2014 10:02 PM, Daniel Gruno wrote: >>> We had a bit of a snafu on adding PR titles to the subject lines, but >>> it's been taken care of now. >>> >>> With regards, >>> Daniel. >>> >>> On 02/07/2014 09:57 PM, Henry Saputra wrote: Ah looks like the missing PR title only happen for the emails describing comments from the Github pull requests. - Henry On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra wrote: > Hi Jake, > > Looks like all the emails from the PR has the same subject: > "[GitHub] incubator-spark pull request:" > > Is there a way to get the Title of the pull request included in the > Subject line? > > Thanks, > > Henry > > On Fri, Feb 7, 2014 at 8:30 AM, Jake Farrell wrote: >> I just wanted to follow up on my previous comments about the Github >> webhooks not posting comments, Daniel Gruno and I have been debugging the >> Github webhooks we had in place to send pull request notifications and we >> have fixed it so comments for issues and pull requests will now go to the >> dev@ lists. If anyone replies to this mail it will stay on the dev@ list. >> >> -Jake >> >> >> NOTE: This still remains a project/PMC responsibility to ensure >> communication is recorded as this is coming from a 3rd party we do not >> control. Communications should be encouraged to occur on our mailing >> lists. >> We (infra) are working to ma
Re: Github pull request hooks
On 10/02/14 14:49, Daniel Gruno wrote: I would suggest you create a new JIRA ticket with this _wish_ and label is as Git+Wilderness, and I'll try to figure out whether we can support this or not. I'd prefer it does not create new issues in Jira. What currently it does, post a comment if any issue is referenced, is enough. See for example: https://issues.apache.org/jira/browse/INFRA-7289?focusedCommentId=13896626&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13896626 -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Github pull request hooks
BTW, where is the mapping file between asf ids and github ones? I've seen some members of the apache organization there, but it looks there were manually added or so. Thanks! On 10/02/14 16:01, Sergio Fernández wrote: On 10/02/14 14:49, Daniel Gruno wrote: I would suggest you create a new JIRA ticket with this _wish_ and label is as Git+Wilderness, and I'll try to figure out whether we can support this or not. I'd prefer it does not create new issues in Jira. What currently it does, post a comment if any issue is referenced, is enough. See for example: https://issues.apache.org/jira/browse/INFRA-7289?focusedCommentId=13896626&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13896626 -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Github pull request hooks
Oh well, I went ahead and implemented this :3 GitHub comments that either include a JIRA ticket name or are made on a PR whose title includes a JIRA ticket name, will result in a comment being made in that specific JIRA ticket, similar to what is posted on the ML. This will result in some double posting, as you'll get both a GitHub email and a JIRA email on the ML when this happens. If you don't want this, lemme know and I can filter your project out. We will not make it so that new tickets are created, you'll have to create a ticket first before this will work. This is an old policy decision that I'm not going to go 180 on just yet. With regards, Daniel. On 02/10/2014 02:49 PM, Daniel Gruno wrote: > cc'ing infra, as this is really an infra topic. > Yes, it is possible - anything is possible, but it will require quite a > lot of work from Infra to make this possible. > > I would suggest you create a new JIRA ticket with this _wish_ and label > is as Git+Wilderness, and I'll try to figure out whether we can support > this or not. > > With regards, > Daniel. > > On 02/10/2014 02:44 PM, Suresh Marru wrote: >> Daniel & Jake, >> >> This is simply nice, appreciate your efforts in integrating this on a quick >> turn around. Can I become more greedy and ask a follow on question/request? >> >> In addition to (or arguably in place of) dev list emails, is it possible to >> have ASF JIRA tickets updated with github PR’s? I mean similar to git and >> svn commits if a pull request is created with a title including issue number >> (like PROJECT-), then it might be useful to have a comment added to the >> JIRA. This of course raises another question of duplicate emails to the dev >> list for these PR's. >> >> I am looking to address this scenario: A contributor would like to provide a >> patch to an issue created in a project JIRA; creates a github PR; all >> discussion of PR is recorded on the JIRA; once a consensus (direct or >> assumed lazy) is reached, a committer/pmc member will merge the PR closing >> both github PR and resolving JIRA. >> >> Comments on usefulness of this? I am sure I am missing something here. >> >> Thanks, >> Suresh >> >> On Feb 8, 2014, at 6:51 AM, Daniel Gruno wrote: >> >>> Let me just get some information across to podlings wondering about this >>> new GitHub stuff we've added, and what is supported so far: >>> >>> - It is now possible to relay new GitHub PRs, comments on PRs and >>> closing/reopening of PRs to your mailing list. >>> >>> - It is also possible for all committers in a project to close PRs with >>> a commit message to the master/trunk branch of a project saying, for >>> instance, "this closes #1234 on GitHub" in the commit message. >>> >>> - This GitHub feature is currently only supported for projects/podlings >>> that have their primary source repository in Git. If you have an SVN >>> mirror instead, we are not fully able to support GitHub PR relaying at >>> the time being, but will support it in the near future. >>> >>> - You have to request PR comments to be enabled for your project, >>> preferably via a JIRA ticket (at >>> https://issues.apache.org/jira/browse/INFRA ). By default, hooks have >>> been set up so that only PR opening/closing gets passed on. New setups >>> will include relaying of comments, but if your project has been set up >>> for a web hook in the past, you must request it be set up with comment >>> notification. This is a new default setting, and all projects that now >>> request PR notifications will automatically receive comments on PRs in >>> their respective mailing list as well. If you are unsure whether your >>> project is set up for relaying GitHub messages (and you want this), make >>> a new JIRA ticket to have it set up, rather one ticket too many than one >>> too few. >>> >>> - Comments _should_ now be nested, so that each new comment has an email >>> reference to the original PR issue, meaning they will nest in mod_mbox >>> and your email client if you have nesting/threading enabled. >>> >>> - We may, in the future, add the possibility to filter out certain >>> comments from being relayed to the ML (such as jenkins workflows etc), >>> but this will all depend on how this initial phase goes along. >>> >>> With regards, >>> Daniel. >>> >>> On 02/07/2014 10:02 PM, Daniel Gruno wrote: We had a bit of a snafu on adding PR titles to the subject lines, but it's been taken care of now. With regards, Daniel. On 02/07/2014 09:57 PM, Henry Saputra wrote: > Ah looks like the missing PR title only happen for the emails > describing comments from the Github pull requests. > > - Henry > > On Fri, Feb 7, 2014 at 12:55 PM, Henry Saputra > wrote: >> Hi Jake, >> >> Looks like all the emails from the PR has the same subject: >> "[GitHub] incubator-spark pull request:" >> >> Is there a way to get the Title of the pull request included in the >> Subject li
Re: Github pull request hooks
You can add your id to https://svn.apache.org/repos/private/committers/docs/github_team.txt -Jake On Mon, Feb 10, 2014 at 10:03 AM, Sergio Fernández < sergio.fernan...@salzburgresearch.at> wrote: > BTW, where is the mapping file between asf ids and github ones? > I've seen some members of the apache organization there, but it looks > there were manually added or so. > Thanks! > > On 10/02/14 16:01, Sergio Fernández wrote: > >> On 10/02/14 14:49, Daniel Gruno wrote: >> >>> I would suggest you create a new JIRA ticket with this _wish_ and label >>> is as Git+Wilderness, and I'll try to figure out whether we can support >>> this or not. >>> >> >> I'd prefer it does not create new issues in Jira. >> >> What currently it does, post a comment if any issue is referenced, is >> enough. See for example: >> >> https://issues.apache.org/jira/browse/INFRA-7289? >> focusedCommentId=13896626&page=com.atlassian.jira. >> plugin.system.issuetabpanels:comment-tabpanel#comment-13896626 >> >> >> > -- > Sergio Fernández > Senior Researcher > Knowledge and Media Technologies > Salzburg Research Forschungsgesellschaft mbH > Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria > T: +43 662 2288 318 | M: +43 660 2747 925 > sergio.fernan...@salzburgresearch.at > http://www.salzburgresearch.at > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Github pull request hooks
On Mon, Feb 10, 2014 at 7:01 AM, Sergio Fernández < sergio.fernan...@salzburgresearch.at> wrote: > On 10/02/14 14:49, Daniel Gruno wrote: > >> I would suggest you create a new JIRA ticket with this _wish_ and label >> is as Git+Wilderness, and I'll try to figure out whether we can support >> this or not. >> > > I'd prefer it does not create new issues in Jira. > > What currently it does, post a comment if any issue is referenced, is > enough. See for example: > > https://issues.apache.org/jira/browse/INFRA-7289? > focusedCommentId=13896626&page=com.atlassian.jira. > plugin.system.issuetabpanels:comment-tabpanel#comment-13896626 This sounds like exactly what Suresh was asking for.
Re: Github pull request hooks
Sergio You have to manually edit a file in the private committers area of the Apache SVN repo. The specific file you need to edit and how to edit it was detailed in an email from Noah Slater that went out on the committers@a.o list on 20th January. It's a private list so I am avoiding mentioning specific details on a public list. Once you add the mapping it takes a while for Infra to get round to updating the organisation but it will eventually happen. Also I found that in order for my Apache commits in the GitHub mirrors of Apache repositories to which I contribute to show up on my personal profile I had to add my Apache email as an email address to my GitHub profile Rob On 10/02/2014 15:03, "Sergio Fernández" wrote: >BTW, where is the mapping file between asf ids and github ones? >I've seen some members of the apache organization there, but it looks >there were manually added or so. >Thanks! > >On 10/02/14 16:01, Sergio Fernández wrote: >> On 10/02/14 14:49, Daniel Gruno wrote: >>> I would suggest you create a new JIRA ticket with this _wish_ and label >>> is as Git+Wilderness, and I'll try to figure out whether we can support >>> this or not. >> >> I'd prefer it does not create new issues in Jira. >> >> What currently it does, post a comment if any issue is referenced, is >> enough. See for example: >> >> >>https://issues.apache.org/jira/browse/INFRA-7289?focusedCommentId=1389662 >>6&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#c >>omment-13896626 >> >> > >-- >Sergio Fernández >Senior Researcher >Knowledge and Media Technologies >Salzburg Research Forschungsgesellschaft mbH >Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria >T: +43 662 2288 318 | M: +43 660 2747 925 >sergio.fernan...@salzburgresearch.at >http://www.salzburgresearch.at > >- >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: Github pull request hooks
Thanks Rob. I missed the mail from Jan 20, but with Jake and your help I found it. Thanks. On 10/02/14 16:42, Rob Vesse wrote: Sergio You have to manually edit a file in the private committers area of the Apache SVN repo. The specific file you need to edit and how to edit it was detailed in an email from Noah Slater that went out on the committers@a.o list on 20th January. It's a private list so I am avoiding mentioning specific details on a public list. Once you add the mapping it takes a while for Infra to get round to updating the organisation but it will eventually happen. Also I found that in order for my Apache commits in the GitHub mirrors of Apache repositories to which I contribute to show up on my personal profile I had to add my Apache email as an email address to my GitHub profile Rob On 10/02/2014 15:03, "Sergio Fernández" wrote: BTW, where is the mapping file between asf ids and github ones? I've seen some members of the apache organization there, but it looks there were manually added or so. Thanks! On 10/02/14 16:01, Sergio Fernández wrote: On 10/02/14 14:49, Daniel Gruno wrote: I would suggest you create a new JIRA ticket with this _wish_ and label is as Git+Wilderness, and I'll try to figure out whether we can support this or not. I'd prefer it does not create new issues in Jira. What currently it does, post a comment if any issue is referenced, is enough. See for example: https://issues.apache.org/jira/browse/INFRA-7289?focusedCommentId=1389662 6&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#c omment-13896626 -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - 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 -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Github pull request hooks
On 10/02/14 16:42, Ted Dunning wrote: On Mon, Feb 10, 2014 at 7:01 AM, Sergio Fernández wrote: On 10/02/14 14:49, Daniel Gruno wrote: I would suggest you create a new JIRA ticket with this _wish_ and label is as Git+Wilderness, and I'll try to figure out whether we can support this or not. I'd prefer it does not create new issues in Jira. What currently it does, post a comment if any issue is referenced, is enough. This sounds like exactly what Suresh was asking for. Looks, right. I just wanted to stand out that what the hook currently does is more than enough, and there is no need to automatically create new issues in jira from pull request at github (potential slightly different interpretation of "new issue", just in case). Thanks for this cool integration! -- Sergio Fernández Senior Researcher Knowledge and Media Technologies Salzburg Research Forschungsgesellschaft mbH Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria T: +43 662 2288 318 | M: +43 660 2747 925 sergio.fernan...@salzburgresearch.at http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Shepherding February 2014
Both reporting and shepherding had weak participation this month. Four podlings did not report. BatchEE DeviceMap NPanday Sirona DeviceMap's potential report lingers on their dev list awaiting approval and posting, but it's now too late to participate in review. Only two projects received shepherd reviews this month. Marvin Humphrey Droids John Ament (johndament): Droids is a long standing podling, with a robust code base but without much need for frequent releases. I think graduating into an existing TLP (not their own TLP) would be a good resolution, it helps avoid some of the over head of many binding votes to carry on while still maintaining an area to work in. The people working on droids were fast to respond and give feedback on what's happening, but like is mentioned the list is not very active (in the past 6 months, the main conversations going on were around status of the project). Open Climate Workbench Justin Mclean (jmclean): Report not submitted. Project is up for graduation at board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding February 2014
Sorry my limited Apache time was taken yesterday by catching up "cadence" issues. I checked DataFu and it is getting started in fine shape. The mentors are doing a fine job. I checked Hadoop Development Tools and there is some concern. Development is either stalled since November when dependency issues were uncovered and/or it is being discussed off of the dev mailing list. Would you please move me to a single podling in future months. Regards, Dave On Feb 10, 2014, at 9:23 AM, Marvin Humphrey wrote: > Both reporting and shepherding had weak participation this month. > > Four podlings did not report. > >BatchEE >DeviceMap >NPanday >Sirona > > DeviceMap's potential report lingers on their dev list awaiting approval and > posting, but it's now too late to participate in review. > > Only two projects received shepherd reviews this month. > > Marvin Humphrey > > > Droids > > John Ament (johndament): > >Droids is a long standing podling, with a robust code base but without >much need for frequent releases. I think graduating into an existing >TLP (not their own TLP) would be a good resolution, it helps avoid some >of the over head of many binding votes to carry on while still >maintaining an area to work in. The people working on droids were fast >to respond and give feedback on what's happening, but like is mentioned >the list is not very active (in the past 6 months, the main >conversations going on were around status of the project). > > > Open Climate Workbench > > Justin Mclean (jmclean): > >Report not submitted. Project is up for graduation at board meeting. > > - > 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 of Apache Olingo 1.1.0 incubating (RC03)
Your wayward mentor agrees. Sorry I have lacked time to review this release. Regards, Dave On Feb 10, 2014, at 1:55 AM, Klevenz, Stephan wrote: > Thanks :-) > > Discussion about graduation will start soon... > > Stephan > > On 10.02.14 10:36, "ant elder" wrote: > >> Also, why doesn't Olingo go for graduation? I had a little look around the >> project and don't see anything holding it up. >> >> ...ant >> >> >> On Mon, Feb 10, 2014 at 9:35 AM, ant elder wrote: >> >>> +1 >>> >>> Looks ok to me >>> >>> ...ant >>> >>> >>> On Mon, Feb 10, 2014 at 8:52 AM, Klevenz, Stephan >>> >>> wrote: >>> No progress on Olingo's release vote. Still one binding vote is missing. What else can we do to get it done? Regards, Stephan On 06.02.14 23:01, "Marvin Humphrey" wrote: > On Thu, Feb 6, 2014 at 7:43 AM, Amend, Christian < christian.am...@sap.com> > wrote: >> Hi IPMC members, >> >> Olingo is waiting to get a third vote for our current release >> candidate. We >> would really appreciate if someone could have a look at this. > > Is it time to enroll Olingo as in our release voting experiment? Or if > anyone > is opposed, how about some votes? > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Tool to generate disclaimer, NOTICE, etc. files
On Sat, Feb 8, 2014 at 8:49 AM, Alan Cabrera wrote: > Do you think it would be helpful if we had a tool that generated these > files? It could work like a command line wizard that prompts the person for > licensing information and then generates a valid disclaimer, notice, etc. > files. > > If this is a good idea, what files should we generate? Currently, all I can > think of is disclaimer and notice. > > Maybe it could add the info into the project's DOAP file. If we worked out > the kinks then we could create sbt/gradle/mvn plugins to read the DOAP file > and insert these files into the correct places in the distributions. Apache > RAT could also use this info as well. > > WDYT? I concur with sebb on the extreme challenges of auto-generating NOTICE -- which is a shame because I'd really love it if the Incubator could benefit when you're inspired to write tooling. One thing I think we could use is a tool which parses mbox archives in people.apache.org:/home/apmail/ and generates statistics: * Total emails sent per list (a measure of activity) * Unique addresses participating (a measure of diversity) * Emails sent by Mentors (a measure of Mentor engagement) We expend a lot of volunteer energy on shepherding each month, and I think such an automated tool could help to free up some of that energy for other tasks. There are two main functions for shepherding: 1. Alert the IPMC to podlings which have gone adrift. 2. Provide an outsider view. (I'd add a #3: being exposed to new communities benefits the shepherd, but that varies by individual.) I think that purpose #1 could largely be accomplished using email stats. I don't know if this is something you'd feel motivated to work on, but I thought it was worth mentioning because your original proposal would save time and energy and so would this. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding February 2014
On Mon, Feb 10, 2014 at 11:50 AM, Dave Fisher wrote: > Sorry my limited Apache time was taken yesterday by catching up "cadence" > issues. Yes, I know what you mean. ;) > I checked DataFu and it is getting started in fine shape. The mentors are > doing a fine job. > > I checked Hadoop Development Tools and there is some concern. Development is > either stalled since November when dependency issues were uncovered and/or > it is being discussed off of the dev mailing list. Thanks for coming through for these two podlings! > Would you please move me to a single podling in future months. Done. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding February 2014
Apologies: for some reason I never clicked on the save on the wiki yesterday. It is done now. The only commend I had was on HDT -- I wanted to reply to Dave Fisher's concerns -- but I'll wait for the summary to appear to chime in. Thanks, Roman. On Mon, Feb 10, 2014 at 9:23 AM, Marvin Humphrey wrote: > Both reporting and shepherding had weak participation this month. > > Four podlings did not report. > > BatchEE > DeviceMap > NPanday > Sirona > > DeviceMap's potential report lingers on their dev list awaiting approval and > posting, but it's now too late to participate in review. > > Only two projects received shepherd reviews this month. > > Marvin Humphrey > > > Droids > > John Ament (johndament): > > Droids is a long standing podling, with a robust code base but without > much need for frequent releases. I think graduating into an existing > TLP (not their own TLP) would be a good resolution, it helps avoid some > of the over head of many binding votes to carry on while still > maintaining an area to work in. The people working on droids were fast > to respond and give feedback on what's happening, but like is mentioned > the list is not very active (in the past 6 months, the main > conversations going on were around status of the project). > > > Open Climate Workbench > > Justin Mclean (jmclean): > > Report not submitted. Project is up for graduation at board meeting. > > - > 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: Shepherding February 2014
On Mon, Feb 10, 2014 at 12:50 PM, Marvin Humphrey wrote: > On Mon, Feb 10, 2014 at 11:50 AM, Dave Fisher wrote: >> Sorry my limited Apache time was taken yesterday by catching up "cadence" >> issues. > > Yes, I know what you mean. ;) > >> I checked DataFu and it is getting started in fine shape. The mentors are >> doing a fine job. >> >> I checked Hadoop Development Tools and there is some concern. Development is >> either stalled since November when dependency issues were uncovered and/or >> it is being discussed off of the dev mailing list. > > Thanks for coming through for these two podlings! As a mentor, I actually share Dave's concerns. Not sure what to do about it but it feels like the velocity of the project slowed down quite a bit. I was meaning to start a thread about that. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Github pull request hooks
Hi Daniel (and Sergio and others for all the comments), You rock for such a quick implementation. I think we would like to have enable this for Airavata projects. I will run it by the PMC and if we have a general agreement I will create a INFRA jira. Thanks again, Suresh On Feb 10, 2014, at 10:05 AM, Daniel Gruno wrote: > Oh well, I went ahead and implemented this :3 > > GitHub comments that either include a JIRA ticket name or are made on a > PR whose title includes a JIRA ticket name, will result in a comment > being made in that specific JIRA ticket, similar to what is posted on > the ML. This will result in some double posting, as you'll get both a > GitHub email and a JIRA email on the ML when this happens. If you don't > want this, lemme know and I can filter your project out. > > We will not make it so that new tickets are created, you'll have to > create a ticket first before this will work. This is an old policy > decision that I'm not going to go 180 on just yet. > > With regards, > Daniel. > > On 02/10/2014 02:49 PM, Daniel Gruno wrote: >> cc'ing infra, as this is really an infra topic. >> Yes, it is possible - anything is possible, but it will require quite a >> lot of work from Infra to make this possible. >> >> I would suggest you create a new JIRA ticket with this _wish_ and label >> is as Git+Wilderness, and I'll try to figure out whether we can support >> this or not. >> >> With regards, >> Daniel. >> >> On 02/10/2014 02:44 PM, Suresh Marru wrote: >>> Daniel & Jake, >>> >>> This is simply nice, appreciate your efforts in integrating this on a quick >>> turn around. Can I become more greedy and ask a follow on question/request? >>> >>> In addition to (or arguably in place of) dev list emails, is it possible to >>> have ASF JIRA tickets updated with github PR’s? I mean similar to git and >>> svn commits if a pull request is created with a title including issue >>> number (like PROJECT-), then it might be useful to have a comment added >>> to the JIRA. This of course raises another question of duplicate emails to >>> the dev list for these PR's. >>> >>> I am looking to address this scenario: A contributor would like to provide >>> a patch to an issue created in a project JIRA; creates a github PR; all >>> discussion of PR is recorded on the JIRA; once a consensus (direct or >>> assumed lazy) is reached, a committer/pmc member will merge the PR closing >>> both github PR and resolving JIRA. >>> >>> Comments on usefulness of this? I am sure I am missing something here. >>> >>> Thanks, >>> Suresh >>> >>> On Feb 8, 2014, at 6:51 AM, Daniel Gruno wrote: >>> Let me just get some information across to podlings wondering about this new GitHub stuff we've added, and what is supported so far: - It is now possible to relay new GitHub PRs, comments on PRs and closing/reopening of PRs to your mailing list. - It is also possible for all committers in a project to close PRs with a commit message to the master/trunk branch of a project saying, for instance, "this closes #1234 on GitHub" in the commit message. - This GitHub feature is currently only supported for projects/podlings that have their primary source repository in Git. If you have an SVN mirror instead, we are not fully able to support GitHub PR relaying at the time being, but will support it in the near future. - You have to request PR comments to be enabled for your project, preferably via a JIRA ticket (at https://issues.apache.org/jira/browse/INFRA ). By default, hooks have been set up so that only PR opening/closing gets passed on. New setups will include relaying of comments, but if your project has been set up for a web hook in the past, you must request it be set up with comment notification. This is a new default setting, and all projects that now request PR notifications will automatically receive comments on PRs in their respective mailing list as well. If you are unsure whether your project is set up for relaying GitHub messages (and you want this), make a new JIRA ticket to have it set up, rather one ticket too many than one too few. - Comments _should_ now be nested, so that each new comment has an email reference to the original PR issue, meaning they will nest in mod_mbox and your email client if you have nesting/threading enabled. - We may, in the future, add the possibility to filter out certain comments from being relayed to the ML (such as jenkins workflows etc), but this will all depend on how this initial phase goes along. With regards, Daniel. On 02/07/2014 10:02 PM, Daniel Gruno wrote: > We had a bit of a snafu on adding PR titles to the subject lines, but > it's been taken care of now. > > With regards, > Daniel. > > On 02/07/2014 09:57 PM, Henry Saputra
permission to edit wiki
I would kindly request edit perms to https://wiki.apache.org. UserName: EnisSoztutar Enis
Re: permission to edit wiki
On Mon, 10 Feb 2014, Enis Söztutar wrote: I would kindly request edit perms to https://wiki.apache.org. UserName: EnisSoztutar Karma granted, enjoy! Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [IP CLEARANCE] Apache Phoenix, a SQL query engine for Apache HBase
Just to wrap it up, the 72 hour window has more than passed, so I'm calling this IP clearance complete. Thanks, St.Ack On Thu, Feb 6, 2014 at 11:31 AM, Craig L Russell wrote: > lgtm. > > Craig > > On Feb 6, 2014, at 11:21 AM, Stack wrote: > > > Please check this IP-Clearance form > > > > http://incubator.staging.apache.org/ip-clearance/phoenix.html > > > > It is for a software grant for Apache Phoenix from Salesforce. > > > > Salesforce were the original sponsors of the Phoenix project and > > have donated the code to ASF. > > > > Thanks, > > St.Ack > > Craig L Russell > Architect, Oracle > http://db.apache.org/jdo > 408 276-5638 mailto:craig.russ...@oracle.com > P.S. A good JDO? O, Gasp! > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[VOTE] Graduation of Apache Spark from the Incubator
Hi Everyone, This is a new VOTE to decide if Apache Spark should graduate from the Incubator. Please VOTE on the resolution pasted below the ballot. I'll leave this VOTE open for at least 72 hours. Thanks! [ ] +1 Graduate Apache Spark from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Spark from the Incubator because.. Here is my +1 binding for graduation. Cheers, Chris snip 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 fast and flexible large-scale data analysis on clusters. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Spark Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Spark Project be and hereby is responsible for the creation and maintenance of software related to fast and flexible large-scale data analysis on clusters; and be it further RESOLVED, that the office of "Vice President, Apache Spark" 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 Spark Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Spark 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 Spark Project: * Mosharaf Chowdhury * Jason Dai * Tathagata Das * Ankur Dave * Aaron Davidson * Thomas Dudziak * Robert Evans * Thomas Graves * Andy Konwinski * Stephen Haberman * Mark Hamstra * Shane Huang * Ryan LeCompte * Haoyuan Li * Sean McNamara * Mridul Muralidharam * Kay Ousterhout * Nick Pentreath * Imran Rashid * Charles Reiss * Josh Rosen * Prashant Sharma * Ram Sriharsha * Shivaram Venkataraman * Patrick Wendell * Andrew Xia * Reynold Xin * Matei Zaharia NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be appointed to the office of Vice President, Apache Spark, 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 Spark Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Spark podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Spark podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Spark from the Incubator
+1 To clarify to others, this is an IPCM vote so only the IPCM votes are binding :) On Mon, Feb 10, 2014 at 10:02 PM, Sandy Ryza wrote: > +1 > > > On Mon, Feb 10, 2014 at 9:57 PM, Mark Hamstra wrote: > >> +1 >> >> >> On Mon, Feb 10, 2014 at 8:27 PM, Chris Mattmann >> wrote: >> >> > Hi Everyone, >> > >> > This is a new VOTE to decide if Apache Spark should graduate >> > from the Incubator. Please VOTE on the resolution pasted below >> > the ballot. I'll leave this VOTE open for at least 72 hours. >> > >> > Thanks! >> > >> > [ ] +1 Graduate Apache Spark from the Incubator. >> > [ ] +0 Don't care. >> > [ ] -1 Don't graduate Apache Spark from the Incubator because.. >> > >> > Here is my +1 binding for graduation. >> > >> > Cheers, >> > Chris >> > >> > snip >> > >> > 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 fast and flexible large-scale data analysis >> > on clusters. >> > >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management >> > Committee (PMC), to be known as the "Apache Spark Project", be >> > and hereby is established pursuant to Bylaws of the Foundation; >> > and be it further >> > >> > RESOLVED, that the Apache Spark Project be and hereby is >> > responsible for the creation and maintenance of software >> > related to fast and flexible large-scale data analysis >> > on clusters; and be it further RESOLVED, that the office >> > of "Vice President, Apache Spark" 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 Spark >> > Project, and to have primary responsibility for management >> > of the projects within the scope of responsibility >> > of the Apache Spark 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 Spark Project: >> > >> > * Mosharaf Chowdhury >> > * Jason Dai >> > * Tathagata Das >> > * Ankur Dave >> > * Aaron Davidson >> > * Thomas Dudziak >> > * Robert Evans >> > * Thomas Graves >> > * Andy Konwinski >> > * Stephen Haberman >> > * Mark Hamstra >> > * Shane Huang >> > * Ryan LeCompte >> > * Haoyuan Li >> > * Sean McNamara >> > * Mridul Muralidharam >> > * Kay Ousterhout >> > * Nick Pentreath >> > * Imran Rashid >> > * Charles Reiss >> > * Josh Rosen >> > * Prashant Sharma >> > * Ram Sriharsha >> > * Shivaram Venkataraman >> > * Patrick Wendell >> > * Andrew Xia >> > * Reynold Xin >> > * Matei Zaharia >> > >> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be >> > appointed to the office of Vice President, Apache Spark, 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 Spark Project be and hereby is >> > tasked with the migration and rationalization of the Apache >> > Incubator Spark podling; and be it further >> > >> > RESOLVED, that all responsibilities pertaining to the Apache >> > Incubator Spark podling encumbered upon the Apache Incubator >> > Project are hereafter discharged. >> > >> > >> > >> > >> > >> > >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduation of Apache Spark from the Incubator
+1 On Feb 10, 2014 8:28 PM, "Chris Mattmann" wrote: > Hi Everyone, > > This is a new VOTE to decide if Apache Spark should graduate > from the Incubator. Please VOTE on the resolution pasted below > the ballot. I'll leave this VOTE open for at least 72 hours. > > Thanks! > > [ ] +1 Graduate Apache Spark from the Incubator. > [ ] +0 Don't care. > [ ] -1 Don't graduate Apache Spark from the Incubator because.. > > Here is my +1 binding for graduation. > > Cheers, > Chris > > snip > > 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 fast and flexible large-scale data analysis > on clusters. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Spark Project", be > and hereby is established pursuant to Bylaws of the Foundation; > and be it further > > RESOLVED, that the Apache Spark Project be and hereby is > responsible for the creation and maintenance of software > related to fast and flexible large-scale data analysis > on clusters; and be it further RESOLVED, that the office > of "Vice President, Apache Spark" 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 Spark > Project, and to have primary responsibility for management > of the projects within the scope of responsibility > of the Apache Spark 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 Spark Project: > > * Mosharaf Chowdhury > * Jason Dai > * Tathagata Das > * Ankur Dave > * Aaron Davidson > * Thomas Dudziak > * Robert Evans > * Thomas Graves > * Andy Konwinski > * Stephen Haberman > * Mark Hamstra > * Shane Huang > * Ryan LeCompte > * Haoyuan Li > * Sean McNamara > * Mridul Muralidharam > * Kay Ousterhout > * Nick Pentreath > * Imran Rashid > * Charles Reiss > * Josh Rosen > * Prashant Sharma > * Ram Sriharsha > * Shivaram Venkataraman > * Patrick Wendell > * Andrew Xia > * Reynold Xin > * Matei Zaharia > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be > appointed to the office of Vice President, Apache Spark, 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 Spark Project be and hereby is > tasked with the migration and rationalization of the Apache > Incubator Spark podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator Spark podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > > > > >
Re: [VOTE] Graduation of Apache Spark from the Incubator
+1 -- Mosharaf Chowdhury http://www.mosharaf.com/ On Mon, Feb 10, 2014 at 8:45 PM, Matei Zaharia wrote: > +1 > > On Feb 10, 2014, at 8:27 PM, Chris Mattmann wrote: > > > Hi Everyone, > > > > This is a new VOTE to decide if Apache Spark should graduate > > from the Incubator. Please VOTE on the resolution pasted below > > the ballot. I'll leave this VOTE open for at least 72 hours. > > > > Thanks! > > > > [ ] +1 Graduate Apache Spark from the Incubator. > > [ ] +0 Don't care. > > [ ] -1 Don't graduate Apache Spark from the Incubator because.. > > > > Here is my +1 binding for graduation. > > > > Cheers, > > Chris > > > > snip > > > > 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 fast and flexible large-scale data analysis > > on clusters. > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > > Committee (PMC), to be known as the "Apache Spark Project", be > > and hereby is established pursuant to Bylaws of the Foundation; > > and be it further > > > > RESOLVED, that the Apache Spark Project be and hereby is > > responsible for the creation and maintenance of software > > related to fast and flexible large-scale data analysis > > on clusters; and be it further RESOLVED, that the office > > of "Vice President, Apache Spark" 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 Spark > > Project, and to have primary responsibility for management > > of the projects within the scope of responsibility > > of the Apache Spark 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 Spark Project: > > > > * Mosharaf Chowdhury > > * Jason Dai > > * Tathagata Das > > * Ankur Dave > > * Aaron Davidson > > * Thomas Dudziak > > * Robert Evans > > * Thomas Graves > > * Andy Konwinski > > * Stephen Haberman > > * Mark Hamstra > > * Shane Huang > > * Ryan LeCompte > > * Haoyuan Li > > * Sean McNamara > > * Mridul Muralidharam > > * Kay Ousterhout > > * Nick Pentreath > > * Imran Rashid > > * Charles Reiss > > * Josh Rosen > > * Prashant Sharma > > * Ram Sriharsha > > * Shivaram Venkataraman > > * Patrick Wendell > > * Andrew Xia > > * Reynold Xin > > * Matei Zaharia > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be > > appointed to the office of Vice President, Apache Spark, 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 Spark Project be and hereby is > > tasked with the migration and rationalization of the Apache > > Incubator Spark podling; and be it further > > > > RESOLVED, that all responsibilities pertaining to the Apache > > Incubator Spark podling encumbered upon the Apache Incubator > > Project are hereafter discharged. > > > > > > > > > > > >
Re: [VOTE] Graduation of Apache Spark from the Incubator
+1! 2014-02-10 20:27 GMT-08:00 Chris Mattmann : > Hi Everyone, > > This is a new VOTE to decide if Apache Spark should graduate > from the Incubator. Please VOTE on the resolution pasted below > the ballot. I'll leave this VOTE open for at least 72 hours. > > Thanks! > > [ ] +1 Graduate Apache Spark from the Incubator. > [ ] +0 Don't care. > [ ] -1 Don't graduate Apache Spark from the Incubator because.. > > Here is my +1 binding for graduation. > > Cheers, > Chris > > snip > > 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 fast and flexible large-scale data analysis > on clusters. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Spark Project", be > and hereby is established pursuant to Bylaws of the Foundation; > and be it further > > RESOLVED, that the Apache Spark Project be and hereby is > responsible for the creation and maintenance of software > related to fast and flexible large-scale data analysis > on clusters; and be it further RESOLVED, that the office > of "Vice President, Apache Spark" 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 Spark > Project, and to have primary responsibility for management > of the projects within the scope of responsibility > of the Apache Spark 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 Spark Project: > > * Mosharaf Chowdhury > * Jason Dai > * Tathagata Das > * Ankur Dave > * Aaron Davidson > * Thomas Dudziak > * Robert Evans > * Thomas Graves > * Andy Konwinski > * Stephen Haberman > * Mark Hamstra > * Shane Huang > * Ryan LeCompte > * Haoyuan Li > * Sean McNamara > * Mridul Muralidharam > * Kay Ousterhout > * Nick Pentreath > * Imran Rashid > * Charles Reiss > * Josh Rosen > * Prashant Sharma > * Ram Sriharsha > * Shivaram Venkataraman > * Patrick Wendell > * Andrew Xia > * Reynold Xin > * Matei Zaharia > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matei Zaharia be > appointed to the office of Vice President, Apache Spark, 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 Spark Project be and hereby is > tasked with the migration and rationalization of the Apache > Incubator Spark podling; and be it further > > RESOLVED, that all responsibilities pertaining to the Apache > Incubator Spark podling encumbered upon the Apache Incubator > Project are hereafter discharged. > > > > > >
