- OrgExplorer could show information related to GitHub teams. Here are some suggestions: - [ ] In the network graph, show team nodes as well, besides repo and contributor nodes. An edge between a contributor and a team indicates that the contributor belongs to that team. An edge between a team and a repo indicates that the team has access permissions to the repo. Different permissions (read, triage, write, maintain, admin) should be shown as edges of different styles/colors. - [ ] In the "Repositories" page, the filter should have a dropdown box to select a team, to show only repos for which that team has access. - [ ] In the "Contributors" page, let's have a dropdown box to filter by team as well. - [ ] In the "Analytics" page, , let's have a dropdown box to filter by team as well.
- The dropdown boxes to filter by team should also allow us to select "no team" to show only things that relate to contributors that belong to no team.
- Let's have a new "Pull Requests" page, which should show all open PRs and should allow to filter by repo and by team, and to group by contributor.
- Let's have a new "Issues" page, which should show all open issues and should allow to filter by repo and by team, and to group by contributor.
- OrgExplorer could have a profile page for every contributor, showing in summarized and detailed ways, the activity of that contributor in a specified period of time. Then we could specify, for instance, a time period going from the beginning of the coding period to the end of the coding period, to see all the contributor's activity during GSoC. This profile should be exportable as a markdown file. Contributors could then use this markdown file as a starting point to prepare their final GSoC reports.