Re: Github Permissions for Committers
jclouds uses Pull Requests to a GitHub mirror of the (primary) ASF repos as a means of collaborating on submissions with contributors [1]. We then apply the resulting patches to the ASF repos directly [2, 3]. If you'd like more information on how this works, please hop on to #jclouds on Freenode IRC! Regards ap https://wiki.apache.org/jclouds/How%20to%20Contribute [1] http://markmail.org/message/6luklhdm2lpkbccx [2] https://gist.github.com/adriancole/5592785 (lines 27-38) [3] -- Andrew Phillips Apache jclouds - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Github Permissions for Committers
Is it possible for committers to get permissions to manage github issues (mainly ability to close them) for the github apache mirrors? The repo I’d like access to: https://github.com/apache/incubator-storm My github username: ptgoetz Also, I’ve heard that opening pull requests to apache/* repositories should trigger emails to the corresponding dev@ mailing list. But for storm I’m not seeing that happen. Is there anything I need to do to enable that? Thanks, Taylor signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Github Permissions for Committers
Comments inline, if you have any other questions or need any help let me know -Jake On Fri, Dec 13, 2013 at 12:53 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Is it possible for committers to get permissions to manage github issues (mainly ability to close them) for the github apache mirrors? No, you can ask infra to help close all open issues. I would recommend that you commented on them first asking that a patch or jira ticket be submitted for it. The repo I’d like access to: https://github.com/apache/incubator-storm My github username: ptgoetz There is a very small number of people who have access to the Github Apache organization and they are the ones responsible for managing and maintaing the mirrors. It would be very difficult to deal with the auth on an external system and cross usernames which do not match up and maintaining each projects permissions not only internally but also externally. Also the audit trail for a pull request being granted use to the ASF is not straight forward Also, I’ve heard that opening pull requests to apache/* repositories should trigger emails to the corresponding dev@ mailing list. But for storm I’m not seeing that happen. Is there anything I need to do to enable that? You can ask infra to set this up for you. Thanks, Taylor
Re: Github Permissions for Committers
Thanks for the clarification Jake. There is a very small number of people who have access to the Github Apache organization and they are the ones responsible for managing and maintaing the mirrors. It would be very difficult to deal with the auth on an external system and cross usernames which do not match up and maintaining each projects permissions not only internally but also externally. Also the audit trail for a pull request being granted use to the ASF is not straight forward Should we discourage the use of github pull requests for code contributions then? Is there a standard procedure or policy for github vs. JIRA? Thanks in advance, Taylor signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Github Permissions for Committers
There is currently no set standard procedure or policy for Github. Apache Cordova is the only project that I am aware of that uses Github as a means for patch ingestion and they require that all contributors have an ICLA on file and explicitly grant use to the ASF for that submission. Apache Usergrid (incubating) has recently decided to follow this method as well. I am personally not a proponent of this workflow and would recommend using the tools that are currently in place and provided by infra. I have found it much easier to move from project to project and help across the board and be able to search, cross link and reference other projects issues rather than having to leave and use external systems. -Jake On Fri, Dec 13, 2013 at 2:25 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks for the clarification Jake. There is a very small number of people who have access to the Github Apache organization and they are the ones responsible for managing and maintaing the mirrors. It would be very difficult to deal with the auth on an external system and cross usernames which do not match up and maintaining each projects permissions not only internally but also externally. Also the audit trail for a pull request being granted use to the ASF is not straight forward Should we discourage the use of github pull requests for code contributions then? Is there a standard procedure or policy for github vs. JIRA? Thanks in advance, Taylor
Re: Github Permissions for Committers
On Dec 13, 2013, at 2:25 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Thanks for the clarification Jake. There is a very small number of people who have access to the Github Apache organization and they are the ones responsible for managing and maintaing the mirrors. It would be very difficult to deal with the auth on an external system and cross usernames which do not match up and maintaining each projects permissions not only internally but also externally. Also the audit trail for a pull request being granted use to the ASF is not straight forward Should we discourage the use of github pull requests for code contributions then? Is there a standard procedure or policy for github vs. JIRA? Thanks in advance, For projects that I’m involved with that have received github pull requests, when it’s committed into Apache’s repo, we then comment on the pull request something to the effect of: “We’ve committed this into the Apache repo. Can you verify that the functionality works for you and, if so, close this pull request. 95% of the time, the user that submitted the request will then close it themselves. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
