Here's a first draft. I was able to discuss goals with @Aklapper and @NiharikaKohli on #wikimedia-ect IRC. I'll try to chat with @Rfarrand and @Spage later today.

The description of this task is now synced with the slide of the Community Engagement Q1 goals slide deck. I will keep both in sync.

Please check the changes made on your goals, adding and fine tuning. Details to be discussed in the respective tasks, when available. @Rfarrand, please create your task, so we can discuss the details there. About mine, see below.

Lila is recommending a categorization of goals by Focus, Strengthen, and Experiment (and by this order, if possible). I like the idea because it encourages a combination of homework and risk, keeping always an eye on the main task of the quarter. The main goal should be the main focus, obviously. I have added these labels to the tasks and I have sorted 1, 2, 3 accordingly.

About my goal, while agreeing on T97283: Plan to focus on the Developer audience is an important goal for this quarter, I felt that the actual implementation was a different story, quite internal, and perhaps forcing too much the machine by making it a quarterly goal. Instead, I am proposing to start covering the void we have on "data" (vs "developer", although these terms are fuzzy and overlapping). Chance or destiny brought me to some conversations with Strategic Partnerships and the Wikidata team about the idea of reaching out to open data organizations to get the interesting parts of their datasets in Wikimedia projects. This also fits with the void on data topics that @Spage has been mentioning in relation to #dev.wikimedia.org. See this discussion in the Wikidata mailing list for some details and examples.

If you think this team goal makes sense, and if the stakeholders proposed also think it is a good goal, I'm happy to push it as "Experiment".

Luis Villa has reviewed this proposal and he sees no blockers.

He mentioned that T101950's measurement of success was a bit vague and perhaps too ambitious. I agreed, and I have edited accordingly. I checked this goal with Lydia (Wikidata) and Sylvia (Strategic Partnerships) and both are on board.

Today #Engineering-Community is meeting to approve our goals for the next quarter. I'm personally happy with the goals proposed. There are some details to be defined, but they are minor and can be discussed in each task.

You will also see that I'm proposing a structure for quarterly goals tasks (i.e. T101950). The intent is to help formulating goals today, and reviewing them at the end of the quarter, knowing which place these goals have in the WMF-Call-To-Action and the WMF strategy in general. As always, feedback welcome.

From now on, WMF employees are not required to agree annual goals with their managers. Instead, all of us are required to define our individual quarterly goals. This fits better with the increased relevance of team quarterly goals and with the idea of an agile organization.

The simplest way to document our individual goals is to add them here, to have a general view of our plans for this quarter. Please check your personal backlogs, #Engineering-Community backlog, or come up with new ideas to be transformed into goals. The sooner we draft, the better. We will use team and 1:1 meetings plus whatever feedback we get to consolidate and approve these goals... by next Tuesday 23?

Note that you might have goals (i.e. related to personal development) that for whatever reasons you prefer not to share publicly. This should be more the exception than the norm (since all of us are expected to focus on public goals first), but it is an exception that all of us have the right for. If you ave one of these, just check with me in our next meeting.

My initial list of goals for Jul-Sep 2015; to be updated more:

• T88531: Goal: Organize a Gerrit Cleanup Day on September 23, 2015
• T101116: Goal: Clarify interaction/sync with TPG, RelEng, CL in areas of Phab practices, QA, community (for June/July already)
• T102611: Goal: Drive more complex long-term tasks closer to resolution
• T103556: Learn from WMDE's approaches how to better explaining actions and processes in Engineering and making "Phab more welcoming"
• T102612: Goal: Clarify the bugwrangler's areas of triage and involvement across dev teams; slice out projects to not follow and make that explicit (but ask teams to CC/escalate to me when needed) and documented
• Tech Community Metrics: Get better stats for paid vs volunteer

Summarizing my (quite improvised) feedback during my 1:1 with Andre an hour ago:

Good draft! But... :)

• We force ourselves not to have more than 5 team goals; let's translate this hard limit in personal goals as well. You can always work on more tasks, but in terms of goals committed, 3 is good and 5 should be the maximum.
• It's good to have goals about improving processes (as opposed to focus on deliverables only), but still deliverables should have its weight.
• The goals about processes need to have a clear explanation of the problem that needs solving, and the steps taken to solve that problem, in order to have a way to measure whether the goal has been accomplished or not.
• Alignment with other teams is good, and it is also a good chance to get members of those teams equally committed to the common goal by making it their personal quarterly goal as well. This will help succeeding with the goal (shared responsibilities) and evaluating it in the first place (multiple points of view).

So I'm going to postpone "Learn from WMDE about better handling requests, explaining actions and processes, and making "Phab more welcoming"" to Q4-2015 - I have hopes to investigate that a bit more at Germany's WikiCon in September.
I'd keep the rest though, at least I want those to get started (not necessarily all finished) in Q3-2015.

I need to work more on defining my deliverables this week.

Main Goals for July - Sep:

• Identify Goals of MediaWiki Developers Summit 2016, begin next steps in planning/finalizing major logistics
• Summarize Feedback/Lessons Learned/Metrics from Zurich, Lyon, Mexico City. Close projects. Suggestions for changes for future years.
• Work with Travel/Quim/Terry/EMGT to come up with a plan for engineering travel approvals to Jerusalem & Esino Lario
• Complete Documentation & Tips for Future Hackathon Organizers (WIP)
• Complete Hackathon 101 Documentation for newbies (planning to make major progress on this in late June/earlyJuly)
• Continue working with teams on their off-sites as needed (probably not going to be an official goal)

@Qgil I read your feedback for Andre about having too many goals... so maybe we can cut down the list together during our 1v1,

My goals for Jul-Sep 2015:

• Respond to feedback on T307: Announcing the Developer Hub prototype release

if no one else steps forward for T101441: Goal: Integrate the new Web APIs hub with mediawiki.org, I will likely be working on it all quarter, and only able to document ad hoc doc requests and changes.
If someone else works on T101441, then I'm freed up to do some work on:

• at least two more articles: something on Wikidata (T92003: Showcase/inspire: Magnus Manske's awesome Wikidata work (Reasonator, Autodesc)? and something else from #dev.wikimedia.org, "Article Candidates". what about the data part of "use our APIs and data"
• task TBD grow a "documentation task force" to contribute to Data and developer hub

Top Three Goals:

1. Wikimania Hackathon complete
2. Developers Summit Plan and logistics
3. Define Travel Approval Process for Engineering Department for Wikimedia Hackathon 2016 and Wikimania 2016

Everything else will be included in sprints

Current thoughts for my personal goals:

1. T101950: Goal: Establish a framework to engage with data engineers and open data organizations
2. Hopefully implement T97283: Plan to focus on the Developer audience
3. A shared goal with S that we discussed yesterday, forming a Documentation task force of sorts to support T101441: Goal: Integrate the new Web APIs hub with mediawiki.org
4. Successful completion of T76199: Goal: Newsletter extension for MediaWiki (GSoC project I'm co-mentoring)

In T101100#1389402, @Spage wrote:

My goals for Jul-Sep 2015:

• Respond to feedback on T307: Announcing the Developer Hub prototype release

"Respond to feedback" is not a goal per se. Listening to feedback, replying, and adapting plans is just part of T101441.

if no one else steps forward for T101441: Goal: Integrate the new Web APIs hub with mediawiki.org, I will likely be working on it all quarter, and only able to document ad hoc doc requests and changes.
If someone else works on T101441, then I'm freed up to do some work on:

You are clearly the owner of T101441. :) It's a big task, but still it should allow you to do some more work.

• at least two more articles: something on Wikidata (T92003: Showcase/inspire: Magnus Manske's awesome Wikidata work (Reasonator, Autodesc)? and something else from #dev.wikimedia.org, "Article Candidates". what about the data part of "use our APIs and data"

At least at this point I'm happy not counting new articles as goals, just like the rest of us has tasks that will happen even if they are not marked as goals. You are a tech writer and you really would need to find time to write content for the Developer Hub. Otherwise we are doing something wrong.

• task TBD grow a "documentation task force" to contribute to Data and developer hub

We agreed that this would be a shared goal between you and me. Please create a task for it and propose measurements of success. We can fine tune things in the task itself.

In addition to these two goals, it would be good to check with @JKatzWMF whether he is counting on Reading team specific goals. In other words, you must have only one list of personal goals (just like the rest of us), regardless of the teams involved.

In T101100#1389417, @Rfarrand wrote:

Top Three Goals:

1. Wikimania Hackathon complete
2. Developers Summit Plan and logistics
3. Define Travel Approval Process for Engineering Department for Wikimedia Hackathon 2016 and Wikimania 2016

Everything else will be included in sprints

Very good! Please create the tasks needed and update the description above as needed.

I have added more information to each of the tasks related to each of my Q1 goals.

Let's mark as blockers only the team goals, not the individual goals. If someone fails on an individual goal they're doomed ;) but the team will survive.