search

dotnet-foundation / ecosystem-growth

Creative Commons Zero v1.0 Universal
21 stars 5 forks source link

Notes for 2021-01-14 #13

Closed terrajobst closed 3 years ago

tomkerkhove commented 3 years ago

Thanks for considering @terrajobst!

tomkerkhove commented 3 years ago

One more question though, I see it's aiming at .NET libraries - How about products built with .NET that are OSS? What if they are related to Azure? Might be out-of-scope but has same issues.

terrajobst commented 3 years ago

How about products built with .NET that are OSS?

That's fair, I believe we certainly have a bias towards libraries in this working group, largely because libraries are bit harder because they become part of somebody else's app. Products or service offerings are a bit easier to control but I believe it's also likely that they have other issues. Maybe it's just me, but I tend to think of "ecosystem" more as "sets of libraries you can use to build apps" rather than "a bunch of offerings you can use" because the latter makes it no longer developer technology specific (i.e. the Node ecosystem vs. the .NET ecosystem) but platform specific (i.e. the Windows ecosystem vs. the macOS ecosystem). And that I'd consider out of scope for this working group.

tomkerkhove commented 3 years ago

In my case it is always about Docker images that people can use in their platforms but never a "product product" but I see what you mean and it's fine.

Thanks for sharing!

terrajobst commented 3 years ago

Curious what others think here @clairernovotny @sbwalker

tomkerkhove commented 3 years ago

Just to give context - I maintain https://promitor.io/ & https://k8s-event-grid-bridge.tomkerkhove.be/ which both extend Azure With .NET.

sbwalker commented 3 years ago

@terrajobst I agree with @tomkerkhove that the survey should not focus solely on "libraries". I personally have never created an open source "library"... projects such as DotNetNuke and Oqtane are comprehensive frameworks that are much broader in scope than libraries. However they still suffer from the same .NET open source challenges.