4 ms·
Release it under GPL if you can, put it on github or bitbucket, document the bugs as "issues," focus on fixing show stoppers and high-visibility user complaints
by pXMzR2A 12y ago
Release it under GPL if you can, put it on github or bitbucket, document the bugs as "issues," focus on fixing show stoppers and high-visibility user complaints, don't worry too much about it (all these apps are buggy, we just don't like show stoppers), ask for donations and for volunteer drive-by coders.
- shouldbeworking 12y agoThis is a bad idea. You have to have a plan if you have a for-profit open source product. You need to give contributors something so they don't feel like they're being taken advantage of. It's complicated. It isn't as easy as just open sourcing it and asking for contributions.
- pXMzR2A 12y ago> You have to have a plan if This is a moot argument. Of course s/he has to have a plan if s/he wants to be in business. What was asked was suggestions, not detailed strategy deliverables.
- bbcbasic 12y agoNot a good idea if the OP wants to profit from the app. Might be an OK idea if he just wants to get his name out there, and have something good for the ol' CV.