Currently the ToS doesn’t mention minors which is likely problematic for many countries i.e. US that requires compilance with COPPA https://en.wikipedia.org/wiki/Children%27s_Online_Privacy_Protection_Act
How do you want to handle this situation?
Personally i don’t think we should prevent these from using the service as this service is a great opportunity for them to learn about computer science and programming, but we can’t really store their personal information in database without their guardian’s written permission.
Coudn’t we implement some kind of access token (to make the e-mail not mandatory as that is arguably a personal information depending on the e-mail used) for these scenarios? So that they woudn’t be prevented from submitting merge requests?
If we make the service usable for minors then the content should be regulated appropriately where i generally don’t like policing from the maintainers.
Recommend to implement Code of Conduct mentioning what content is allowed to be public and allow community to assign themself a role that allows the repository to be suspended from public so that if there is something inappropriate that Code of Conduct mentiones the repository would be forced private with option for the maintainers to invite members in their organization to provide view access?
This proposal makes it harder for some projects to present themself to the public so to avoid this we could implement some way that allows specifying i.e two README.md files for the project where one should be adapted for minors (censored nudity, adapted language appropriately, etc..) and the other for accounts that are non-minors which would avoid the requirement to keep the repositories private assuming that only the README file is an issue
For the repository content i guess we could make some kind of UI that would allow flagging the relevant files and directories to be inaccesible by the minors without their guardian’s password or alike.