2020-12-03 1st meeting

Attendees

The Microsoft document

The Microsoft document doesn't make it clear whether we're trying to grow the set of trusted libraries (regardless of OSS) or whether it's OSS
Our thinking in this working group is primarily focused around OSS because that's the 99% of packages on NuGet and is what drives the .NET ecosystem
Jeremy: Guidance, examples: how do you use the set of libraries (e.g. NHibernate vs EF vs Dapper)
Shaun: More choices also make things harder
Eriawan: specific quality issues on nuget
- Write metadata include (e.g. properly declaring references, no dangling references, .NET SDK versions)
- P/Invokes that tie an API to Windows
- Compat rules
Folks would like to see a revival of the maturity ladder, BUT:
- Not as finished gospel
- With more perspective & empathy for library developer
Claire
- .NET Foundation can host documentation, akin to docs.microsoft.com
- This could, and should, provide an interactive running experience

Interests

Interested in NuGet feature
Grow the set of trusted libraries that aren’t controlled by Microsoft
- Shaun: Sustainability/avoid maintainer burnout
3rd party experiences can be as good as 1st party experiences
- Jeremy: Guidance on how to use the library
- Tanner
- John
Developers have access to guidance & tools that supports them in building cross-platform packages
- Eriawan: NuGet validation
- Tanner:
Customer Development
- Ken: Survey design, session design
Next steps
- Immo: Present feature work we have in mind some areas in the doc
- Immo: Add README.md, the doc, goals, members, meeting notes
- Eric: private deps/shading
- Claire: supply chain presentation