>But what does this mean in the 'real world?' By this I mean that the GPL is
>sorta sacred and NOT to be altered. We are making a change to it, right? Is
>this type of thing done eleswhere?
Mark,
no, we're not changing the GPL. Rather, we're just putting our files under
the GPL with an exception. Everyone who wants to use FreeCard with GPLed
code will be able to do so under the GPL, but people who want to use GPLed
code with it will not be able to take advantage of the exception.
>What is the rest of the OpenSource community going to say/think?
It came from Richard Stallman. You could say "it comes from the open
source community". For everyone interested: I went to the GNU web site and
looked up the e-mail address to send licence questions to. I received an
answer by Richard and then we worked out the details.
>Will the code base be able to freely cross over with other GPLed code? I
>think so, but must ask as I'm mostly ignorant about these type of detailed
>license issues and implications.
see above.
>Is the license to a point, and that exception mostly, where we can go out
>and talk about it in other places beyond this list? These discussions are
>just for discussion reasons. I see no harm in doing so. Perhaps if someone
>has massive objections, then we should have them be mentioned NOW.
I don't think there would be harm in talking about it, as long as you make
clear it's only a proposal for a licence. It would be especially useful
hearing from potential users what they are thinking. They're the ones most
likely to become aware of any difficulties users might encounter. Should I
post a polite message to the HyperCard list?
>In due time, I also feel that we need some type of plan for the license
>approval. But, it is too early, way to early, to put it up for a vote, IMHO.
>I'd like to see a staged vote as well as lots of other discussions to happen
>in this license picking process yet. First stage, initial agreement to
>proceed on the broad concepts. Second stage, formal approval some 3 months
>later.
Since we are already writing code, it would be good to have a yes or no on
the licence as soon as possible. Once we have a licence (any licence, just
a final one), we can go out and ask other programmers to join in. If we did
that now, they might write a code module which we rely on and then pull it
back because they don't like the licence etc. Also, if we write code and
put it under this licence now and in three months decide to use a different
one, we would have to write all code anew if the licenses are not
compatible. Once code is under a licence we cannot revoke it if we are
using a safe free software licence.
>How about this, if there are no serious objections in the next week, then
>let's take our "proposed" license out to others beyond this list and see
>what type of endorsements or otherwise that comes from its mentions. Wider
>public discussions are needed soon.
Generally, no problem doing that right now. Just take into consideration
the above things. Especially stating it's a first proposal is important so
people know they can still change it. Else we might get a bad reputation
because of some malformed statement in there which we neither intended nor
noticed.
>Please, let's put the proposed license onto the main web site as well as
>some FAQs about the license. Thanks!
That would really be useful.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
