Created an initial version of [[Developer Advocacy/Venue coverage]] on officewiki. Also linked to it from my personal internal Continuity page.

@mseckington: I'd love to see some progress on this lingering task and I'm tempted to assign this to you. :)

After discussion with the team, I'm going to remove it as a sub-task of the social media strategy task (T327213) because it is more about defining the role of Developer Advocacy in facilitating the flow of information between various spaces across the tech community, especially between volunteers and WMF, with potential goals like creating connections and reducing duplicate work. So, it's larger than social media strategy, but also is still stalled because we remain in need of a clear set of team goals and policies around this type of work.

The great decision-making of April 2023:

1. when this task is assigned to you, update your information on https://office.wikimedia.org/wiki/Developer_Advocacy/Venue_coverage. Follow the new instructions at the top of the page - only use YES or NO.
2. check your name off on this list when you're done
3. assign the task to another team member on Developer Advocacy who has not yet done their update

• Andre
• Srishti
• Komla
• Kamil
• Tricia

[later] Onyinyechi

In T244396#8776832, @TBurmeister wrote:

2. check your name off on this list when you're done

You will need to put the list into the task description which is group editable for that to happen. Individual comments are only editable by their original authors.

Should we use Yes/No, or ✅ / ✗? I think the latter option is not accessible, the "✗" character isn't read by my screen reader making a given cell seem empty when read out loud (and ✅ is read as "checkmark", which is unnecessarily long compared to "Yes").

In T244396#8784638, @KBach wrote:

Should we use Yes/No, or ✅ / ✗? I think the latter option is not accessible, the "✗" character isn't read by my screen reader making a given cell seem empty when read out loud (and ✅ is read as "checkmark", which is unnecessarily long compared to "Yes").

Seconded. I'm on standby to change my updates to Yes/No.

I wasn't aware of screenreader issues. Please replace as suitable; no need to wait or stand by just because of that.

In that case my column is up to date. Passing the potato to @TBurmeister