How to make a closed source application open source

oldpond · 2011-09-29 02:51:20

Hi folks. I have an Android application on the market, and I want to make it open source so the community can work on it. I know this isn't exactly Arch related, but I wouldn't mind some advice on how to do that. The source is hosted on git now, so I can just open that up. I guess I should pick a license to release it under. Anything else I should be thinking of?

ewaller · 2011-09-29 04:01:20

Assuming you hold all of the copyrights, you can release it however you want (Assuming you are in the US. Some countries don't have the notion of public domain).

If you want others to have the right to distribute, they need permission from you, hence the license.
If you want to force those distributing the code to give back to the community (and you), choose a "Copyleft" license
If others don't distribute, I don't think you can require they give back.

You can, as the copyright holder, dual license -- have your cake and eat it too.

I use the GPL. Here is an article on how to use it

oldpond · 2011-09-29 04:10:44

That's helpful, ewaller. I hold all the copyrights although my application uses libraries from an LGPL project. I also have a trademarked logo for the icon, etc. That shouldn't change anything, correct?

I also need to set up a forum and bug database. I noticed today my hosting company (BlueHost) doesn't seem to have a bug tracker. They have phpBB. What are the popular choices for these things?

bernarcher · 2011-09-29 13:14:16

It appears this is a more general discussion.
Moving to GNU/Linux Discussion.

oldpond · 2011-09-30 15:12:07

Yeah, so, basically a web site, a bug tracker, a forum, and a code repository. Add the OSI license to each source file, and open the repository. Make some coolaid and wait for the crowds to arrive.

Done and done. Thx for the help.

barzam · 2011-10-01 13:15:39

Basically the way licensing works is that you grant others certain rights to use your work. This works the same for everything: books, images. paintings, software.. However it might be advantageous to use a proper software license for the code and another license for documentation and/or artwork as these are usually better written. The easiest way is to see how eg. a free computer game has licensed its graphics.

One more thing, decide whether you want to use a copyleft license (most famous example being the GPL) or a non-copyleft license (BSD-style license). Personally I think the GPL is the better choice but it's up to you of course.

I don't know about the Android Market when it comes to free software, but it's not allowed in the Appstore (if you'd want your application there as well). If Google by any reason prohibits the distribution of free software you must dual license your application and provide the non-free version in the Market. This is perfectly fine if you are the copyright holder.

Good luck with your project, and thanks for making the world a better place by making it free software!

Arch Linux

#1 2011-09-29 02:51:20

How to make a closed source application open source

#2 2011-09-29 04:01:20

Re: How to make a closed source application open source

#3 2011-09-29 04:10:44

Re: How to make a closed source application open source

#4 2011-09-29 13:14:16

Re: How to make a closed source application open source

#5 2011-09-30 15:12:07

Re: How to make a closed source application open source

#6 2011-10-01 13:15:39

Re: How to make a closed source application open source

Board footer