Sorry... I should have read through the full email chain before I
responded.
The "Handling Git Contributions" link is intended to provide
specific help for contributions coming from a public (non-Eclipse)
Git repository (e.g. GitHub). I don't believe that this is the case
here.
The link that Ian sent probably is pretty accurate. The first and
perhaps most important part is to make yourself known: discuss your
contribution on the project mailing list; make your contribution
available through some public channel. Since I assume that the
contribution is currently not available in a public forum, attaching
it to a Bugzilla record is probably the right way to go.
The process can be summarized as such:
1. Get the project to want your contribution (use transparent forums
to discuss the contribution).
2. Make the contribution available for open community and committer
review.
3. An existing project committer will complete a "contribution
questionnaire" and send the contribution off to the IP team for
their review. This may take a while depending on the size and
provenance of the contribution.
4. When the IP team approves the contribution, the committers will
push it into the public repo.
In parallel with #3, the project committers will nominate the
contribution's developers to become committers on the project. By
the time step #4 rolls around, your developers should be part of
that group of committers.
As part of the IP check, you will have to assert the code owner's
(generally the employer) permission to contribute the code to open
source and answer some provenance questions.
If you have any questions, let us know.
HTH,
Wayne
On 02/26/2013 04:00 PM, Wayne Beaton
wrote:
That gives the general gist. I like the text and may leverage some
of it on some other pages.
However, the "attach your code on bugzilla bit" is not longer
accurate.
http://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions
Wayne
On 02/26/2013 02:04 PM, Ian Skerrett
wrote:
John,
Here
is a link to a document describing how to do a large
submissions.
http://wiki.eclipse.org/TM_and_RSE_FAQ#How_do_I_submit_a_contribution_beyond_a_simple_bug_fix.3F
There
are lots of people on this list that can also help you, so
please don’t be shy about asking. I think other people
will have similar questions so the discussion will help
others.
Ian
From: paho-dev-bounces@xxxxxxxxxxx
[mailto:paho-dev-bounces@xxxxxxxxxxx]
On Behalf Of John Rotach
Sent: February-26-13 12:27 AM
To: General development discussions for paho
project
Subject: Re: [paho-dev] Software Contributions to
the Paho Project
Hello Andy,
I apologize. I have been conversing
with Scott de Deugd about this and now realize it has
been off of the list.
- I had some trouble creating a Bugzilla
report to get this started but believe I've got it
figured out now. Report to be created this week.
- I spoke with Scott about getting a list
of submission tips (do's / don't do's for code
submissions) so we could start cleaning up the code
before submission. He's working on that now.
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
|
