...
Goal: enable Sam to create and edit pages on the Confluence wiki at lyrasis.org in support of the working group.
Privileges: use your own wiki account; each working group chair and vice-chair confers admin privileges to next generation.
Process:
- If Sam doesn’t yet have credentials on this wiki, establish credentials (an account) by emailing wikihelp@lyrasis.org and CCing Sam.
- Sam should receive an email with instructions to create a wiki account.
- Once Sam completes them, you login to the wiki with your own credentials.
- In the space “ARKs in the Open”, go to the sidebar and select Space Tools > Permissions.
- Add the Sam’s account to the list of users and then check off the appropriate permissions similar to the others.
- Sam should now have privileges for all working groups in the space. For more advanced issues, email itsupport@lyrasis.zendesk.com.
- Edit the group homepage, https://wiki.lyrasis.org/display/ARKs/Advisory+Group, and add Sam and Sam’s affiliation to the list of group members.
...
Goal: add Sam to the google email group used to contact the entire group. Be aware that all group archives are publicly readable except for the NAAN group.
Privileges: use your own google account; each working group chair and vice-chair confers admin privileges to next generation.
Process:
- Visit (for example) https://groups.google.com/g/arka-advisory-group
- From the sidebar, select People > Members, then “Add members”.
- Enter Sam’s email address, toggle “Directly add members” with no invitation message (they're expecting it, and you’re busy and don’t want to have to remind them to accept it if they didn’t see the invitation), and “Send invites”.
- Make sure you have invited Sam to the calendared meeting (above).
- Make sure you have added Sam to the working group home page.
...
Goal: enable Sam to edit content on the official ARKA website (arks.org).
Privileges: use your own account; each working group chair and vice-chair confers admin privileges to next generation. Alternatively, login with info@arks.org.
This is currently a Wordpress site hosted by Dreamhost, although we hope to convert it to a github Pages site. Not everyone needs edit access right away to the official websiteGenerally edit access isn't needed unless Sam is creating or editing a blog post or a document, so adding Sam may be deferred can usually wait until the need arises.
Process:
- Login to arks.org/wp-admin as user info@arks.org (; this email address is also where site “contact us” feedback is sent (it gets a fair amount of spam, despite the anti-spam filtering in place).
- From the sidebar, select Users.
- Press “Add New” and enter information for Sam.
- (optional) To add a guest blogger with no other privileges, from the sidebar, select Authors (under Posts), and “Add New” (this uses a plugin).
...
Goal: connect Sam to the main ARKs forums in English and French. Consider asking another member with admin privileges to grant you admin privileges on one or both of these lists.
Privileges: use your own google or framalistes account; each working group chair and vice-chair confers admin privileges to next generation.
Process:
- If not already subscribed, Sam should visit https://groups.google.com/g/arks-forum to subscribe to the main ARKs forum.
- (optional) Sam may wish to visit https://framalistes.org/sympa/info/arks-forum-fr to subscribe to the French ARKs forum.
...
Goal: allow the general public to submit a NAAN request that will be processed by the NAAN Registry working group.
Privileges: use your own google account; each working group chair and vice-chair confers admin privileges to next generation.
The request form https://n2t.net/e/naan_request is a google form owned by arksalliance@gmail.com and is jointly managed by “editors”. Similarly there is also an Expression of Interest form at https://docs.google.com/forms/d/1ylEeI3hUVHcLl-wNtDI7-F7JReBtVbgx65y9Uiy78q8.
...
Goal: allow working group participants to manage the process by which an ARKA newsletter is generated.
Privileges: login as info@arks.org.
People subscribe to the newsletter via links on the arks.org site. Currently, the newsletter goes out on the 4th of the month, but only if there were new blog entries posted since the previous newsletter went out.
...
Twitter.com and youtube.com
Privileges: login as @arks_org for twitter and arksalliance@gmail.com for youtube.
The ARKA twitter user/handle @arks_org is used for tweeting. An automatic tweet is triggered by mailchimp if an ARKA newsletter goes out.
A youtube channel at https://www.youtube.com/channel/UCZkjLNV0CvxA92mSOzTuGxg is set aside for ARKA-related content such as tutorials and webinars. The associated user is arksalliance@gmail.com.
Github
Privileges: login with your own github account.
The official ARKA github repo is https://github.com/arks-org. This is envisioned to be the home of the NAAN registry, the ARK specification, the resolver code, and possibly the arks.org content (replacing the Wordpress site). New users are invited by an existing user.
Credentials
Logins and passwords are stored with keybase.io under the “ARKAadmin” team. You will need to create a Keybase account and be invited onto that team by a current member in order to get access.