As someone who is also working on an open source website, I'd love to
hear your reasoning for suggesting a different term. Why does it
matter if it's a website or code which runs locally?
--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -- Benjamin Franklin
I think the key takeaway is that the term "open source" has nothing to
do with where the code actually runs (see disclaimer below). It has
to do with who has access to the code and what they can do with the
code. By opening up the source code according to most OSS licenses,
it's perfectly valid to take the code, rebrand the site and start a
competitor site- just like there have been forks of traditional
software (Emacs vs. XEmacs for example).
* Disclaimer: Depending on the license used I may not even have to
redistribute the changes I make to my competitor site (BSD, Artistic
and GPLv2 for example). Of course some licenses have special clauses
for "web delivered applications". So yes, where it runs is a factor
in the "redistribution" clause, but most OSS licenses don't force you
to share code changes for web applications.
--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
I won't guess what snitko wants to do (his list of reasons may or may
not be comprehensive), but I will say that snitko should choose a
license which is appropriate for his goals. For better or worse his
stated goals aren't really legally enforceable.
I see Teachmate.org is GPLv3 and know at one point in time RMS was
complaining about websites using GPL'd code but since they weren't
redistributing binaries they didn't have to share their improvements-
I don't recall if/what changes were made in the GPLv3 to address this.
I don't know if I could recommend a license... I'm not a lawyer and
all that. I will say that I don't believe there exists an OSS license
which would prevent someone from starting a competitive site using
your code. The only all the open source licenses I'm aware of would
control is under what circumstances would they have to release their
code changes back to you & the world.
I can say this from personal experience:
Making code open source (regardless of the license) doesn't magically
cause people to contribute to your project. That takes a community of
individuals who want to solve a shared problem.
IMHO, if you're looking for people to help you with the project, then
your best bet is probably to seek out qualified developers (or people
interested in learning) within your existing user base who already
find it useful and would like to give back.
There are only two reasons I can think of that someone would download
your code and do anything with it:
1) They want to help you out
2) They want to start their own site using your code
You could easily have people email you to get access to the code for
#1 and filter out people interested in #2 all without releasing the
code under the GPL, etc.
I will say this though. Either GPL your code or have people assign
their copyright to you. I was involved in a web project where the
main developer kept the copyright and didn't assign a license which
allowed it to be redistributed other then the server. Then when the
developer decided she didn't want to work on the site anymore she
wouldn't allow us to give it to other developers- which basically
meant we had to start over from scratch.
Good luck,
Aaron