1156863 - Executive Dashboards' GitHub repos aren't accessible to everyone--only to owners and metrics team members

Status: NEW

(Cloud Services :: Metrics: Dashboard, defect)

Comment 1

[Ali Almossawi]

Each of the dashboards--plus the landing page--has a private repo on GitHub under the Mozilla organization. The point is to give absolutely anyone viewing the dashboards the ability to see the code, submit PRs and file issues.

As it turns out, only owners and members of the Metrics team on GitHub can currently access those private repos. We've linked to this bug in each dashboard's footer to hopefully preempt any confusion on the part of users who end up seeing a 404 Not Found page when they try to access the repos.

Katie had suggested creating a new team on GitHub and giving it access to the repos. That seems to be the best solution at present, despite the fact that it would involve the tedious task of adding people to the team, one by one.

Comment 2

[Axel Hecht [:Pike]]

Why would the code be confidential, though?

Comment 3

[Ali Almossawi]

No data is ever committed, so the only thing one would learn from looking at the code is which of our products we're tracking, what metrics we consider important and the data files' relative paths. Having that third one be public might make some people nervous.

The topic has come up in the past, and the majority thought it best to keep things private. Considering that the dashboards are accessible to anyone behind LDAP and the tedious process involved in giving people access to the repos, I think that, on balance, it might be a more useful use of energy to make the repos public. But then again, I'm happy to submit to whatever the majority thinks.

Comment 4

[Erik Vold [:erikvold] (please needinfo? me)]

(In reply to Ali Almossawi from comment #3)
> No data is ever committed, so the only thing one would learn from looking at
> the code is which of our products we're tracking, what metrics we consider
> important and the data files' relative paths. Having that third one be
> public might make some people nervous.
> 
> The topic has come up in the past, and the majority thought it best to keep
> things private. Considering that the dashboards are accessible to anyone
> behind LDAP and the tedious process involved in giving people access to the
> repos, I think that, on balance, it might be a more useful use of energy to
> make the repos public. But then again, I'm happy to submit to whatever the
> majority thinks.

+1 on making this repo open.

Comment 5

[Ali Almossawi]

It would appear that this is no longer an issue, now that we can assign the team 'admin-all-org-members' to a project?