RepoMirrors/mpv
1
0
Fork 0
mirror of https://github.com/mpv-player/mpv synced 2024-12-27 01:22:30 +00:00
Code Issues Releases Wiki Activity
29ea6e5e4a
mpv/CONTRIBUTING.md
wm4 07d8a0e142 CONTRIBUTING.md: encourage users to ping forgotten issues 
Now I'm not sure if this is really necessary to explicitly mention. But
then there have been issues and pull requests without being properly
looked at for a week or longer.
2016-02-01 20:13:39 +01:00

1.3 KiB
Raw Blame History

Reporting bugs

  • State your platform and mpv version.
  • Make sure you're actually using the latest mpv release. Linux distributions in particular love redistributing ancient and unmaintained mpv releases.
  • Attach a log file made with -v or --log-file=output.txt.
  • Avoid attaching text files packed in archive files (zip/rar/...), unless explicitly asked so. There are better means, such as using http://sprunge.us
  • If you think this is file specific, upload a sample file and link it.
  • Don't report multiple unrelated/barely related bugs in one issue.
  • If you don't get a reply after days, be sure to post a new message to the issue - it could have been overlooked or forgotten.
  • Read: https://mpv.io/bug-reports/

Asking questions

Preferably, asking questions should be done via IRC (#mpv on irc.freenode.net), but asking questions by opening a github issue is also barely tolerated.

When asking on IRC (#mpv on irc.freenode.net), don't ask to ask, just state your problem. Stay long enough until someone gets a chance to reply. Sometimes it can take hours.

Sending patches

See: https://github.com/mpv-player/mpv/blob/master/DOCS/contribute.md

In particular, be aware that all changes to GPL code must come with the implicit agreement that they might be LGPLv2.1+ relicensed at a later point.