Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

onboarding #1401

Open
jnurthen opened this issue Feb 16, 2021 · 5 comments
Open

onboarding #1401

jnurthen opened this issue Feb 16, 2021 · 5 comments
Assignees
Labels
editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo
Milestone

Comments

@jnurthen
Copy link
Member

How to better deal with onboarding to the WG. Address the following feedback

Quarterly onboarding would be helpful. Or at least have a guide where new comers could familiarize themselves with thing like:

  • Team introductions
  • Team rituals
  • Expectations for team members
  • How to work with others on the team
  • What to work on and where (how to get setup locally)
  • How to communicate (ie., tooling; email, Slack, etc)
  • Code formatting requirements for PRs
  • Who to reach out to for help, code reviews, etc

For example, I find the emails that are sent with meeting details are difficult to read to find info on how to connect. Perhaps I’m spoiled as meeting invites from Google Calendar are very clear and easy to add into my calendar. I also didn’t know there were two separate meetings; one for APG and another for the spec.

Anything that can ease onboarding for new folks would be ideal.

@schne324
Copy link
Contributor

Do we think it'd be helpful to document some basic irc commands? Specifically, I think it'd be useful to document common scribe commands.

@carmacleod
Copy link
Contributor

  • Link to Github/Git primer.
  • Link to ReSpec primer, plus link to the ReSpec that we use.
  • Relationship between all the ARIA-related repos and specs, including aria-common.
  • Invitation to web-a11y Slack.

@a11ydoer a11ydoer self-assigned this Feb 25, 2021
@a11ydoer
Copy link
Contributor

a11ydoer commented Feb 25, 2021

@jnurthen
I assigned this issue to myself as I volunteered to help. I hope it is ok with you. My plan is coming up with a sort of "cheat sheet for new ARIA working group members"

@cookiecrook
We apprecaite your extra time today to give ARIA github repo orientation to new members as well as exisitng members. It was an impromptu training meeting but the impact was immense. THANK YOU!

@carmacleod
Copy link
Contributor

carmacleod commented Feb 26, 2021

IRC notes (for everyone and for scribe)

I just use IRC in my browser (Chrome, usually): http://irc.w3.org/
Type in your nickname and use #aria for the channel.

When you first enter the channel, type:
present+

Commands anyone can use:

q+  (to add yourself to the speaker queue)
q+ to say [what you want to say]  (to add yourself to the speaker queue with reminder message)
ack me  (take me off the q; or can use q-)
ack ja  (take james off the q; or can use q- ja)
q?  (to find out if anyone is on the q)

s/old text/new text/  (to replace something that was typed. Make sure "old text" is unique)
s/old text//  (to delete "old text")

/me message  (sends message to channel without adding to minutes. Adds * prefix, i.e.)
* joanie says Zakim is named after a bridge in Boston and pronounced Zay come

If you are scribing, these commands can be used for setup:

meeting: ARIA WG
chair: JamesNurthen
scribe: your nickname
agenda?  (to list the agenda items - chair usually enters agenda using `agenda+ item`)

Scribing commands used during the call:

zakim, next item
zakim, close this item   (might need this if we try to move to the next item too soon)
zakim, take up item 6   (might need this to go directly to a specific item)

action: name - sentence about action item  (we only rarely add action items)
topic: topic name  (ARIA WG doesn't use this, but APG does)
github: [github issue url]  (adds current topic discussion to github issue)

When scribing conversation, tab key will (usually) complete the person's name after 2 or 3 letters, for example:

ja[tab] completes to jamesn: 
jc[tab] completes to jcraig: 

Scribing commands used at the end of the call to prepare the minutes:

zakim, who is on the call?  (list of everybody who typed present+)
zakim, who is here?  (list of everyone on IRC, even those who forgot to type present+, and some who never log off)
present+ name  (if anyone who was on the call is missing from the list)
regrets+ name  (for anyone who sent regrets)
rrsagent, make minutes

Open the minutes link in a new tab, and check that they look ok (may need to refresh several times).
If all is well, email minutes link to group (I usually just reply to the agenda email).
If anything is missing, add it, and then rrsagent, make minutes again.

The following links have way too much information, but here they are for completeness:

@a11ydoer
Copy link
Contributor

@carmacleod Thanks so much for starting to add the info. This will be handy for new commers.

I have switched to use irccloud.com since last year. I found irccloud is much easier for managing all the different channels and copying and pasting text to IRC. I will also add irc cloud setting info to the doc.

"ARIA WG onboarding - cheat sheet for new members" is a google doc for now. I will transform this as .md file in github after the consultation with ARIA chairs, @jnurthen and content review by ARIA group members.

@jnurthen jnurthen removed the Agenda label Dec 9, 2021
@pkra pkra added this to the ARIA 1.3 milestone Jun 27, 2023
@pkra pkra added the editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo label Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial a change to an example, note, spelling, grammar, or is related to publishing or the repo
Projects
None yet
Development

No branches or pull requests

5 participants