welcome: please sign in

Diff for "IrcMeetings/20071118"

Differences between revisions 14 and 15
Revision 14 as of 2007-11-18 19:58:00
Size: 3086
Editor: MichaelOlson
Comment:
Revision 15 as of 2007-11-18 20:02:26
Size: 3278
Editor: MichaelOlson
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 * An admin runs {{{create-user $USER}}}.  This gets password from {{{/var/lib/portal/passwords/$USER}}} and deletes the file.
 * User should be automatically subscribed to hcoop-announce mailing list?
 * 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.

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.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:

  1. Make sure NO DNS SERVER is running on deleuze or other (port 53 closed)
  2. Create ns5.hcoop.net and ns6.hcoop.net, point them at deleuze+other
  3. Add ns5.hcoop.net and ns6.hcoop.net to the root servers
  4. Wait 48 hours
  5. Simultaneously:
    • shut down tinydns on fyodor
    • shut down tinydns on krunk
    • start bind on deleuze
    • start bind on other
  6. Confirm that everything is happy; if not, revert #5
  7. Wait a week
  8. 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

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?

2.5. Other things

IrcMeetings/20071118 (last edited 2008-07-07 04:27:55 by localhost)