Discussion for: Using the "Home" repo for issue management of other repos

[Eilon]

This is a discussion issue for: aspnet/Announcements#283

[kevinchalet]

Terrible idea, IMHO, as it will make the Home repo so noisy that virtually nobody will want to watch it.

Having tickets opened on dedicated repos (e.g aspnet/Security) allows receiving notifications for topics you're potentially interested in. With your new approach, it's no longer possible...

[natemcmaster]

Does anyone know if there is a good way to filter GitHub notifications by tags or by comments from specific users or teams? For me, GitHub notifications are already useless, even before this change.

[Eilon]

@PinpointTownes thanks for the feedback, we're aware of that limitation and we hope to come up with some solutions to that. For example, we can create GitHub teams and let anyone (even non-ASP.NET/EF team members) add themselves to the teams, and a bot would notify all team members of new issues in that area.

We started out with some of the lower-trafficked repos first because we figured it would be less of a problem, while we figure out how to overcome the limitations.

[davidpeden3]

Couldn't agree more. This change is a huge mistake. And the bot that migrated the issues doesn't update pull request links correctly. See https://github.com/aspnet/Home/issues/2496 (second to last comment containing a link to #46 which should've pointed to aspnet/Proxy#46).

[Eilon]

@davidpeden3 ah yes that is indeed not intended. Granted, that type of issue has already been problematic before because even today we often have to move issues between repos and the links can get broken. I'll try to fix this in the issue mover.

[kevinchalet]

@Eilon that sounds super convoluted.

BTW, is there even a pro for adopting this change (e.g does it make triage easier?) or is it one of those arbitrary decisions you guys like to take from time to time? 😅

[davidpeden3]

@Eilon thank you

[Eilon]

@PinpointTownes we wanted to make things clearer with:

1. Where to log bugs? Answer: Home repo. (Anyone who has followed the repos here has seen us move bugs back and forth anyway.)
2. Where to find bugs? Answer: Home repo. (Even for us, trying to find where a bug was logged is a tedious chore.)
3. Easier for the team to triage bugs, including consistency with milestones and labels.
4. Ability to use GitHub Projects that cover issues from multiple repos. Today GitHub projects can be public only if they are within a repo. We want to share with everyone our overall planning and linking multiple issues from multiple repos and that isn't possible. By consolidation issues in one issue tracker, we can share more about our future plans.

[tugberkugurlu]

Ability to use GitHub Projects that cover issues from multiple repos.

I believe you can already do that across repos with org level project boards, no? https://github.com/blog/2272-introducing-projects-for-organizations

[Eilon]

@tugberkugurlu unfortunately that doesn't work for non-members. Only members of the org can see org-level projects.

[Zoxive]

So when I want to open an Issue who is going to triage all new issues to assign the right tags so the right team can be notified of them? It seems like an added delay/another user in the process.

Also the issue template for this repo still says

To address your issues more quickly, please open the issue in the most appropriate repository. 
These are some of the most common repos:
...

Other than that, I like the idea of one location so we can see combined milestones/etc.