www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Blue (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-249) Use GitHub issues instead of JIRA
Date Wed, 18 May 2016 17:28:13 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289389#comment-15289389

Ryan Blue commented on LEGAL-249:

It sounds like you agree with the assessment of the legal requirement here: to track the intent
to contribute in ASF infrastructure.

Perhaps your gray area argument would be understandable with a specific example. If the ASF
mailing list for a project gets a copy of a patch submission, what is a situation where the
contribution could be repudiated later and we would not be able to show intent? What is a
situation where we would be "unable to leverage" this record?

I think that using github makes this clearer because we can argue that a "pull request" against
apache/foo project inherently constitutes intent to contribute, and a github workflow uses
pull requests far more often than patches attached to github issues.

> Use GitHub issues instead of JIRA
> ---------------------------------
>                 Key: LEGAL-249
>                 URL: https://issues.apache.org/jira/browse/LEGAL-249
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Chris Riccomini
> Is it possible for us to use GitHub issues instead of JIRA for issue tracking and discussion?
This was raised on a new project that we're beginning to incubate (Airflow). I asked INFRA,
and they suggested that I ask LEGAL as well as the board.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message