maemo.org positions and qualifications

Hi,

We would like to assemble the complete list of all positions on
maemo.org infrastructure, in order to fill in any empty slot with
volunteers from community.
Please help us assemble the full list which should include:

1. position name
2. short description of responsibilities
3. required skills
4. estimated time per week
5. required number of people manning position. (if more than one is
required)

Based on your input, the missing positions will be advertised at TMO, so
community members can volunteer.

Momcilo

I think the list should also indicate the level of access/admin rights to
the infrastructure and other community assets for each position. Also, it
might be better to estimate the amount of time per month rather than per
week. I think that's how it has been done in the past and gives recognition
that these are volunteer positions and people may be taken up for an entire
week with their other work.

On Mon, Oct 24, 2011 at 6:17 PM, Momcilo Majic <momcilo.majic@gmail.com>wrote:

> **
> Hi,
>
> We would like to assemble the complete list of all positions on maemo.orginfrastructure, in order to fill in any empty slot with volunteers from
> community.
> Please help us assemble the full list which should include:
>
> 1. position name
> 2. short description of responsibilities
> 3. required skills
> 4. estimated time per week
> 5. required number of people manning position. (if more than one is
> required)
>
> Based on your input, the missing positions will be advertised at TMO, so
> community members can volunteer.
>
> Momcilo
>
>
>

Hi,

On Tue, 2011-10-25 at 00:17 +0200, Momcilo Majic wrote:
> We would like to assemble the complete list of all positions on
> maemo.org infrastructure, in order to fill in any empty slot with
> volunteers from community.

See http://wiki.maemo.org/Maemo.org_team , though that might be
partially outdated?

> Please help us assemble the full list which should include:
> 1. position name

maemo.org Bugmaster

> 1. short description of responsibilities

See http://wiki.maemo.org/Maemo.org_team

> 1. required skills

Hard to say in these silent times. Normally I'd say:
Quick understanding of what a bug report is about and what exact info is
missing and how to provide it;
Work, interact and communicate closely with multiple projects and their
maintainers and the corresponding community with its culture and
demands;
Good overview and prioritization;
Ability to resolve conflicts;
Basic Bugzilla admin skills (adding a new product etc);
Bonus points for having a good capacity for remembering bug numbers,
existing reports, and interest in investigating on complex issues

> 1. estimated time per week

Not much nowadays as there's not much development apart from Community
SSU and 3rd party applications hosted in bugs.maemo.org - maybe 2 hours?
(I spent the rest of the time on MeeGo.)

> 1. required number of people manning position. (if more than one
> is required)

1/2?

andre
--
Andre Klapper (maemo.org bugmaster | MeeGo QA)
http://blogs.gnome.org/aklapper/ | http://www.openismus.com

Hi,

Thank you for the link and bugmaster description. I did not spot the
link at first, but it was navigable after visiting "Use the wiki" link.
I've assumed it was the link to wikimedia help content, so I've ignored
it until you've sent the direct link.

I will try to contact all persons from the list in order to determine
their current status.

Momcilo

On 10/25/2011 03:59 PM, Andre Klapper wrote:
> Hi,
>
> On Tue, 2011-10-25 at 00:17 +0200, Momcilo Majic wrote:
>> We would like to assemble the complete list of all positions on
>> maemo.org infrastructure, in order to fill in any empty slot with
>> volunteers from community.
> See http://wiki.maemo.org/Maemo.org_team , though that might be
> partially outdated?
>
>> Please help us assemble the full list which should include:
>> 1. position name
> maemo.org Bugmaster
>
>> 1. short description of responsibilities
> See http://wiki.maemo.org/Maemo.org_team
>
>> 1. required skills
> Hard to say in these silent times. Normally I'd say:
> Quick understanding of what a bug report is about and what exact info is
> missing and how to provide it;
> Work, interact and communicate closely with multiple projects and their
> maintainers and the corresponding community with its culture and
> demands;
> Good overview and prioritization;
> Ability to resolve conflicts;
> Basic Bugzilla admin skills (adding a new product etc);
> Bonus points for having a good capacity for remembering bug numbers,
> existing reports, and interest in investigating on complex issues
>
>> 1. estimated time per week
> Not much nowadays as there's not much development apart from Community
> SSU and 3rd party applications hosted in bugs.maemo.org - maybe 2 hours?
> (I spent the rest of the time on MeeGo.)
>
>> 1. required number of people manning position. (if more than one
>> is required)
> 1/2?
>
> andre