Solid/HowWeWork: Difference between revisions
| Line 23: | Line 23: | ||
=== Objectives === | === Objectives === | ||
Forge has | Forge has two main objectives related to our community: | ||
* | * Hacking away to nail down the remaining hot topics for the N+1 release | ||
* | * Identify further areas to tackle for the coming year | ||
Revision as of 10:51, 27 November 2010
What is a Solid Project
A Solid project is any kind of software or initiative related to hardware or system integration which is ruled by the Solid Team. All the projects operate in the same way, being this the only requisite to be a Solid project.
Communication
We use primarily two ways of communication, irc and mailist. Each project can have they own, but everybody should be in kde-hardware-devel and #Solid in irc.freenode.org
Bugs
As many other KDE applications, we're using the kde bugtrack to manage bug tracking. All projects are within the product Solid as components, using the most friendly name possible, for example instead of BlueDevil we're using "Bluetooth".
Each project has a general category, on which a bug triager is assigned who should move the bugs to a more low level component, for example moving a bug from libsolid to libsolid-udev.
Patch Review
We're using (as many other KDE projects) reviewboard as web interface to submit patches, it allow to us to keep tracking of patches.
Currently there are two review boards, git and svn, you should use one or the other depending on where the project is hosted (SVN or Git). Since KDE is moving towards Git, is to be expected that in the future will be only one reviewboard.
Sprints
What is a sprint?
Sprint is a small event where we all sit together (in a physic place) and work on Solid related things.
The Solid sprint has a proper name "Forge", and we try to organize 1 a few months after Akademy.
Objectives
Forge has two main objectives related to our community:
- Hacking away to nail down the remaining hot topics for the N+1 release
- Identify further areas to tackle for the coming year