Collaborative development tool
- " In February 2009 some of the developers of GForge continued development of the old open source code under the new name of FusionForge "
'GForge' is a fork of the 2.61 SourceForge code. It includes Jabber support: system events, such as bug submissions, are optionally sent via jabber and email; an easier installation: due to removal of much SF.net-specific code, like caching and image servers, many install dependencies could be eliminated; a new interface, which should make it easier to navigate as well as know your present location; and code cleanup: since GForge does not need to scale to 500,000+ users, various hacks and optimizations have been removed.
DocumentationSee http://gforge.org/docman/?group_id=1 for a complete list of documentation
released on 9 December 2016
|License||Verified by||Verified on||Notes|
|License:GPLv2orlater||Janet Casey||24 July 2003|
Leaders and contributors
Resources and communication
|Bug Tracking||VCS Repository Webview||http://gforge.org/tracker/?atid=105&group_id=1&func=browse|
|Required to use||Apache 1.2x or later|
|Weak prerequisite||GNU Mailman (for mailing list support)|
|Required to use||PostgreSQL 7.1 or later|
|Required to use||PHP 4.x or later|
|Weak prerequisite||jabberd (for Jabber support)|
|Weak prerequisite||JPGraph (for Gantt charting and graphing support)|
|Weak prerequisite||PHP Accelerator|
This entry (in part or in whole) was last reviewed on 15 March 2017.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.