Last changed on mar 16, 2006
by Rahul Singh
For guides on how to develop a module look here Modules currently on the dashboard:
- [Creating a Module Control Center]
- Creating a Control Center subpage
- New Module Control Pages should be children to this page, so that the index is alwasy up to date.
This is kind of an experiment. It would help in keeping valuable information concerning Module development centralised. This way developers that are working on a module - at some point in time - will find the information they need. Why in Dashboard? Because of it's flexibility it is a good way to experiment towards a good working structure and methodology. Later we then can decide to implement it on a different platform (for example Rainbow Portal)
Every Module gets its CONTROL CENTER consisting of a Home Page and Subpages.
ALL activity on the development of a control is reported here. Thus we get a repository on all aspects of the development of a module for future reference.
Control Centers = Structured pages
Every module gets its own page (called homepage) and Child pages. Every page has a fixed structure (defined in next chapter).Anybody can change pages
There is no project leader. You help when you can. But you must follow the strict Methodology that is/should be clearly/extencively be documented. (which is what we are trying to do here).Be informed AND KEEP INFORMED
This way of working will make you informed BUT you are obliged to inform others! Decide OR Ask for decision
Anybody can add information. So if you decide something, then just add it. If you want a decision ASK FOR IT.
Items that need to be developed and documented:
*The decision process:
0 comments
|
