@Qgil i don't mean to totally rain on the language of the goals you all have come up with, but I am concerned about the way this one is formulated. What happens if there are teams and individual contributors that DONT follow the general guidelines (which I imagine is inevitable)? Will this goal then not be met? May I suggest a slight modification?

"Common project management guidelines to be followed by individual teams and contributors are published."

Also, feel free to assign this to me ;)

You got it! :)

Ok, now the goal is simpler to measure. I think we could start trying to agree on the skeleton of the guidelines, in order to have a common understanding of the topics we want to cover. With the skeleton agreed, the rest is just details. ;)

@Qgil awesome :) I can give this some more brain bandwidth next week.

@Qgil @Aklapper Can you guys share at a high level or point me to some of the constraints (as you understand them) to project management in Phab? I suspect some decisions have been made in terms of how things are set up in this Phab instance that will impact how we will need to go about project managing at a base level (eg the semantic meanings of projects/teams, needing to create new workboards for each sprint, etc)?

I am thinking it would make sense to start compiling the basic limitations/configuration decisions first and then start writing some concise prose around those to serve as a basis of the documentation.

After that, we'll probably need to start experimenting and gather input from teams who are beginning to use phabricator for project management in order to understand what the day-to-day best practices are.

@Awjrichards three weeks have passed, and three weeks is basically what we have to bring this task to a level that allows us to consider it complete.

Also, on December 3rd we have T557: Tech Talk: Phabricator for Wikimedia projects.

When do you think you will be able to work on this? If you start editing, I will help.

(Last Monday we had a checkpoint about WMF's top tech priorities, and there was a question specific to the status of this document. No, they won't forget. :)

@Qgil I've added the task to the Team Practices backlog and anticipate starting to work on this after this holiday weekend. Let's plan to check in at the end of next week to review the document and its status - that will help me ensure I keep the task high on my own priority list.

Were you hoping to have this complete in time for the December 3rd tech talk? I am not understanding how that's related, but I realize I have a limited view :)

In T558#788662, @Awjrichards wrote:

Were you hoping to have this complete in time for the December 3rd tech talk?

Not complete, but it would be nice to send people interested in that session to a page that has real work-in-progress. Also, it's the only date I had at hand other than "end of year". :)

@Qgil is there anything else you need/would like to see from the TPG on this goal/task? We will of course keep an eye on the doc and continue to help evolve it, but I want to make sure we've fulfilled expectations on this :)

Great @Qgil, thanks. I've responded :)