Hello, @ZhaoFJx! I wanted to check in and see if there has been any community discussion on the above proposal: "Perhaps the ZH community can start with the default state (i.e., admins only manage the event-organizer right."

Hello, @Sadads & @Udehb-WMF. I have created a basic draft ticket for a project idea we may pursue later in the year. I am not sure if we will work on it yet or not, but the first step is to do some design explorations. Adding you to this ticket see what comes up for you and what ideas you have. Thanks!

cc @Udehb-WMF, heads up about a new potential power/ability available to those with the event organizer right

Updates from a Sept 24 meeting to discuss Community Configuration + CampaignEvents extension:

• We will remove the ability to configure management of the Organizer right because a) We anticipate that this will add great complexity from a technical and product perspective, and b) We do not think it is strictly required for the MVP.
• The namespace question was also highlighted as a potential technical complexity, but it may be worth investigating, so we'll see what is uncovered in the course of the technical investigation (T374069)

Great, thank you, @ZhaoFJx!

Notes from sprint planning discussion:

• Namespace question - big topic for us to think through
  • Once event namespace is turned on, we probably don't want the event namespace to be turned off
• Complexity is a concern - what is the simplest first version?
  • For example: Maybe only start with essentials

Hi @ZhaoFJx! Thank you for this update. It is great that the community was able to quickly come together to reach consensus!

Update: The feature is live, but we do not know if there is any usage yet.

Update: Error state work will be covered in the scope of T374837.

Sounds good; thank you, @ZhaoFJx!

@KStoller-WMF: Yes, done! I have merged the other task and added some of the details you included in it into this task. Thank you!