Hey guys. My ears were burning and now I know why. I've read through the thread and picked here to jump in for a few comments below. Generally I have no big disagreement with the direction or comments. We just need to be empowered by the right people (as noted below).
Here's some more stuff to throw into the discussion. We've been focusing on the netbook "garage" client with the hopes that governance would be clear on how to proceed with process. - My team has created a v0.5 garage netbook app. We hope it will be shipped in MeeGo 1.0 (May). If not, it will be available for download from garage.meego.com/garage http://meego.com//sites/all/files/users/u13/MeeGo_Garage_Community_Review.pdf - Source is open: http://gitorious.org/meego-garage (it links w/packagekit and therefore licensed as GPL v2.0) - The Garage client needs a repo(s) :) - <I think> we will provide 3 servers to setup at OSU for the purpose of enabling this group, managed by this group, for "Community Apps" repos. - I'd like to see us formalize the process for getting apps into the stable repo. I suppose this process would need to be ratified by the TSG -- I need to get updated on MeeGo governanace. A Maemo-like process is proposed in the pdf link above. - We (Intel) are partial to using Drupal for the infrastructure as meego is based on that - I met recently with daniel wilms (nokia) who is working on next-gen N900 garage installer to try and sync up on meego handset garage and closer alignment of the backend protocol. (FYI) - We need to have an OBS package service for community IMO. Other comments below. > -----Original Message----- > From: David Greaves [mailto:[email protected]] hello David and thanks for the thread. Have we met? > [email protected] wrote: > > Hi, > > > > I think we have a mismatch between the name and the content. > > How to call this? Names carried from maemo.org or > moblin.org would be "Downloads", "Extras" or "Garage". > "Apps", "Addons", "Catalog" are also used in similar > contexts. None of them is perfectly accurate but calling it > "Universe/Multiverse" is probably not the best solution either. :) > Heh :) > > > So what about "Downloads" as a compromise between clarity > and accuracy? > I agree the name is actually quite important; now we almost > have the scope we > can address it. > Personally, I like "Surrounds". > I find "Downloads" a little mundane and non-inspirational? > Surrounds clearly says "not core" and is nicely embracing and > quite positive :) wrt to this group (not exactly your discussion) I prefer calling those working on Garage-like activities including repos, process, packaging, etc the "Community Apps Working Group". But I'm not particular wrt names. > > > > David Greaves wrote: > >> I think two main issues were raised: [2] > >> * Is a WG needed? > > > > At this point it is clear that "Working Groups" are being > defined as teams primarily in charge of vision, strategy and > roadmapping. The TSG plans to set up some of those for the > different UX categories, and probably that's it. > OK. I'm not hung up on the structure/label. > I *am* keen that it is empowered to influence the quality of community > contributions to and around MeeGo. Agree. Those commenting are part of our group. Let's go forward. The key is to be empowered by the right people so we can move more freely. > > However, this doesn't affect the purpose, scope and "power" > of this team if it gets up and running. Let's leave behing > the "WG" and let's continuw with the definition work? > *nod* > > >> * Isn't this covered in the MeeGo 'Core' project structure? > > > > At least I don't see it. The Program Office has a clear > mission which consists on shipping great MeeGo > releases every 6 months. The proliferation of a great > offering of additional > software is a different mission that deserves its own focus. > Fully agree. > My only 'worry' was that the 2 types of surround (individual > applications and > 'universe') would be split apart. > > > Can we discuss and agree first on all these general terms? > Once they are clear and agreed it will be easier to agree on > more specific details. > > > > Arjan said something in the MeeGo work group last week that > got stuck in my little brain: any topic that ends up in the > TSG is a failure in the system. :) There is no officially > nominated responsible for this area but a key person is Bob > Spencer from Intel. We discussed few weeks ago at Portland > about how to approach the Downloads repository and how to > introduce a reliable and community friendly QA process. All > in all the maemo.org Extras process was seen as good source > for inspiration - http://wiki.maemo.org/Extras > > > > For practical reasons, I would say that getting Bob on > board and syncing with whatever are his ideas and plans is a > first step in the right direction. If Bob is not in the loop > or disagrees with the proposal then is quite pointless to > jump to the TSG again. > so, with brick-like subtlety... he's To'ed..... "Hey Bob, > come talk to us" :) I'm here. Let's rock. Bob > David > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
