Currently, our participant and contributor consolidators are super slow. We actually have this data already available to us when we do the parsing, so why not just add this logic to the parser? Here's what we need:
In CodeReviewParser, for each code review, initialize a new Set of participants and a new Set for contributors.
Refactor the contribution?(txt) method by moving it to the Contributor class. Should be a static method, i.e. def self.contribution? txt
When a new participant is added (i.e. sender of a comment or a message), add this dev id to the participant set. Add it to the contributors set if the text of the message or comment is considered a contribution.
At the end of parsing the code review, dump the participants and contributions to their own CSV files like the others. Add a nil to the "reviews with owner" - this gets updated in the rake run:analyze
Update the loader to dump this data into the table properly
Currently, our participant and contributor consolidators are super slow. We actually have this data already available to us when we do the parsing, so why not just add this logic to the parser? Here's what we need:
CodeReviewParser, for each code review, initialize a new Set of participants and a new Set for contributors.def self.contribution? txtrake run:analyze