Open-source, not open-contribution

This page summarizes the projects mentioned and recommended in the original post on

Our great sponsors
  • Mergify - Tired of breaking your main and manually rebasing outdated pull requests?
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • SonarQube - Static code analysis for 29 languages.
  • litestream

    Streaming replication for SQLite.

  • github

    Just a place to track issues and feature requests that I have for github

    Github really needs to allow people to disable the "Pull Request" tab on repos, to reduce the stigma around not accepting pull requests. 3 years and counting.

  • Mergify

    Tired of breaking your main and manually rebasing outdated pull requests?. Managing outdated pull requests is time-consuming. Mergify's Merge Queue automates your pull request management & merging. It's fully integrated to GitHub & coordinated with any CI. Start focusing on code. Try Mergify for free.

  • Picnic CSS

    :handbag: A beautiful CSS library to kickstart your projects

    I've disabled Issues in some of my more popular but end-user libraries and I couldn't be happier. Specially notorious was a CSS library[1] where many of the issues were on the level of "hey can you give me the code for X" or "how do you do X" where X was a general CSS question and not related to the library at all. I've received a bit of hate when I closed some of my repos issues as a PR [2][3]:

    > If you spot a bug or any other issue you may go to hell because this software is officially Bug Free(TM).

    > part of offering these to the public through open software is maintaining them and allowing feedback from users.

    > It seems umbrella.js project suffers the same desease.

    I've noticed there was a strong push around 2016-2018 to recommend newbie programmers NOT to go to Stackoverflow, but instead to ask the questions straight in the Github issues. Turns out, the problem was low quality questions and not the medium at all, and that just converted an issue that StackOverflow had solved long ago into burnout for open source developers on Github.

    There's so many entitled developers out there that will come and demand changes. Github needs to step up their game and give authors more powerful tools. It might make new devs feel less welcome, but the balance is tipped way too much to allow anyone to create massive spam for projects right now.




  • is a JavaScript, client-side editor for general diagramming and whiteboarding

    This was a problem for us and the lack of the ability to switch off PRs continues to cause problems.

    Community submissions are virtually always throw away, particularly on a complex code base. We ended up saying it's a legal problem [1], which it partly is. But throw away not only because of quality issues, always because of project scope issues.

    Yes, you feel the project is completely useless unless emoji icons animate in diagrams. That's great, fork the project and kill ours off by adding the feature (which they won't and it won't).

    When you know what the project scope is, tight enforcement of that scope is critical to prevent the complexity of the project from running away and ultimately killing the project entirely.

  • git2html

    github clone of

    On that list, there are projects like . It makes a set of static files, which could be uploaded to any static hosting provider, including github pages.

  • hub

    A command-line tool that makes git easier to use with GitHub.

    Did you ever try setting up an issue template for bugs only, like this project [1]? I'm considering doing that for my own project and I hope it will be effective.


NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts