mpv-player / mpv

🎥 Command line video player
https://mpv.io
Other
28.68k stars 2.93k forks source link

code of conduct in the multi-cultural user base - non-violent communication #13109

Closed PurryPlatypus closed 11 months ago

PurryPlatypus commented 11 months ago

How do i start; i think, i should leave the template intact, annotate in-line, and append the actual focus of discussion at the end, see also below the logfile.

Don't ask questions about issues, errors or problems you have and instead open a proper issue with the right template from the previous selection. check, done

This template is meant for questions about the workings of mpv, to clarify about unspecified behavior of options or command, or anything else that is not well described and needs clarification.

Before asking a question make sure it hasn't been asked or answered yet. https://github.com/mpv-player/mpv/labels/meta%3Aquestion checks out - no results for the provided link + the keywords code of conduct

Log file

Even if you think it's not necessary at first, it might help us later to find possible issues. Make a log file made with -v -v or --log-file=output.txt, attach it to the issue, and replace this text with a link to it. done output.txt

here we go

I'd like to insist that this here issue is not meant as a continuation of a previously deemed "too heated" discussion. I'm quite new to the contributing to FOSS/FLOSS projects thing - so, if you dare to call it that, i'm not quite broken in, yet. Since the project Wiki, as well as the FAQ, and an additional search for "code of conduct" didn't yield useful results, I intent to establish a code of conduct by which no-one will have to endure an abrupt shut-down of their contribution attempts.

I've heard about "non-violent communication" and communication theory in general, which should be useful for everyone. In short; there's a sender and a recipient - one intends to send meaning, via their personal POV, kind of "encoding" the meaning into a public message, and the multi-coloured recipients (in this here scenario) try their best to translate that intended meaning back into their own POV / frame of reference - everyone has a rather unique internal model of reality - i acknowledge this scientific fact. I'm by no means a communications expert, myself - my skills certainly require some honing. I'd like to leave these keywords here, for peaceful on-topic consideration.

I'm humbly asking, to take the issue #13082 as a case study - or any other "too heated" discussion - as an example.

How should we communicate with each other, in order to not unintentionally "slap someone in the face"?

llyyr commented 11 months ago

Hi, I'm not really part of the mpv org so I can't speak on their behalf but I do contribute sometimes so I might be able to respond to this and the previous issue.

First of all, "too heated" is just the text that Github shows when an issue is locked for any reason. [1] Based on previous history with such tickets, they have a high likelihood of onlooker trolling, which is why it was locked from what I can tell.

mpv does have a Code of Conduct that you can find in DOCS/contribute.md.

As far as #13082 goes, I don't believe the Santa hat represents any religion but that's beside the point. mpv isn't opposed to other festive icons being added to the osc, including the santa hat, given someone cares enough about it to send a PR. mpv is the product of the culture that builds it, not the other way around. There just happen to be mpv users who care enough about the Santa hat to add it to mpv. mpv also has a ton of Chinese users and plenty of mpv's users are anime enjoyers, so if any of them wanted to add a logo for the Lunar New Year or anime icons, they would be welcome too.

There is no exclusion here, if a particular festive logo isn't there it just means that people who care about it just don't care enough about mpv to add it. I don't think a PR adding more festive logos for the osc idle screen would be rejected.

PurryPlatypus commented 11 months ago

mpv does have a Code of Conduct that you can find in DOCS/contribute.md.

Thank you! Turns out, there is an established code of conduct - mildly occluded by the project structure: https://www.contributor-covenant.org/version/2/0/code_of_conduct/

I'll have to read this tomorrow - it's late here (local time). Please keep this issue open, until i had a chance to summarise what i might've done wrong - i'd like to do that. Meanwhile, please keep posting your thoughts - i intended this issue to be a calm learning experience, for me, and for the inclined reader. (I won't judge anyone else's behaviour [publicly] - that's for their consideration.)

EDIT: please tell if you oppose using issue #13082 as a case study - preferably with a reason. (scientifically, it seems, we've got N=1 in favour [implicitly]) EDIT2: well, including myself, that'd be N=2 - but i might be biased, so, let's call it N=1.5 ;)

N-R-K commented 11 months ago

I'm quite new to FOSS/FLOSS projects

Issue trackers are mainly meant for submitting bug reports and/or feature request. It's not a place for conducting "scientific experiment on communication" or whatever on earth you're trying to do in here. If you're trying to improve your social skills, then an issue tracker for a media player is certainly not the place for it.

no-one will have to endure an abrupt shut-down of their contribution attempts.

If you want to contribute send a pull request fixing a bug or adding a feature that's been requested in the tracker (and not disapproved by any of the devs).

Opening an issue that's already been shut down multiple times before (talking about https://github.com/mpv-player/mpv/issues/13082) is not contributing anything, it's wasting time at best and annoying nagging at worse. Only thing that was shut down there was further waste of time. Which is the proper course of action for this issue as well.

haasn commented 11 months ago

If you want to contribute send a pull request fixing a bug or adding a feature

Fixed

Agree with the rest, though. Sir, this is a bug tracker.

mia-0 commented 11 months ago

So, my take on this, since it’s been on my mind…

One fundamental property of free software is that it takes shape through the people who build it. Conflict often arises when a vision of what it should and shouldn’t be is imposed on it—by project leaders, by people waging culture wars, by financial incentives…

13082 imposes such a vision, not only making demands of programmers to make changes and additions to the code in a purely practical sense, but more crucially dictating cultural values to follow and in a wider sense how the project should understand itself and how it is to be operated and governed in order to meet these demands.

In an attempt to neutralize the source of this conflict (seeing as its resolution seemed impractical to say the least), I removed the accursed hat (which was intended not as a symbol of religious commemoration but as a fun, cute gimmick to make people smile). But even if it was done out of mere avoidance, not taking either “side” of the argument, this also was seen as a forceful intervention. I imposed my idea of where fun and playfulness are outweighed by the potential to provoke external hostility, and disregarded what that meant for people who enjoyed building something they like through free creative synthesis; who had put time and effort into something only to see it thrown out and declared harmful at a moment’s notice.

mpv itself, as mplayer-uau before it, is the result of irreconcilable conflict between contributors and the visions of people who reigned over the code, sometimes more or less as uncompromising gatekeepers. And mpv has already seen multiple incidents of that past threatening to repeat itself. The hat issue might appear rather insignificant, but it has the potential to set a precedent with far-reaching consequences for the future of the project.

So yeah, this is one of those cases where I believe “contributions welcome” is an appropriate response. If you want to make a difference here, you’ll have to be part of the change.

paulguy commented 11 months ago

Could it be possible for external scripts to change/modify the existing icon in the way the santa hat is added? :p Someone making a bunch of festive, with some maybe being time-sensitive icons/additions to the icon that can be optionally dropped in to the scripts directory would be fun. Obviously this doesn't have to be any sort of official thing, just some third party thing that's maybe linked to from the wiki.

TheAMM commented 11 months ago

Having osc.lua check the userdata property for a custom logo (or headwear) would be fairly trivial, yeah. Add a userscript to manage a directory of logos and probabilities, and get all the flavour you would want. As long as people are able to procure the ASS vector commands.

2023-12-13_21-22-51

MimaHakurei commented 11 months ago

Considering that the poster is a brand-new account with no actual commit-history whatsoever... and claims that something as secular as the modern-day Santa hat 🎅🏻 is a "Christian" symbol somehow....

Can we just close the issue and treat it like the spam it is?