Skip to content
This repository was archived by the owner on Sep 9, 2024. It is now read-only.
This repository was archived by the owner on Sep 9, 2024. It is now read-only.

Sustain Planning - Oct 15, 2019 #26

@coderberry

Description

@coderberry

Attendees

  • Megan
  • Benjamin
  • Justin
  • Eric
  • Pia
  • Gunner
  • Cat

Actionable Items

  • Pia will send save the date to email list
  • Justin will provide website boilerplate
  • GitHub issue for criteria for attendance
  • Email thread for building invite criteria
  • Look for community evangelist
  • Ben will follow up with friends around GitHub|Google involvement

Goals for sustain

  • Which past objectives do we need to continue to aim for?
  • What are new/different objectives for 2020?

Revised Vision & Goals SustainOSS UK 2018 - Google Docs
Sustain 2018 postmortem notes
Sustain Summit 2018 - Participant Input - Google Docs

Most important topics (from participant input):

  • Lift up and document models, strategies and approaches to sustainability of OSS projects, and work toward a more sustainable future for OSS
  • Identify gaps and needs, and prototype ways in which to provide ongoing support and leadership in sustainability practices
  • Overall, map and compare visions for the long term health of free and open software communities around the globe
  • Licensing

Room to fill in documenting (how to fund your projects, etc).

Ideas that came from sustain lacked a place to let them grow with structure. If the past couple of years was an indication, we need to provide more of a structure for projects.

“Bring your sustainability problems” and create teams to workshop them.

If you get to workshop your problem, you commit to a minimum of a blog post. If more, even better. Blog post to appear on the sustainoss website as well.

“Tactical” is better than “Strategic”

Two wave process. 1) Who do we want to invite knowing what we know now? Based on past events, those we’ve met since. 2) when opening up to more, it would ask “Do you have experience to share, skills to contribute or interesting problems to work on?”

Create database of “symptoms” and “solutions”. Create something that is easy to access (maybe Wiki)? Confidentiality must be taken into consideration. Documented evidence of what was discussed.

Template for documentation instead of free notes.

Who do we invite?

Do not create “project pageant” dynamics. Spectrum of criteria for participation will allow us to create a good participant list.

  1. Who do we want to invite knowing what we know now? Based on past events, those we’ve met since.

  2. Ask those invited whom else we should invite. Criteria may include “Do you have experience to share, skills to contribute or interesting problems to work on?”

Individually identify projects that need help with sustainability that provide value to the community as a whole.

Maybe correlate with the projects that will be at FOSDEM.

What do we want to achieve?

  • Holistic around sustainability. Is there a way to take stock at scale to how sustainability is trending and what are the major drivers?

How do we stay all connected publicly?

Discourse? It’s difficult to make it part of our flow. We probably need a community catalyst or gardener. Focusing on the “sustainability hub” is not on anyone’s plate. What is the process? Who is driving it? Contributions are appropriately honored. We need a governance model for collecting, building, sharing and using knowledge.

Owner or process is needed. Someone interested in community catalyst? Decide after event.

Give up on discourse maybe? At next sustain meeting, take a poll of what people are using. Cat prefers mailing lists.

Notes

Confirmed date: Jan 30 in Brussels

Justin working on landing page for website. Up with new date.

Justin working with Elio to create boilerplate to do multiple events. Africa + Gitcoin event as well. Will have something early next week.

Sustain Africa (part of OSS Festival in Legos)
Sustain Web3 in Denver

Pia sent survey for open source companies / CEOs. Survey has been done.

Ben would like others to go over notes and determine what the conclusions are in order to put them into document.

Google location in Brussels? Space isn’t large enough. It’s a no-go.

As we discuss bringing in others to help, be mindful of diversity and inclusion. Can we have balance in gender and other regards when we broaden the group.

Community Evangelist.

Financial support from GitHub, Google? Google is on board.

Perform due diligence to make sure we are flying out people that are not a liability.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions