Hi, about http://wiki.meego.com/Marketing/Meego.com_1.2_update
After almost a month, the situation around - conference.meego.com - The apps catalog - Community OBS - Packages interface Is basically the same: one can assume that there is work going on but there is a lack of documentation and updates for anybody to follow and get eventually involved. The work on the conference website is visible if you are involved in the organization team, not too bad. About the Community OBS, lbt is at least answering questions at #maemo. http://wiki.meego.com/Build_Infrastructure/Community_Builder exists and I just created a bug to follow the progress http://bugs.meego.com/show_bug.cgi?id=12471 I have no idea of what is going on with the apps catalog and the packages interface. Tero and I had a call before Xmas where he agreed to make sure that things are documented in wiki pages and reports are made via bugzilla, but there hasn't been any progress that I could see. I couldn't get any updates from Niels either. Can we move all these meego.com activities to normal open mode? And if not, what are the obstacles? Personally I have enough having to chase deep corporate teams to work in the open, but all these tasks are in the hands of dudes with good awareness of community work and openness, and good knowledge of how to work with wiki pages and bug reports. Thank you for your understanding and please move your pieces out to the MeeGo channels. -- Quim On Sat, 2010-12-18 at 19:55 +0100, Gil Quim (Nokia-MS/MtView) wrote: > Hi, read the following if you are involved in the development of > > - meego.com > - developer.meego.com > - planet.meego.com > - conference.meego.com > - The apps catalog > - Community OBS > - Packages interface > > http://wiki.meego.com/Marketing/Meego.com_1.2_update is the starting > point to follow all the *.meego.com related tasks that the Community > Office wants to address before MeeGo 1.2 is released. > > Each item listed under Goals needs to have its own bug report to > follow the status. An associated wiki page up to date with the related > documentation is also welcome. This way anybody can subscribe to > automatic email notifications when a bug report or a wiki page is > updated. > > The main features to be implemented need to have their own bug report. > Bugs found need to be filed as well. All the items aimed to be > resolved before the MeeGo 1.2 release need to be set to High priority > (asap) or Medium (later, but before end of April). > > The work in some areas is quite clear now (meego.com, > developer.meego.com, planet.meego.com...) while in other is no clear > at all (apps catalog, package interface, community OBS, conference > site). If you are dlocumenting your work elsewhere please add the > links. If you are basing the work on CC mail, IRC etc please put the > minimum documentation in place to allow others following your work, > reviewing, giving feedback, etc. > > I'll be on holidays until Jan 5. Please do the homework in the > meantime (as I did, in a precious Saturday). :) > > Thank you! > > -- > Quim _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
