--- Anil Patel <[EMAIL PROTECTED]> wrote: > Chris, > How is the work done at the developer's conference > is different then work > done at my Home. As long as I create a Jira Issue > and submit a patch there. > The advantage will be I'll have commiter accros the > table who can get it > from Jira and review and apply the patch. > > Anil Patel
If you're the only worker on the the contribution, there is no difference, however as soon as you get two hands (or minds) on that contribution there is collaboration and there's a potential issue. Only one of you can submit the patch to JIRA or to SVN. Therefore only one of you has formally granted license to Apache. There is no physical proof that the person who collaborated and has copyright of the material he's contributing or has granted sufficient license to Apache (or relinquished enough rights to another entity so that they may legally grant license to Apache) for inclusion of that code enhancement in the project and in all the liberal ways that Apache can use a contribution. Without additional consideration, the person pressing the Apache grant radio button in JIRA is lying as they are not the "Licensor" and cannot enter the agreement. Because the Developers Conference is not an official Apache gathering, I would suspect any collaborated contribution would be a similar scenario to the sandbox scenario that is being discussed on the general-incubator ML, regardless of the level of involvement of a committer in the conference. (If that were the case, I would just need to ask one of the committers to have involvement in the sandbox. I don't think that is sufficient to cross the legal hurdle of who the licensor is.) IANAL, and I'm not sure what the potential repercussions are. I'm simply asking you guys to consider what the potential repercussions are because it would be an obvious shame for all that hard work to have the potential to be subject to the scrutiny of IP law when we're all here just trying to contribute in the spirit of open source. Regards, Chris
