2010/11/28 Arjan van de Ven <[email protected]>: > On 11/28/2010 8:47 AM, Carsten Munk wrote: >> >> 2010/11/28 Michael Leibowitz<[email protected]>: >>> >>> On 11/28/2010 06:59 AM, Zhu, Peter J wrote: >>>> >>>> It’s not used by any verticals or included in any pkg groups. >>> >>> How are these decisions made? OpenCV is a computer vision library that >>> enables developers to create applications that use image recognition. >>> This >>> is an area of active interest by several developers and is one of the >>> areas >>> where developers on competing platforms are making interesting use of >>> computer vision to make compelling applications. By removing libraries >>> and >>> utilities, we simply make it harder for developers to get started making >>> something compelling and interesting with MeeGo. >>> >>> Shouldn't our goal to be to enable the vast amount of software out there >>> for >>> Linux/Unix that enables application development, rather than removing >>> anything that isn't directly used? Aren't we making a distro for mobile >>> application developers? >> >> Disclaimer: I actually like OpenCV, used it for my master's thesis.. >> >> I think the question is also a bit, where's the FEA# for this, who's >> the maintainer and who QA's the APIs provided by OpenCV? > > actually > > you need a FEA to add or remove a package. > > to maintain status quo.. not so much. > > your case of "program did not get added due to no FEA" is clearly such a > case of adding.. not keeping status quo. >
This was more in terms of QA and knowing who's responsible - I know full and well that it's for addition, not status quo, though the removal is a new one I haven't seen anywhere. Just throwing this out there - maybe we ought to have FEA#'s for the status quo too. I mean, we can't have too deep FEA#'s for some things as it's just impossible to map. But, for me (as I understand it), in terms of QA, a FEA# is: * A manifestation of the principle that someone needs to be responsible for a feature in MeeGo, maintain it or it'd be dropped. * A starting point for our QA teams to generate test cases and do their work. * Making sure that each single package we ship in MeeGo is tested somehow through verification of feature availability by QA. All of these make sure we are shipping a quality distribution.. Using OpenCV as an example -- how do we actually know that the OpenCV we shipped in MeeGo 1.1 Core actually works? QA didn't test it at all. If it had a FEA#, it would have been verified and that's why I'm asking if it has a FEA#. We shouldn't be shipping untested software to millions of devices.. BR Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
