>> Alain: 6. The third tactic for providing the FreeCard
>> application is the controversial one that I have been
>> suggesting since the beginning: Do like HyperCard does
>> in this regard (e.g. save a copy of a stack as
>> licence-free standalone). It is controversial because
>> it blurs the distinction between document and
>> application that is necessary to maintain if we do not
>> wish our works to be considered 'derived' works, and
>> thus have our FC-related work subject to FreeCard's
>> GPL-like licencing conditions (e.g. to remain free and
>> open).
>
> We can certainly say that FreeCard standalones are free of FreeCard
> licencing requirements, but this opens a LARGE loophole in anything
> else.
>
I think that the HyperCard arrangement allowed users to do two things:
Create stacks which they could distribute as they please; and create
enhancements to add to HyperCard itself or a stack, which they were also
free to distribute as they pleased. The constant was HyperCard. There was
only one official version from Apple, kind of a standard that anyone could
create a stack for end expect anyone else to be able to run it. I'd like to
see a standard version of FreeCard. A plug-in kind of facility would allow
enhancements (like PhotoShop or Netscape), but the basic functionality would
be universal. Nobody would be allowed to change it. Over time, some plug-ins
would become extremely popular. After much deliberation, a committee could
approve their inclusion in the basic structure of FreeCard thus making them
available to everyone.
When I say nobody would be allowed to change it, I was referring to the
technical sense that if they change it, they must not redistribute it under
the name FreeCard. The plug-in facility has the benefit of allowing the
casual user to look in a folder and quickly identify every item that
modifies the performance of their copy of FC. HyperCard made it difficult
for the casual user to identify modifications.
By the way, I'm a technical writer. I met Uli on the 'net due to some common
interests. I'm new here and I'm very excited about this project and the
thoughtful people behind it. I know you won't need a tech writer here
because this system will be so well designed that it explains itself.
Tom Swell
San Diego, California
[EMAIL PROTECTED]
