Infrastructure

This article describes the infrastructure that is needed to run the PARPG project effectively.

Temporary infrastructure in the starting phase

 * We could rely on fifengine.de infrastructure (website, forums, IRC, etc.) at least until we've agreed on a name for the project.

Blog

 * Our blog.
 * Shorter regular blog postings seem to working out better than longer postings that sound more official but take far longer to write.
 * Blog postings could be shown at fifengine.de as well. LinuxDonald (new FIFE project manager) got some plans that go into this direction.

IRC channel

 * #fife @ quakenet or #parpg @ freenode until we actually agreed upon a name for the project.
 * Current advantage of #fife: logging bot functionality is available there.

Forums
Our forums.

Task tracker
Trac @ cvsdude.com.

Website

 * Temporary website at fifengine.de until we've agreed upon a name.
 * We could register an own domain if wanted later.

Version control software

 * SVN @ cvsdude.com. Hosting should be available when recruitment starts.
 * Linux-based developers could use git locally in case they prefer decentralized version control.
 * As there is a lack of easy to use git clients for Win32, SVN seems like the better option for the online repository.

Wiki

 * Stick to an own wiki, the one you're reading in in this very moment.

Additional software

 * Daily updated code documentation.
 * IRC logging bot with IRC channel archive.
 * Both would require an extra server where these kind of functionality gets hosted.