[maemo-community] Sprint meeting & process

[From: Jeremiah Foster]

On Jun 17, 2009, at 16:44, Andrew Flegg wrote:

> On Wed, Jun 17, 2009 at 15:21, Dave Neary<dneary at maemo.org> wrote:
>>
>> Ah! I see what you mean. Something like a mail that gets sent a week
>> before the meeting, with "Please report status of your tasks", to  
>> which
>> everyone should reply with their tasks.
>>
>> What happens if someone doesn't reply?
> [...]
>>
>> I just think that fundamentally the problems we have right now are  
>> not
>> so much technological as human. Part of the issue might be that there
>> are no consequences to not updating status, so it isn't a high  
>> priority.
>> But then, you can't have all stick, no carrot, you need to set the
>> incentives right.
>
> Would it be too blunt to say that the reporting and committing to
> tasks is one of the primary roles and processes of a maemo.org paid
> contributor; and performance against these will feed into any
> mechanism by which they are judged?

Of course it would too blunt, it is not up to you to decide who gets  
hired and fired.
>
> We haven't formalised exactly the process by which the 6-month
> contracts would get renewed (or not); but suffice to say "having a
> job" is a pretty big carrot and "not having a job" is a pretty big
> stick, IMHO.

I think we need to tone down the rhetoric. Threatening people's jobs,  
however implicitly, is known to be counter productive.

Jeremiah