[maemo-community] Sprint meeting & process

[From: Qole]

I just want to say a big public "thank you" to Andrew for pushing so hard in
this area.

As some of you may have heard, I've felt the same frustration at the lack of
feedback from the maemo.org team. I just want to know what's going on, and
sometimes that seems to be very hard to find out.

To me, interfacing with the paid maemo.org team is one of the primary jobs
of the Council. The team is accountable to the community, and we're the
community's representatives, so we need to keep pushing to get the team to
open up and tell everyone what they're doing.

And team members, please don't take an adversarial stance here; let's work
together to fix the processes so it's reasonably clear to the community
what's going on. We shouldn't have to get to the point where we start trying
to figure out whether the Council has the power to not renew a team member's
contract. That kind of talk is born of frustration, and I think it is in
everyone's best interest to minimize that frustration. Rather than arguing
about what power the Council has, look at the motivation here; why are we
even mentioning it? Are we trying to get you fired? No! Of course not! We're
trying to get you to communicate with us, the community you're working for.

Let's all play on the same team here, OK?

The ideal situation would be a system that let the team members report their
progress without making the reporting a difficult task. Is there no Midgard
module or something that we can use here? There's got to be some kind of
Sprint Process software that we can use...

I will do my best to be at the sprint meeting. I'll try not to kick any
hornets' nests.


On Wed, Jun 17, 2009 at 8:18 AM, Andrew Flegg <andrew at bleb.org> wrote:

> On Wed, Jun 17, 2009 at 16:10, Jeremiah
> Foster<jeremiah at jeremiahfoster.com> wrote:
> >
> > On Jun 17, 2009, at 16:44, Andrew Flegg wrote:
> >
> >> 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.
> >
> > Andrew, this is a threat. I think this is the wrong way to go about
> > getting people to report their status on the wiki.
>
> It is not intended as a threat: as I say, I don't know how Nokia will
> decide whether to continue funding positions, or renew individuals'
> contracts (hell, I haven't even seen the contracts, nor do I want to).
>
> However, the point of this discussion is to try and find 1) how to get
> people to report their status, 2) whether the wiki is the right place
> and - as Dave's raised - 0) why we're reporting status in the first
> place.
>
> I know I've certainly been very frustrated by the lack of updates on
> the wiki when trying to organise a sprint meeting so that minutes and
> documentation can be accurate and comprehensive. If the participants
> aren't taking it seriously, or it's not proving valuable, or it's not
> being done for some other reason, why should I give up _my_ free time
> to try and shepherd a flawed process?
>
> Cheers,
>
> Andrew
>
> --
> Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/
> Maemo Community Council chair
> _______________________________________________
> maemo-community mailing list
> maemo-community at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-community
>



-- 
enthusiast, n. "One whose mind is wholly possessed and heated by what
engages it; one who is influenced by a peculiar fervor of mind; an ardent
and imaginative person."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maemo.org/pipermail/maemo-community/attachments/20090617/d6ee50e8/attachment.htm