[MeeGo-dev] Some questions about the Technical Steering Group & TSG meetings

[Sousou, Imad]

Carsten Hi

> -----Original Message-----
> From: meego-dev-bounces at meego.com [mailto:meego-dev-bounces at meego.com]
> On Behalf Of Carsten Munk
> Sent: Sunday, February 28, 2010 2:14 AM
> To: meego-dev
> Subject: [MeeGo-dev] Some questions about the Technical Steering Group
> & TSG meetings
> 
> As described in http://meego.com/about/governance we have a TSG that
> has range of responsibilities also includes creating and dissolving
> working groups to support the fulfillment of the project objectives,
> appointing subsystem maintainers and operational leaders, setting
> technology vision, and defining policies and compliance programs. No
> objection here as I believe there has to be someone making a final
> word in discussions where a decision is being made.
> 
> I have some questions that hopefully help to get the ball rolling on
> some issues - I hope that someone in the know, perhaps even Imad or
> Valtteri will answer with exact information.
> 
> Currently enthusiasts for MeeGo only hear the sound of crickets when
> arriving to the project, even though there is non-code related
> community projects that can start.

to be honest with you, both Valtteri and I are spending 200% of our time 
getting the initial MeeGo sources out so there is something to ground 
the discussions...

> 
> We need to show newcomers there's an actual project going on - right
> now it feels a bit like there's no approachability to the TSG or the
> project governance, which is not what it should be in the long term,
> hence my questions.
> 
> First off, it is not clear who is exactly in the TSG. Is this Imad &
> Valtteri or do they organisationally sit on top of TSG?

For now, its both... until we get things going

> 
> If they organisationally sit on top of TSG, how is TSG chosen (I
> understand there might be an initial one chosen already, question is
> for the 'next TSG', and will this selection also include non-technical
> merit such as community work?

Your question presumes a specific slice of the community; IMO, those of us
involved in MeeGo need to address the various "slices"... meaning the
operating system developer community, the app developers community, the 
user community, etc... but going back to your question; yes, we need all
the above to be well represented in the structure and governance...

> 
> When will the first public TSG meeting start and will they be held in
> #meego-meeting on FreeNode IRC?

In the next week or two... not sure whether we should do on IRC or maybe
we can also try a real voice conference and see how that works

> 
> What will be the method of adding items to the agenda for a TSG
> meeting (WG creation, getting opinions about issues, solving disputes,
> etc)? I suggest items on the agenda should be available a week before
> the meeting, in public, in order to give everyone the possibility to
> familarize themselves with the issues before meeting.

Yes, we want these to be open, so we'll take agenda suggestions before
mMeetings...

> 
> I wouldn't mind in the name of transparency to have some proper
> procedures for MeeGo governance written down so it's clear what can be
> expected of TSG and community, methods to resolve issues, processing
> proposals, etc.
> 
> Regards,
> Carsten Munk/Stskeeps
> maemo.org distmaster
> _______________________________________________
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
> http://lists.meego.com/listinfo/meego-dev