|
|
|
|
|
|
by wimagguc
3410 days ago
|
|
|
I love the looks, the texts and just how much effort Github put into these docs. After having read quite a few pages, I'm just a bit puzzled: who are these guidelines for? Corporates usually have their own open-source guidelines (we had one at my R&D jobs even before Github existed), and these docs are a bit overdone for the tiny projects that lone devs usually put online. You know what I mean, for the ones where a single-line guideline would have been enough: "Please, if you don't want to write a readme, at least add some in-line comments". |
|
|
My understanding (you'll find some of my work quoted here, and I contributed a small amount before that this was public) is that this resource is for individuals who want to be involved in open source, either as contributors or maintainers, to learn about how it works. That is, a lot of open source development is sort of a shared, "oral" history; this resource spells out a lot of things that those of us who have been in the scene for a while just know, but you have to learn at some point.