This page aims to present the CodingTeam software and the advantages and defaults of this forge. First, we will see what we exactly means with the term "forge". After, we will take a look at the history of CodingTeam and we will see the differences between a few free (as in freedom) forges. That'll allow us to write down the list of advantages and defaults of CodingTeam.
If you are searching for a complete and user-friendly presentation of CodingTeam, you could take a look at this webpage!
Explanations on forges
A forge is a collaboration platform allowing collaborative software developement over a network.
Basically, we can imagine two kinds of use: inside an enterprise, to increase the collaboration of employees or for free software projects, to ensure the developement is transparent.
The main goal of a forge is to gather a lot of tools in something integrated and consistent and to make them available to more people so that they can develop their projects. These tools are often:
- a <acronym title="Version Control System">VCS</acronym>
- mailing-lists or forums
- a bugtracker
- a documentation (based on the wiki model)
- a download archive system
- a news system
- a screenshots system
Some forges aim to bring innovant things like chatrooms, translation system, tests and packaging systems, continuous integration tools…
The project is born in march 2005 but the first public version (0.42) was released in june 2007. The first motivation of this project was to make a good and easy to use forge for French-speaking users. Now, CodingTeam is available in many languages and the starting philosophy "lightweight but powerful" can benefit to all!
More than one year after the first public version, developers released the 0.9 wich contains a complete rewrite of the code and a lot of new features. Most important news of this version was OpenForge 0.1 full integration, XMPP integration (<acronym title="Multi User Conference">MUC</acronym>s, presence and avatars), Subversion integration (with a source browser), the Timeline, the Roadmap, the SVG statistics and the notepad.
After that, the 0.9.1 was released and it provides a few bugfixes and improvements (like advanced commit hooks, new timeline…). It also comes with a basic template engine based on the PHP alternative syntax, the ability to make a project private, the ability for anonymous to report a bug or add a comment to a bug…
Now, the 0.9.2 is released and comes with major enhancements. These improvements are the gettext-based translation system, the advanced user-rights management, the ability to filter bugs and the support for multiple templates themes.
The 0.9.3 was released in june 2010 and came with Mercurial support, the new dashboard, the private messaging system and the notification system.
Differences between free software forges
This section aims to provide a lot of useful informations to easily differenciate any forge software.
Before, SourceForge was a free software but in 2001, they stopped that and now all versions of the SourceForge software are proprietary. As SourceForge was a pionnier, a few forges are based on SourceForge 2.5.
|Sources: Wikipedia and The Big Internet|
|Savane||16||Yes.||Yes.||This forge has been written for GNU Savannah.|
|GForge||18||Yes.||Yes.||The GForge Group works on a proprietary version of their software.|
Besides that, there are a few innovant softwares that are not based on anything existant.
|Sources: Wikipedia and The Big Internet|
|Trac||16||Yes.||Yes.||This software was not developed for a specific forge.|
|ShareSource||1||No.||No.||This project is initially developed for ShareSource.org.|
|CodingTeam||1||Yes.||No.||The forge we are talking about. ;)|
The good and the bad with CodingTeam
- CodingTeam is innovative
It brings a few new things: Jabber/XMPP, OpenForge, SVG statistics…
- CodingTeam is easy to use
Just look at it! :)
- CodingTeam is in perpetual development
And a lot of things are planned!
- CodingTeam is not very popular
So, there are less people to use the software and to find bugs.
- CodingTeam is developed by only one developer
Even if there are a few contributors, one developer is not enough to make something really reliable.
As we could see before, popular forges are maintened by a lot of contributors. But, contributors come when a project is popular. So, if we want CodingTeam to grow up, everyone need to add his bricks to the wall. And everyone could.