You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Tony Stevenson (Closed) (JIRA)" <ji...@apache.org> on 2012/01/10 19:44:40 UTC
[jira] [Closed] (INFRA-4104) JIRA-GitHub Experiment
[ https://issues.apache.org/jira/browse/INFRA-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson closed INFRA-4104.
---------------------------------
Resolution: Invalid
This should be on the ML not bug tracker,
> JIRA-GitHub Experiment
> ----------------------
>
> Key: INFRA-4104
> URL: https://issues.apache.org/jira/browse/INFRA-4104
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: Git
> Reporter: Jerry Chen
> Priority: Minor
>
> Hello Infra,
> I am currently a committer for the Libcloud project. We have occasional pull requests created in GitHub which we manually have to reply and request the contributors to create JIRA tickets.
> Theoretically, we could use GitHub's pull request web hooks to:
> * Create a new JIRA issue
> * Link or copy the content of the GitHub pull request issue
> * Provide instructions on the GitHub pull request, and provide a link to the JIRA issue
> * Close the GitHub pull request
> My questions for Infrastructure are:
> * Would it be possible to create a test JIRA project so we don't have to pollute the LIBCLOUD JIRA?
> * Would infra be willing to host the webhooks (small Python app perhaps) which GitHub would call on a pull request?
> * Does Apache have any control over the apache organization on GitHub, or should I contact GitHub?
> If this experiment proves to be successful, we could share this technology with the rest of the Apache projects that have an active community for GitHub, to at least reduce the barrier to entry for contributions.
> Cheers,
> Jerry
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira