1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in
Version 36 (modified by moorman, 4 years ago)

--

Our Open Source releases

SourceForge (1) has released the following materials under Open Source license:

What is it?LicenseInitial ReleaseStatusWhat does it do?
jsonchkApache License 2.02009-04-24ActivePerl-based JSON validation which provides the location of any validation errors. 2
dotProject patchesGNU GPL (same as original)2009-01-21ActiveSourceForge.net modifications to dotProject
Gallery patchesGNU GPL (same as original)2009-01-21ActiveSourceForge.net modifications to Gallery
Laconica patchesAffero GPL (same as original)2009-01-21ActiveSourceForge.net modifications to Laconica
MantisBT patchesGNU GPL (same as original)2009-01-21ActiveSourceForge.net modifications to MantisBT
Piwik patchesGNU GPLv3 (same as original)2009-01-21ActiveSourceForge.net modifications to Piwik
TaskFreak! patchesGNU GPL (same as original)2009-01-21ActiveSourceForge.net modifications to TaskFreak!
Trac patchesBSD (same as original)2009-01-21ActiveSourceForge.net modifications to Edgewall Trac
WordPress patchesGNU GPL (same as original)2009-01-21ActiveSourceForge.net modifications to WordPress
LimeSurvey patchesGNU GPL (same as original)2008-09-15ActiveSourceForge.net modifications to LimeSurvey
MediaWiki patchesGNU GPL (same as original)2008-09-15ActiveSourceForge.net modifications to MediaWiki
phpBB patchesGNU GPL (same as original)2008-09-15ActiveSourceForge.net modifications to phpBB
ViewVC patchesBSD (same as original)2009-01-21ActiveSourceForge.net modifications to ViewVC

Older releases:

Our license selection

We wanted to pick a license that was simple, easy to understand, permissive, and provided compatibility with the GPL. The Apache License version 2.0 is GPLv3 compatible (as covered by the ASF and the FSF). We've selected the Apache License version 2.0 as our standard license for original software we release effective April, 2009.

In the case of software we've written which is a derivative of existing Open Source software, it is our general practice to license that software under the same license that the original software used. This should help keep licensing requirements, attribution needs, etc. simple.

In those cases where we're producing a derivative, it is our preference to release our patches along side a re-release of the matching original sources. This gives the user a copy of the original code which they can examine along with our changes.

Other Open Source involvement

The SourceForge.net team is a huge fan of Open Source software. In addition to the software we've released through SourceForge.net, our team has been involved with a diverse set of Open Source projects.

Footnotes

1 Some of the software listed here was released under prior names for our company, including VA Software, OSTG, OSDN, or VA Linux Systems.

2 Related to JSON, as found in CPAN.