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

Release Candidate Comments (Code Changes) #280

Closed
klumb opened this issue Dec 30, 2019 · 5 comments
Closed

Release Candidate Comments (Code Changes) #280

klumb opened this issue Dec 30, 2019 · 5 comments
Assignees

Comments

@klumb
Copy link
Member

@klumb klumb commented Dec 30, 2019

This issue was created to collect comments about the upcoming metrics release.

This thread is for comments about Code Changes

GitHub location: https://github.com/chaoss/wg-evolution/blob/master/metrics/Code_Changes.md

See all release candidates of metrics are at:
https://chaoss.community/metrics-202001/

@xavierbol

This comment has been minimized.

Copy link

@xavierbol xavierbol commented Jan 9, 2020

Hello everyone,

For this release, I agree about the existing, but I think we could use the message of commits.
For me, this message can contain some important information to analysis the Code Changes into a project.

If in a project, a certain structure is defined to write the message for the commits, then we would have the possibility to classify the commits.
For example, in Odoo, they have a guideline to write the message of theirs commits. They use a system of tags to know if the commit is :

  • [ADD] for adding new modules;
  • [IMP] for improvements;
  • [FIX] for bug fixes;
  • and so on...

I put the link of this guideline.

Thus, I think we can use this information to know how much code changes have in this differents categories and compare the result in the differents categories on a certain period.

I've already done this condition to search a substring into the message of commits and I have made the example for this metric and the one about Code Changes Lines.

I've created a pull request about this for this metric here : #299 and another pull request about Code Changes Lines metric #300

If you are agree, I will add the implementation.

@germonprez

This comment has been minimized.

Copy link
Contributor

@germonprez germonprez commented Jan 13, 2020

"Resources" should be "References"

@germonprez

This comment has been minimized.

Copy link
Contributor

@germonprez germonprez commented Jan 13, 2020

Augur provides this metric both as Code Changes and as Code Changes Lines. Both metrics are available in both the repo and the repo_group metric forms - more on that in the Augur documentation.

The links in this line are leading to some 403 errors

@ccarterlandis ccarterlandis self-assigned this Jan 14, 2020
@klumb

This comment has been minimized.

Copy link
Member Author

@klumb klumb commented Jan 25, 2020

Is this metric ready to go?

@klumb

This comment has been minimized.

Copy link
Member Author

@klumb klumb commented Jan 25, 2020

I am marking this as ready for release and closing. Please reopen if that is not the case.

@klumb klumb closed this Jan 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.