Internally, a couple of teams are talking about posting these for first draft by 10 Dec. Thinking that might be a good time for us too.
|Duplicate||Qgil||T125545 Phabricator Q&A session for Community Liaisons|
|Resolved||Qgil||T116025 Goal: Align Community Liaison and Developer Relations project management practices|
|Resolved||Qgil||T119387 Community Liaison and Developer Relation quarterly goals for January - March 2016|
|Resolved||• Rdicerb||T118703 Community Liaison quarterly goals for January - March 2016|
Individual goals have been very useful for Developer Relations. See T109829: Developer Relations quarterly goals for October-December 2015 and previous quarters. Even if they might sound as "more obligations", in fact they define less, well focused obligations.
Defining your individual goals and agreeing them with your team is also a way to define and agree what will not be a goal for you during the quarter. This might not sound too different in quiet times, when you have more flexibility to pick tasks and may take new tasks brought suddenly by others. However, the difference is big when you are busy, and you have no other option than prioritizing tasks and saying "Not this quarter, sorry". Or "Yes, but only if I agree with my team that this other current goal can be pushed to the next quarter."
For people dedicating a lot of time to regular workflows (like i.e. @Aklapper and many community liaisons), individual goals are also a way to commit yourself for non-regular tasks that you want to complete, and that otherwise end up slipping month after month because you are caught by "regular work".
Can you link each goal to its corresponding task in Phabricator, please?
Also, any comments on my reply about individual goals? Developer Relations will list the individual goals right underneath the team goals, and I recommend you to do the same in your team goals page. This way whoever is interested in the team goals can find the other CL goals right there.