Skip to content
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

Review of contribution instructions for GQM #36

Open
dellagustin-sap opened this issue Oct 6, 2023 · 2 comments
Open

Review of contribution instructions for GQM #36

dellagustin-sap opened this issue Oct 6, 2023 · 2 comments
Assignees

Comments

@dellagustin-sap
Copy link
Contributor

dellagustin-sap commented Oct 6, 2023

@dellagustin-sap dellagustin-sap self-assigned this Oct 6, 2023
@dellagustin-sap
Copy link
Contributor Author

@rrrutledge I have reviewed the instructions.
What I think is missing is information on how the graph is generated (even if that is a manual process at the moment that is not available to the contributor).
Is it currently a manual process, or is there a script for it somewhere?
Eventually it would be good if the contributor could generate the graph, as a way to validate if the format of the markdown is as expected.

Another comment, even though the contribution instructions are clear, the current structure of the chapter What, When and How to Measure is confusing.
For instance, the Goal-Question-Metric Approach sub-section is separate from the sections Goals using Metrics and Use Goals, Questions, and Metrics.

@jeffabailey
Copy link
Collaborator

@dellagustin-sap

Is it currently a manual process, or is there a script for it somewhere?

Yes, it's a manual process at the moment.

Future state is a script, but that's not done yet. I created a local branch that's parsing the markdown and will eventually build the mermaid graph.

Another comment, even though the contribution instructions are clear, the current structure of the chapter What, When and How to Measure is confusing.

Agreed, I noticed that as well. We'll make sure it all makes cohesive sense.

@rrrutledge rrrutledge moved this to In Progress in ISPO Working Group Oct 6, 2023
rrrutledge added a commit that referenced this issue Oct 6, 2023
@rrrutledge rrrutledge moved this from In Progress to Proposed in ISPO Working Group Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants