The Keys to Success When Launching Your Own Open Source Concept
Have you been thinking of launching an open source project or are you in the process of doing so? Doing it successfully and rallying community support can be more complicated than you think, but a little up-front footwork and howework can help things go smoothly. Beyond that, some planning can also keep you out of legal trouble. Issues pertaining to licensing, distribution, support options and even branding require thinking ahead if you want your project to flourish. In this post, you'll find our newly updated collection of good, free resources to pay attention to if you're doing an open source project.
The Open Source Definition is where every project leader should start when it comes to how open source projects should be distributed, and what actually qualifies as open source. It's also good to review Open Standards requirements.
It's also worth taking note of why some open source projects fail There are some common reasons, as noted in this post from opensource.com. The post includes these key tips:
If your codebase is too big, it's going to limit who's going to be able to download your code.
There is no good reason in 2015 for a FOSS project to not have public source control. This helps people contribute and determine the health of your project based on the date of the last commit.
If your source control has no web viewer and/or no documentation, these two are obvious things to have.
As we noted in this post, the Software Freedom Law Center has a set of very good online resources on how open source licenses and copyrights work, and much more. Legal issues are smart to anticipate up front. The authors are attorneys who were part of creating popular open source licenses. It's also an excellent idea to keep up with urrent and archived editions of the International Free and Open Source Software Law Review
For an easy to digest, plain language discussion of license types for open source projects, and which license will work best for your project, try FOSS License Wars. The discussion is broken up into chapters that you can skim as you see fit, and the information is solid. We have much more information on licenses available here, and the Free Software Foundation has a good primer. It's also an excellent idea to visit SourceForge and GitHub to review the many projects housed there, which types of licenses they have, how their communities work, and more. Should your project be housed there?
If you're stitching together open source code or deploying applications, Hewlett-Packard's free application Fossology is designed to analyze the source code for any project and report accurately on which licenses are being used.
For developers who want learning resources, Developer.com offers useful tutorials on topics such as Python programming, and W3Schools has excellent, free tutorials on web development topics. You can find many more free development resources in our post here.
Finally, don't forget that OStatic itself is an excellent forum for getting questions answered. Type a question in at any time in our Member Questions area (see the Questions button on the home page) and you'll get answers from experts. You can also read some of OStatic's many interviews with open source project leaders, some of them found here, here, and here, and find a whole series of interviews on open source cloud-based projects here.