3 ms·
As the founder of an Open Source Startup, I absolutely support startups going the open source route. But, FWIW, I will add that this: Releasing your software
by mindcrime 14y ago
As the founder of an Open Source Startup, I absolutely support startups going the open source route. But, FWIW, I will add that this:
Releasing your software under an open source license will quickly expand your developer team.
is not necessarily true. Whether or not other developers jump in depends on a lot of factors, and it's entirely possible to release something as Open Source and get no pull requests or other contributions at all.
The reason I know this, is because I'm there. Our Enterprise Social Network - Quoddy[1] - is Open Source, licensed under a liberal license (ALv2) and is on GitHub, and has been for some time, and we've never gotten a pull request. Now to be fair, some guys did fork it and make some changes to support MySQL, in order to support some academic research they were doing. But we never got a pull request from them, so we'd have to go dig through their fork and sift through it to figure out what to bring over.
Now, our project might not have generated much interest from other hackers for a lot of reasons... it's a niche area (enterprise social networks), is written in Groovy (which is popular, but nowhere near as popular as some other languages), and we haven't really done that much to market the project. But that's kinda the point - going OSS can result in lots of outside developers jumping in to contribute, but it by no means guarantees that they will.
[1]: https://github.com/fogbeam/Quoddy https://github.com/fogbeam/Quoddy
- vorg 14y agoQuoddy seems to be an addon to Grails, which is a self-contained ecosystem. Despite the claims otherwise, Grϕϕvy has no real uptake outside Grails, only sporadic use. And Grails may be about to switch to vert.x [2], a polyglot (i.e. JavaScript, CoffeeScript, Ruby, Python, Grϕϕvy, Java) framework, which would make Grϕϕvy even more irrelevant. [2]: http://grails.io/post/48599814766/more-on-where-next-for-grails http://grails.io/post/48599814766/more-on-where-next-for-gra...