[FFmpeg-devel] [RFC] marking non developer tickets

Michael Niedermayer michael at niedermayer.cc
Wed Sep 7 22:43:26 EEST 2016


On Wed, Sep 07, 2016 at 09:48:55AM -0800, Lou Logan wrote:
> On Wed, 7 Sep 2016 13:31:37 +0200, Michael Niedermayer wrote:
> 
> > Hi
> > 
> > Most of the tickets on trac are about ffmpeg code. I belive this makes
> > it hard for non developers to find things to contribute to, yet at the
> > same time there are quite a few non devel tasks that need to be done
> > and that arent done ...
> 
> Do you have some examples of current tickets that you consider to be
> non-developer candidates?

see link below


> 
> > Can type = task be used for non devel tasks or should a key word
> > be added (which keyword?) or something else ?
> 
> If you want to use "task" for this then that would be fine with me.

ok


> 
> Alternatively, a wiki page could be setup similar to:
> <https://wiki.multimedia.cx/index.php?title=Small_FFmpeg_Tasks>
> 
> Keeping it up-to-date of course could be problematic.

yep, i think we should use tickets for this, that way a page like
https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&type=task&col=id&col=summary&col=status&col=type&col=priority&col=component&col=version&order=priority
stays magically up to date

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The worst form of inequality is to try to make unequal things equal.
-- Aristotle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20160907/8967381a/attachment.sig>


More information about the ffmpeg-devel mailing list