Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
bold italic
  • Loading branch information
benbalter committed Mar 17, 2015
1 parent b0e08ef commit 8a46a5a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
Expand Up @@ -65,4 +65,4 @@ Put another way, if you’re happy with your code when it leaves the firewall, i

While it's certainly possible for your organization to maintain a waterfall or closed-source workflow and then hit publish, the likelihood of that project's open source success is exceedingly rare. If you're looking to take your first (or second) step into the open source community, start not by optimizing for external engagement, but by optimizing for internal collaboration.

*This post is part of a series on best practices in open source. You may also be interested in [Five best practices in open source: external engagement](http://ben.balter.com/2015/03/17/open-source-best-practices-internal-collaboration/).*
***This post is part of a series on best practices in open source. You may also be interested in [Five best practices in open source: external engagement](http://ben.balter.com/2015/03/17/open-source-best-practices-internal-collaboration/).***
Expand Up @@ -95,4 +95,4 @@ As a result, to be successful, you'll want to explicitly let developers know tha

There's a world of difference between uploading a zip file to an FTP server and open source. Open source is about fostering communities around shared challenges, and as the maintainer of an open source project, that responsibility falls squarely on your shoulders. To be successful, simply publishing code isn't enough. Go out of your way to encourage, praise, and support each contributor and each contribution as if the project's success depended on it, because in reality, it does.

*This post is part of a series on best practices in open source. You may also be interested in [Five best practices in open source: internal collaboration](http://ben.balter.com/2015/03/08/open-source-best-practices-internal-collaboration/).*
***This post is part of a series on best practices in open source. You may also be interested in [Five best practices in open source: internal collaboration](http://ben.balter.com/2015/03/08/open-source-best-practices-internal-collaboration/).***

0 comments on commit 8a46a5a

Please sign in to comment.