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

[Michael Niedermayer]

On Thu, Sep 08, 2016 at 03:23:36PM +0200, Carl Eugen Hoyos wrote:
> 2016-09-07 13:31 GMT+02:00 Michael Niedermayer :
> 
> > Can type = task be used for non devel tasks
> 
> No objections although I don't understand how #5832 can be "fixed"
> and I don't like tickets that by definition are unfixable.

we have someone who monitors all mailing lists for non subscriber
mails.
Finding someone to moitors fate similarly for new failures may be hard
but its not an impossible task.
Also purely from a man-hours point of view what we do currently
is everyone looks at fate a bit which has to duplicate alot of looking
as its unsynchronized and at the same time alot is not looked at
It should be less man hours if this done by a single person in some
semi automatic/manual way.
new failures can be detected automatically, some unstable tests and
unstable clients may need to be filtered the rest then could
potentially be sent to #ffmpeg-devel.
The human in this case would only need to maintain the list of
unstable tests/clients, some limits to avoid a failing test to trigger
a seperate message for every single fate client. And (s)he would have
to contact people who are known not to follow IRC (for example a
fate client maintainer whos client went out of disk space)

Its not that noone is doing this currently but someone doing this
semi-official and lifting the work from everyone else would be nice
and ATM noone feels responsible to attempt to automate this more
where possible, even though everyone would benefit from more automation
...

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

Does the universe only have a finite lifespan? No, its going to go on
forever, its just that you wont like living in it. -- Hiranya Peiri


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

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

[Michael Niedermayer]

On Wed, Sep 07, 2016 at 10:24:15PM +0100, Josh de Kock wrote:
> On 07/09/2016 18:48, Lou Logan wrote:
> >If you want to use "task" for this then that would be fine with me.
> >
> >Alternatively, a wiki page could be setup similar to:
> >
> 
> Are all these on the trac?

probably not
carl is the one who can probably judge quickest how many of these
are missing and still relevant


> It might be worth adding a 'small'
> keyword to help people find easier coding tasks on trac (also
> keeping it central).

agree

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

Into a blind darkness they enter who follow after the Ignorance,
they as if into a greater darkness enter who devote themselves
to the Knowledge alone. -- Isha Upanishad


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

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

[Josh de Kock]

On 07/09/2016 18:48, Lou Logan wrote:

If you want to use "task" for this then that would be fine with me.

Alternatively, a wiki page could be setup similar to:



Are all these on the trac? It might be worth adding a 'small' keyword to 
help people find easier coding tasks on trac (also keeping it central).


--
Josh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

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

[Michael Niedermayer]

On Wed, Sep 07, 2016 at 09:43:26PM +0200, Michael Niedermayer wrote:
> 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:
> > 
> > 
> > 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=open=reopened=task=id=summary=status=type=priority=component=version=priority
> stays magically up to date

shorter URL created:
https://trac.ffmpeg.org/report/15

also link added to wiki so people can find it

if anyone has a non developer task, just open a ticket and set its
type to task

[...]

-- 
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

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

[Michael Niedermayer]

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:
> 
> 
> 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=open=reopened=task=id=summary=status=type=priority=component=version=priority
stays magically up to date

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

The worst form of inequality is to try to make unequal things equal.
-- Aristotle


signature.asc
Description: Digital signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

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

[Lou Logan]

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?

> 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.

Alternatively, a wiki page could be setup similar to:


Keeping it up-to-date of course could be problematic.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel