Last changed on mar 16, 2006
by Rahul Singh
This living page will contain the minimum requirements for ALL modules. In order for a module to be included in Rainbow it must pass all requirements on this check list.
- Module has full code documentation - this means vs.net should be able to produce an xml help file for the code comments properties and methods
- All Module keys are localized using esperantus controls as well as present in Rainbow.resx
- Complies installs and run against latest version and rb15 with no errors, warning can be left if removing a warning implies breaking rb15 compatiblity.
- Automatic installation within Module Control
- Rainbow Integrated help files (the stuff in rb_Documentation folder that comes in the zip)
- A responsible person that is in charge when a bug is discovered in module to solve or delegate to right person; he takes care of bug until it is fixed and the fix is released. This person can be the author or a volounteer. One person can be responsible of more than one module and maybe have a pool of people that can help him in the job.
- A module control center page in confluence where the module is described in standard format
Note:
- Ideal would be have it support new plug and play install
I have created the basic idea for the Rainbow Modules with the help of Ace. So here is what we have now…
SVN Checkout Once of these two addresses
1) http://www.internet-rs.com:8080/repos - Gets all stuff even new rbmodules folder…
2) http://www.internet-rs.com:8080/repos/rbmodules - gets you just the modules area which we setup like this…
- PendingModules - These are modules that do not comply with standards defined on CONFLUENCE Modules Standards page. these module may or may-not compile and should only be used by professionals <smile>
- BetaModules - These modules meet all standards and are to be installed on the RainbowBeta web site for final testing by the Core Team and Module Leaders as well as public to see if any final changes need to be done before module is a candidate for release. Some modules may never get out of this area as the target group that use them is to small and not worth being added in the default installation. Yet uses can download them and use them as they are safe to use.
- DesktopModules - These modules have been approved by the leaders to be included in all releases of Rainbow. (Some standards should be published) They have already been through the Beta Site. Also this is where the Admin/Core modules should be stored. These are the modules that are expected to be moved to the release.
- OtherModules - For now ecommerece module is here. I was not sure what group listed above it really belongs to if Any.
Now the idea here is when we are ready to make a move from Dev -> Beta the DesktopModules folder can be copied into the BetaSite for testing. As will the BetaModules… Working Examples of all modules should be usable for all visitors to the Beta Site.
Developers who checkout the Dev code would have to also Checkout the DesktopModules folder and copy it into the Dev folder if they are wanting to make a site. This is because we will not have the DesktopModules folder in the Dev repos any more in the very near future. Or it can be there but it only has the Core Admin modules left in it so the site can run.
0 comments
|
