Skip to content

Latest commit

 

History

History
36 lines (25 loc) · 1.88 KB

CONTRIBUTING.md

File metadata and controls

36 lines (25 loc) · 1.88 KB
Raw

Contributing to github-drama

What qualifies as drama?

There's no agreement on what's considered dramatic enough to be included in github-drama. There are plenty of "non-serious" GitHub threads, where the usual GitHub politeness gives way to reaction GIFs and one-word replies, turning into something like a 4chan thread, but less funny. Common signs of drama: many unconstructive comments, many downvote reactions, removed or hidden comments. If a repository's maintainer has locked conversation on a thread, that's also a good indicator that it could be included here.

How do I find drama?

Go into a GitHub project's issues, and sort by "Most commented" or "Most reactions".

Adding new drama

A new drama entry can be added into the list in the short or extended format. Short entry consists of the single link:

[user/repo/issues/1](https://github.com/user/repo/issues/1)

Extended entry can contain drama summary and one or more links:

user/repo - Drama title
* Summary line 1
* Summary line 2
* [issues/1](https://github.com/user/repo/issues/1)
* [issues/2](https://github.com/user/repo/issues/2)
* [Other link text](https://example.com/other-link-url/)

Writing guidelines

  • If there are non-github links that describe the drama, consider adding them. High priority external links to add are articles in popular journalistic media.
  • Adding drama summary is not mandatory. In the simplest case the entry can just consist of the single link to the dramatic thread. Summary can be helpful when there are multiple links that need to be logically grouped to better understand the drama.
  • When drama summary is added, it must be as neutral as possible. Describe facts and events, but do not assess drama participants' actions, advocate for any political/ideological views, or use a negative speech. When in doubt, leave out any details and make summary as short as possible.