Task:Collaboration infrastructure
 |
This is an accepted task and it is currently in the maemo.org development backlog. Probably nothing is stopping you from starting on it, though. Please see the talk page for discussion. |
 |
This task is related to Objective:Release soon and often.
Here we want to define the infrastructure needed to develop projects in an open and collaborative way. Thre is two views to the question: the project-centric view and the platform-centric view.
Examples of potential conflicts between both views:
- Garage offers bug tracker and wiki to al projects. However, do we want to use those or push the projects to concentrate in bugs.maemo.org and wiki.mamo.org?
- Tero is figuring out a strategy to offer git in maemo.org. Is it about enabling git for garage projects or creating a generic git.maemo.org where everybody uploads their code?
Please leave your opinions in the discussion page.
[edit] Project level
Let's take as an example the open development of the Application Manager. What there is now and what is needed.
[edit] Visible infrastructure
- Static website, with basic documentation.
- Garage project.
- SVN and git (in Gitorious.org) repositories.
- Component in bugs.maemo.org (Garage Tracker available but not used.
- A wiki page in wiki.maemo.org.
- Lists - a Commits list exists; th discussion happens in maemo-developers.
- Forum available, although not maintained.
- Marius' blog, lead developer - actually more into microblogging.
- Tasks, not used.
- Docs, not used.
- News, not used.
- Files, not used.