[maemo-developers] [maemo-developers] Too busy to accept help?]

From: Devesh.Kothari at nokia.com Devesh.Kothari at nokia.com
Date: Thu Apr 20 11:00:50 EEST 2006

> -------- Original Message --------
> Subject: [maemo-developers] Too busy to accept help?
> Date: Wed, 19 Apr 2006 13:14:13 +0200
> From: ext Murray Cumming <murrayc at murrayc.com>
> To: maemo-developers at maemo.org
> The Maemo community is alive, but not thriving as much as it 
> could. This
> is because the Nokia developers are so busy and are often unable to
> respond to the simplest of requests for changes or information, and
> often unable to even acknowledge that contributions have been 
> accepted.

I agree. but sometimes, I believe also community cannot be pushed 
too hard either, things just take time (simple example is if
something itches, you step in to solve :)

> It's OK to be busy, so this isn't a personal attack on those 
> developers.
> It's a suggestion for how to take the weight off them.
> I think Nokia needs to assign a dedicated community liaison, full time
> or part time, while still demanding that all developers are involved
> with the community as much as possible. This person would maintain the
> web site, and help the community to maintain it by extracting
> information from Nokia. This person would also do simple patch and bug
> triage and apply obvious changes without bothering the developers with
> trivial stuff.

I rather turn this other way to identify clear problems today and expectations
e.g (here is my list), feel free to add

1. Responsive discussion on mailing list (this should decrease, as Maemo matures,
  and more things get documented) - so patience advised
   [Thing community can do for us] : Create a Wiki page with concrete How-To's needed. Remember so 
   many things are discussed on mailing dev list, which are asked again and again. Also it is easier
   to update things at one place, when things change
2. clear forums for feature/enhancements discussion
3. more transparency from Nokia about Maemo roadmap (with ability for community to be involved)
4. responsive bugzilla [this should now start to work :)
5. ability for community to be involved with bleeding edge Maemo, to contribue and experiment
   baby step [http://maemo.org/pipermail/maemo-developers/2006-April/003550.html]
6. ability for community to contribute and share Maemo applications
7. Clear process from each project (in Murrays case HAF) 
   - how they accept contributions (e.g access rights, patches, feature enhancements)

I still see a lot of value in Murrays proposal, and as Carlos pointed out :) there are hiring announcements :).


> It must be politically acceptable for this person to be under less
> pressure than a regular developer. If the community liaison 
> ever has no
> problems to solve then that's good.
> If you need a more traditional job title, you could squeeze these
> responsibilities into "Documentation" or "Q & A".
> Nokia will get a lot of the advantages of open source if they don't do
> this, and the community will survive if they don't do this, 
> but I think
> the extra salary would be a good investment to get even more valuable
> advantages.
> -- 
> Murray Cumming
> murrayc at murrayc.com
> www.murrayc.com
> www.openismus.com
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://maemo.org/mailman/listinfo/maemo-developers

More information about the maemo-developers mailing list