You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Jerry Chen (Created) (JIRA)" <ji...@apache.org> on 2011/11/09 19:49:51 UTC

[jira] [Created] (INFRA-4104) JIRA-GitHub Experiment

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

        

[jira] [Closed] (INFRA-4104) JIRA-GitHub Experiment

Posted by "Tony Stevenson (Closed) (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Commented] (INFRA-4104) JIRA-GitHub Experiment

Posted by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150135#comment-13150135 ] 

Jukka Zitting commented on INFRA-4104:
--------------------------------------

Github pull request are currently handled by a simple email script [1] that just forwards the request to the appropriate dev@ list (based on some heuristics).

It should be possible to extend that script to do what you're describing, or as you suggest we could set up a new script using Github web hooks.

I guess the main question is whether you want to actively support Github pull requests as a way to submit patches. Does doing that meet the ASF audit trail requirements? For example with Jira and Bugzilla we at least have a verified email address and a "grant license to Apache" checkbox to associate with all incoming patches. I guess it would be good to check on legal-discuss@ on whether a Github pull request is good enough for us.

As for the individual questions:

> 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? 

Assuming the above concern is addressed, I think these shouldn't be a problem.

> Does Apache have any control over the apache organization on GitHub, or should I contact GitHub? 

We do control the apache account on Github, though the mirroring setup is managed by the Github team. What settings would you need changed?

[1] https://svn.apache.org/repos/infra/infrastructure/trunk/projects/git/bin/email-github.pl

                
> 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

        

[jira] [Commented] (INFRA-4104) JIRA-GitHub Experiment

Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178257#comment-13178257 ] 

Joe Schaefer commented on INFRA-4104:
-------------------------------------

How does this relate to the tool Eric Evans wrote for Cassandra?
Ditto on the request to move this discussion to a mailing list.
                
> 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

        

[jira] [Commented] (INFRA-4104) JIRA-GitHub Experiment

Posted by "Jerry Chen (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150159#comment-13150159 ] 

Jerry Chen commented on INFRA-4104:
-----------------------------------

Thanks for answering my various questions about the current setup.

> I guess the main question is whether you want to actively support GitHub pull requests as a way to submit patches.

The more I think about it, it seems the goal should be making the transition from GitHub pull requests to JIRA issues as painless as possible, for both the contributor and the commiter. I certainly don't want to reinvent wheels and truly bridge GH and JIRA for a 1:1 experience, but at least automate the steps from taking a GH pull request to creating a JIRA issue.

The email script appears to be useful from a notification standpoint, but I think the following steps could/should be automated:
* Creating a new JIRA issue
* Populating the issue with GH pull request patch, comments, author info
* Notifying the contributor on GH on how to transition to JIRA
* Providing pull request with link to JIRA issue, instructions

As far as legal concerns go, we could notify the GH contributor to log into JIRA to explicitly grant Apache the license, and/or indicate future pull request should grant this explicitly in the description of the pull request. I can probably ask legal-discuss@ if this project starts getting underway.

>> Does Apache have any control over the apache organization on GitHub, or should I contact GitHub?
> We do control the apache account on Github, though the mirroring setup is managed by the Github team. What settings would you need changed?

This question was geared more towards how one would update the webhooks for an apache project, assuming everything worked.

As far as next steps go, assuming this project is agreeable and supportable, I see them to be:
* Determine web hook technology. What is lightweight Python and supported by ASF? Something like Flask would be perfect, and I'm looking to avoid something heavier like Django or anything that rhymes with "Qwisted"...
* Test JIRA project. This should be the only component I'd need help with. I can set up my own test GH project, and use a local development server for the Python part, before we would try moving onto ASF's servers.

Thanks,
Jerry
                
> 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

        

[jira] [Commented] (INFRA-4104) JIRA-GitHub Experiment

Posted by "#asfinfra IRC Bot (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/INFRA-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150273#comment-13150273 ] 

#asfinfra IRC Bot commented on INFRA-4104:
------------------------------------------

<danielsh> please have discussions on-list not in the issue tracker, thanks.  (infra-dev@)

                
> 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