On 11/28/10 8:47 AM, "Carsten Munk" <[email protected]> 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?
>
>I thought I saw utility programs denied because of having no FEA# so I
>would assume we'd have a FEA# (and a good reason) for having OpenCV as
>part of MeeGo.
>
>In the new project setup [1], I assume OpenCV would be in
>Applications/Reference? Maybe we should first delete packages after
>reorg when it's more clear what's Core and what's Reference
>applications/libs.
>

I think it comes down to a couple of different things.  First, as Carsten
states, it has no FEA#.  To be specific, we should not be including things
in MeeGo.com that do not have requirements to be there.  MeeGo.com is a
requirements driven program.

That said, OpenCV is a useful program and shouldn't be lost from MeeGo.
That's why we have the Community OBS (https://build.pub.meego.com/).  If
someone things it's important, they can volunteer to be the maintainer for
it there.  Until there are requirements that it's needed in MeeGo.com, it
shouldn't be there.

Ryan

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to