[HCoop-Discuss] Membership freeze?

[Michael Potter]

On Sat, May 12, 2007 at 02:38:37PM -0700, Adam Chlipala wrote:
> Nathan Kennedy wrote:
> > Since we're not actively soliciting members we are not exactly getting a 
> > flood of applicants.  I don't want to turn a single one away at a time 
> > where we are going to need an expanded membership shortly.  Not all 
> > qualified prospective members are going to wait around for us to get our 
> > act together.
> >   
> 
> I don't want to turn anyone away, either, but I also don't want to be 
> scrambling around synchronizing two worlds of data.  The state of the 
> portal is related to the database of UNIX users.  In a hcoop-sysadmin 
> post, I motivated why we should switch ASAP to using the portal on 
> deleuze as the official one.  It can't work very well for processing new 
> users without an idea of which user accounts exist; for instance, in 
> determining which usernames are available to request.

You could give new members a choice:

1.  Wait until the new systems are production-ready.
2.  Get an 'as is' account on the new systems only with no service guarantee. 

If this is impractical because the migration procedure only handles
users who are on Fyodor, a freeze may be the best solution.

-- 
Michael Potter
mpotter at hcoop.net