I just want to +1 that Dawn would make an excellent chair. 💯

 

If Dawn is interested, is this something that the group or the TOC votes on?

 

From: cncf-tag-contributor-strategy@... <cncf-tag-contributor-strategy@...> On Behalf Of Paris Pittman via lists.cncf.io
Sent: Tuesday, January 11, 2022 10:35 AM
To: cncf-tag-contributor-strategy@...
Subject: [tag-contributor-strategy] Paris resigning as TAG ContribStrat Co-Chair; focus on Maintainer Circle

 

Team, 

 

I'd like to resign my Chair hat for the TAG and nominate Dawn Foster in my place. Explanation below but first about Dawn:

Dawn leads the open source community strategy efforts within VMware’s Open Source Program Office. She is on the Board of OpenUK, committed to develop and sustain UK leadership in Open Technology. She is on the Governing Board and is a maintainer for the Linux Foundation’s CHAOSS open source metrics project and is also on the TODO Group Steering Committee.

 

She has more than 20 years of experience in business and technology with expertise in strategic planning, management, community building, community management, open source software, market research, and more. She is passionate about bringing people together through a combination of online communities and real-world events. She has experience building new communities, and managing existing communities with a particular emphasis on developer and open source communities.

 

Most recently, Dawn was a consultant at The Scale Factory after being Director of Community at Puppet. Prior to Puppet, she was leading the Community Office within Intel’s Open Source Technology Center. In addition to working at Intel, Dawn was an online community consultant, and she has worked at Jive Software, Compiere, and a Midwestern manufacturing company in positions ranging from Unix system administrator to market researcher to community manager to open source strategist.

 

 

 

**Whats Next:** 

I submitted the proposal to the Technical Advisory Council (TOC) for the then Special Interest Group that we now call Technical Advisory Groups over [two years ago]. The group has flourished to be a helpful resource to the TOC and CNCF projects through ad hoc services, tooling, and programs. We've grown to include many contributors, a new tech lead role: Carolyn!, a repo of templates AND guidance, a cncf contributor site to house said guidance!, and a maintainer circle to support the humans behind the code. 

 

And the last point brings me to my 2022 goals: I'd like to focus on Maintainer Circle! Bringing that up not only to a solid state but an industry leading resource for the thousands of maintainers and leaders of CNCF projects. After coorindating the events we have had virtually and in-person, we've gotten feedback that folks not only really like this but want to see more of it. With this focus, it would be best if I step back from Chair and concentrate on this area. There is a lot of power in maintainers coming together to learn, share, and grow; really looking forward to this thriving.   

 

I have the utmost respect and trust in Dawn to co-chair our group; she has stepped up in countless ways with contributions including organizational functions and leadership. Dawn will be an excellent TAG Chair!

 

Paris

 

 

Hi Saad and Alena,

 

TAG Contributor Strategy needs your approval for the three pieces of content below. I keep track of them on our project board, in the Needs TOC Approval column.

 

• https://github.com/cncf/tag-contributor-strategy/pull/113
• https://github.com/cncf/tag-contributor-strategy/pull/114
• https://github.com/cncf/project-template/pull/12

 

Thanks!

Carolyn Van Slyck
she/her
CNCF TAG Contributor Strategy Tech Lead

 

Hi everyone -

Problems:
- We’ve talked at our meetings and on slack (https://cloud-native.slack.com/archives/CT6CWS1JN/p1616606723019300) about setting up a dedicated time with a dedicated calendar invite for Maintainers Circle so it doesn’t cause confusion with maintainers and/or our regular SIG attendees that are working on issues and guidance.
- We have 5 SIG meetings; 3 a week at least twice a month which is very heavy. Now that we are up and running, we can do more to drive triage async with updates.

Solution:
- First Thursday of the month is Maintainers Circle with a dedicated invite (not a sig-contrib strategy meeting invite)
- Third Thursday of the month is our main update meeting; we keep the bi-weekly working groups where a large amount of discussion happens.


Are there any objections? We’ll time box this for at least 72 hours and come to a resolution with any calendar invite changes or impacts made by next Tuesday, April 27th.

If passed, we will update the charter and reflecting documents. 






Paris Pittman
Apple
OSPO
One Apple Park Way
Cupertino, CA 95014, USA
iPhone +1-410-440-8754
paris_pittman@...

This email and any attachments may be privileged and may contain confidential information intended only for the recipient(s) named above. Any other distribution, forwarding, copying or disclosure of this message is strictly prohibited. If you have received this email in error, please notify me immediately by telephone or return email, and delete this message from your system.