Welcome to the second edition of this update. Each start of the week, there will be a summary post for this team sharing what happened last week and setting out some plans for the week ahead.

As with any process on this team, please give feedback for anything you would like to see improved, iterated or adjusted. This team is made better with each piece of feedback.

SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. happenings

These are focused on the #core-program team Slack itself as a summary, wider work is called out in the next section.

• We had a lot of people join us and say hi, which was great.
• @estelaris started a discussion around recognising contributions, specifically how and what is a contribution, that is continuing.
• There was a discussion thread around paper cuts in team setup.
• Several times Community Summit notes were shared in response to threads. This raised the point that these should be reviewed by this team for the points which could be actioned and learnt from.
• Core Importers was brought to the team as needing a maintainer, this was taken to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to resolve. However, it’s worth noting the discovery here is some areas might not need a maintainer.
• A roadmap was being sought for AI to help with workshops. This inspired the roadmap page in handbook.

If you don’t see anything mentioned here you would like called out please mention in comments.

Work done

• Pledges now show up for team.
• Post looking for feedback around Communication for team.
• A handbook page was begun to collect Roadmaps.

Did you do something this week from this team? That’s awesome, please raise it up in the comments of this post.

Get involved

Things are just getting started but already there are some things you can help with:

• Feedback is being asked around Communication for team.
• Feedback is being asked around paper cuts to flows in setting up teams, make sites and pledge pages.
• The team itself can be joined at #core-program on Slack.

Plans this week

These are the ones known about. As the team grows we can surface more people’s work within these teams.

• Continue the team handbook.
  • Create a handbook page for Community Summit note collecting and sorting: this is specifically in response to how many have been shared so far as relevant to discussions.
  • Create a handbook page for ‘Resources’ that can include talks which might be relevant around this team. Potentially put the Community Summit notes under this also.
  • Look at where Guidelines for repo management should live.
• Summarise the feedback and take next steps on communication post.
  • Ensure if we do decide on repo it meets the guidelines for management.

If you have any plans of things you are going to do please share them as a comment.

#this-week