A README.md seems like a great place for this.

https://github.com/servo/servo/wiki/Tag-label-names-and-definitions now contains content. It would be great to allow people to understand the tags they read on this page by linking to it somehow.

I think it's better to exclude easy issues with S-blocked-on-external label. New contributors can get confused and start to work on it before it can be fixed.

Make Servo Starters adapt to different screen sizes (on my phone it's a small version of the view I see on desktop).

I was also thinking of push notifications for alerts on new issues. Any thoughts?

It looks silly, otherwise.

Specifically, some visitors will want to only see the issues marked "Good first PR", and others will only want to see the issues not marked "Good first PR". We should support this.

Isolating the ones that require python vs. rust would be a good start.

See here:

@mfeckie presumably started using a JS linter in #14. We should enforce that for all PRs using Travis. Could you elaborate on the tools, @mfeckie?

Some sort of explanatory text? Some text beside each one say "X days since last comment"?

Due to white text on a white background e.g.

This seems intentional due to https://github.com/servo/servo-starters/blob/gh-pages/site.js#L104, but I thought I'd point it out anyway.

I'd like to add https://github.com/rust-lang-nursery/rustfmt/ to this (to infuse more new contributors into rustfmt). However, it uses a different tagging system (easy instead of E-easy), and isn't under the servo org.

As it stands this app searches for all appropriately tagged issues under the servo org, and sorts them.

We should make it so that besides doing this, you can also add repos in other orgs and specify what their easy label is.

It would be interesting to see how many visitors the page gets, and how many issue links are clicked.

This would let us start surfacing issues from auxiliary repositories, which would be great!

This might just be a personal problem, so feel free to close this, but whereas the "Good first PR" tag sent me in the right direction, I wasn't sure what to make of the "Mentored" tag. I thought maybe there was a mentorship process that those were a part of, but it sounds like that's not the case.

I found #1, but I'm not sure where the terminology originally comes from.

They're currently designed for power users and ordering concerns. We can do translations like this:

• A-foo => "area: foo"
• E-easy => "good first PR" (maybe even put a friendly star next to the issue)
• E-less-easy => "mentored"
• L-foo => "language: foo"
• B-foo-bar => "foo bar"
• S-foo-bar => "status: foo bar"
• I-foo => "category: foo" (not thrilled with this one; we may want to just ignore I- labels)
• C-foo-bar => "status: foo bar" (whee organizational duplication)
• P-foo => "platform: foo"

Now that servo-starters have multi-repo support, this issue's description should read "servo-starters #21" instead of just "#21" in the brackets. It would also be nice for the repo name and issue number to all be part of the link to the issue, since single-character links like low numbered issues can be slightly difficult to click.

It's hard to find the relationship between the rendered page and this repository.

Issues like servo/servo#6888 appear there even thought there's been activity quite recently.

I noticed a few issues I am actively working on are labelled as "Potentially Open Issues" based on the issue's post last message. However, mine are seen to be more active in the PR. I was thinking it would be great to take this into consideration. Perhaps @highfive can add a tag to an issue saying PR submitted? (this could also help the Servo team sort and track the progress issues more easily)