|
Size: 3278
Comment:
|
Size: 4788
Comment: Describing application process
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 35: | Line 35: |
=== What we decided on for the account creation process === * Someone applies via https://join.hcoop.net/ * In case it wasn't obvious above, we're switching it to SSL. ;) * The portal generates a random password, stores it with the user's application, and shows it to him. He must remember it until the application process is over. * A majority of board members approve the application on the portal. * Some designated person clicks a button on the portal to approve the application. * This sends an e-mail to the applicant that contains a link to MemberManual/GettingStarted/NewMember. * The applicant pays via Pay``Pal or Google Checkout * An admin logs into that payment service to verify the payment and see the official payment amount with service fees deducted. * That admin uses a feature to be added to the portal, which matches a Pay``Pal/Google Checkout e-mail address with an application. * That admin uses the portal to create the user. * The portal does as much as it can without needing root privileges. * It also prints a single command-line something like this to be run on deleuze: {{{magic-create-user-wrapper $USERNAME $PASSWORD $REALNAME $EMAIL}}} These all come from the application database. `$EMAIL` is optional. If present, it should be used to initialize the new member's `~/.forward` file. * After this is done, the portal sends an e-mail to the new member linking to MemberManual/GettingStarted/AccountCreated. |
1. Meta
Date: Sunday, November 18, 2007
Time: 19:00 UTC
Type: Admin-only
2. Agenda
2.1. Joining HCoop procedure
Re-opening membership requires a few more fine-tunings of our social processes. The following need to work, though they've not been tested in a while:
- Prospective members apply on the web via SSL. They get to choose username.
They get a randomly-generated password. Save a copy to /var/lib/portal/passwords/$USER.
- A majority of board members approve their applications.
- They get an automated e-mail with instructions on what to do next.
- They make a payment.
- Their initial payment is processed.
An admin runs create-user $USER.
This gets password from /var/lib/portal/passwords/$USER and deletes the file.
- Create .forward file? Would need to get their email address somehow, and whether they indicated that they want this on web form.
- User should be automatically subscribed to hcoop-announce mailing list, in the case that they provided an email address.
Once we figure this out, we can re-open membership.
Other related issues:
- Passwords and join procedure:
- Shouldn't have users give a public SSH key anymore. Too confusing for them.
- Several TODO bug reports filed about it.
- Make join.hcoop.net SSL, and have them enter password there, after applying.
- This password is
2.1.1. What we decided on for the account creation process
Someone applies via https://join.hcoop.net/
In case it wasn't obvious above, we're switching it to SSL.
- The portal generates a random password, stores it with the user's application, and shows it to him. He must remember it until the application process is over.
- A majority of board members approve the application on the portal.
- Some designated person clicks a button on the portal to approve the application.
This sends an e-mail to the applicant that contains a link to MemberManual/GettingStarted/NewMember.
The applicant pays via PayPal or Google Checkout
- An admin logs into that payment service to verify the payment and see the official payment amount with service fees deducted.
That admin uses a feature to be added to the portal, which matches a PayPal/Google Checkout e-mail address with an application.
- That admin uses the portal to create the user.
- The portal does as much as it can without needing root privileges.
- It also prints a single command-line something like this to be run on deleuze:
magic-create-user-wrapper $USERNAME $PASSWORD $REALNAME $EMAIL
These all come from the application database. $EMAIL is optional. If present, it should be used to initialize the new member's ~/.forward file.
After this is done, the portal sends an e-mail to the new member linking to MemberManual/GettingStarted/AccountCreated.
2.2. DNS
Go with [http://worldwidedns.net] for backup DNS?
When do we want to migrate DNS for domain hcoop.net?
MichaelOlson thinks we should do this after forced migration ends, to minimize the possibility of member uncertainty while migrating.
Procedure proposed by Adam Megacz:
- Make sure NO DNS SERVER is running on deleuze or other (port 53 closed)
- Create ns5.hcoop.net and ns6.hcoop.net, point them at deleuze+other
- Add ns5.hcoop.net and ns6.hcoop.net to the root servers
- Wait 48 hours
- Simultaneously:
- shut down tinydns on fyodor
- shut down tinydns on krunk
- start bind on deleuze
- start bind on other
- Confirm that everything is happy; if not, revert #5
- Wait a week
- Remove ns[1-4].hcoop.net from the root servers
The important part about this is that every potentially problematic step (mostly #6) can be reverted instantaneously.
2.3. New Machine Readiness
AdamChlipala has finished his non-wishlist items for Domtool.
MichaelOlson finished Mailman stuff, needs to double-check new Domtool Mailman directives and write them up in manual.
- Abulafia?
MichaelOlson thinks we should wait until after forced migration.
- IPKVM?
AdamMegacz says no deadline, but we will wish we had at some point.
- Particulars being worked out on the bug report.
2.4. Bugzilla/email
Need to remove admins AT hcoop.net from Cc: to avoid annoying duplicates.
- Removed from all default settings now.
- Admins should add themselves to whichever components they want notifications.
Send portal emails to addresses other than admins AT hcoop?
- Needs aliases?