www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-4104) JIRA-GitHub Experiment
Date Tue, 15 Nov 2011 01:02:13 GMT

    [ 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

        

Mime
View raw message