@SciresM If you allow me a bit of constructively meant critique:
While you have certainly made progress (cudos), there is still a lot of work to be done. A bit more then the people who are currently contributing can produce in the near future, I think.
I would like you to reconsider your exploit disclosure policy. Not many people are fit to implement exploits or are interested in doing so in general - esp. when a bunch of people have already implemented them (waste of time being second, possibly costs weeks to do proper esp. on 2.0+).
However, there is an entirely different group of people interested in OS development (a good amount more then those who are interested in exploits probably) who can read specs, reverse code, implement hardware initialization, os drivers, patches and loaders. And who would be super interested in contributing to a custom firmware.
You are currently missing out on these people because they don"t have an exploit to be able to develop on their switch.
As such, I belief that progress is currently hindered by that exploit wall, for not much of a reason. I really see very little benefit in not readying the exploit for 3.0 (which most have) and releasing it to get more developers to help out.
I would be interested in your thoughts. Thanks for your efforts!