6 Things to Avoid When Contributing to Open-Source Projects

• webapp

  1 4 0.0 Vue

  Discontinued Qvault web app frontend (by qvault)

  

Let’s take a look at some common pitfalls that developers fall prey to when working on an open-source project. As a side note, we recently open-sourced the Qvault front-end, so take a lookat that if you want to help out.

• go

  2,073 119,718 10.0 Go

  The Go programming language

  

Some codebases have thousands of open issues, take the Go language project, or the nocode repository as an example. No one wants to read your duplicate issue or review your duplicate pull request. Make sure there isn’t an existing open or closed issue for what you are trying to address.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• WHATWG HTML Standard

  137 7,695 9.4 HTML

  HTML Standard

  

Rewording documentation and other frivolous changes make you look like these assholes. This particularly atrocious example is not only scoped to pointless documentation changes but actually makes the documentation worse.

• wprig

  8 1,265 6.7 PHP

  A progressive theme development rig for WordPress.

  

Not every project will require (or care) about commit squashing. That said, there are no projects that require not squashing commits. To be on the safe side just give ’em a squash.

Suggest a related project