At 12:44 PM +0200 on 7/30/99, M. Uli Kusterer wrote:
>> a) Release it under a different name; and
>> b) preferably (but optinally) Give credit
>
>Anthony,
>
> We should make sure no markings (like copyright notes etc.) are removed
>from the sources. We can ask that much.
Agreed.
>
>> OPENCARD shall mean a certain product being created by OODL in order
>> to be a new, OpenSource, HyperCard-like product.
>
> Much better than "replacing" HC.
It's going to get better :)
>>I propose that MAINTAINER shall gather code under LICENCE and combine them
>>to form OPENCARD. I further propose that MAINTAINER or his designee shall
>>write or callaborate to have written any neccisarry code to glue together
>>different parts, and to have that code released under LICENCE.
>
> This means the MAINTAINER may appoint a programmer to write this code if
>he isn't able to write the code, right? This is certainly necessary, I
>don't want the office of the MAINTAINER to be restricted to programmers.
Yes, that means that the maintainer may appoint someone to program. This
would allow someone who is not a programmer to be MAINTAINER, but I'd not
recommend it... it really is a programming position. But I could see if,
for example, we had a UI person as maintainer, and he designated someone to
handle the technical aspects.
>
>Cheers,
>-- M. Uli Kusterer
>
>------------------------------------------------------------
> http://www.weblayout.com/witness
> 'The Witnesses of TeachText are everywhere...'
>
>--- HELP SAVE HYPERCARD: ---
>Details at: http://www.hyperactivesw.com/SaveHC.html
>Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
