Originally posted on TechCrunch:
cool site for generating a report card for open source projects on GitHub
The purpose of SourceContribute.com is to give organizations enough information to create a well-defined and clear strategy for interacting with Free/Open Source Software communities.
According to an article on Linux.com, http://www.linux.com/news/enterprise/biz-enterprise/707402-four-open-source-best-practices-enterprise/
“[financial services firms] haven’t yet developed the processes, culture and mechanisms needed to work directly with the community to obtain support, make contributions and influence project directions.”
how Puppet Labs deals with community: http://www.linux.com/news/featured-blogs/196-zonker/707984-puppet-labs-ceo-how-to-grow-an-authentic-open-source-community/
According to the thread about this on reddit (r/programming), the electrical costs are for the servers.
This is one of those essential costs that’s required when developing free/open source software that is meant for servers or for particular hardware configurations. This is also required for mobile web app development, to ensure that the interface works on all sorts of smartphones. Donating to a free/open source project helps a lot with the essential costs. Donations may not be able to pay for more full-time development work but they can at least keep the electricity flowing to the hardware and keep the servers running!
- Mersenne Twister
Re-blogged from: http://www.scei.co.jp/ps4-license/
Getting back to that ROI thing. I’ve found success from being attached to the ui-router project, in particular writing good documentation. Having that under my belt has opened up so many opportunities to me and helped to expand my network. It isn’t why I contribute, but I’d be lying if I said it wasn’t nice to get that payoff.
There are lots of stories of others who’ve experienced documentation success. Joel Hooks, told me his story. He got his start by writing the documentation for the RobotLegs framework for ActionScript. He stumbled onto his project just like me. After researching it he felt like he found a diamond in the rough. Here was this obscure yet beautiful project. In his heart he knew it needed documentation to become popular. Writing the docs for that one project kickstarted his entire career! He was propelled into an evangelism role for the project and started speaking at conferences (even though speaking was absolutely nerve wracking to him). Writing docs compressed his five year career plan into about one year. Ha, I knew there were kickbacks! He ultimately became a consultant and even wrote a book and now he also teaches important concepts online via articles and video tutorials.
The key point is that he would have never written the RobotLegs framework—it was the stuff of legend—but he could write the fucking docs. I’m crying right now, it’s too beautiful.
I also spoke with Matias Niemelä who found success in a similar fashion. He blogged for a while, mostly about MooTools, hence his site’s name yearofmoo. He started to learn Angular and wasn’t really finding good learning materials on the web (back during the pre-1.0 days). So he made an article on SEO and it was really popular. So he wrote another article and the popularity continued, more and more. This caught the attention of the core team and somewhere between Matias’ third and fourth article Misko (an angular core team member) asked him if he’d be able to help revamp the Angular docs as well as create ng-animate as a contractor for Google. It paid off for Matias.
Well there you go, Google can act like Apple whenever it wants to. Building their proprietary products on top of free/open source software, just like Apple does with the nicest user interface, Cocoa.
While you can’t kill an open source app, you can turn it into abandonware by moving all continuing development to a closed source model. Just about any time Google rebrands an app or releases a new piece of Android onto the Play Store, it’s a sign that the source has been closed and the AOSP [Android Open Source Project] version is dead.
Excellent article on making your first free/open source software contribution. Aimed at software developers, software engineers, web developers, computer scientists (and comp.sci. students).
Originally posted on Spencer Moran:
As a senior Computer Science student, I am constantly hearing about how great it is to contribute to open source projects on github. Many job listings list it as a qualification or a “plus”, and it is casually thrown around in conversation at all kinds of seminars and events at school. Sounds great, I should do that! The only problem is: I’m a huge noob! I’ve done well in my computer science classes at school, sure, and I’ve built some projects that my family and friends think are cool, yes, but surely I can’t contribute in any meaningful way to a project with real users, right? Right?
Wrong!! There are a variety of different ways to make substantive contributions to open source projects on github, even as a total rookie. You don’t have to be able to read and understand all 100,000 lines of rails or know how to fix that issue with the dynamically stacking grid in bootstrap to be able to do something meaningful that affects real users. There are ways for everyone to contribute.
I recently made my first real contribution to an open source project, and as small as it was, I got a refreshing sense of accomplishment knowing that there were people out there using something that I had written a tiny part of. You have to start small and work your way up. Here is my advice to anyone who wants to contribute to an open source project on github, but has just felt overwhelmed trying: