Wider goals

[karmatosed]

We already have some goals discussions that are firmly focused on time frames:

• Goals for WordPress 6.9 Release #5 : WP 6.9
• Let’s form some goals for Q4 #4: Q4

What about wider, bigger goals? What about papercuts and ‘what ifs’? This could be a good place to start collecting things that might come up and have some discussion around what could be covered.

What would you like to see covered by this team that fits within the goal:

The WordPress Core Program Team is focused on strengthening coordination across teams, improving efficiency and empowering contribution. It’s a home for those who span across product and project work.

[peiraisotta]

Chiming in with a thought about the WP Credits program, though what I’m sharing would be useful for all contributors who need guidance. It would be fantastic if each team had (and kept updated) a list of immediate contribution opportunities and even entire contribution projects. For example: WordCamp Pisa needs to edit and upload all talks to WordPress.tv, or the following Learn courses need to be translated or recreated in specific languages, with an estimate of how many hours each task would take to complete and the Slack handle of the project’s point of contact. And the same for each contribution team/program.

This would provide clear guidance to contributors who want to help but don’t feel comfortable choosing individual tasks from a long list, and instead prefer to work on more structured projects that are already “prepared.” It would also open up opportunities for project-based sponsorships.

In addition, this approach would benefit contribution teams by giving visibility to their priorities, helping them attract support for the work that matters most to them, and ensuring their projects progress more efficiently.

I'm curious to hear other people's thoughts about this idea. Thank you @karmatosed for giving us this space!

[karmatosed]

It would be fantastic if each team had (and kept updated) a list of immediate contribution opportunities and even entire contribution projects.

I love this as an idea. It makes me wonder how to do it and have it both easy to find project and wider across all. Similar, how it could be relatively automated / not end up out of sync with how things are going on. I don’t want to dwell on that too much, but I know past manual attempts for example in the design team failed because of the burden to maintain.

Your comment @peiraisotta touches on two areas and think both are good to explore:

• Surfacing what each team does and opportunities in general within them.
• Showing individual teams current projects. Which also might be ‘cross team’ (I actually personally hope for more cross-team collab).

Musing on this idea a bit having a place where someone could as an organiser of a contribution day as you mention go and get ‘one-stop’ everything could be incredible.