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

Status: "In review" for commits from a long time #165

Closed
Princu7 opened this issue Oct 16, 2016 · 5 comments
Closed

Status: "In review" for commits from a long time #165

Princu7 opened this issue Oct 16, 2016 · 5 comments

Comments

@Princu7
Copy link

Princu7 commented Oct 16, 2016

I don't know whether this is the appropriate place for this type of queries. So pardon me if it isn't and redirect me to the right place. Anyway, I really like the concept of code curiosity and it has given me the motivation to contribute to the open source.
I have made several commits this month.But most of them are still showing the status "In review" from a very long time(some commits were made almost 10 days ago) and no points have been awarded on them. Also some commits fetch no points which is a little disheartening considering they also required some effort to make.

Here is the screenshot showing the status
screenshot from 2016-10-16 15-41-09

I kindly request someone to please look into this issue. I would also love to know the scoring logic and how points are distributed to the various commits. Thanks for your time.

@gautamrege
Copy link
Member

@Princu7 I shall check why the 5-Oct commits are in "in review". Thanks for the ticket.

The automated scoring algorithm is being improved as we learn more code patterns and usage. So, hang in there - it will start getting better!

@Princu7
Copy link
Author

Princu7 commented Oct 16, 2016

@gautamrege Thank you so much for your time. Are there any docs which state how the scoring is done currently? I tried to read the source code but was not successful as I am unfamiliar with ruby. I would love to suggest an idea or two.

@prasadsurase
Copy link
Contributor

@Princu7 The whenever schedule file calls a rake task daily which triggers autoscoring. The task calls ScoringJob. All the scoring logic is in ScoringEngine. We use bugspot as a major component for scoring. You can refer this issue to discuss about changes needed in scoring logic.

@Shwetakale
Copy link
Contributor

This might be because of this issue .

@gautamrege
Copy link
Member

@Shwetakale No - this is not related.

@Princu7 - please check the issue is resolved. I think there may be a clash between parallel 'git pull'. we are seeing if that is indeed the case and will resolve.

re-open is you still see issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants