Announcing Open Source Guides
github.com
Announcing Open Source Guides
1–10 of 28 posts
Re: Announcing Open Source Guides
#2[deleted]
Re: Announcing Open Source Guides
#3I thought this was going to be a GitHub implementation of GitBook. Excitement fell when I clicked through. However, anything that makes getting into open source easier is good in my books.
Re: Announcing Open Source Guides
#4Good move. Should help newbies and fence-sitters participate more!
Re: Announcing Open Source Guides
#5I thought this was going to be a GitHub implementation of GitBook. Excitement fell when I clicked through. However, anything that makes getting into open source easier is good in my books.
ditto. I was thinking it would be along the lines of Digital Ocean's curated how-to's/guides.
Re: Announcing Open Source Guides
#6They are quite good but why do I get the feeling the domain name was bought before the idea was decided on.
Re: Announcing Open Source Guides
#7Building a successful and sustainable long term open source project is hard. It's nice to see GitHub contributing some knowledge share that will hopefully be useful to those wishing to get started or validate what they've learned the hard way.
Re: Announcing Open Source Guides
#8This is an excellent starting resource. As one of the maintainers of a popular open source project I was wondering how I could get help with the project by attracting new contributors as I work full time and find the balancing act hard.
Users have previously enquired about donations and I didn't know the best way to set up the project to accept them in a responsible manner. This guide points me in the right direction!
Re: Announcing Open Source Guides
#9Also check out the book "Producing Open Source Software: How to Run a
Successful Free Software Project" by Karl Fogel.
He just finished up the 2nd edition and made it freely available online: http://producingoss.com/
Re: Announcing Open Source Guides
#10I 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".