[MeeGo-dev] Approved feature number(was Re: 9241: New package Trunk:Testing/u-boot)
sivan at omniqueue.com
Sat Nov 6 04:08:24 PDT 2010
If we can find the time for it, I am inclined to discuss the feature
shaping and decision process in Dublin.
I don't remember off the top of my head if there were dedicated
sessions for that, I'd be nice to have some informal unconference
gathering for it.
On Fri, Nov 5, 2010 at 4:33 PM, Foster, Dawn M <dawn.m.foster at intel.com> wrote:
> On Nov 5, 2010, at 7:06 AM, <eric.le-roux at nokia.com> wrote:
>> Hi Menon,
>>> -----Original Message-----
>>> From: meego-dev-bounces at meego.com [mailto:meego-dev-bounces at meego.com]
>>> On Behalf Of ext Nishanth Menon
>>> Sent: 05 November, 2010 15:58
>>> To: Nanjappa Madhusudhan.3 (EXT-Wipro/Helsinki)
>>> Cc: meego-dev at meego.com; meego-packaging at meego.com; meego-
>>> commits at meego.com
>>> Subject: [MeeGo-dev] Approved feature number(was Re: 9241: New package
>>> ext-madhusudhan.3.nanjappa at nokia.com wrote, on 11/05/2010 09:39 AM:
>>> 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
>>> 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?
>> Nobody's trying to make your life difficult ;)
>> You're not looking into the right place I reckon.
>> Here's the process:
> The requirements / feature request process is new and still be refined. I've added
> a note about following this process, instead of contributing a patch for new features
> to both of these pages:
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
More information about the MeeGo-dev