Joining the project
At the moment the only most of the development and all of the (non-site) administration is being done by Ryan (email@example.com. If you want to join the project ask him to put your email address on the (currently unused) mailing list, if you haven't already, get yourself a PGP key and a github (or similar) account. People looking to work with the site will also need an account with sourceforge.
One-off patches and contributions of command profiles should just be sent in by email.
Getting the code
The latest working copy of the code can be found at github.com/RyanMcCoskrie/VisualShell. However if you are looking to work on this project over the long term the best way to gain the source is to use git as shown below:
[yourname@yourhost ~]$ git clone firstname.lastname@example.org:RyanMcCoskrie/VisualShell.git
and after that keep the resulting directory up to date with:
[yourname@yourhost ~]$ git pull origin
Hacking the code
Some tips for hacking on the VisualShell.
Read everything on the file types page.
File I/O, user settings and all other information that is not being edited in a widget is to be handled by the Application class (or equivalent
in acessory programs)
Add as little behavior as possible to the main.cpp file. If you can help it, this file (for all programs) should only call KCMDLineArgs::init, set up the 'about' data and then pass control over to the Application class
If you are unsure of anything or have an idea please bring up the topic for discussion on the mailing list. It's there for that sort of thing
The prefered code layout is that recomended by Linus Torvalds in the Linux kernel documentation