[FFmpeg-devel,RFC,Type,2] Revert "doc/developer.texi: Add a code of conduct"

Submitted by Derek Buitenhuis on May 14, 2018, 4:50 p.m.

Details

Message ID 1526316627-25927-3-git-send-email-derek.buitenhuis@gmail.com
State New
Headers show

Commit Message

Derek Buitenhuis May 14, 2018, 4:50 p.m.
It was never enforced, and there is no documented way to enforce it,
rendering it useless.

This reverts commit 89e9393022373bf97d528e6e9f2601ad0b3d0fc1.
---
 doc/developer.texi | 29 -----------------------------
 1 file changed, 29 deletions(-)

Comments

Josh de Kock June 10, 2018, 7:56 p.m.
On 2018/05/14 17:50, Derek Buitenhuis wrote:
> It was never enforced, and there is no documented way to enforce it,
> rendering it useless.
> 
> [...]

I think this is the best thing to do first. We could always re-add a 
more 'proper' CoC later, but for now there's no point creating more 
confusion. I stated this on IRC but saying this on the ML so it is 
documented more publicly.

Also, it has been more than a month since this was posted with no 
resolution, when do you intend to take, or expect others to take, actual 
action with regards to this?
Ivan Kalvachev June 11, 2018, 6:02 p.m.
On 6/10/18, Josh de Kock <josh@itanimul.li> wrote:
> On 2018/05/14 17:50, Derek Buitenhuis wrote:
>> It was never enforced, and there is no documented way to enforce it,
>> rendering it useless.
>>
>> [...]
>
> I think this is the best thing to do first. We could always re-add a
> more 'proper' CoC later, but for now there's no point creating more
> confusion. I stated this on IRC but saying this on the ML so it is
> documented more publicly.
>
> Also, it has been more than a month since this was posted with no
> resolution, when do you intend to take, or expect others to take, actual
> action with regards to this?

If I remember correctly, the CoC has been voted, so it would need
another vote to remove it.

I do not see any immediate problem that compels messing with CoC and
the politics associated with it.

The less people are involved in politics, the more work on code could be done.

Keep Calm and Carry On.

Patch hide | download patch | download mbox

diff --git a/doc/developer.texi b/doc/developer.texi
index a0eeefe..0d72966 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -419,35 +419,6 @@  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.
 
-@chapter 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}
 @chapter Submitting patches