Re: [incubation] "Contribution Record" field in CQ

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

Having the public record of the contribution is a matter of operating in an open and transparent manner.

Attaching the contribution as either straight code or as a patch provides us with a very convenient and consistent way of keeping track of the contribution. While Git repositories are relatively durable and commits can't be tampered with, repositories do disappear, move, get merged, etc. and it's possible (however improbable) that we may lose track of it. 

In more practical terms, attaching code to the CQ is relatively easy for you, but relatively time consuming for the IP Team. I think that everybody will agree that anything that anything that we can do to make the IP Team just a little more productive is better for everybody.

So, please follow the instructions and attach the code.

FWIW, IPZilla is a fairly old system that we put in place long before Git came onto the scene. We've been talking (informally) internally about an eventual replacement system which may provide us with some opportunities for better automation. We haven't opened a bug, but we'll be sure to let everybody in the community know when we're ready to start getting input into the process.

Wayne

On Wed, Jul 26, 2017 at 5:04 AM, Rémi Druilhe <remi.druilhe@xxxxxxxxx> wrote:

I successfully pushed my new content to Gerrit and added the link to the CQ, in the "Contribution Record" field. Now that the CQ has been sent, the IP Genie Eclipse is asking me the source code of the new content.

Because there is already the link to the Gerrit commit in the CQ, should I duplicate the source code both in the Gerrit and in the CQ (through an attachment as the Genie is asking me to do) ?

--
Rémi DRUILHE

2017-07-25 20:00 GMT+02:00 Wayne Beaton <wayne.beaton@eclipse-foundation.org>:

IPZilla is a not a publicly-facing property (it's accessible only to Eclipse Foundation committers) and so doesn't count as a transparent means of presenting content to the community.

Open source projects should operate in an open and transparent manner.  Any content destined for the project's code base should have some public record of contribution. Otherwise, the project is operating (at least in part) hidden from community involvement and so counter to the open source rules of engagement. The initial contribution is a bit of a special case and gets a pass.

Please don't use a bogus URL in this field.

Let's take the conversation regarding whether or not this field should be optional to Bug 520162 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=520162).

Wayne

On Tue, Jul 25, 2017 at 1:49 PM, Jens von Pilgrim <developer@xxxxxxxxx> wrote:

I had the same problem. I simply added a dummy link (https://bugs.eclipse.org/bugs/show_bug.cgi?id=00000) ;-)
I would suggest to make that field optional. If there has been a bug or issue, fine. But if there isn't, you cannot make up something.
At least, the description could be improved.

Regards,
Jens

_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

--

Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation

_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

--

Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation