SqueakSource policy

Philippe Marschall philippe.marschall at gmail.com
Thu May 17 09:53:01 UTC 2007


2007/5/17, j blatter <jblatter62 at gmail.com>:
> Sorry if this was asked....
>
> Is the SqueakSource meant to be
>
> a) Code repository for public projects? (you uploaded because you want to
> share it)

yes

> b) Code repository for private projects (you can download from there because
> people just wanted the repository-internet-backup and don't minded it was
> public)

You can do that if you want. Just remember that all the files are on a
server on the University of Berne and the admins can access them.

> c) Both of the above?
> d) None of the above?

Additionally it's also used for exercises in lectures. We know there
is a lot of "junk" but so is on SourceForge.

> If a) how it's happening that people are taking the time to register the
> account, uploading the files and doesn't provide a description or link of
> what they did?

Ask them.

> Is there a reason for the SqueakSource program not enforcing
> a minimal description of what a package does? this is an #ifTrue: ...isn't
> it? (I imagine is not *that* hard to implement that)

We don't want to step on people's balls. If a code repository has
public write access you don't even need to register.

> If c) there's a way to filter public from private?

There is no real public/private distinction but it could be made with tags.

Cheers
Philippe

> If d) please explain me what it is :)
>
> thanks
>
>
>
>
>



More information about the Squeak-dev mailing list