Regardless if this change was good or bad, I'm surprised this sort of stuff are not communicated over to either meego-community. Since this affects the community at large, I would expect it to be there.
Also, -community seems to be very quite ever since the 11th/02 so I don't think it will create a problem to RFC on -community, potentially receiving feedback from developers out side meego core. -Sivan On Thu, Jun 30, 2011 at 10:58 AM, Andrew Flegg <[email protected]> wrote: > On Thu, Jun 30, 2011 at 02:25, Zhou, JieX A <[email protected]> wrote: >> >> Was there any body realize the potential risk/impact of this to the >> other parties (let's say meego-dev@ mailing list here) when the original >> mail of this change sent out? > > Andre seemed to, but was assured that it had come from the development > community/management: > > https://bugs.meego.com/show_bug.cgi?id=19369#c5 > > Cheers, > > Andrew > > -- > Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ > _______________________________________________ > MeeGo-qa mailing list > [email protected] > http://lists.meego.com/listinfo/meego-qa > _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
