Mockup for GitHub integration

[slinna]

Design mockup for the integration

[slinna]

GitHub integration v5.pdf

@TuomasTammi here's the latest mockup. What's new:

• GitHub uses OAuth, ZenHub uses API key
• Pull requests have a pull request icon in Team Status screen
• Checking/unchecking all should work using same checkbox when selecting repositories

[TuomasTammi]

@slinna

• Does the possibility to select multiple repos for one dashboard affect the aggregate charts were planning to have too? We would have aggregation on top of aggregation.
• Users have to give names to dashboards somewhere, so that when they select a source they know what they're selecting

[slinna]

Good points. I'm wondering what should be shown in the 'Sources' tab in GitHub case:

1. Screenful dashboards
2. GitHub repositories
3. Sources tab doesn't exist, user can use filter to select repos

What do you think?

[TuomasTammi]

Hmm.. Let's see

1. Is problematic if we allow users to map several repos to one dashboard: What happens when the same repo is included in two dashboards that are then combined? We'll have duplicate issues. This is the problem with aggregation on top of aggregation.
2. Makes sense if there is 1:1 mapping between dashboards and repos, but even then the user is (conceptually) selecting a dashboard rather than a repo.
3. No obvious problems.

So either we enforce a 1:1 mapping between repos and dashboards and the aggregation works exactly the same way as for the other tools or we don't allow aggregation at all (no sources tab) and the users can do the aggregation when setting up the dashboard.

[TuomasTammi]

From the implementation point-of-view I'd prefer to keep the 1:1 mapping, just to keep things simple and consistent between tools.

[slinna]

@TuomasTammi here's the latest mockup:
GitHub integration v6.pdf