History: Migrate to Allura
Preview of version: 34
- «
- »
What
Migrate from the current SourceForge.net setup to the new Allura platform.
When
- The transfer was initiated on 2012-12-08
Who
- changi
- you?
What end-users need to know
- You need to change your SVN repo: https://dev.tiki.org/Update#If_you_got_your_check_out_before_2012-12-12
- We still use subversion in the same way as before. The subversion tree did not change, it just moved to a new repository.
Questions
- Is old space kept in read-only so we can compare?
- How do I get a view like this: http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/tags/ to put here: http://dev.tiki.org/SVN+Tips
Issues
- 2012-12-11 marclaporte: I see new interface here: http://sourceforge.net/p/tikiwiki/news/ but if I click the top menus, some seem like they need an adjustment (Summary and code at least)
- 2012-12-12 marclaporte: http://sourceforge.net/project/memberlist.php?group_id=64258 no longer shows list of users with commit access and doesn't redirect to a list
- 2012-12-12 marclaporte: why does it now ask for a password for https checkout? Before, we could get anonymous checkout via SSL.
- 2012-12-13 marclaporte: did a fresh checkout from new repo, edited a file and tried to commit
- Copy to clipboardssh-w00ec615@dd29038:/www/htdocs/w00ec615/cartograf-fr$ svn commit -m "French translation: View source is about a wiki page, not a file" lang/fr/language.php svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to MKACTIVITY request for '/p/tikiwiki/code/!svn/act/cc397d35-8e6c-4d56-846b-550b7a033442'
-
Needs to be updated
- https://www.ohloh.net/p/tikiwiki/enlistments
- 2012-12-12: done by Marc for SVN, leaving CVS untouched
- https://doc.tiki.org/Server+Check
- https://dev.tiki.org/Version+Control+Bridge
- https://dev.tiki.org/Convert+a+site+installed+via+FTP+to+now+use+SVN
- http://dev.tiki.org/Commit+Code Some are done but not all
- https://code.tiki.org/ (especially the templates)
Check these periodically
- https://encrypted.google.com/search?q=site:dev.tiki.org%20svnroot
- https://encrypted.google.com/search?q=site:dev.tiki.org%20viewvc
Things to test
SVN browse
Eventually, we will loose
and
For something like:
Commit messages
- Will messages to https://lists.sourceforge.net/lists/listinfo/tikiwiki-cvs change? If so, are we OK with new messages?
An example of a commit message received for jCapture in Allura
Copy to clipboard
---------- 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
- http://sourceforge.net/projects/tikiwiki/files/
- We need to make sure WebPI still works OK
POTM
Reviews
News
Stats
- http://sourceforge.net/projects/tikiwiki/stats/traffic
- http://sourceforge.net/projects/tikiwiki/files/stats/timeline
Feature requests for Allura
- Add jCapture applet support to make it easy to add screenshots and record a screencapture with audio comments
- Web-based commits, like GitHub and Google Project Hosting, with JavaScript-based source code editors
Mail from Rich Bowen
Copy to clipboard
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.