Our community team at Microsoft also comprises the Open Source Programs Office (OSPO). Recently we funded 175 #OpenSource organizations and developers representing hundreds of packages in June. This blog post describes what was learned! https://opensource.microsoft.com/blog/2024/06/27/5-things-we-learned-from-sponsoring-a-sampling-of-our-open-source-dependencies/
@shanselman @shanselman re #1, I'd love if you worked with the GUAC project to help build out that kind of tooling for the community more broadly
@shanselman @funnelfiasco How and when to best to translate this currently internal-specific approach that is still prototype to something usable by others is an open question. I’m a big fan of GUAC. It’s one of the obvious choices. One limitation is deps.dev lacks some of the needed metadata about the community developing each source repo that releases a package. A description of our approach for other OSPOs is at https://github.com/microsoft/OSPO/blob/main/bulk-targeted-sponsorship/README.md
@shanselman thank you for sharing, I have not read it yet, but it is a good reference to encourage other companies to do the same!