Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Interested in Becoming Orbit committer

Hey Scott,

The interesting thing is to understand what things you (potential committers in general) would work on.  Eclipse projects that have approval to use some third party libs should also look to have these libs bundled in Orbit.  The libs may already be a bundled or you may need to "contribute" bundled versions.  In the former case you are done and there is no particular need to take on the responsibilities of being an Orbit committer.  In the latter case you can decide to contribute and maintain the bundled version (and future versions) of the libs you need.  In that way it is akin to how it works on other projects:  you are coming with an initial contribution and committing to nurturing and maintaining it.

Look at it this way, if you are already setting up and maintaining bundled versions of third party libs in your project then you are a prime candidate for being an Orbit committer and doing that work in Orbit where it can be easily discovered and shared.

Make sense?


Scott Lewis <slewis@xxxxxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

10/23/2006 02:10 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

[orbit-dev] Interested in Becoming Orbit committer

This is Scott Lewis, committer and project lead for the Eclipse
Communication Framework.

I'm interested in becoming an Orbit committer.  Would this be possible?  
What should I do to make it so (assuming this is OK with existing
committers, of course).



orbit-dev mailing list

Back to the top