Hi, ext Sousou, Imad wrote: > 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...
And we are working to get detailed architecture as soon as possible. This can come before a first integrated release and would already help a lot focusing discussions on technical matters. Still, there is a % of discussion that doesn't depend on source code release (Carsten's example is good: should we have a web forum?) and we need to find the way to balance the role of the TSG. It's good that the TSG has an overall vision over the project and makes sure such vision is implemented, but the TSG members (specially if they are 2 at the moment) have surely better things to do than engaging in the discussion about a web forum. >> 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... In our case the TSG is not even supposed to lead or be the meritocratic authority in many areas. Imad and Valtteri are not going to be the ones with the keys of the repository looking at the incoming patches to give them a green or red card. Their leadership role is more strategic and organizational. The sooner they can start nominating and delegating into an official MeeGo staff the better. If we imagine the noisy day to day in MeeGo, it should be originated mostly by the work around - the code (repos, bugzilla, dev blogs...) - the releases (SDK, images, developer support, testers, contributors...) - the working groups (strategy, planning, tough discussions) Most of the daily decisions will happen around these contexts without requiring any TSG direct approval. Hopefully the current bootstrapping / bottleneck situation can ve overcome soon. I have no doubt about the good willingness of the TSG and I'm seeing these guys working really hard 24/7, but it is true that all this activity behind the doors can't be seen from the current MeeGo channels. >> 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 Question: how does the Linux Foundation operate with meetings and discussions? The W3C consortium is another organization that comes to mind (working groups, individual & corporate involvement...) fwiw the first MeeGo IRC meeting was quite productive and the use of http://wiki.debian.org/MeetBot resulted in very cool automatic minutes: http://meego.mkdir.name/logs/meego-meeting/2010/meego-meeting.2010-02-24-20.04.html -- Quim Gil open source advocate Maemo Devices @ Nokia _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
