Damith C. Rajapakse
Damith C. Rajapakse
How about this? * Ramps represent _changes_ (not contribution). Hence, their size matches the number of lines touched (added | edited | deleted) * Contribution bar represents _authorship of lines...
> Don't think git provides edit, we may have to implement our own algorithm for that if that is preferable. We can go with what Git provides. The size of...
Something shorter, like this? `Based on the current sorting order, this item is in the top 15.5%`
> Hi prof @damithc, > > What do you think now? I think it reads better. > > @jbkim1999 I'm OK with this version, although others are welcome to suggest...
> Prof @damithc, what do you think? Let's use the longer version, to be on the safe side. Although it is mostly obvious, I can imagine a few students wondering...
> The reason I appended the help icon is that when the user first launches the report, he/she will encounter the rather unclear percentage label, but because there is a...
> How does this look now? Considering that percentage label is not of a great importance like mentioned in one of the comments, I think it also makes sense not...
> Hi @dcshzj, I wonder if this is still ongoing and if I can attempt it? @dcshzj what do you think?
> Prof @damithc, @eugenepeh , may I confirm if we can create a single ramp chart that captures the work attributed to all virtual authors (as opposed to 1 ramp...
> This is because each group can be merged or unmerged independently. I see. I guess we can optimize e.g., have two parameters `merged` and `unmerged` and use the one...