Proposals

This is a place to collect drafts and proposals that should be implemented into Jarifa. Feel free to add your own thoughts.

##PHP-based Installer

An automated PHP-based installer should:

• check the prerequisites
• generate the conf/jarifa.conf file according to user input
• create the database tables
• change the Jarifa root passwort to something the user supplied

##Debian package

The Debian package should condense the installation process to a single click.

Another idea: Create a user (e.g.: name: anonymous password: jarifa) with the role Volunteer and supply the credentials to the local students. They can now attach there clients to the Jarifa server and log into the website to see there stats. They are not allowed to change the password for this user, it has a read only permission by Jarifa. So we don't need the user to create an account and get the computing power. We have to ensure that there is no private data that can be seen by this anonymous user.

##Version numbering

Define a definition for major and minor version numbers (e.g. 0.1 means beta, 1.0 means first full featured release). Major version will increase when new features are added and minor version increases when bugs are fixed for this particular major version. This is similar to the Wordpress version numbering which is IMHO a good way for small PHP only projects.