On Thu, Apr 15, 2010 at 11:09, Carsten Munk <cars...@maemo.org> wrote:
>
> This is a DRAFT proposal for TSG eventually to consider, in order to
> encourage or establish policy of best practices for working should be
> like for MeeGo groups, teams, WGs, appointed groups of people. In the
> following, team/group/WGs/appointed groups of people is shorted to
> 'team'.
>
> Instead of pointing out how each team is doing it wrong and each and
> every problem, it was cooked down to this proposal, so we can have
> something to point to when things aren't being as open as it should be
> - which is effectively blocking public R&D as intended.
Excellent stuff. All seems spot on; the only change I'd make (and I'll
make it later today if I have time) is to clarify in the introduction
that this is intended to be working practices for *everyone* working
on MeeGo itself, whether the TSG; teams in Intel; Nokia's MeeGo
devices or the more obvious Working Groups that we're trying to get
the TSG to sign off.
Although you make that point, I think a quick skim could leave the
reader coming away with the impression that it's only of relevance to
the community-led work; and that it doesn't apply to them working in
an internal team.
> These simple Do's and Don'ts were supposed to be obvious, but we are
> not seeing this happen in practice, hence this proposal. The scope of
> these practices is any team organised underneath the MeeGo umbrella
> which works with the public MeeGo project.
Actually, having typed that, I've got another:
* Do talk to your manager if you're working internally currently
and think your work should be being done in the open.
> We are seeing a lot of secrecy and non-public development which is
> effectively harming the project and I personally think that TSG should
> lead the way and point out this is not how things are supposed to be.
Indeed. It became a frustrating cliche during the first years of Maemo
that "you can't expect a big company like Nokia to change overnight."
However, I *do* expect Nokia and Intel to change overnight when they
announce a big, public and open project like MeeGo. Especially since
both members of the TSG have been leading large open projects
internally for years. I certainly hope your proposal helps spearhead
the transition and we can avoid a similar cliche in MeeGo.
Cheers,
Andrew
--
Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/
Maemo Community Council chair
_______________________________________________
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
