On 7/05/2013 1:19 PM, Martin Buchholz wrote:
On Thu, May 2, 2013 at 9:06 AM, Andrew Hughes <[email protected] <mailto:[email protected]>> wrote:HotSpot is even more of a problem because not being able to commit directly risks people losing credit for the work they've done and, with an open source project, credit is the only reward. It *is* possible with mercurial to create/import/manipulate changesets with a different user, so that credit remains with the true author even when first submitted into mercurial by an Oracle employee. And that should be the standard practice.
Absolutely! If a non-Oracle person can create a changeset then the Oracle sponsor can import it and push via JPRT. Otherwise the sponsor should create a changeset with a Contributed-by attribution.
David
