2010/11/5 Nishanth Menon <[email protected]>: > [email protected] wrote, on 11/05/2010 09:39 AM: >> >> You could start from here.. >> >> http://bugs.meego.com/enter_bug.cgi?product=MeeGo%20Core%20OS%20Features >> >> The feature request gets assigned to the Core product manager, who then >> will make a decision.. >> > + MeeGo-dev, changing subject as well. > > http://meego.com/about/contribution-guidelines - the nice lil pic does'nt > point me to this Bureaucracy ;) > > http://wiki.meego.com/Contributing_to_MeeGo Does'nt tell me to file a > bugzilla. > > in fact if the MeeGo has some internal process, why should I(as a community > member) be forced through this process? > > infact googling for "approved feature number" in google on the site > meego.com does not return anything - why are we making the life of a > community contributor difficult? > > http://www.google.com/search?q=approved+feature+number+site%3Ameego.com&hl=en&num=10&lr=&ft=i&cr=&safe=images#sclient=psy&hl=en&lr=&source=hp&q=%22approved+feature+number%22+site:meego.com&aq=f&aqi=&aql=&oq=&gs_rfai=&pbx=1&fp=f436bf9c73b5ce9d > > > PS: for the meego-dev folks, thread of the discussion: > http://lists.meego.com/pipermail/meego-packaging/2010-November/245770.html
Just adding in some reading material that might be useful to add to the wiki - for good measure, it's not an internal process, it's actually a public requirements process.. http://meego.com/developers/meego-roadmap http://meego.com/developers/requirements (most informative drawing) http://bugs.meego.com/buglist.cgi?query_format=advanced&classification=MeeGo%20Features for the actual featurezilla http://bugs.meego.com/showdependencytree.cgi?id=3211&hide_resolved=0 BR Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
