# SIG - Contributor Experience Agenda & Notes

Meeting Notes

Standing items for each meeting:

Reminders: https://spinnaker.io/community/contributing/code-of-conduct/

Meeting Times:
First Thursday, 9:00am Pacific Time
Third Thursday, 9:00pm Pacific Time

Link to Zoom is posted in Spinnaker Slack
## September 16, 2021
Attendees: Nikema Prophet
no meeting

## September 2, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda:

Ige: @Nikema can contact Thomas McGonagle and ask if he will speak about DevSecOps. Think about others...

Nikema: Added a page to the spinnaker.io website https://spinnaker.io/docs/community/contributing/content-contributing/

Ige: Had a dev.to blog post featured

https://dev.to/aws-builders/tackling-security-vulnerability-at-an-early-stage-in-sdlc-1kl

https://dev.to/aws-builders/using-github-actions-to-build-packer-ami-on-aws-3p12

## August 19, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda:
- How do we add value as a SIG?
- Mentoring
- Webinars (talk with people in the community)
- Blog posts
- Revisiting Gardening Days?
- Needs to be planned
- Have resources available (engineers on-call, compute, prizes)
- Socialize content created and seek collaboration
- Monthly event hosted by the Contributor SIG?

Action items:
- Make a pull request to add the Contributor SIG to the index https://github.com/spinnaker/governance/blob/master/sig-index.md
- Interview volunteers/contributors and share to raise awareness
- Create questions list

## August 5, 2021
Attendees: Nikema Prophet, Alexander Tyutyunnik, Ige Adetokunbo Temitayo

## May 21, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda:
- Start planning for the Spinnaker Summit session
- Prepare bios, headshots, and description as requested by CDF
- Start creating content
- It's a busy time right now, but in a month or so we can have something to put out

Action items:
- Start planning the Spinnaker Summit meeting
- Nikema: Reach out to Fernando about collaborating on documentation.(Due May 21)
- Nikema: Email Jennifer Crowley to ask that she include Ige as a speaker and co-lead for the SIG (Due May 21)
- Ige, Nikema: Finish bio and provide headshots
- Nikema: Will email Ige with summit bio and session description draft by Friday May 21

## May 7, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Next Actions:
- We need to discuss and plan for our Spinnaker Summit presentation (June 22, 10:30am EDT)
- Nikema wants to try a meeting over Slack. We can try it with Zoom to start and decide if it's worth keeping.
- Take a step back with Spinnaker.io and get a final design approved before coding. This will allow for better documentation and collaboration
- Nikema: Reach out to Fernando about collaboration on EKS guide

## April 15, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Spinnaker Summit - June 22-24, 2021
- Co-located with CD Con

Ige: Working on an installation guide for Spinnaker on EKS
Nikema: Check and see if we can collaborate with Armory. Invite Fernando to SIG channel

Next Actions:
- Nikema: Finish up with website, possibly ask for help from the community
- Ige, Nikema: Attend CDF SIG Best Practices meeting
- Ige: Will push progress on getting started documentation

## April 1, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Justin Schuhmann

Notes:
- Documenting getting started with Spinnaker that is accessibile asychronously
- Ige and Justin will sync on documentation
- We could reach out to Fernando and Cameron from Armory and ask them to share their methods for getting started
- Armory community team and the Spinnaker docs SIG are working on the spinnaker.io website refresh
- Nikema is working to get editor access to the community blog
- Nikema attended the SIG lead meeting and it didn't take place

Action Items:
- Ige: will look over documentation again
- Nikema: will shift focus to work on the Spinnaker website

## March 18, 2021
- No one showed up for this meeting, so it was canceled.

## March 4, 2021
- Motivations:
- barrier to entry is high- difficult for folks to get started in Spinnaker
- wants to make it easier for folks to find docs, work on Spinnaker
- sees opportunity to add value
- Challenges:
- Action not taken after SIG approval
- Pull request approvals lag around for a really long time and issues/PRs sit around
- Folks want to contribute but they feel worried when they don't get responses. They want to add value but don't know how to.
- Goal after last meeting was to reach out to people who had submitted issues or PRs
- Ige reached out to 3 people. Connected with member of Azure SIG (Justin! WELCOME) who has not heard back on his pull requests.
- Have been added to the SIG Leads channel! Can make some noise there. Can address concerns there.

- Feedback from Justin:
- Make this a better experience for contributors and new contributors. This SIG needs to have the information before it can be passed along to the community.
- The amount of time it takes to get started is too long. There is not good doc on
- Needs: doc for getting spun up, doc for contributing. It took 3 months to have an environment set up to test. 6 months to submit a PR.
- New contributor - how to set up Spinnaker locally:
- Minnaker guide from SGD: https://github.com/armory/minnaker/blob/master/guides/setup-dev-environment.md

- There need to be a couple different methods
- Opportunity for better documentation. The SIGs are public information. Can someone create better documentation of the SIGs and what they do.
- We are pausing Outreach until we have more to say and a better "map" of how the project works.

Action Items:
- Nikema - reach out to Tracy Miranda at CDF
- Ige - run through this guide: https://github.com/armory/minnaker/blob/master/guides/setup-dev-environment.md and validate the steps
- Roz - start conversation with Lou Groshek on spinnaker.io
- Nikema - ask in SIG Leads channel about being added to the GH organization to see collaborators

## February 18, 2021

- Questions and Concerns: How can we start contributing in the community?
- How can we collaborate with other SIGs?
- Roz send intros to leads and active folks in different SIGs
- Question to answer: What is our first objective when contacting SIG folks?
- Come up with a format for engaging contributors who have contributed to any Spinnaker project.
- Mailing List, to help Send out messages to contributors and watchers?
- Need to have a plan. Need to polish things up to show there is something happening.
- Good documentation so everyone in an enterprise implementation can be on the same page. Articles etc will add value.
- Onboarding Document for the SIG - document our mode of engagement so that
- Invitation to write content and be featured on community channels
- Outreach and inviting people to attend these meetings, to have more collaborators.
- Sending messages to people who might be interested in getting engaged with this.
- Set a goal - template for responding to PRs that come in
- We could be doing work off to the side of this community that has little to no impact
- Problem: we don't have the permissions to actually see who had leadership roles in the community
- CD Foundation should be facilitating shared equitable access to project resources and can advise on governance best practices re: rungs for "earning" access to OSS assets
- Can we set a target of how many people to reach out to?
- Minimum of 5 a week? Point is just to reach out.

### Working Session

#### Triggered on PR
Send contributor a message:

Thank you for creating this pull request. We appreciate it. We recently started a Contributor Experience SIG for Spinnaker. You can read more on the [community blog](https://blog.spinnaker.io/in-search-of-a-delightful-spinnaker-contributor-experience-99141567c0a4) and in our (charter)[https://github.com/spinnaker/governance/blob/master/sig-contributor-experience/charter.md]. You are always welcome to join us in our Slack channel [https://spinnakerteam.slack.com/archives/C01BL8MCLA2].

Event invitation [something about removing barrier to entry for Spinnaker]

#### Triggered on Issue
Thank you for creating this issue. We appreciate it. We recently started a Contributor Experience SIG for Spinnaker. You can read more on the [community blog](https://blog.spinnaker.io/in-search-of-a-delightful-spinnaker-contributor-experience-99141567c0a4) and in our (charter)[https://github.com/spinnaker/governance/blob/master/sig-contributor-experience/charter.md]. You are always welcome to join us in our Slack channel [https://spinnakerteam.slack.com/archives/C01BL8MCLA2].

## February, 4 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda:
- Review progress from the last two weeks
- Nikema: Let's make plans for what tasks we want to complete before our next meeting

- Ige: Communications
- Format for messages to contributors
- Link to newsletters, articles, governance repo
- We need to start engaging with contributors
- Write articles on the YouTube videos
- Documentation for Spinnaker
- We have a lot of opportunities. We are headed in the right direction
- Need to move faster
- Ige: Create our own documentation
- Ways of working as a contributor
- Ways of working for us as co-leads

- Ige: Check on newsletter update

Next Steps:
- Nikema: By next meeting make progress on newsletter
- Nikema: I will start a document and share with Ige today.
- Ige: We can look for people to talk about plugin development (experts from Armory) tutorial, easy to learn. Nikema will check with Armory crew to see if anyone is interested
- Connect with other SIGs for collaboration

## January 21, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda:

* Spinnaker Summit 2020 videos - content creation
* Spinnaker Summit Playlist link: https://youtube.com/playlist?list=PL4yLrwUObNku4sn3eUScl_0GzC5HnYARf
* Spinnaker.Live Playlist link: https://youtube.com/playlist?list=PL4yLrwUObNkvO80Bjln8_DJXxQNSYrtEs
* Anyone who wants to write Spinnaker content and be featured in the blog can watch one of these videos and create a post about it
* Good thing to add to contributing section of Spinnaker.io. This kind of thing was being done by the Docs SIG kind of but makes more sense for CX SIG.

* Nikema is setting up Slack channel reminder for this meeting
* Took a really long time for the meeting PR to be merged!
* Review of contributor documentation on Spinnaker.io and the ongoing project to consolidate contributor documentation
* Roz tag Ige & Nikema on PRs going forward
* Gatsby.js is great for documentation and has a cool community
* Gamification app for contributors
* Stalled - question: when we do have people making non-PR contribution would these be tracked
* What's the plan to represent them? Some info here: https://github.com/ExitoLab/spinnaker_gamification_app/blob/master/docs/features-apis.md#feature--apis
* Will use user-generated links and hope to have page preview incorporated
* Slack Notifications:
* Slack token for integration between GitHub Actions and Slack
* try https://github.com/marketplace/actions/slack-notify ?
* Ige found: https://github.com/marketplace/actions/send-message-to-slack
* Planning to try this this week.
* May need some help getting a token, and to add the action
* Need to do a PR to add the action?
* Nikema: you may be able to just subscribe to the repos that you want to get notified in Slack, since Github is already authenticated.
* Use the /Github command in Slack
* Testing subscription to a personal repo now
* Result: may need an Approver on the Spinnaker org in Github to approve. Test file showed up on push.
* Need someone to be logged into Slack and subscribe and be logged in. Or use token?
* Prior art: archived GitHub stream.
* IT WORKED
* Any time there is a Pull request, we would get a notification in a private Slack channel
* Has noticed a poor response to pull requests. People need these responses and acknowledgement
* Is there an SLA for Pull Request review?
* probably better data on this in GitHub via APIs than in DevStats

Next Steps:

- Ige: We should introduce ourselves to the other SIGs in preparation for future collaboration
- Ige: Ask Roz about next steps for creating newsletter
- Start content creation, choose a cadence ()
-

## January 7, 2021
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda:

- Happy new year!
- Review last meeting's items
- Ige: Saw an GitHub integration that we can use for Slack.
- Have a slack channel where the GitHub notifications will land
- Ige: Can't stay long, but able to give a quick update.
- Nikema: Made a [pull request](https://github.com/spinnaker/spinnaker/pull/6266) to update the outdated issue template on Spinnaker/Spinnaker.
- Nikema: Commented two days ago to request approval for Ige's [pull/208 (Create the SIG folder)](https://github.com/spinnaker/governance/pull/208)

Next Steps:

Nikema: Plan for content creation, community outreach (invite people to meetings?)

Unfinished from last meeting
TODO:
- Set up newsletter

## December 17, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Rosalind Benoit

- Reviewing draft of blog post about Ige & plugin
- README and new directory PR are in progress
- Getting meetings scheduled
- Adding our meeting invites to the "official" SIG calendar
- Need to reach out to a release manager or Netflixer about starting a mailing list

Project idea:
- Update/add documentation around being added to the SIG calendar

TODO:
- Set up newsletter

## December 10, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Rosalind Benoit

SIG is approved!

Next steps:
- decide on official meeting time and frequency
- figure out how to incorporate the charter (extent of linking, etc.)
- review README draft and add missing info
- create a new pull request to spinnaker/governance to add a folder containing the Contributor Experience SIG materials
- figure out how to get onto the SIG calendar
- investigate SIG mailing list stuff

Notes:
- Ige: wants to identify what work we are going to do first (according to goals)
- Let's meet biweekly
- Let's rotate times so that people in different time zones are trading on evening vs. morning.
- 9 or 10 PM works for Ige, Nikema's days don't start until 9 AM
- Friday AM/Thursday PM once a month and flip flop for the alternate
- What we're doing first:
- Get community buy-in
- Nikema's intro blog post (done)
- Blog post featuring Ige re: Plugins (Nikema & Roz to-do)
- Get meeting time and governance artifacts squared away (Ige to-do)
- change SIG channel name (done)

- Celebrate and recognize contributors
- Next steps: Nikema to ask K8S CX SIG to share their processes, and Ige to start researching

- Ideas:
- mentoring (reference: https://github.com/spinnaker/spinnaker/issues/4953)
- new contributor workshops
- set up Slack automation around GH events
- talk to CDF first or get Adam/Rob assist as a one-off?
- K8S SIG is very open, so if she asks someone will help
- Marky's advice was that full automation is problematic, so notifications with human-driven processes may work better
- Can we set up alerts to let us know when PRs come in?

## December 3, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Rosalind Benoit,

We only have on pending approval left from @plumpy!

- Possible tasks to work on pending SIG approval
- define goals
- write a post to introduce ourselves
- list of ideas around automation
- actions around welcoming/congratulating new contributors

## SIG goals (what can we work on now to move the needle)
- Celebrate and recognize new and existing contributors
- Create reccommended processes for issues and PRs
- Get community buy-in
- Introduce ourselves and the SIG in a blog post

## Quick Wins
- Different blog posts on Spinnaker
- simple
- consistent (weekly cadence?)
- challenges/problems
- start conversations
- Weekly posts
- Short biographies (draft due date: Monday, December 7)
- Why are you passionate about this?
- What do we hope to accomplish

## October 29, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Rosalind Benoit, Kuti Olaribigbe, Augusta Verbickas

Notes:
- Was it a good idea to copy so much from the Kubernetes charter? Rather than follow what they are have already done, can we do a better description of what we want to do?
- Can we give an example of onboarding a SIG ?
- Good question - gave example of inviting a SIG to "onboard" to using enablement that helps them to follow a best practice, such as recording SIG meetings and uploading them to YouTube, or using automation to send out emails requesting agenda items prior to meetings

- We went through a number of requested changes

Next Steps:
- Add language to "how this SIG interacts with other SIGs." - also look for a place to explicitly put the thing about onboarding/suggesting/opt-in:
- ideas: make this stuff a new section inside of Projects & services or include a few clearer words about communication methods:
- Help SIGs with being as transparent and open as possible through creating best practices, guidelines, and general administration of YouTube, Zoom, and our mailing lists where applicable
- Document and assist SIGs/WG Chairs and Technical Leads with organizational management operations

- Rosalind: reach out to Tracy M about CDF access/ownership of shared tools and best practices
- Rosalind: reach out to Marky about GitHub mgmt stuff to consult
- Nikema: accept suggested changes and look for any low-hanging fruit convos to resolve
- Roz & Nikema talk offline about next meeting timing and then Nikema to follow up with Ige to schedule

## October 15, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Rosalind Benoit

Agenda: Finalize charter, start prioritizing deliverables, check progress metrics/KPIs

### Notes:
Worked on finalizing charter to get that done. Outstanding work: add parenthetical links. Then submit.

Next steps:
- finish charter
- Roz schedule open meeting during Gardening
- work on a roadmap, and start prioritizing deliverables

## October 13, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo

Agenda: Set KPIs based on the objectives identified in last meeting

### Questions:
- How do we recognize new contributors?
- Are we monitoring issues, pull requests?

### Action items:
- Create an onboarding guide for new contributors
- Decide on meeting cadence. How often do we hold meetings?
- Update charter document to reflect the additional goals and KPI - [charter PR](https://github.com/spinnaker/governance/pull/182/files?short_path=9d0b963#diff-9d0b9636a86ecc25c1b1d05d3d014d319b63f5c4170a50260558f0c26ef3df9e)

## What are our main goals and objectives?

### Pull Requests

Have GitHub bot post to a slack channel every time a PR is opened

Metrics:
- How long have pull requests been opened?
- PRs should be monitored, responded to

### Spinnaker Getting Started Articles

Target folks from Jenkins

Metrics:
- Number of articles per month

### Welcoming new contributors
- Create a system where real people reach out to new contributors
- New Contributor: Create a robot that send a message to administrator when a new contributor commits for the first time.
- Administrators: Administrators will reach out to new contributors privately
- Make an announcement on slack when a new contributor commits


Ige: Let's ask Marky how they automated, so we can do the same

Metrics:
- Number of people we reach out to (quarterly, monthly?)
- See if reaching out to more people leads to more engagement
-

### What is missing from CX?

###
Ige:
- Always wanted to contribute to open source. People are looking for opportunities to contribute and need information about how.
-
Nikema:
- No clearly defined way to find a starting point for contributors. Would like to see examples of code and non-code contributions I can make
- Is anyone here? Will I be noticed and welcomed in?

### Create an ambassador/champions program (not urgent)
- Outreach to the Spinnaker community
- Incentivize content creation
- Tutorials and Articles (getting started documentation needed)
- Share stories of Spinnaker Success

## How will we measure success?

## October 8, 2020
Attendees: Nikema Prophet, Ige Adetokunbo Temitayo, Marky Jackson, Rosalind Benoit

Goal: make people feel good!

- Pull request is in progress in Nikema’s fork of the governance repo:
- https://github.com/spinnaker/governance/blob/10722d752fb14e3d9b112226ac2ea72b4f62bfbd/cx-sig-charter-draft.md
- Spinnaker saves folks who are coming from Jenkins a lot of time!
- Ige’s goals with the SIG:
- Help people understand how to use Spinnaker correctly/according to best practices
- Training?
- Creating articles for people to use to get familiar with Spinnaker
- It’s so painful when you’re trying
- Nikema’s passion:
- Seeing the barriers come down
- General “Nikema’s life in tech” goal! Wants to see more inclusion across the board
- There are a lot of barriers that N faced as a person coming into these communities that she doesn’t want to see other people having to deal with
- Every part should be available to everyone
- That includes helping out with foundational things like GitHub as well
- Creating a clear pathway to getting started
- Welcoming new contributors
- Low hanging fruit - GitHub Action with a congratulatory message
- Robot messages may not work per K8S experience?
- Instead create automation that notifies humans to reach out on Slack
- Risk: no one wants their confidence blown by a lecturing robot, LOL
- Honoring all kinds of contributions - outreach, content
- Interested in starting a champions/ambassador program to get the wider community involved and raise awareness of Spinnaker
- Anyone who takes the time to contribute should know that they are noticed and wanted
- Subprojects in the K8S CX SIG:
- Group mentoring, 1:1 mentoring, and conference mentoring
- Show people how to use K8S - this is part of their role but they don’t publicize it that much
- Getting people to the SIGs is a huge part of creating a clear pathway
- There is NOT enough content that allows folks to understand how to get started
- Particularly for Jenkins users, there isn’t a full understanding of how Jenkins & Spinnaker work together - Jenkins can be CD but that is painful. So, when people find Spinnaker for the first time it’s a big deal