Developer Nsɛm a Wɔka Kyerɛ
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. This Wikimedia Foundation team was blown apart by the wind of change in June 2023. Its remnants can be found in various places: |
The Developer Advocacy team is a sub team of the Technical Engagement team. The Developer Advocacy team supports the technical communities who use Wikimedia web APIs and software projects to spread and improve free knowledge. They collaborate with teams in the Wikimedia Foundation, the larger Wikimedia movement, and external organizations to promote the use of the Wikimedia platforms via documentation, sample code, libraries, articles, and reference applications. The team also supports programs to actively recruit and mentor new technical contributors who will become the next generation of Wikimedia Foundation staff and FLOSS project maintainers. Our primary focus is to help the developer community build and scale successful projects using Wikimedia technology. We encourage them to contribute to our free and open source projects as a way to achieve their own goals.
Extended content | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
To contact us, see #Team below. AreasThese are regular tasks that usually don't make it to our goals or backlogs explicitly, but take a significant portion of our time and attention. Everywhere (within reason)
Task managementScan new tasks in Phabricator , bringing them into good shape and looking for potential issues that need escalation.
For a more detailed description of workflows, see Bugwrangler . Events
DocumentationCoordination of entry-level and mid-level documentation with a focus on documentation for volunteer contributors that encourages developers to use Wikimedia data and APIs. More info at Documentation. Tech BlogSee Wikimedia technical blog editorial guidelines. Outreach programsCoordinate Wikimedia's participation in Outreach programs (Google Summer of Code , Outreachy , Season of Docs , etc.) to bring in new contributors to our technical projects and introduce them to free and open source software. Technical Community MetricsMaintain https://wikimedia.biterg.io which offers some statistics about Wikimedia's technical community. See Community metrics . ProjectsSee Wikimedia Technical Engagement/Goals for a list of ongoing work. Some recent or ongoing projects:
Also see Wikimedia Technical Engagement/Workshops and talks . PlanningYou can follow our work and get involved. Contributors of all disciplines and skill levels are welcome! We mainly use Phabricator for planning work. You can find our workboard at phab:tag/developer-advocacy/. Every significant task that doesn't belong to a regular workflow needs to have its own Phabricator task associated to the team project. Our Phabricator workboard columns have the following meaning:
Quarterly goalsSee the corresponding entries on Wikimedia Technology/Annual Plans for goals since July 2021. For historical goals, see the "Technical Engagement" section in the corresponding quarter linked on Wikimedia Technology/Goals before July 2021, and #Historical data below. Also see the corresponding quarterly columns on the Phabricator team workboard. Team
ContactYou can contact the entire team
To contact individual team members, see the contact information on the individual user pages (linked above). Historical dataBefore July 2018, this team was called Developer Relations. Before September 2015, this team was called Engineering Community. Our previous activity is in the links on the Engineering Community Team template on MediaWiki wiki. Before April 2016, the team used monthly Sprint projects in Phabricator to plan work. For older monthly sprint projects before the team name was changed in Sep2015, see Oct2014, Nov2014, Dec2014, Jan2015, Feb2015, Mar2015, Apr2015, May2015, Jun2015, Jul2015, Aug2015. Quarterly goalsSee the "Technical Engagement" section in the corresponding quarter linked on Wikimedia Technology/Goals. For older goals:
Quarterly check-insThe Wikimedia Foundation performed Quarterly Reviews for a while. They were later renamed to Quarterly Check Ins:
|