0.11.09: Difference between revisions

Line 15:

* Bug importing actually, reliably, works. Goal: Fewer than 10% of bugs are stale (>3 days).

** The problem here seems to be that some bug trackers suffer from really high latencies, or maybe just drop packets entirely and we don't time out in a reasonable way.

⚫

* You can add bug trackers to our import entirely from the web UI.

⚫

** The big obstacle here is that the we haven't decided the UI for it. Next step: Asheesh can come up with a coherent, implementable mockup.

⚫

* When you click on "Mentors (149)", we should visually break that number down so that people understand how we calculated it.

⚫

** Suggestion by Michael Stone: Use an infographic. Instead of a number, we can show two visual indicators: one for language, one for project. Can be e.g. signal bars, or "Lots" "a few" "some": <a href="/people/?q=can_mentor%3A%22C%2B%2B%22">Mentors [:::] []</a>

=== Project pages ===

Line 52:

Line 48:

This section contains optional goals that would rule, but aren't strictly part of the milestone.

== Volunteer opportunity finder ==

⚫

* You can add bug trackers to our import entirely from the web UI.

⚫

** The big obstacle here is that the we haven't decided the UI for it. Next step: Asheesh can come up with a coherent, implementable mockup.

⚫

* When you click on "Mentors (149)", we should visually break that number down so that people understand how we calculated it.

⚫

** Suggestion by Michael Stone: Use an infographic. Instead of a number, we can show two visual indicators: one for language, one for project. Can be e.g. signal bars, or "Lots" "a few" "some": <a href="/people/?q=can_mentor%3A%22C%2B%2B%22">Mentors [:::] []</a>