response 13 of 85:

Dec 2 19:44 UTC 2010

resp:12 What information are you referring to, specifically?  Right 
now, the stuff we ask for get's put into the user's .plan file.  Well, 
the email address gets used to email the user their new password.  The 
only other real use is for resetting passwords if the user forgets: 
traditionally, this was done via an emailed request; if the user's 
plan is private, but has information that could be used to verify the 
user's identity in it, then staff could look at that and ask the user 
a question based on it to get at least some idea that they are who 
they say they are.  Of course, if the request comes from the email 
address the user used to register, then that's not really necessary.

response 15 of 85:

Dec 3 00:27 UTC 2010

resp:12 nope, darn - me unclear:
1. Strip newuser to the barest minimum.
2. If the user decides to do the mkhomepage/mkplan routine, then ask him
 for stuff - meanwhile highlight the cool home-pages bit in motd and on 
the site

response 17 of 85:

Dec 3 01:45 UTC 2010

When I took a look at the web newuser it was the usual questions about
all the details and settings, so yes, somewhat complicated.  I realize
it isn't complicated for anyone who has set up a Unix acount before, but
for the uninitiated it can be quite complex and confusing.  And time
consuming. If this extra information is not needed for people who want
to access Grex via the web, I'd question the value of collecting it.

I'd probably strip it back to full name, login id, password, optional
telephone number and optional e-mail address, assuming we can use some
default values for the other information like shell, terminal type,
backspace key, etc.  I'd be interested to hear what others think of this
idea.

I tried to run the web newuser on Nov 22 and it failed.  The command
line newuser was successful.  Has there been a change to the web newuser
so that it actually creates an account?  If so, this should be announced
and it would be good if we said something about it on our web page.

I see it still errors out today: 

Your application for an account on Grex has not been processed due to a
system problem.

    * Could not access directory /usr/noton/nu/ 

Sorry. This system error has been logged and will be addressed by our
staff. Please, try again later.

I'd say we probably want at least the Board to hear about this.  We can
discuss at our next meeting, unless we all think it's a good idea to do
it now.  What do the rest of staff think?

response 19 of 85:

Dec 3 02:17 UTC 2010

It's a relatively significant change to an application that's been in
place for eons, so keeping the Board and the rest of staff in the loop
would be good, I think.  It's also good to get multiple opinions on your
question of what exactly needs to be asked by newuser.  We don't usually
get opinions from many people in coop.

Anyway, I understand about other priorities, so don't feel you need to
attend to Grex constantly.  I see the error I got out of the web newuser
was different than the one I had on Nov 22, so something maybe changed.
It doesn't look like it's too far off from working if the most recent
message is accurate.  

In the short term, what we need is to have the web newuser working as it
used to, using the old program.  If that's easy to do, great, it'll give
us more time to hash out the details of any changes.  If not, then we'll
just have to be patient.

response 21 of 85:

Dec 3 03:12 UTC 2010

Looks like /usr/noton/nu doesn't exist so that's why I got that error.
But if the new one is easier to get in place and it works, that might be
better (and more maintainable).

response 23 of 85:

Dec 3 15:23 UTC 2010

Here's what I see we need to do, in order of priority:

  1. Get the web newuser working.  If that means getting it working
     as it did when it was last working, with all the questions and
     technical stuff, so be it.  Not having it working at all is more of
     a harm to us than a complicated new user process.

  2. Simplify the web newuser.  From what I've seen we should be able to
     do this if we have a working web newuser and just use some default
     values or no values for options, for the things we're no longer
     asking (in the data submitted from the web page).  If this is not
     the case, speak up.

     The "how" (or "how much") to simplify is one of those consensus
     questions we get from time to time.  Let's give the Board and Staff
     and the rest of the users some time to weigh in.  Perhaps they see
     other issues with any simplification proposal.  If we hear nothing
     in a reasonable amount of time (e.g. 1 week), I'll assume no one
     has an objection.  Then let's simplify it and see how it works out.

Let me know if you see issues with this process (such as it's more work
to re-do the web newuser or web page to simplify it than it is to just
take the time to simplify all of it now).  We can adjust accordingly.

(I've also e-mailed staff and board with a summary of what we're talking
about in this item).

response 25 of 85:

Dec 3 16:21 UTC 2010

I understand your point of view, Dan.  Maybe it's time to not try so
hard for a consensus or the involvement of others and just get things
done.  From what I've seen, generally, the people who care have little
or no interest in actually making things happen, so I'm tempted to just
say "do it this way" and let the chips fall where they may.

response 27 of 85:

Dec 3 18:25 UTC 2010

resp:25 Thanks, Kent.  Don't get me wrong, consensus is good, but it's 
also this community's achillies heel.

resp:26 Quick!  Someone upload slynne's post to wikileaks!

response 29 of 85:

Dec 4 21:04 UTC 2010

Re resp:20 - "Actually, I think the short term solution is to get the
new one written.  The code that's there now is, well, complicated and 
confusing and very, very old."

I quite agree.  Web newuser is around 2400 lines of C source code, and
the TTY-based newuser around 5700, code that nobody currently active on
Grex had anything to do with writing.  Wading through that to fix
problems, when a new TTY newuser is already in place and a new web
newuser shouldn't be far behind, strikes me as not worth the effort.

response 31 of 85:

Dec 5 01:05 UTC 2010

resp:29 Agreed.

resp:30 The new newuser needs some cleanup, but overall, I think it's a lot
less crufty than the old newuser.

response 33 of 85:

Dec 9 18:04 UTC 2010

What's not a good idea about mailing the password?  This isn't the
Pentagon or anything. We've talked about an an offsite e-mail address
being more or less required, as in automatically send the user an
e-mail and they can respond and be validated.  It also gives us contact
information if there are other issues (including forgotten password).

I suppose we could require the password be changed when they first
log in.  Or at least, suggest strongly that they do so in the e-mail
we send.

response 35 of 85:

Dec 10 04:35 UTC 2010

Okay, then, sounds like we're in good shape.