Weekly to Monthly meetings
The following meetings are specific to the Technology department or especially relevant:
- Scrum of Scrums (weekly cross team tech scrum)
Face to Face (F2F) Technology Management meetings
As the Technology management team is highly remote, managers try to get together physically multiple times per year to have high-bandwidth in-person meetings.
- Upcoming in-person meetings
- none at this time, due to covid-19 global pandemic
There are no contact lists specifically for the Technology Department. General resources include:
- Office wiki contact list (internal or private and managed by the individual folks)
- Wikimedia Foundation Staff & Contractors page (Public - managed by Talent & Culture)
- TBD: norms for the department? Should each team have a channel? What are the expectations for responsiveness, if any? When should you use IRC to ask for attention vs filing a ticket or emailing or other?
There are no video tools or norms specific to the Technology Department. Our primary tool for meetings is Google Meet.
Some lists are open to any subscriber or archived publically. Other lists are restricted to WMF staff or subsets of staff. Assume that anything written to any list may ultimately become public.
Key public mailing lists
|wikimedia-l||Active list with passionate community members - let’s chat about this. General hub of information.|
|wikitech-l||Developers of mediawiki|
|engineering||Anyone (fully public now. Was previously private)|
|ops||Operations staff, volunteers and some developers|
Technology Department lists
|firstname.lastname@example.org||Everybody in the Technology Department|
|email@example.com||Information primarily for managers in the Technology Department. Includes people who do some managerial work but are not formal people managers, such as Product Managers. Open to anyone at WMF.|
|firstname.lastname@example.org||Similar to tech-dept-info, but limited specifically to people managers and used only for information that should remain private. Note that long-term privacy is not guaranteed and should not be assumed.|
|email@example.com||Community Tech team|
|firstname.lastname@example.org||CTO, Program Managers in Technology, eng-admin|
|email@example.com||Search Platform public list (formerly known as Discovery team)|
|firstname.lastname@example.org||Project Coordinators and Assistants in Technology|
|email@example.com||MW core team|
|firstname.lastname@example.org||Release Engineering team (internal/coordination only, otherwise all on qa@ and wikitech-l@)|
|email@example.com||“a cross-departmental list for researchers at the WMF”. Also includes research fellows and NDA’ed collaborators|
|firstname.lastname@example.org||WMF Research department (internal discussion)|
|email@example.com||Operations and Security experts across the org.|