[FFmpeg-devel] [PATCH] doc/developer.texi: Add a code of conduct

Michael Niedermayer michael at niedermayer.cc
Mon May 23 18:26:41 CEST 2016


On Sat, May 21, 2016 at 05:28:09PM -0400, Ronald S. Bultje wrote:
> Hi,
> 
> On Sat, May 21, 2016 at 11:32 AM, James Almer <jamrial at gmail.com> wrote:
> 
> > On 5/18/2016 3:40 PM, Michael Niedermayer wrote:
> > > Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>
> > > ---
> > >  doc/developer.texi |   29 +++++++++++++++++++++++++++++
> > >  1 file changed, 29 insertions(+)
> > >
> > > diff --git a/doc/developer.texi b/doc/developer.texi
> > > index 6db93ce..4d3a7ae 100644
> > > --- a/doc/developer.texi
> > > +++ b/doc/developer.texi
> > > @@ -403,6 +403,35 @@ finding a new maintainer and also don't forget to
> > update the @file{MAINTAINERS}
> > >
> > >  We think our rules are not too hard. If you have comments, contact us.
> > >
> > > + at section Code of conduct
> > > +
> > > +Be friendly and respectful towards others and third parties.
> > > +Treat others the way you yourself want to be treated.
> > > +
> > > +Be considerate. Not everyone shares the same viewpoint and priorities
> > as you do.
> > > +Different opinions and interpretations help the project.
> > > +Looking at issues from a different perspective assists development.
> > > +
> > > +Do not assume malice for things that can be attributed to incompetence.
> > Even if
> > > +it is malice, it's rarely good to start with that as initial assumption.
> > > +
> > > +Stay friendly even if someone acts contrarily. Everyone has a bad day
> > > +once in a while.
> > > +If you yourself have a bad day or are angry then try to take a break
> > and reply
> > > +once you are calm and without anger if you have to.
> > > +
> > > +Try to help other team members and cooperate if you can.
> > > +
> > > +The goal of software development is to create technical excellence, not
> > for any
> > > +individual to be better and "win" against the others. Large software
> > projects
> > > +are only possible and successful through teamwork.
> > > +
> > > +If someone struggles do not put them down. Give them a helping hand
> > > +instead and point them in the right direction.
> > > +
> > > +Finally, keep in mind the immortal words of Bill and Ted,
> > > +"Be excellent to each other."
> > > +
> > >  @anchor{Submitting patches}
> > >  @section Submitting patches
> >
> > I agree with this. It can and should be improved/extended over time, but
> > it's a good
> > start.
> 
> 
> +1.
> 
> Constructive criticism for next version: I agree with most people that we
> need a conflict resolution clause in here. We don't need to be as specific
> as VLC in terms of how to punish misconduct, although I think it would be
> good to have, but at the very least we need to document how it will be
> managed and who's in charge of managing that. Right now, if people violate
> the CoC, w'll throw our hands in the air and nobody knows what to do next...

we first try to politely point it out to people that their tone is
insulting/disrepectfull or whatever.
has happened recently, and worked in stoping it
i would count that as a success

But lets assume someone doesnt stop or keeps restarting 

if we really end up needing to, and i hope we wont then in the case
of the mailinglists, the mailinglist admins could take care of it like
they do with other unwanted content

ATM the mailinglist admins are lou logan and compn
The critical factor is of course that they are neutral (no history
of taking sides in conflicts) which i belive applies to both.
And that whatever they do, they do it consistently,
same offense ->  treated similar
and some attempt is made to do the minimal and effective thing
for example if talking with people makes them
stop thats better than baning them for some period ...

And i belive being told by the ML admin to stop and not do something
again has some weight ...

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

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.
-------------- 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/20160523/a0f14c70/attachment.sig>


More information about the ffmpeg-devel mailing list