search

AWiderDotNET / AWiderDotNet

An attempt to foster more involvement in the .NET OSS world. This repo is for discussions and features surrounding the effort. See http://github.com/awiderdotnet/awiderdotnet.github.io for the web site itself.
MIT License
17 stars 0 forks source link

Potential Use Case: The .NET OSS Maturity Model #5

Open SeanKilleen opened 8 years ago

SeanKilleen commented 8 years ago

What I'm thinking is, this could be a guide to companies to help figure out where they are on the scale of being good OSS citizens, and how to get to the next step.

We'd need to define steps along the maturity model (e.g. level 0 -- unhealthy fear of OSS, OSS banned, etc.) up through level x (5? -- policy in place that encourages developers to give back, donates to OSS, open-sources their own helpful libraries, etc.)

I think this could be a great exercise. The power here would be in drafting something that helps us clarify examples of what immature and mature dev shops look like in regards to OSS, and in presenting concrete next steps for companies at a given stage to take so that they can move in the right direction over time.

Thoughts?

SeanKilleen commented 8 years ago

Companies often think about and are concerned with where they are on CMMI (capability maturity models), but essentially what I'm thinking about is constructing an OSS Maturity Model -- an OSSMI, essentially. Though we'd have to start smaller.

SeanKilleen commented 8 years ago

A quick note here that we'll want to call it something else. Otherwise it might conflict with the OpenSource Maturity Model commonly used around the production of OSS.

What we're looking into is more on the lines of a Contribution Maturity Model for companies -- something that helps them gauge where they are as contributors to the wider open-source community.