I have written a website, which is my big idea. Now I'm planning a version for intranets.

The big question in my head is: "shall I make it open source?" and next are:

  • What do I have to prepare
  • What do I need for a good start
  • What is the best way to find people with the same interests
  • Who gives me the proof that I won't find a copy of my idea on another page, stolen from my open source code (edit: meant like: somebody breaks the open source spirit takes the idea and makes it a big business instead of contributing to the original like all others; please do not focus on this question, I guess I already understand by the yet given answers)
  • is SourceForge really THE resource / market place for open source

edit due to a comment:

  • in what format do I publish the code (it's acutally ruby on rails)
  • what license should I use
  • what's the best way to distribute it

Please Discuss with me, give some good arguments pro and contra.

Yours, Joern.

link|improve this question
Interesting question, though you do ask quite a lot of questions within this one question. I would focus on the technical aspect: in what format do I publish the code, what license should I use, what's the best way to distribute it. That way it's less subjective and at least they are all part of "how to open source my website". – Ivo Flipse Apr 30 '10 at 8:44
Voting to close because this question, even if interesting, has several issues. First, it's not one question, it's 8 of them. Second, "making your project open-source" is probably more a programming issue, and should go to StackOverflow.com. Third, you ask for a discussion, and this site is not a discussion board, it's a Q&A site. Fourth, your questions are anyway too wide and hard to answer precisely ("what is the best way to find people with same interests"). – Gnoupi Apr 30 '10 at 15:04
sorry, it's just the best board I know and there are many; ok no discussion, at least not such a deep discussion concerning to the reply depth – Joern Apr 30 '10 at 15:44
1  
i'm sorry, i don't see how this belongs here. you need a discussion forum for this. – quack quixote Apr 30 '10 at 20:22
feedback

closed as not constructive by Gnoupi, quack quixote Apr 30 '10 at 20:22

This question is not a good fit to our Q&A format. We expect answers to generally involve facts, references, or specific expertise; this question will likely solicit opinion, debate, arguments, polling, or extended discussion. See the FAQ for guidance on how to improve it.

4 Answers

up vote 2 down vote accepted

For one part, your idea cant be protected so easily. Even if you manage to patent it (good luck), the patent is worth next to nothing if you dont have the money to pay the lawyers. If you had that money, you probably wouldnt ask here, but be busy hiring programmers.

Now just look at all the StackExchange clones out there. Show a good idea, and quite a few people jump at it and reprogram it. Its not that much of a deal. Many people have time on their hands, but not the great idea. The idea of StackExchange is great and new, and what sets it apart. But ideas are fair game.

You can protect your code, though. But if you do, you are out of the game if someone rewrites your program and is more successful as you.

By making your program open source, that same guy might actually help improve it. Your customers will still pay for your knowledge about the tool, which becomes better by others contributing. You may get more customers, and do more support, and less programming.

That means, if your idea is good enough to become a success, and you dont have money to back you, open source opens a chance to evolve your idea. If you stay on your toes, you might make more money from it than otherwise.

One particularly painful part of the open source project is this: Other people read your code and tell you what mistakes there are. But if you are willing to pick up on that, you will become a better programmer faster than with hacking alone. The price you pay is less control over the idea.

Also, if your idea is good for big business, the big ones might just take it over anyway. The year or so of programming you may have put in there means nothing to a firm. They just rewrite the thing and ignore you. That way they get the knowledge of the code, written by their standards by their people, which makes it more valuable to them than your code would be, stolen or not.

If you choose to go open source, I recommend using a license that prevents commercial use of your code. They should at least pay for the programmers. Make selling your code or knowhow an option.

link|improve this answer
sorry not enough repu for up voting, very good post! helps me a lot – Joern Apr 30 '10 at 15:39
flagging this as the right answer doesn't mean I'm not interested in more answers :) – Joern Apr 30 '10 at 15:42
feedback

The bottom line about disclosing source code under free licenses is allowing other people to reuse it. There is a benefit for you too: you get more people looking at the code, finding bugs and eventually reporting them to you or even fixing them and sending you patches.

But you said "stealing", not "reusing", which proves you have a wrong mindset.

No, please don't open-source your code. We don't need it. Because we don't call eachother thieves. We don't need many people jumping into our free software boat just because it's trendy. If that keeps happening, the boat will sink.

link|improve this answer
sorry it was more meant like, somebody takes the idea and makes a big business out of it, just look at how similar some IE features are compared to Firefox features. – Joern Apr 30 '10 at 8:57
Firefox had a popup blocker an the password save function and some time later the IE had the same features AND the same visual design / the same visual implementation of these features – Joern Apr 30 '10 at 9:05
Look and feel aren't the same as open source code: en.wikipedia.org/wiki/Look_and_feel – Matthew Lock Apr 30 '10 at 9:22
ok; I understand already, you're both right; but as I wrote my questions, I also had this in mind; I guess I know now how to deal with open source in this case; it's more a certain spirit... – Joern Apr 30 '10 at 9:32
1  
@geek - not sure there is a need to be overly judgmental though. The second paragraph is not really useful to the question, it's only a pretentious "you don't understand the spirit, we don't need your code, get lost". Keep it objective. – Gnoupi Apr 30 '10 at 15:21
show 2 more comments
feedback

First I'd recommend to find the project code storage, such as SourceForge.net, codeplex, google code, etc.

For a good start you need strong willing only.

Same interests people are hard to find. That is my experience.

Open source can't be stolen. So either do not open your code, or change the way you think of "open source".

The best open source license is more dependent on your tastes than on circumstances. IMO

The best way I found to distribute my software is to make announces on as many sites as possible. I made three announces of three different sites, since than I have 10 downloads per day.

link|improve this answer
sorry cannot upvote; to less repu – Joern Apr 30 '10 at 9:07
what is the url to your page? now I'm interested :) – Joern Apr 30 '10 at 9:10
The project website is in Russian. English in on the way. ovulyashki.dp.ua The project sources can be found here: sourceforge.net/projects/ovulyashki – Vasiliy Borovyak Apr 30 '10 at 9:14
2  
Sure Open Source can be stolen! The license allows you to do some things, and you are not allowed to break those rules... If you use GPL, and then someone puts that code into a closed source product and then sell it and do not share the new code, they stole your code.... But if this is what you are afraid of then don't do it, since this will happen and you can do little to stop it. – Johan Apr 30 '10 at 11:11
1  
@Johan, It's not stolen, you haven't deprived someone else of it. They have made illegal reproductions, something quite different from larceny. Regardless, you're right; if you don't want someone using the software against your terms, keep it closed source. – Chris S Apr 30 '10 at 13:38
feedback

Make sure you really want your code Open Source. It's one of those decisions that's somewhere between "extremely difficult" and "impossible" to undo once you've released your code.

link|improve this answer
good point, simple, clear and definately very important – Joern Apr 30 '10 at 20:07
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.