SOURCEFORGE
ISAE opensource project management

The ISAE FORGES offer digital services for the management of ISAE projects.

There are four different forges, adapted to different use cases:

• https://forge.isae.fr : to manage ISAE internal projects;
• https://openforge.isae.fr: to manage ISAE projects that may include external users (in particular, research projects)
• https://eduforge.isae.fr : to manage projects carried out by students within the framework of ISAE training courses
• https://sourceforge.isae.fr (soon): to manage “open source” ISAE projects with the possibility for users to open an account on the platform to contribute to projects.

The main specificity of the forges is related to the types of users that can connect to them and browse or contribute to the projects. More specifically, the characteristics of the different forges are presented in the following table:

Comparative features of the different ISAE forges

FeaturesForge	Openforge	Eduforge	Sourceforge
Internal Projects	External Projects	Teaching Projects	Open Source Projects

ISAE Users|||||

External Users declared ISAE

Self-declared users

Single sign-on (CAS)

ISAE Authentication (LDAP )|||||
Local Instance Authentication|||||
Internet access|||||
|Version Redmine|3.4.6|3.4.6|3.4.6|3.4.6|

Each project space can be public or private. A public project space is visible to all users of the forge, a private project space is only visible to members of the project.

FORGES ISAE, powered by Redmine

ISAE forges are mainly based on Redmine, a web application for flexible project management. Redmine is an opensource software under GPL license and written in the Ruby language.

The main features of Redmine are :

• Multi-project management;
• Public or Private project by project space;
• Role-based control;
• Flexible tracker system (ticket types);
• Gantt and Calendar associated with ticket dates;
• News, Documents and files;
• RSS feeds, Email notification;
• Wiki by project space;
• Time management;
• Specific fields for tickets, time tracking;
• Source Code Management (SCM) associated with SVN and GIT;
• Forum by project space;
• Ticket creation by email;
• Multiple authentication, including LDAP ISAE;
• Self-registration of utilities (only on sourceforge);
• Multilingual;
• etc.

For more information about Redmine, please visit the original website: https://www.redmine.org.

Common documentation for forges

The software used in the forges is documented on their associated website.

• The complete documentation of Redmine is available here.
• For more information on SVN, see https://subversion.apache.org/docs/
• For more information on GIT, see https://git-scm.com/documentation

The forge instances are extended with some plugins, including :

• The Wiki is extended with two plugins allowing many additional functions:
  • Redmine Wiki Extensions Plugins: see the documentation;
  • Redmine Wiki Lists: allows to query tickets in plugins. See the documentation
  • Wiking: extends Wiki syntax. See documentation;
• The list of Macros usable in WIKI fields (in the WIKI, but also in tickets, forum, etc.) is available here by typing the macro @macro_list@ in a Wiki field;
• AGILE: facilitates the handling of tickets in particular in the framework of an AGILE method (SCRUM, Kanban) - see the documentation of the plugin here.

Make a request on the ISAE IS Service Center to create a new project space in one of the proposed forges.

Specificities of the FORGES

OPENFORGE

Access

This system is accessible from the Internet but an ISAE or “openforge” account is required to access the platform. Once connected, the project spaces can be public or private, i.e. visible to the members of the platform (public) or only to the project (private).

Source Code Management

The default SCM of openforge is SVN.

Each project space can be set up by the local administrator of the space, with different activities: Ticket management, Wiki, File repository, Discussion forum, Announcement publication, and Source repository (SVN).

Concerning the source repository, it is Apache Subversion - SVN. To associate a repository to a project space, no configuration is necessary except the validation by the local administrator of the project, of the repository service in the Modules sub-tab of the project configuration. Then, access to the repositories is possible using the URLhttps://openforge.isae.fr/svn/. For example, the checkout of the “Sandbox” project whose identity is sp will be possible with the command :

svn co https://openforge.isae.fr/svn/sp

SOURCEFORGE

Access

This system is accessible from the Internet and the “public” project spaces (a parameter of your projects) are visible without having an account on the platform. It is possible to connect with an ISAE account or users can create an account and thus access the requests in the projects (to be able to post a request, a bug, a message in a forum, etc).

Source Code Management

The sourceforge SCM is based on the GIT tool. Many tutorials exist on the use of this tool, see for example the documentation of the tool on the GIT site or a guided simulation allowing you to make your first steps with GIT.

By default a GIT repository is created when a project space is created. The repository is visible in the REPOSITORY tab of the forge.

Assuming your project has the identifier ( also used in the project URL), access to the associated GIT repository should use the :

git https://sourceforge.isae.fr/git/<IdentifiantProjet>

For example, once you have initialized your local GIT repository, the following command will initialize the sourceforge repository to that local repo:

Then, it is possible to synchronize the last changes:

More information