Part of Mozilla’s aim with the Sprint is to help people/projects outside of engineering apply “open” principles -- to educational resources, to civic projects, etc. That’s why you see some light-weight, non-technical issues. But there are plenty of more typical coding projects to work on! You can try searching by project or language to find those.

Here's background on the larger mission: https://blog.mozilla.org/blog/2018/05/07/mozillas-48-hour-ha...

Unless I'm missing something, the answer from the link is ~nothing and/or taking credit?

- Curated a list of bugs/features/issues that are accessible to noobs as well as veterans

- Coordinated with project owners that wanted to be involved

- Setup a structure for mentoring and leadership on projects

- Broadcast the initiative

- Focused the project list on things that would build a "more healthy internet"