I noticed that currently project FTP directories end up as:
ftp://ftp.common-lisp.net/pub/<foo>
I propose that we put them under
ftp://ftp.common-lisp.net/pub/project/<foo>
instead. This provides a nice symmetry with the web addresses, and allows for some future hierech to take place if we so desire.
Likewise I propose that we put freely distributable stuff in either
ftp://ftp.common-lisp.net/pub/misc/
Or replace misc with software, free, etc.
Cheers,
-- Nikodemus
I noticed that currently project FTP directories end up as:
ftp://ftp.common-lisp.net/pub/<foo>
I propose that we put them under
ftp://ftp.common-lisp.net/pub/project/<foo>
instead. This provides a nice symmetry with the web addresses, and allows for some future hierech to take place if we so desire.
Ok. I buy into that.
Likewise I propose that we put freely distributable stuff in either
ftp://ftp.common-lisp.net/pub/misc/
Or replace misc with software, free, etc.
I don't follow. Can you give me an example of a freely distributable something?
Erik.
On Wed, Aug 13, 2003 at 04:44:32PM -0000, erik-nittin@imeme.net wrote:
I don't follow. Can you give me an example of a freely distributable something?
http://www-2.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/code/ext/c...
[ The code is copyrighted and *apparently* freely usable and distributable, but most definitely makes no provision for distribution of derivative works. ]
Or anything else that is
a) Common Lisp related b) Freely distributable, but not necessarily open source, or has eg. a license that prohibits commercial use (eg. Picasso) c) Not necessarily hosted on common-lisp.net.
Time will tell if this is a significant group or not, of course. But the point is that it would be nice to have a anon FTP without any license requirements beyond free redistribution. This means also smaller workload for maintaining the FTP, since there is not need to wonder if license Foo fullfills the policy.
Alternatively we could have pub/free for anything DSFG-free and pub/non-free for non-DSFG-free, but still freely distributable.
Cheers,
-- Nikodemus
Nikodemus Siivola demoss@random-state.net writes:
a) Common Lisp related b) Freely distributable, but not necessarily open source, or has eg. a license that prohibits commercial use (eg. Picasso) c) Not necessarily hosted on common-lisp.net.
I see. So, projects that are not really maintained any more but need a home. Ok, cool.
Erik.
-
Erik Enge -
erik-nittin＠imeme.net -
Nikodemus Siivola -
nikodemus＠random-state.net