Let’s form some goals for Q4 #4
Replies: 4 comments
-
|
I'm curious most about the roadmaps and how we can ensure there's consistency in how they are surfaced, even as I understand they will likely be written differently. Having a similar place each are visible and available that folks can look for feels like a big win for getting involved. Another area that comes to mind is establishing AI guidelines as this cuts across all the teams and feels like something the Program team could facilitate standardizing. |
Beta Was this translation helpful? Give feedback.
-
|
I shared a wider goal here, and as an immediate goal and preparatory step, may I suggest that by the end of 2025 this team connects with the contribution teams to identify these projects and assign points of contact, so that in 2026 we can move toward the larger goal of creating such pages/dashboards? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @karmatosed, I am so excited to see this come to fruition! I agree that it is a bit too much for q4. A shared roadmap, easy contribution start up, and recognition I think are great priorities to start now. @felipevelzani has been looking into recognition and those would be strong starting points. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks everyone. I am now going to close this and focus on a summary post on make to get the Q4 and beyond goals out. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Let’s get within the next week or so ideas here on the goals to focus on for Q4. The first ones I am going to suggest are based on looking at the conversations in Slack, the summit notes and original goals for this team.
It’s worth noting that having small goes and large goals is good. However, having tasks from goals that can be done and given to people is key. I am going to try and suggest things that give us options to work on areas can both be ‘documentation’ but also delivery.
Another thing worth noting is this is a first suggestion, if you have other ideas please surface them. We form these together.
Goal Proposals
This work falls into some key areas:
Discovery
This work is auditing, not deciding. The work will be existing and gathered. Most likely part of this is documenting for a start in the program team handbook.
Iterating
Being able to start work more easily is key for contribution. One aspect perhaps this team can think of is providing kits and soothing papercuts in flows.
New
Sometimes new things are good to also create and giving space for goals that draw on the knowledge of those in this team might be useful.
There are lots of things we can do, this is about what we can do in Q4. In honesty this is a long list for that and could be cut shorter happily. The point is to have I would suggest work in both discovery, iterating and new at all times for the team to keep us flowing between types of tasks. It is also different types of work so will appeal to different contributors.
Once we have all the ideas, a post on make.wordpress.org/program will be made outlining the ideas. These then can have more input. The idea is with each collaboration the refinement can happen. Finally, they can be decided and focused on.
Beta Was this translation helpful? Give feedback.
All reactions