[MeeGo-dev] What are you waiting for to happen in MeeGo?
carsten at maemo.org
Sat Mar 6 14:02:44 CST 2010
This might have fit better on a forum. but since we're between day
zero (announcement) and day one (source code release) and well, things
aren't that publically active right now to the extent I'm almost
hearing the sound of crickets.
I thought it might be good to have these questions aired so we are
ready to go when day one of MeeGo happens, or organise activities
until or after day one.
The questions are:
* What are you waiting for to happen in the MeeGo project?
* Do you know what is currently blocking these things to happen, if so, what?
* What would you contribute with if these things happened? What area,
what specific things - how can you help, where's your talents in this
area and interest?
When replying to the questions, please cut out everything else than
the questions and your answers :)
The idea is to help get an impression of what latent and waiting
contributors that is interested in helping out in the project. This
can also help prioritising some activities as to help this community
This is -not- a thread where you discuss heavily, but where you think
how you, as someone interested in making MeeGo great, will show what
you're helping to bring to the table. The hope is that it'll help
organise people into groups as well.
So, I'll start with myself:
* I'm waiting for TSG meetings to start, the source packages of MeeGo
being published, OBS access for the community opened so we can
contribute on equal footing as Intel and Nokia employees can.
* Blockers: TSG: The current negotiations, Source packages: day one,
OBS: current setup and policy (AFAIK)
* If these things happen, I would participate in helping the project
to operate in a open manner, establish policies. If source packages of
MeeGo got published, I'd try to build MeeGo for the Nokia N810 ;) If
OBS access got opened i'd build it there. What I hope to bring to the
table is organising newcomers to contribute to the project, making
porting MeeGo easy as eating pie to devices much like Mer was and my
experiences with Mer, both organisationally, policy and code-wise.
Along with that, my role as maemo.org distmaster in communication of
licensing change requests with Nokia to help community development and
many other things.
More information about the MeeGo-dev