The key here is to provide a public record of the contribution. For an initial contribution, you can (as Didier suggests) cite the project creation tracking bug. I'd rather that you not do this for later contributions.
Pushing the content as a Gerrit review request would be a great way to provide a public record of the contribution and give the project team and community an opportunity to comment/review the contribution. AFAICT, however, you're set up for Gerrit, but aren't using it. You might create a new record in your issue tracker (Bugzilla) that describes the functionality, where it comes from, etc. You don't need to actually attach a patch; that would be nice, but is not strictly necessary. Having that record is a public means of looking back to see where the decision to include the functionality was made and give the project's community a reasonable opportunity to participate in the process. HTH, Wayne On Tue, Jul 25, 2017 at 11:41 AM, Rémi Druilhe <[email protected]> wrote: > I thought that pushing new code was supposed to pass through the IP > process first. Because it is private code, I do not have any link to it. > > So according to your mail, I am supposed to push the code first on our > public repository and point to the commit URL in the CQ, am I right? > > -- > Rémi DRUILHE > > 2017-07-25 17:36 GMT+02:00 Wayne Beaton <wayne.beaton@eclipse- > foundation.org>: > >> I've opened a bug report to mark the field as required. >> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=520162 >> >> Wayne >> >> On Tue, Jul 25, 2017 at 11:30 AM, Wayne Beaton < >> [email protected]> wrote: >> >>> You should specify a URL in that field that points to the public record >>> of contribution. This might be a link to the Gerrit commit, or a GitHub >>> pull request. It could even be a link to a URL in a mailing list that >>> itself contains a link to the actual contribution. The value ends up in the >>> "URL" field on the CQ. >>> >>> The basic idea is that projects should be operating transparently; part >>> of this is that all contributions must have a public record. >>> >>> HTH, >>> >>> Wayne >>> >>> On Tue, Jul 25, 2017 at 10:41 AM, Rémi Druilhe <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> I am trying to create a new CQ for adding a new set of modules >>>> developed internally to the Eclipse public repository. On the CQ form, a >>>> field is named "Contribution Record" and seems optional (there is no star >>>> on it). I don't know what kind of information is required in this field, so >>>> I fills up the form and let this entry empty. But when I validate, the web >>>> page tell me that this field must be a valid URL. >>>> >>>> What am I supposed to put inside this field? >>>> >>>> Thanks, >>>> >>>> Best regards. >>>> -- >>>> Rémi DRUILHE >>>> >>>> _______________________________________________ >>>> incubation mailing list >>>> [email protected] >>>> 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 >>> >> >> >> >> -- >> Wayne Beaton >> Director of Open Source Projects >> The Eclipse Foundation >> >> _______________________________________________ >> incubation mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/incubation >> >> > > _______________________________________________ > incubation mailing list > [email protected] > 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 [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
