The Forge

This is a user's guide to using the Polarsys forge.

Polarsys accounts are identified using the email address of the individual, except where noted otherwise.

Getting an account

Polarsys uses the Eclipse Foundation account for authentication purposes. Anyone can register for an Eclipse account. If you wish to access the forge as a committer, you need to nominated by an existing project committer and elected by the existing project team before joining a project.

Code

• Git and GitHub are the only SCM used on Polarsys.
• Gerrit is used for code reviews on Polarsys.
• All the code repositories are available at http://polarsys.org/c
  • Use your committer ID (e.g. wbeaton), Do not use your email address
  • For http protocol you need to use the password generated by Gerrit under Settings > Http Password
  • For ssh protocol you need to upload your ssh public key to Gerrit.
• Polarsys on GitHub
• To create a new repository, please file a bug (using the Eclipse Bugzilla) against the Polarsys Working Group. Don't forget to state for which Polarsys project you want the new repository.

Bugzilla

• Bugzilla is available at https://polarsys.org/bugs/
• Log in using your email address
• To create Bugzilla products, components and milestones, please file a bug (using the Eclipse Bugzilla) against the Polarsys Working Group. Don't forget to state for which Polarsys project you want the new items.

Continuous Integration

• https://ci.polarsys.org/ - Hudson docs at Eclipse
• Log in using your email address
• Each Polarsys project can have one Hudson instance (called HIPP)
• HIPP owners can administer their instance
• Using Hudson as a file download service is not appropriate. Promote builds to your project's download area (see below).
• To request a HIPP, please file a bug (using the Eclipse Bugzilla) against the Polarsys Working Group. Don't forget to state for which Polarsys project you want the new Hudson instance.

Downloads

• Each project has a downloads area is available at http://download.polarsys.org/ .
• HIPP can be configured with write access into your project downloads for easy build promotion.
• If you do not use HIPP, you can copy build artifacts to /home/httpd/downloads/yourproject or upload them with an SCP/SFTP client using your Committer ID.
• Download stats are available to all committers from your Eclipse account:
  • https://dev.eclipse.org/committers/committertools/stats.php
• As the downloads area uses donated bandwidth from mirror sites worldwide, download performance is based on Best Effort basis.
  • Organizations that make heavy use of Polarsys downloads and require specific, guaranteed performance can mirror the Polarsys downloads repository using RSYNC from GTLib: rsync://rsync.gtlib.gatech.edu/PolarSys. Please contact the Eclipse webmaster (webmaster at eclipse dot org) if you prefer to rsync from download.polarsys.org directly.

Forums

• http://polarsys.org/forums/
• Log in using your email address
• Projects typically get a single forum for discussion. If more than one forum is required for a project, please contact your working group's Steering Committee.

Mailing lists

• http://polarsys.org/mailman/. Users can then subscribe to the mailing lists using the list's info page.
• To request a new mailing list, please file a bug (using the Eclipse Bugzilla) against the Polarsys Working Group. Don't forget to state for which Polarsys project you want the new list.

Help documentation

Help documentation is not installed yet. Contact Webmaster for more information.

• http://polarsys.org/help/
• Documentation plugins must be uploaded to /home/httpd/help/eclipse/dropins/ by the webmaster. Please contact Webmaster, and provide the location of your doc plugins.

Website

• http://polarsys.org/
• Only designated editors can modify content.
• Project-related content can be modified by project leads committers, and PMC leads and members.
• Log in using your email address

See also

• Eclipse IT Infra Doc