Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With ~100 contributors, I think this section would get too unwieldy, and it's also not necessary to "@" notify each contributor.
I still like the idea of showing some aggregate stats. Could we do something like this instead?
Contributor stats
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about it, but I decided to add it anyway because there is one piece of information that is not readily available anywhere, "in how many chapters a specific member is involved in and in what ways?", which I think is an important thing to know to properly distribute workload.
That's a very good point, I will certainly remove auto-mention feature.
Summarized statistical table is a great idea, but we can perhaps do it in a separate iteration (due to time constraints at my end).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rviscomi I think I have taken care of the issue of getting too unwieldy by hiding the list under a "details" element, so it will be there, but won't bother.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than making the contributors a
<details>
element could you not make each sub-team the<details>
element? So can always see the team counts but can expand for names in a team.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can do it, but I think the current approach is more friendly in some ways (I am open to be convinced otherwise):
It may also depend on how the information is used often, a specific role at a time or a specific person (across rolls) at a time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rviscomi I have added stats table as well. Please have a look at tunetheweb#73 for an example.