You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, it'd be great for http://rusty-dash.com/fcp to list each subteam with its open FCP proposals underneath -- ideally, with a "days since proposed" counter which acts as the sort order. That will make it easier for teams to keep on top of stragglers.
Conversely, the list of team members is not so important to have here.
What I would like is a list of the FCPs for each team, along with a matrix showing who has yet to respond, so I can nag them. =)
Should team members just be expected to create a URL with their GitHub username and bookmark it? I'm fine with that, want to double check everyone else is.
The text was updated successfully, but these errors were encountered:
It's also fine to keep the current team member link list somewhere -- I think the main point is that we're interested in seeing a more "item-oriented" global dashboard.
Some way to view the outstanding motion-to-FCPs for each team is high priority.
This can be very simple, e.g. on the main /fcp page, have something like:
Lang team
RFC 1234: waiting for foo, bar, and baz
PR 567: waiting on bar, quux
Libs team
RFC 555: waiting for quibble, baz
etc.
We're working hard to get everybody checking their dashboards etc, but this kind of overview is essential for team leaders to make sure things are progressing.
Note: I'm very short on time so I haven't implemented anything for the cases where everyone has marked as reviewed but there are still outstanding concerns. The FCPs page links to the rfcbot comment, so I think it shouldn't be too confusing but I'd like to fix this once I have time to work on the bot again.
@aturon, #61 (comment):
and @nikomatsakis, #61 (comment):
Should team members just be expected to create a URL with their GitHub username and bookmark it? I'm fine with that, want to double check everyone else is.
The text was updated successfully, but these errors were encountered: