Difference between revisions of "CcTools Berlios"

From Creative Commons
Jump to: navigation, search
m
m (Reverted edits by Deyong (talk) to last revision by Nathan Yergler)
 
Line 5: Line 5:
 
'''If you're a user: '''
 
'''If you're a user: '''
  
Not much; we'll still host official [http://goo.gl/Sqtwh gambar animasi] stable versions of our applications at creativecommons.org.  If you want to report a bug or feature request, you'll still record it in the [http://roundup.creativecommons.org/ccpublisher ccPublisher Issue Tracker].  
+
Not much; we'll still host official stable versions of our applications at creativecommons.org.  If you want to report a bug or feature request, you'll still record it in the [http://roundup.creativecommons.org/ccpublisher ccPublisher Issue Tracker].
  
 
'''If you're a developer: '''
 
'''If you're a developer: '''
  
Slightly more, [http://goo.gl/z4wbF contoh kata pengantar] but not much.  developer.Berlios.de runs a fork of the software used to power SourceForge.net, so the overall interface should feel pretty familiar to you.  You will need to create a developer.Berlios.de account if you want to commit code to the ccPublisher project.  You can do that [http://developer.berlios.de/account/register.php here].
+
Slightly more, but not much.  developer.Berlios.de runs a fork of the software used to power SourceForge.net, so the overall interface should feel pretty familiar to you.  You will need to create a developer.Berlios.de account if you want to commit code to the ccPublisher project.  You can do that [http://developer.berlios.de/account/register.php here].
  
 
The most noticeable change is the use of Subversion instead of CVS for source control.  You can find details on how to check out the code using Subversion on the [[Developing ccPublisher 2]] page.
 
The most noticeable change is the use of Subversion instead of CVS for source control.  You can find details on how to check out the code using Subversion on the [[Developing ccPublisher 2]] page.
  
Finally, if you'd like to [http://goo.gl/E1HXO ramalan jodoh] keep up to date on what's going on with the ccPublisher 2 source code, we recommend you subscribe to the cctools-svn list at Berlios.  This list receives all the commit messages for the repository.  You can subscribe [http://lists.berlios.de/mailman/listinfo/cctools-svn here].
+
Finally, if you'd like to keep up to date on what's going on with the ccPublisher 2 source code, we recommend you subscribe to the cctools-svn list at Berlios.  This list receives all the commit messages for the repository.  You can subscribe [http://lists.berlios.de/mailman/listinfo/cctools-svn here].

Latest revision as of 03:57, 22 July 2013

In order to take advantage of Subversion source control and other features, Creative Commons moved the ccPublisher 2 project from SourceForge.net to developer.Berlios.de during November, 2005. What does this mean for you?

If you're a user:

Not much; we'll still host official stable versions of our applications at creativecommons.org. If you want to report a bug or feature request, you'll still record it in the ccPublisher Issue Tracker.

If you're a developer:

Slightly more, but not much. developer.Berlios.de runs a fork of the software used to power SourceForge.net, so the overall interface should feel pretty familiar to you. You will need to create a developer.Berlios.de account if you want to commit code to the ccPublisher project. You can do that here.

The most noticeable change is the use of Subversion instead of CVS for source control. You can find details on how to check out the code using Subversion on the Developing ccPublisher 2 page.

Finally, if you'd like to keep up to date on what's going on with the ccPublisher 2 source code, we recommend you subscribe to the cctools-svn list at Berlios. This list receives all the commit messages for the repository. You can subscribe here.