No goal related to our annual plans on #community-wishlist-survey (Program 8)? Program 7 is covered in the goals proposed.

In T131915#2348195, @Qgil wrote:

No goal related to our annual plans on #community-wishlist-survey (Program 8)? Program 7 is covered in the goals proposed.

I think that's just "Regular workflows" now.
Although we could repeat "A plan for the top ten Community Wishlist tasks driven by volunteers" with another 10?
I'm also considering this as a personal goal: T136866: Improve the per-programming-language listings for our tools

I'd rather focus deeper on the 10 tasks we commit to in this quarter rather than trying to embrace too much by adding 10 more... I don't know, what do you (plural) think?

In any case, if there is no clear goal for the CW in this quarter, then there is no need to force one.

I took the VE task (T96500) out of my goals, because it doesn't relate directly with Editing's goals for this Q as far as I understand them, and since I haven't been able to figure out what the plans are for further rollouts, I _will_ keep it as something I work on (obviously), but I don't want to commit to a quarterly goal.

My goals:

• T137795: Work on Edit Review Improvement project, to involve communities on development process and tests
• T137796: Help to define next steps concerning Flow development, based on the Flow Satisfaction Survey

I'm lowering the previous ones, due to a lack of time. I prefer to focus on daily work about products that have an important community input instead of more theoretical (but still important) tasks.

• T121500: Unify product documentation for users to make it easier to share, translate and edit or T129088: Create an easy to maintain glossary to facilitate documentation translation (help pages and technical documentation) are possibly expandable by Johan's work on translations
• T113490: 10 tips for communicating with communities when developing software will benefit of Keegan's work.

I'm still watching your work and supporting you, guys.

We have agreed our team goals on time, but there is still some more work to do with individual goals. I hope we can complete the list of individual goals by the end of Thursday, July 7.

Update on individual goals:

• Most of them are considered stable: @Aklapper, @CKoerner_WMF, @Elitre @Keegan, @Qgil, @Whatamidoing-WMF.
• I am sharing feedback with @Rfarrand, @Quiddity, @Trizek-WMF about possible improvements.
• I have discussed individual goals with @Johan and @Moushira, and I have asked them to document them here.

I've updated my goals:

• T125632: Plan, write and submit a satisfaction survey concerning Flow to communities and T130730: Draft and review a public announcement concerning Flow support to define next steps on supporting communities which are happy to use Flow
• T123538: Rethink the way we communicate with communities concerning Collaboration team work as a practical case for @Keegan's work - collaboration team needs to have a way to communicate main changes about products (Notifications, Flow, Edit Review Improvements)

There are still a couple of people that need to document here the goals agreed in 1:1 conversations (last week). I am hoping to see the list of individual goals completed by the end of this week. We can blame Summer vacation for the delay.

Individual goals finally defined by all team members. The review of this quarter will happen at some point in October.

Both the dry run and the quarterly review went in my opinion well, in terms of delivering a concise message about our activities, our motivation behind them, the outcomes, and a glimpse of how these achievements in the previous quarter are continuing in this quarter. I didn't get any questions in the quarterly review, which might mean that everything was very clear or something different...

I will close this task as soon as the quarterly review slides have been published.