[maemo-community] [Council] Community issue tracking

[From: Quim Gil]

Hi, just a couple of comments with my pure maemo.org shirt [1]

>> Maybe some level of integration with the Sprint organization would be
>> useful. I'd like to hear what the maemo.org guys think about that.
> 
> Indeed, there's an interesting question about how much (if at all),
> the council should/could get involved in the day-to-day maemo.org
> operation.

I would start simply with the current process, and expand it if needed
to make the new requirements fit. Three reasons:

- Continuous growth principle: don't get more/bigger shoes until you are
certain the current ones got too constrained. The current sprint process
is young and I don't feel we have squeezed it fully yet.

- Limited communication channels: we were just discussing about the big
amount of channels to follow and interact with. The idea is to simplify
them, not to make them grow.

- Everything is related anyway: the maemo.org tasks should ultimately
respond to the needs of the community, which is basically what the
council wants to assess. Having an integrated council/website process
will help seeing why we do what we do with a more holistic vision.



> Although Quim's been doing a sterling job steering it, if
> maemo.org is to really become community owned, I guess it means us
> working quite closely in the sprint organisation.

I'm helping ramping up the sprint process and the "community
emancipation" but being a Nokia employee I assume that my work can be
taken by others. This would mean more % of pure community initiative and
more time for me to work on the things you want us to work inside Nokia.


> As you say, though, they've been working under an "official" maemo.org
> banner a lot longer than us, and it doesn't make sense to introduce
> hurdles to getting things actually *done*.

Having council and maemo.org separate sounds more of a hurdle to me than
having them well integrated.

-- 
Quim Gil
marketing manager, open source
Maemo Software @ Nokia