Classic Block hidden from inserter in 7.1; 7.0.1 RC1 testing open
Start of the meeting in Slack, facilitated by @audrasjb 
See the agenda post.
Announcements 
7.1
- Roadmap for 7.1
- Recent proposals:
- Recent dev notes:
7.0.1
General
- Guidelines for Syncing Code From Gutenberg Into WordPress Develop
- Performance Chat Summary: 30 June 2026
- WordPress Contributor Dashboard: New Views, Custom Ladder, and More
Discussion 
From @amykamala about handbook updates to AI policies
“I’d like to also propose a new policy: disclosure of use of AI in posts and announcements. It can just be a quick sentence at the bottom of the page saying AI tools were used in the creation of this article or something to that affect.”
@westonruter also proposed to apply such a policy to Slack comments, and @desrosj also has some draft for this topic for posts and comments.
@amykamala shared that a draft is being worked on here or here. The core-ai update draft could use some feedback. It’s based on Jonathan’s comments and the comments in the thread. The post comment guidelines draft doesn’t have changes to review yet but folks are welcome to work on it.
@audrasjb advised to use a new section for this topic in the Core Handbook.
Dev Chat scheduling during 7.1 cycle
With all the coming release parties scheduled on Wednesday, it looks like we need to move the meeting to another time slot.
@amykamala and @audrasjb suggest to switch the devchat time slot to 15:00 on Thursdays, starting the week of 7.1 beta 1.
@jorbin noted that it will conflict with the monthly Developer Blog Editorial Group meeting, the bi-weekly Accessibility team meetings and a weekly core-test meeting. Which is not a blocker, but worth taking this into account. He also noted that Tuesdays are more open but this day is not the best for Amy and JB.
@joedolson noted that the Accessibility team moved its meeting for the 7.0 schedule, which was also on Thursdays, and they could do that again.
@amykamala and @audrasjb will come up next week with one or two proposals so a decision can be made.
From @dmsnell about concerns about WPCS discrepancies in GitHub and Trac, and proposed change in the general policy
The concern raised in this thread is especially about the array elements alignment rule.
The attendees agreed that while 90% of the time, alignment is prefered, there are some cases where it makes things worse.
From @joedolson: “It seems to me like the primary point of @dmsnell‘s thread was about misaligned standards between Gutenberg and Core, but he seemed to walk that assertion back in the thread? Is there a real issue here? If the standards aren’t aligned, one of them needs to change”
Fetched July 1, 2026
