You are viewing a condensed mobile version of this NASPA webpage.
Switch to full version.
(→Problems receiving Yahoo! Groups messages: + make-director-user) |
(→NASPAWiki editors: updated for 2022) |
||
(16 intermediate revisions by 2 users not shown) | |||
Line 8: | Line 8: | ||
# Verification: all changes in committees, committee leadership and committee memberships may be authorized by [[Executive Committee]]. Changes in committee membership or members’ roles may also be authorized by the any of the chairpersons of the committee. Committee members may also resign by their own announcement. | # Verification: all changes in committees, committee leadership and committee memberships may be authorized by [[Executive Committee]]. Changes in committee membership or members’ roles may also be authorized by the any of the chairpersons of the committee. Committee members may also resign by their own announcement. | ||
− | # | + | # NASPAWiki access: <!-- check if the person needs to edit NASPAWiki in any of his/her current roles and add or remove access as necessary. --> |
− | # Mailing list update: our mailing list administrators ([[Chris Cree]], [[John Chew]] or [[Dallas Johnson]]) shall update the mailing lists as appropriate. | + | #* We used to have to manually add NASPA committee users to the NASPAWiki user list. |
+ | #* As of 2017-08-02, we made custom code changes that permitted any current NASPA committee member may use their regular NASPA ID and password to sign onto NASPAWiki; they no longer need to keep track of separate authentication information. | ||
+ | #* As of 2020-08-03, we determined that a MediaWiki security update had partially broken this mechanism. New committee members now need to have local MediaWiki accounts created for them manually, but can thereafter log in using their NASPA credentials. This can be done from the command line with: <code>www-data% php5 files/wiki/maintenance/createAndPromote.php AAnnnnnn RANDOM-UNUSED-PASSWORD</code>. Note that the username is case-sensitive. | ||
+ | # Mailing list update: our mailing list administrators ([[Chris Cree]], [[John Chew]] or [[Dallas Johnson]]) shall update the mailing lists as appropriate. When adding a member, follow up with them to make sure they accept the emailed invitation. | ||
# Database update: Use the [{{SERVER}}/cgi-bin/add-to-committee.pl add-to-committee] or [{{SERVER}}/cgi-bin/remove-from-committee.pl remove-from-committee] Committee Services to update the database. | # Database update: Use the [{{SERVER}}/cgi-bin/add-to-committee.pl add-to-committee] or [{{SERVER}}/cgi-bin/remove-from-committee.pl remove-from-committee] Committee Services to update the database. | ||
# Contact page update: create the contact page if necessary, copying an existing committee member’s page to get the database access right, update the contact information as needed (do not publish private contact information without permission). | # Contact page update: create the contact page if necessary, copying an existing committee member’s page to get the database access right, update the contact information as needed (do not publish private contact information without permission). | ||
Line 72: | Line 75: | ||
Follow these steps to help diagnose why a user may not be receiving Yahoo! Groups messages. | Follow these steps to help diagnose why a user may not be receiving Yahoo! Groups messages. | ||
− | # Go to the group website, click on Members | + | # Go to the group website, click on Management > Manage Members > Bouncing, see if the user is listed. If they are listed as Soft Bouncing, follow the instructions to try to reactivate them. If they are listed as Hard Bouncing, ask the user to resubscribe. |
# Go to the group website, click on Members, Members, search for the user, make sure they are set to receive Individual Emails or Daily Digest (not No Email). | # Go to the group website, click on Members, Members, search for the user, make sure they are set to receive Individual Emails or Daily Digest (not No Email). | ||
# Ask the user if they are receiving other Yahoo! Groups email at their same address. If yes, and if you have administrative access to those other groups, check that the user is in fact ubscribed at the same address. If yes, their mail client software is likely hiding the specific group’s messages from them for some reason. | # Ask the user if they are receiving other Yahoo! Groups email at their same address. If yes, and if you have administrative access to those other groups, check that the user is in fact ubscribed at the same address. If yes, their mail client software is likely hiding the specific group’s messages from them for some reason. | ||
Line 80: | Line 83: | ||
== NASPAWiki editors == | == NASPAWiki editors == | ||
+ | |||
+ | If a NASPA committee member complains about the cryptic login message | ||
+ | |||
+ | Auto-creation of a local account failed: Automatic account creation is not allowed | ||
+ | |||
+ | the most common cause is entering their username in using lower-case letters; suggest that they enter it capitalized. | ||
+ | |||
+ | As of 2022, MediaWiki code changes have broken something again, and it may be necessary to use maintenance/createAndPromote.php to create the user first (all caps) using an impossible password. | ||
+ | |||
+ | See also naspa-auth.log for debug information about the authentication system. | ||
+ | |||
+ | The rest of these instructions were obsoleted in 2017, when we extended MediaWiki's authentication method to accept NASPA internal authentication from committee members. | ||
Follow these steps to create a new NASPAWiki login for a person that will be editing web content. | Follow these steps to create a new NASPAWiki login for a person that will be editing web content. | ||
Line 86: | Line 101: | ||
# Create a contact page for the user. | # Create a contact page for the user. | ||
# Create a Wiki user page for the person and redirect it to the contact page. This allows every entry in Wiki page edit history to be linked to the actual person who performed the edit. | # Create a Wiki user page for the person and redirect it to the contact page. This allows every entry in Wiki page edit history to be linked to the actual person who performed the edit. | ||
+ | |||
+ | == Yearend Tasks == | ||
+ | |||
+ | Perform the following tasks close to the end of the year: | ||
+ | |||
+ | Perform the following tasks close to the beginning of the year: | ||
+ | |||
+ | * Update [[Tournament results]], [[Ratings]] and [[SOWPODS rating system]] for the new year. | ||
+ | * Increment the year in the webpage inc/std-bot.html. | ||
+ | * Increment the year in the webpage wiki/LocalSettings.php. | ||
+ | * Increment the year where appropriate in scripts in ~scrab/bin | ||
+ | * Increment the year where appropriate in scripts in http://www.../cgi-bin | ||
== NASPAWiki password recovery == | == NASPAWiki password recovery == | ||
− | + | The following instructions were obsoleted in 2017, when we extended MediaWiki's authentication method to accept NASPA internal authentication from committee members. | |
+ | |||
+ | Follow these steps when an authorized | ||
NASPAWiki editor forgets their username | NASPAWiki editor forgets their username | ||
and/or password | and/or password | ||
Line 97: | Line 126: | ||
# Email them the new password and instruct them to change it right away. | # Email them the new password and instruct them to change it right away. | ||
+ | == Zyzzyva Offline Licence Activation == | ||
+ | |||
+ | Follow these steps to respond to a member request for the activation of a Zyzzyva licence on a computer that cannot be connected to the Internet. | ||
+ | |||
+ | # Check that the member has provided the uuid and a nickname for their Zyzzyva device. | ||
+ | # Verify their membership expiry date. | ||
+ | # Optionally, use the get-zyzzyva-info to get and check the uuid and nickname provided against any previously provided values. | ||
+ | # Go to http://scrabbleplayers.org/cgi-bin/check-zzl.pl?naspa=NASPAID&nickname=NICKNAME&uuid=UUID replacing the values of NASPAID, NICKNAME and UUID with the correct ones for the member; this will download an activation certificate. | ||
+ | # Email the member the .ZZA activation certificate file, ask them to open the Licenses dialog, click on Add Licenses..., select the .ZZA file type (the default is .ZZL), and open the emailed file. | ||
+ | |||
+ | == Zyzzyva Offline Licence Creation == | ||
+ | |||
+ | Follow these steps to respond to a member request for the issuance of a Zyzzyva licence on a computer that cannot be connected to the Internet. | ||
+ | # Verify their NASPA ID and membership expiry date. | ||
+ | # Use the get-zyzzyva-info command-line tool to see if they have a previously issued licence, and increment the serial number if necessary. If they have no previous licence, use 1. | ||
+ | # Use the make-zzl command-line tool with arguments ''--issuance-subject NASPA:NASPAID --issuance-serial SERIAL --issuance-date IDATE --validity-not-after EXPIRY > NASPAID.zzl'' replacing the values of NASPAID, SERIAL, IDATE and EXPIRY with the correct ones for the member | ||
+ | # Email the member the .ZZL licence certificate file | ||
[[Category:Procedures]] | [[Category:Procedures]] |
Web Committee procedures are used by the members of Web Committee to perform routine tasks.
This is a living document; the contents are updated as procedures are refined and developed.
When any NASPA committees invite new members or members retire or change roles, Web Committee updates the committee roster as follows:
www-data% php5 files/wiki/maintenance/createAndPromote.php AAnnnnnn RANDOM-UNUSED-PASSWORD
. Note that the username is case-sensitive.Our web site shall have a personal contact page for each current and former committee member, person with specific duties (spokespersons, NSC division leaders, office staff etc.), person of the year, and national champion.
Creating a new Committee should only be done at the request of a member of the Executive Committee, who should provide the name of the new committee, its initial chair, and any other initial members.
Each NASPA committee needs a Yahoo! Group in which to conduct and archive its official correspondence, and to offer an email address to which public inquiries may be directed. We currently use the yahoogroups.com system for doing so. Requests for new group creation should be directed to the Web Committee, who should follow these steps to ensure that the group is correctly configured.
Follow these steps to create a director FTP account for use in live coverage of a NASPA sanctioned tournament.
Follow these steps to help diagnose why a user may not be receiving Yahoo! Groups messages.
If a NASPA committee member complains about the cryptic login message
Auto-creation of a local account failed: Automatic account creation is not allowed
the most common cause is entering their username in using lower-case letters; suggest that they enter it capitalized.
As of 2022, MediaWiki code changes have broken something again, and it may be necessary to use maintenance/createAndPromote.php to create the user first (all caps) using an impossible password.
See also naspa-auth.log for debug information about the authentication system.
The rest of these instructions were obsoleted in 2017, when we extended MediaWiki's authentication method to accept NASPA internal authentication from committee members.
Follow these steps to create a new NASPAWiki login for a person that will be editing web content.
Perform the following tasks close to the end of the year:
Perform the following tasks close to the beginning of the year:
The following instructions were obsoleted in 2017, when we extended MediaWiki's authentication method to accept NASPA internal authentication from committee members.
Follow these steps when an authorized NASPAWiki editor forgets their username and/or password
Follow these steps to respond to a member request for the activation of a Zyzzyva licence on a computer that cannot be connected to the Internet.
Follow these steps to respond to a member request for the issuance of a Zyzzyva licence on a computer that cannot be connected to the Internet.
This page was last edited on 6 January 2022, at 19:37. Privacy policy
Copyright © 2024 NASPA All rights reserved. SCRABBLE is a trademark of Hasbro, Inc. in the USA and Canada, and of Mattel, Inc. elsewhere. NASPA and its activities are neither endorsed by nor affiliated with Hasbro or Mattel. For more information about NASPA or for comments or issues with this page, please email us.