goran.hultgren@bluefish.se wrote:
And finally with a cherry smiley on top - there are too many words in these postings... Paul? Code talks. ;-)
I agree with the sentiment.
However, essentially, what I am writing with the charter is code -- code for the operation of a social process. Wouldn't suprise me if it (the charter) was buggy or missed some requirements -- as code is likely to do the first few times around.
Yes, the license incompatability of GPL with Squeak-L is an issue.
Actually, the more I think about this, the more I come around to seeing that what I should develop first is more a tool to manage these licensing issues -- sort of a code repository and configuration management tool that is license aware (think of it warning about loading code with a license incompatible to code already loaded...). Because if people (like Tim in a previous post) want to say their code or email posts are public domain or whatever, they should have a chance to for their part, even if the rest of the application was for example contaminated by GPL code, and the system should record that. Then I can use that system to build up a new version of Squeak with an arbitrary license by picking subsets of the entire codebase and knowledgebase.
-Paul Fernhout Kurtz-Fernhout Software ========================================================= Developers of custom software and educational simulations Creators of the Garden with Insight(TM) garden simulator http://www.kurtz-fernhout.com