-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metric Idea: Planning metric #98
Comments
Matt G mentioned the https://www.openchainproject.org/ as related. This is for vendors who can get a Conformance Badge. The OpenChain metric is discussed in the Risk WG. -- maybe above proposal is already covered by this, discuss with Risk WG? |
@vinodkahuja do you have thoughts on how to move this forward? |
@germonprez my initial thought was to check whether an open source project has a planning document or not. Planning documents can be in various forms like our CHAOSS planning document of metric or AGL Road map. These documents guide the activities performed in these open source projects and work is done systematically. Though new work ideas come in random but still work is executed in a planned fashion following a defined process. |
Okay. I've labeled it as a metric idea. The idea seems difficult to determine but that shouldn't preclude taking a closer look. Yes, if you want to create a template and put it in the spreadsheet, that would be great. |
Goal is to evaluate whether open source project has systematic plan for work they do or they just do on ad hoc basis. For example some projects have plans and goal and they develop software and add features as planned in their planning document. As with corporate involvement many open source are performing very planned actives. Where as other open source projects just adding features on ad hoc basis as and when need arises without any formal planning.
This metric can track the planning document of an open source project.
Reference:
Fitzgerald, B. 2006. The Transformation of Open Source Software. MIS Quarterly. 30(3) 587-598.
The text was updated successfully, but these errors were encountered: