Some additional background: contributions via mail lists,
actually a little broader than the EPL, a subtle but important point). The
reason why we ask that contributions come in via Bugzilla is that when you
just a little extra comfort for the legal types. Plus, as I mentioned before
Bugzilla is where most of the interesting conversations happen J
To be honest, I’m not entirely sure that this is written
in the IP Policy. I believe it is documented in the development process “How
To’s”. But it is most certainly a best practice for tracking IP provenance,
and the convention used throughout Eclipse.
I’ve asked this before: who are EPS’s mentors? A lot
of these helpful hints should be provided by them. Even if our documentation
was absolutely perfect --- and its not --- there is a lot to digest and we had
hoped that the mentors would be a valuable resource for new projects starting
[mailto:eclipselink-dev-bounces@xxxxxxxxxxx] On Behalf Of Douglas Clarke
Sent: Monday, November 05, 2007 9:51 AM
To: Dev mailing list for Eclipse Persistence Services; Tom Ware
Cc: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Re: Code submission
Thanks for clarifying what the issue was with original email. We will review
the IP policy again and ensure our evolving development process conforms. I was
under the impression that all email and newgroup posts were covered under EPL.
We are transitioning to a bugzilla centric process where attachements to the
bugs can be used for communicated proposed changes for peer review/discussion
and track completed changes.
From Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent Thu 01/11/2007 7:17 PM
To Tom Ware <tom.ware@xxxxxxxxxx>
Cc Dev mailing list for Eclipse Persistence Services
Subject Re: [eclipselink-dev] Re: Code submission
No, it wasn't calling it a "code submission" that was the problem
that caught my eye: it was including the patch in the email (http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00219.html).
The patch needed to be attached to a bug, not be in an email; that's an IP
P.S. You can call it whatever you want :-)
Tom Ware wrote:
In this case, the issue is just the choice of words
for the subject line.
Guy is a committer and contributing a relatively small change to the code
base that he has developed himself. I guess we should be careful not to
use the words "Code Submission" when adding this kind of code.
eclipselink-dev mailing list