You are not logged in.
Pages: 1
This is a report about the development-team meeting from 15th March 2010.
Points
1. Lack of testing, consistency and finish?
2. Coordination tasks
3. Attracting new developers
4. Things to do before pluck 4.7 can be released
5. theme_menu function
1. Lack of testing, consistency and finish?
For more information about this point, see http://www.pluck-cms.org/forum/viewtopic.php?id=773
We made the following decisions:
1. For big changes, a new branch should be started. About these development-specifics, a team protocol page will be created on the wiki.
2. We will revert the main branch to no. 306.
3. The coding guidelines will be used more strictly.
4. Better communication about development (using the forums).
2. Coordination tasks
Someone needs to be responsible for coordinating tasks like making sure bugs get fixed, approving merges for branches, and managing blue prints.
Sander will make a function description for the coordinator. We'll discuss this further on the forums.
3. Attracting new developers
The new coordinator (see point 2) will make sure that branches will get used better. This will make it more attractive for developers to deliver code for pluck, because if the code is good, it'll get used.
Once the development becomes more active and communcation will get better, we hope more people will participate in working on pluck code.
We will expand the “Get started contributing code”-guide to also include information on how to get into the development-team.
4. Things to do before pluck 4.7 can be released
Will be discussed on the forums: http://www.pluck-cms.org/forum/viewtopic.php?pid=3608
5. theme_menu function
Will be discussed on the forums: http://www.pluck-cms.org/forum/viewtopic.php?pid=3609
Offline
Pages: 1