NotesThe tasks on this page are listed in order of priority. Tasks higher up on the list need to be completed before tasks lower on the list. Developers looking to contribute to the BurstCMS project should look to help on one of the tasks that are at the top or close to the top of the list. To complete BurstCMS 1.0 stableDatabase APICurrently, the database API allows any query to be run. The problem with this is that databases have slightly different syntaxes for creating and modifying tables. To make sure that the same code can work with MySQL and PostgreSQL tables. A good looking, easy to use, and fully functional installerThe installer needs to clearly explain instructions to users that might not be programmers. The installer also needs to be nearly completely bug free, as installation bugs would be a major issue for BurstCMS adoption as a content management system. It is also a requirement that the installer be good looking, as an ugly installer reflects poorly upon BurstCMS. Module and component loaders fully testedThe module and component loaders are currently not completely tested. They need to be bulletproof because they are a critical part of BurstCMS. Advanced error logging and handling systemErrors in BurstCMS modules, components, database classes, and so forth are inevitable. The BurstCMS error logging features need a user friendly interface as well as advanced functionality that helps both developers and users find errors in any BurstCMS related code. User registration, removal and permissionsBurstCMS is going to be a multiuser content management system, and this involves user registration, removal, and a permissions system. A good looking and easy to use admin interfaceAn administration interface to modify the settings of BurstCMS and BurstCMS modules is very necessary. Without a good looking and powerful administration interface, BurstCMS has no hope of adoption. Page caching API tested and put into a componentThe page caching API stores HTML in files on the disk to reduce the number of SQL queries that need to be executed. Currently, the page caching API is completely untested (and probably buggy) and will need to be moved. Theming systemA theming system is necessary for modules to be styled with. Specific details on how the theming system will be implemented have not been finalized. A moduleThere has to be at least one module for BurstCMS to be useful to anybody. The module that would be easiest to create would probably manage a very simple website. Tasks that have been completed
|
Sign in to add a comment
Should we set a specific date that we should aim for all the features to be completed?
I think that the features ought to be completed and debugged by June 1st, 2009.
That certainly allows a good chunk of time. It even allows me to perhaps free up my schedule to the point where I can actually contribute some PHP code. :D (Ha ha ha... :P )