I've added the Treated project.

It turns out you were right that although the menu offers the choice to
move a version, only one with admin rights could do so.  I chose to
change this, so now for the entire site anyone with write access to a
project has the write to move a version from the project to another
project.

A long range todo project would be to expose an interface to adjust
fine-grained access capabilities on a per project basis for SS.

Ken

P.S. I have to say I did not find the discussion of the Treated inbox on
the Pharo page at all clear.  It sounds to me like it says that an issue
goes from the inbox into treated whether or not it is considered valid.
It then goes on to say that if it works it is 'published' to the Pharo
project.  Am I to take this to mean that it is either moved out of
Treated or deleted?  Also frankly, I don't understand what the word
'treated' means in this context.

On Wed, 2009-08-12 at 20:20 -0700, Andreas Raab wrote:
> Serge Stinckwich wrote:
> > Andreas Raab a écrit :
> >> Good questions. How do the Pharo people deal with these issues? 
> >> Anybody know?
> > 
> > You can read : 
> > http://code.google.com/p/pharo/wiki/IntegrationProcessDescription
> > http://code.google.com/p/pharo/wiki/HowToContribute
> 
> Thanks. This sounds very reasonable. It means we'd need a "Treated" 
> repository that we can move the integrated packages to. Ken, could you 
> set this up?
> 
> One thing I'm not sure is if every developer is allowed to move packages 
> or only the project admins. If it's only the project admins we might 
> consider making all developers admin for the inbox to simplify the process.
> 
> Cheers,
>    - Andreas
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090813/8d09eee6/attachment.pgp