[Pkg-sugar-devel] Bug#813258: Bug#813258: sugar-record-activity: Should sugar-record-activity be removed?

[Tony Anderson]

You are discussing a procedural issue.

However, I wonder what is a 'modern' gstreamer. Why would anyone remove 
a useful capability because it isn't up to their parochial definition of 
'modern'?
Why should the very limited resources available to Sugar be forced to 
divert their efforts to this 'modernization'?

Would you remove all of the Python code in Sugar because it isn't 
written in modern Python 3? Should we remove Scratch because it isn't 
Scratch 2? Should we stop using Moodle because it isn't Moodle 2?

Tony

On 01/31/2016 10:46 AM, Jonas Smedegaard wrote:
> Quoting Moritz Muehlenhoff (2016-01-31 04:00:28)
>> Should sugar-record-activity be removed? It depends on gstreamer,
>> which is scheduled for removal and there doesn't seem to be any
>> upstream activity to port it to modern gstreamer.
>>
>> Please address the outstanding bugs or reassign this to ftp.debian.org
>> for removal.
> Thanks for the concern.  Upstream is quite slow but not dead, so I will
> keep waiting.
>
>   - Jonas
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-sugar-devel/attachments/20160131/b3944a8a/attachment.html>