TODO Guide: OSS Sponsorship

[ashleywolf]

Creating an issue to track a new guide for OSPOs on sponsoring open source. We'd like to produce an artifact that makes it easier for organizations to get funding and have decision making framework to sponsor OSS projects/organizations/foundations.

We started a draft in this Google doc. We invite you to add your thoughts and ideas to the doc! Around mid-February we will review the contents of the doc again.

Topics include:

• Digging into your dependencies
• Funding types
• Motivations
• Sustainability

[anajsana]

This is great @ashleywolf ! thank you so much 👍 I have four questions for this guide:

Around mid-February we will review the contents of the doc again

1. Do you want to schedule sync guide Zoom calls with the guide participants to review the progress?

We'd like to produce an artifact that makes it easier for organizations to get funding and have decision making framework to sponsor OSS projects/organizations/foundations.

2. Do you want TODO to actively look for potential contributors to the guide promoting this issue within the main communication channels (slack, mailing lists, social media)?

We started a draft in this Google doc. We invite you to add your thoughts and ideas to the doc!

3. I love g.docs to work on content. However (and IMHO), sometimes G.docs limits collaboration for those people who can't access google tooling. We can either keep the g.doc and see if someone complains OR I could open a PR to work on this guide using a .md file at todogroup.org/guides and add your initial content (to work directly there) 🤔 Which option works best?

4. Does it make sense to add in the issue description the participants (@gyehuda @DuaneOBrien @benmont and @ashleywolf ) that are willing to contribute to this guide (and if anyone else shows interest, give them the right permissions to contribute and add them to the list)?

[jsmanrique]

It sounds like an interesting approach. I have requested access to the doc. Thank you @ashleywolf

[dviner]

I requested access to the doc. One quick observation is that there are two pretty different topics here - finding dependencies versus supporting/sponsoring projects. Finding dependencies is tied in with a bunch of other efforts across the ecosystem (e.g., gitbom, SBOM, dependency graphs, etc). It may be useful for this doc to simply point to those other efforts for how to discover dependencies. In contrast, supporting projects is something that isn't clearly dealt with in other areas, to my knowledge. So I'd focus on that aspect.

[ashleywolf]

Added all the folks that requested. Feel free to add content in - let's start with a 🧠 dump and then we can edit later.

[ashleywolf]

Thank you to @jzb who is contributing to this guide during the TODO Work Day session today!