Migrate to Allura


Migrate from the current SourceForge.net setup to the new Allura platform.


  • The transfer was initiated on 2012-12-08


  • Changi
  • Jyhem
  • you?

What end-users need to know



UTF-8 encoding of web view


Needs to be updated

Check these periodically

Things to test

SVN browse

Eventually, we will loose


For something like:

Commit messages

An example of a commit message received for jCapture in Allura
---------- Forwarded message ----------
From: Repository jCapture applet code 
Date: Thu, Jun 21, 2012 at 2:39 PM
Subject: [jcapture-applet:code] jonnybradley committed to jCapture applet Code: new param for the token name in the post - tokName as it needs to be different in tiki (plus jar and project file)
To: Repository jCapture applet code 

: new param for the token name in the post - tokName as it needs to be different in tiki
(plus jar and project file) http://sourceforge.net/p/jcapture-applet/code/32/


Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/jcapture-applet/code/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/prefs/

Mailing lists

File downloads





Project Summary


Feature requests for Allura

Mail from Rich Bowen

On Oct 8, 2012 4:25 PM, "Rich Bowen" wrote:
> Dear Tiki Wiki CMS Groupware project admin,
> As one of our top projects, we want to be sure that you are aware of
> what's coming in the near future. As you are no doubt aware by now,
> SourceForge is upgrading our core development product from the "Classic"
> forge to a new product, code-named "Allura". Allura is itself Open
> Source, and is developed on SourceForge, at http://sf.net/p/allura/
> Allura is also incubating at the Apache Software Foundation, to become
> an ASF project. (http://incubator.apache.org/projects/allura.html)
> Early next year, we hope to be 100% migrated off of the classic
> platform. As a developer yourself, you understand that we want to
> retire the legacy code base, so that we can spend less time in
> maintenance, and more time moving forward.
> We'd like for you to have the opportunity to upgrade on your own
> schedule, rather than ours. You can read about the upgrade process at
> https://sourceforge.net/p/upgrade/ and then press the 'Upgrade' button
> next to your project name.
> In our surveys of projects that have upgraded, 97% of respondants tell
> us that the upgrade improved, or at least didn't change (12% said that),
> their developer experience.
> Please don't hesitate to email me with any questions or comments you
> might have about the upgrade process.

Related links

Page last modified on Saturday 30 November 2013 01:50:15 GMT-0000

Upcoming Events