Forking from T183278.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Elitre | T183278 Set up a Phabricator workboard/project for #techambassadors and experiment with it | |||
| Declined | None | T199424 Expand the Tech Ambassadors program beyond the top 25 Wikimedia communities | |||
| Declined | None | T193878 Check the current processes for Tech Ambassadors and iterate on it | |||
| Resolved | Quiddity | T191399 Write documentation about the role of tech ambassadors and their workflows |
I've created a sub-page grouping all names for messaging them on Meta: https://meta.wikimedia.org/wiki/Tech/Ambassadors/List/Messaging. It can be used in the future. There are 65 names on it.
I've created a temporary list to avoid spamming already subscribed users. The distribution has been made to 44 people.
I've used T195993: Coordinate with Tech Ambassadors for graduating New Filters on Watchlist out of beta as a trial to see if the Phab board is used at some point. I think setting up a meeting will be needed for the following reasons:
I think setting up a meeting will be needed for the following reasons
I'd be happy to attend if that could be helpful (and if I can make it).
the avalanche of emails
https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications explains reducing that.
Noted, thanks!
the avalanche of emails
https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications explains reducing that.
I think there are two things to see about that: check what are the default settings for a board like the one created and see how people are at ease with Phabricator.
... and being very careful about which tasks make it to Tech Ambassadors & Translators. The board currently has three tasks only, but the three of them are noisy indeed.
From the three tasks, one is specific about Ambassadors, so I guess notifications are the price to pay if you are interested, and if not you can unsubscribe.
The other two tasks are not Ambassadors specific, they are about development, "fyi" type of tasks. If we want to keep adding these, then Ambassadors need to learn how to fine tune their email preferences and be good at unsubscribing / muting / deleting.
All of which has been communicated several times to them already, with pointers etc. Hopefully more documentation and a meeting will help even more.
This is related to T191399. We need to figure out what's working and what not if we are to expand the program to more wikis.
After discussing with @Elitre, I'm rescoping a bit that task. The new elements listed may be subdivised in specific tasks.
@Quiddity and I are going to work on T191399: Write documentation about the role of tech ambassadors and their workflows first, while this document is gathering efforts I planned to make with ambassadors. Clearly, document first and iterate is the best solution.
T191399: Write documentation about the role of tech ambassadors and their workflows has been improved enough to consider that task to be resumed.
Qgil set Due Date to Dec 31 2018, 12:00 AM.
Assuming that this goal is to be completed during the current quarter. If you think it should be done before, please edit it accordingly. If you think it should have a later deadline, please explain.
The overall discussion about the role has allowed us to fix some points that were unclear in the role itself. We can consider the role as well defined.
However, on other points raised up by Ambassadors, none of them were about blockers on using the tools. I think they will be more visible on practical cases.
Concerning activity and rewarding, that point hasn't been raised-up and still need to be asked.
This is not a goal anymore. Any work done with Tech Ambassadors will start from scratch in a new program.