-
Notifications
You must be signed in to change notification settings - Fork 61
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
How to add the Metrics into Manuscripts #50
Comments
In parallel to work with the notebooks, I think we should start studying which changes Manuscripts would need, and the schema we would use in it. For now, I think we could design a report which, if the If you agree with this simple specification, we could start looking at the code that needs to be changed, and how to change it. |
@jgbarah, I am a little confused. Why do we need to have a I was thinking of dividing the report into 4 parts, each one corresponding to Diversity-Inclusion, GMD, Risk and Value. Can you please expand on the |
Currently, Manuscripts has some functionality (produces a certain kind of report). The idea of the --chaoss option is for including, optionally, in addition to that functionality, the CHAOSS metrics. Which for now will be the GMD metrics. The main reason is that Manuscripts already has users, so that I would prefer not to break current functionality (the kind of report it produces now). If users don't include Is it more clear now? |
@jgbarah, @valeriocos: I've made some changes to manuscripts, specifically What do you think? |
As per the discussion with Jesus, this ticket is about how to add code for Metrics into Manuscripts.
Branches! It was so obvious, that I didn't think of it at all.
We can start with writing dirty code in Jupyter-notebooks and structuring the code there and then once it gets finalised, we can add clean code into the Master branch of Manuscripts so that the commit history has only clean code and definite updates on the project.
When we want to add a functionality into Manuscripts, a new issue can be created and that can be linked back to this main issue.
Other ideas are welcome! :D
@jgbarah @valeriocos @acs
The text was updated successfully, but these errors were encountered: