Thanks for your interest in this project. Contributions to the Eclipse Packaging Project are most welcome. There are many ways to contribute, from entering high-quality issue reports, to contributing code or documentation changes.
For instructions on how to run a build locally, follow the instructions of the README.md.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Contributor Agreement:
Please ask questions via discussions.
This project uses GitHub issues to track ongoing development and issues. Be sure to search for existing bugs before you create another one. Contributions are always welcome!
For each EPP package, there is a committer who is the package maintainer. The maintainer is expected to participate in overall project discussions and to be involved in making decisions that affect the maintained package.
If someone is a committer on another Eclipse project, and they state they are interested in contributing and maintaining an EPP package or, transferring ownership of an existing EPP package, that history with other Eclipse projects suffices for them to be nominated and voted-in as a committer. This differs from most other projects where, for good reason, a person must (usually) have a history of contributions to that specific project, not just Eclipse in general. There still could be reasons an existing committer would note "no" (-1) for a nomination, for example, "no, I am the current maintainer and I do not agree to this!" Normally people do not vote "0" just because they have no first hand knowledge of a person's committer history (as they might on other projects), but vote "+1" if basic criteria are met, to be welcoming and supportive of new people coming in.
Normally, as with most other Eclipse projects, unless a committer explicitly "resigns" there would be no automatic removal of a committer just because package responsibility is transferred, except eventually the usual "inactive" reasons would apply. If someone is no longer responsible for maintaining a package and has not been active on mailing lists, issues, or discussions for a period of roughly six months, the Project Lead can remove them via Eclipse Portal for "inactivity". And, of course, committers should explicitly resign, when appropriate, such as when they are changing responsibilities and know they have no interest or time to be involved.