Thats a lot of repos. I note this is a milestone and beta forum area, so maybe in this case that makes sence, and I would agree with no more updates from OSS/non-OSS.
But IMHO that does not apply to a nominal GM version of openSUSE, as in such an nominal GM version, OSS and Non-OSS are likely to do far less damage than the other repos.
If it were me, for a GM version, I would get what I want off of all the other repos and as soon as I do, I would immediately disable them, and then leave OSS and Non-OSS enabled. When there is an update proposed by OSS and Non-OSS (in a GM openSUSE) I recommend checking to see what the update is, PRIOR to accepting the update. If its a “kernel” or “xorg” update, then ensure one has the latest graphic driver (for an installation using the method coined “the hardway” (even though it is easy)) and ensure I have appropriate webcam, and wireless drivers, PRIOR to updating. Also, always ensure one has a recent backup of one’s /boot/grub/menu.lst and one’s /etc/X11/xorg.conf file.
I’ve read of many dozens of users whose GM version of openSUSE has been messed up because of adding repos such as the list noted above. Caution is the operative word here, and a mess up from such repos can be unrecoverable. This is in contrast to any hiccup from OSS and Non-OSS where it almost ALWAYS is recoverable.
For a GM version, I always recommend only 4 repos: OSS, Non-OSS, Update and Packman and I mostly follow that philosophy myself. When I add other repos, after getting the package I want, I immediately remove them (the added repos).
But for a beta/milestone version, I typically have only OSS and Packman enabled, and every update I do with caution. I add other repos only with caution, and I remove them immediately afterward. Typically I don’t accept any updates, as when I test, I want a solid baseline without some obscure package confusing the results of any testing that I might be doing. If one keeps installing applications adhoc, how can ones testing be of any use. No one knows what version of applications that one is testing. Its very very confusing.