Development Resources/Reaching out
Eclipse committers, you aren't alone. If you're seeking advice, guidance, or even just an opinion from fellow committers, please refer to the channels below. Make use of these channels since we're a Community! If you're an Eclipse user and need assistance, please use the newsgroups. Someone will help you there.
- Inquiries about a specific project should be addressed on the project's newsgroup or -dev mailing list.
- Inquiries about the servers should be addressed to email@example.com
- Inquiries about coding, builds or release engineering should be addressed to the cross-project-issues-dev mailing list. If someone there cannot help, they will indicate who can.
- Inquiries about the development process, guidelines, best practices and HOWTO's should be addressed to your project lead, who can escalate the issue with your PMC (typically via their mailing list) your Mentor or the Architecture Council
- Inquiries and announcements to the entire committer population should be sent to the eclipse.org-committers mailing list. We like seeing that channel get active, but you must provide an alternate channel for follow-up discussion. This can be a bug (preferred), a project newsgroup, or another mailing list.
- All committers are subscribed to this mailing list.
- This list is moderated, however, and the friendly moderators may recommend a better channel for your inquiry.
eclipse.org-committers Moderation Guidelines
- Inquiries and announcements deemed appropriate for the entire committer population will be approved if the message contains a link to a follow-up channel.
- Foundation staff announcements are not generally moderated
- Follow-up discussion will always be rejected
- Messages that are too narrow in scope may be rejected, and the moderator will suggest an alternate channel.
Moderators will always provide an explanation for rejected messages.