Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Development Resources/Committer Cheat Sheet

< Development Resources
Revision as of 06:12, 26 March 2015 by Unnamed Poltroon (Talk) (Created page with "=Getting Help= * For IT assistance--including help with account access--contact the [mailto:webmaster@eclipse.org webmaster@eclipse.org] or open a bug (see below). * For ques...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Getting Help

  • For IT assistance--including help with account access--contact the webmaster@eclipse.org or open a bug (see below).
  • For questions concerning the intellectual property due-diligence process, contact emo-ip-team@eclipse.org.
  • For questions regarding the Eclipse Development Process, or anything else regarding open source project management, contact emo@eclipse.org.

The Webmaster team uses Bugzilla to track requests. You can create the request directly yourself, or the Webmaster may do it on your behalf. In general, these requests are found under the Community bugzilla product, but if it makes more sense, you can open a bug under your project's Bugzilla product with the webmaster@eclipse.org in copy.

Open a bug to request help with:

Identity

We maintain your identity with your Eclipse Foundation Account. Visit My Account (a link to "Edit my account" is on the top of most of our web pages). Use this page to:

  • Edit your personal information (email address, postal address, other contact information);
  • Access your project's Hudson instance;
  • Other committer tools.

Every account has a "committer id" (this is typically your first initial and your last name, e.g. "wbeaton"), a primary email address, and passord.

Use your email address to log into most of Eclipse Foundation services, with these exceptions:

  • Use your committer id and password to authenticate via SSH with Git or Gerrit; and
  • When accessing Gerrit via HTTPS, use your committer id in combination with the password generated by Gerrit.

Back to the top