Heck, I used to have a "light" text edit project going on sourceforge
(lexi.sourceforge.net) I have no idea what state its in... I passed off the
project to another fellow.
> Also I checked into SourceForge about storing documents there. One issue
is
> that as I read it, (reading legalese quickly makes my brain hurt, so I
> don't do it often) once you store something there you can't later make it
> "un-open source". So you can't (in my case) publish a draft of a book and
> then at the time of publication, take those files away and only publish an
> outline and excerpts, and 'transfer' ownership of the draft to the
> publisher. So for me that's a show stopper. But the embedlet project
should
> have no such concerns. Just though you might want to know.
Yah, a sticky issue for sure. Under any of the licences, you still hold the
licence... so at any time you could take the resources for the project, and
start a new version that wasn't open source.... you just can't remove
something from the community once its been distributed and made available...
The best practice (IMO) in a case like yours, is to only release the parts
of the project you *want* people to have access to... or if its going
commercial, branch your project into two related streams, one open, the
other not so open.
- Brill
|
