Sean P. DeNigris wrote:
Since there is a major push in both Squeak and Pharo to be clear about what's
loading where, and get more and more projects loadable; and the community is
fixing projects that we don't own...
I propose:
1. Everyone make your SqS repos globally writable unless you have a reason
not to.
2. SqS admins, send an email to all the repo admins requesting this.
I don't think using global write is the right way to fix the problem.
How about a SqS usage policy:
- the project admin(s) are responsible for keeping their email contact
up-to date
- periodically (monthly?), project admins are ping'ed. If no
acknowledgement is received after three attempts, then the project admin
reverts to the community
- any community member can then ask to become the project admin
This solution wouldn't get you a fast response, but would guarantee you
an eventual response. And, the project admins will still be in charge,
which is as it should be, IMO.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
