Greetings Eclipse Architecture Council
I apologise, but it appears that I have completely forgotten to capture notes from our last meeting. I'd like to consider possibly using the Zoom AI features to capture a summary of our discussion. I'll make that the first topic of discussion.
I have a couple of things that I want to chat with you about on this week's call. Both are intended to address an opportunity that I believe that we have to help our project teams better understand how to operate a vendor neutral, open, transparent, and meritocratic open source project at the Eclipse Foundation.
First, I would like to discuss the potential for adding a formal committer training requirement. We already have some
committer training videos, but I'd like to explore options for using a learning platform to deliver a 20-30 minute training session that touches on the important aspects of open collaboration in general, and in the context of Eclipse Foundation governance. The idea being that we use this as an opportunity to ensure that the candidates know what they're signing up for, and what we need from them. Depending on how our discussion goes, I'll open an issue for further discussion.
The other topic that I'd like to discuss is the potential introduction of a formal notion of coach into our process. I'm thinking along the lines of an Agile Coach for the project team, but with responsibilities aligned with ensuring that the project team is engaged in good open source development practices. We might argue that this is something that project leads should be doing, but I'm thinking that -- while it might be held by the same individual -- it is a distinct role. This may be something that we consider adding to the EDP. Again, based on our discussion tomorrow, I'll open an issue.
If anybody has anything else that they'd like to add to the agenda, please let us know.
Wayne
-- Wayne Beaton (he/him)
Director, Open Source Projects | Eclipse Foundation
