• "Wikimedia OS community feedback and backlog" feels unclear to me: "backlog"? "developer community" instead?.
• Wondering where/how to cover bug wrangling.

I have posted a first draft in the description.

Everybody: is the picture of the current quarter accurate?

@Aklapper

• "Wikimedia open source community feedback and backlog" is supposed to be equivalent to "bug wrangling" aka all the time you spend in Phabricator, lists, pumps, etc, trying to assure that useful feedback is documented and receiving the attention it deserves. Better wording is welcome. "developer community" is not precise enough, because you are (going to be) the main ECT contact for free software contributors, not for third party developers. [[[ https://www.mediawiki.org/wiki/Engineering_Community_Team/Developer_Relations_team#Types_of_developers | 1 ]]]. In any case, I'm proposing a restriction of 50% of your time, as discussed.
• We need to agree who invests how much time in outreach programs: Google Code-in, Outreachy, GSoC. Is it 0.25 or actually less? For instance, in the last GSoC / Outreachy round I didn't have to invest 0.25 at all thanks to Niharika and a better process that required less attention altogether.
• "Wikimedia tech metrics and reports" now in fact mixes our "tracking goal" of improving code review performance with our continuous work of improving tech community metrics with Bitergia. Two different activities but they are actually connected... and in any case I believe they will require a significant amount of dedication. But 0.25? If we really want offer a SLA by the end of June 2016, this percentage probably is not exaggerated.

@Rfarrand

• Please check that my estimations for our main events are correct. I have the impression that I'm allocating too few % of time, but then again, are you really investing more than 0.25% of your time (say 8-10 hours weekly, every week of a quarter) for the hackathons? The Developer Summit is a different beast because we are the local organizers.
• You are doing many little different things and I'm having difficulties to circle 0.25 around any. Probably we should group tech talks and offsites in one activity and allocate 0.25 there every quarter?

@Spage

• Your picture is simple in the surface: you are dedicated to the Web APIs. However, should we count 1 or 0.75% to leave space for other activities, acknowledge that you are working on other things?

@Qgil

• I have to update my own data properly. For now it seems like I'm doing almost nothing, which I can tell it's not the case. :)

@Qgil

• Added Wiki Loves Open Data aka T101950
• Added Wikimedia Tech Code of Conduct, which is going through its way as a goal for the next quarter.
• Added outreach to 3rd party developers because this is the main novelty of the Developer Relations plan, and it will be connected to the Web APIs hub and our events. We haven't discussed this yet, but it makes sense to pencil this down.

The list of projects above is now in sync with the Master Project List document. With this we can pass today's deadline for Community Engagement. We can fine tune this list in our team meeting and 1:1s next week. It's a work in progress by design, anyway.

I plan to mark this task as Resolved after our team meeting next Tuesday.

In T108935#1574713, @Qgil wrote:

Everybody: is the picture of the current quarter accurate?

As "feedback and backlog" and "outreach" are intermingled (e.g. when I point people in VPs to corresponding Phabricator tasks to get them potentially closer involved with developers, or explaining in Phab tickets how to provide more info by e.g. using the web browser's developer console and in the long run hopefully making some reporters "a bit more tech-savvy") it sounds vaguely correct I'd say.

@Aklapper

• "Wikimedia open source community feedback and backlog" is supposed to be equivalent to "bug wrangling" aka all the time you spend in Phabricator, lists, pumps, etc, trying to assure that useful feedback is documented and receiving the attention it deserves. Better wording is welcome.

By that definition it's still more in this quarter and somewhere around 0.6 or such, pending T102612 to reduce that value to 0.5 for the next quarter.

• We need to agree who invests how much time in outreach programs: Google Code-in, Outreachy, GSoC. Is it 0.25 or actually less?

If we manage to have community co-organizers again for GCI and if we end up attracting many great self-learning students who don't need too much handholding it should be less and something between 0.1-0.2, though it's hard to come up with some average value - the value is definitely higher before the program starts when outreaching to potential mentors and updating docs etc. takes place.

• "Wikimedia tech metrics and reports" now in fact mixes our "tracking goal" of improving code review performance with our continuous work of improving tech community metrics with Bitergia. Two different activities but they are actually connected... and in any case I believe they will require a significant amount of dedication. But 0.25? If we really want offer a SLA by the end of June 2016, this percentage probably is not exaggerated.

The value also depends on how much I manage myself to contribute more code-wise and how much communication and coordination will be required. But all in all 0.25 sounds fine to me.

In T108935#1574713, @Qgil wrote:

@Spage

• Your picture is simple in the surface: you are dedicated to the Web APIs. However, should we count 1 or 0.75% to leave space for other activities, acknowledge that you are working on other things?

I think 0.75%. E.g. T107804: Document ResourceLoaderImage module is not API documentation, yet it was a request from Reading team that I fulfilled. T108864: Update mediawiki.org templates to link to Diffusion, not gitblit is similar.

If you also count time spend on documentation and survey analysis into hackathons I would say .25, even more sometimes when you start to look at all the logstic work that goes into organizing the WMF engineers participation/logistics.

Lightning talks, tech talks, off-sites could be another .25

OK, MPL synced with the information above. I will close this task after our team meeting in a few hours unless someone stops me with solid arguments. :)