[MeeGo-dev] Precision of what it means to 'be responsible for' / committing to maintaining a feature/package/whatever in MeeGo?
carsten at maemo.org
Sat Jan 8 02:26:54 PST 2011
Some of us are currently discussing how to deal with hardware
adaptations (also 'community' ones) and one question by Thomas B.
Ruecker from Tieto was that came up is what exactly our concept of
maintenance is and how it works in practice?
I'm sure this is an issue that most vendors wonder about too in our
feature process/package maintaining/etc, so here they are:
* what are the requirements for a maintainer in terms of:
* time commitment
* response to requirement changes
So, anyone who is able to answer those?
MeeGo Nokia N900 Hardware Adaptation Maintainer
More information about the MeeGo-dev