Skip to content

Rework FCPs dashboard view to be more generally relevant #90

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

Closed
anp opened this issue Oct 7, 2016 · 3 comments
Closed

Rework FCPs dashboard view to be more generally relevant #90

anp opened this issue Oct 7, 2016 · 3 comments

Comments

@anp
Copy link
Member

anp commented Oct 7, 2016

@aturon, #61 (comment):

Feature request: global dashboard.

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.

and @nikomatsakis, #61 (comment):

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.

@anp anp added the rfcbot label Oct 7, 2016
@aturon
Copy link
Member

aturon commented Oct 7, 2016

I think that's fine, yes.

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.

@aturon
Copy link
Member

aturon commented Oct 22, 2016

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.

@aturon aturon added the P-high label Oct 22, 2016
@anp anp added this to the Adam goes incognito milestone Oct 22, 2016
@anp anp closed this as completed in 527c4ac Nov 2, 2016
@anp
Copy link
Member Author

anp commented Nov 2, 2016

@aturon I'm deploying this now.

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.

anoadragon453 pushed a commit to matrix-org/mscbot that referenced this issue Jul 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants