I'll watch LEGAL-92 with interest.
I saw the maven one which is what caused be to ask - JENA-78 is simpler,
and isn't itself a problem because the contributor has attached the
content of the patch.
At the time, I didn't think it was workable to provide a link because of
lack of clarity over ownership of the content. The JIRA file attachment
statement seems to apply to the link, the not content of the link.
And so we conclude that not every problem can be solved by another level
of indirection.
Andy
On 03/07/11 16:59, Benson Margulies wrote:
I just asked legal-discuss this very question.
https://issues.apache.org/jira/browse/LEGAL-92. Since your JIRA is at
ASF, this should make it good to go.
.
On Sun, Jul 3, 2011 at 11:50 AM, Andy Seaborne
<[email protected]> wrote:
(mentors, mainly)
Suppose a JIRA has patch but it's a link to a file on a non-ASF machine from
someone who has not signed a xCLA. The "Apache can use it" check box is
checked.
Can this be accepted as-is, or should/must the contents be placed on the
JIRA?
The 2 issues I see are
1/ that the link does not provide a proper record of the contents of the
file (the contents may change or disappear)
2/ it's not so clear the submitter has the rights to contribute (could be a
link to someone's content; it's hard to verify the ownership of link
content)
When this happened to me, I asked the contributor to attach the patch, which
they kindly did (more a question to driving JIRA), but to be prepared for
next time, I wanted to check the situation.
Unless there established practice, I'd not accept linked contributions
because of 1 and 2 not leaving a trail in JIRA. The only exception might be
very large contributions - but if it's that large, then a software grant
would be clearer anyway.
Andy
