Workflows
From espressopp
This section lists the workflow we use in the ESPResSo++ project. This section also summarizes the decisions we made during our project meetings regarding the organization and development of the ESPResSo++ software.
Contents |
Meetings
We distinguish between technical and core meetings. Technical meetings focus on the technical stuff while core meetings are more general about the whole project.
Topics to be discussed should be put on the agenda of the next meeting. All developers should see what is next on the meetings and might also add topics. This agenda is available in the Espresso++ MediaWiki [1].
For each meeting we take minutes that are not public but all relevant stuff will be put in the corresponding areas on this GForge server. It has been proven that currently the person who writes the minutes gets implicitly too much work to be done. Therefore we agreed on the following:
- ToDos become tasks of this project and these tasks will be added after the meeting (Responsible: Dirk Reith)
- Workflows and decisions about project organization will be put on this page (Responsible: Thomas Brandes)
- Technical decisions and other information (technical concepts) will put on the WikiPages of the project; the protocol should specify the person who does it (otherwise the keeper of the minutes has to do it by himself).
Discussions via Jabber
Each developer should have a Jabber id. Jabber ids are not public but should be exchanged between the developers. Developers are encouraged to be online to allow bilateral discussions. For discussions between many people there is a conference room (XXX).
Room: Espresso++ Server: conference.jabber.org
This conference room is by invitation only.
As jabber client we recommend using psi (PSI jabber client using Qt) or kopete (Instant messenger of KDE).
Tasks
Each kind of work (ToDo's) becomes a task. We distinguish between:
- Requirements of the ESPResSo++ project
- Administration (Administrative Tasks)
- Design (Design Tasks)
- Proof of concept (Current development)
- others follow
Usually information of tasks specified in the task manager is not sufficient or too hidden. Therefore additonal information should be put in the Wiki whenever it is useful. The corresponding Wiki page(s) contains a reference to the Task. By default, the Wiki page is in the responsibility of the person that the task has been assigned to.
Use of MediaWiki
Instead of having Latex documents for the system design and the developers guide, we use MediaWiki. This makes it easier to incorporate changes. The organization of the corresponding pages should be hierarchical so that at every time it is possible to generate a document out of the Wiki pages.
Bug Reporting
Contact the person if a bug is found. Email is fine. Later this workflow will most likely change (e.g. by using the tracking system of this server).
Open Points
Here we put a list of open points regarding the workflow that need to be defined or clarified.
