Re:GitHub user sends notification to 400k users
by throwaway892238 on Sunday June 05, 2022 @12:07AM
(#31627918)
Creating a team with 400,000 users is antisocial. GitHub teams, and all their inter-related features, are built around a small group of people collaborating together on code. GitHub teams are not intended solely to grant access to source code after signing a EULA. Making a team with 400K users is just a bad idea and this problem was waiting to happen. Unreal needs to find a different solution for what they want.
Re:GitHub user sends notification to 400k users
by Gigachad on Sunday June 05, 2022 @01:10AM
(#31628213)
What other solution? What tools does Github provide to give access to a private repo without creating a namespace which can be pinged? It seems like exactly the use teams were created for just on a scale not seen before. The answer would be Github adding a feature to mark a team as semi public and remove the ability to tag it.
Re:GitHub user sends notification to 400k users
by iuri1 on Sunday June 05, 2022 @01:29PM
(#31633040)
They will probably get a special treatment from Github and Github's code will get an unnecessary `if` clause for the special cases (right now probably only the epic one).
Re:GitHub user sends notification to 400k users
by Ansil849 on Saturday June 04, 2022 @11:40PM
(#31627796)
> Sending email notifications to 400,000 users for unimportant things is antisocial.
What about requiring people to join a specific team to access the source for no apparent reason? In other words, how are the conditions which led to the creation of this inflated team not antisocial as well?
I don't think anyone sits down and thinks the intentional behaviour should be "we should make it easy for someone to send a notification email to 400,000 people". That would clearly be annoying.
I think the behaviour is accidental, arising from "notifying all people in a team is useful".