Move Beats et al. to mixxx namespace

[JaviVilarroig]

This is just a technical PR. I have moved the Beats class, and associated ones, to the mixxx namespace.

[Be-ing]

Looks good to me. Anyone else want to take a look?

[Be-ing]

Do we have any guidelines on what belongs in the mixxx namespace? There doesn't seem to be any pattern that I have noticed.

[JaviVilarroig]

I understood from the Coding guidelines that we wanted top have a mixxx namespace to contain all the mixxx classes, at some point.
I also understood that we wanted to have classes moved to mixxx namespace when we work on them.
This is "in preparation" for #2512

[Holzhaus]

Do we have any guidelines on what belongs in the mixxx namespace? There doesn't seem to be any pattern that I have noticed.

Most newer stuff goes into the mixxx Namespace. I think it makes sense to gradually switch over all our code to this namespace to avoid naming clashes with third party libraries.

[daschuer]

Hi @JaviVilarroig, I have just noticed that we are missing your contributor agreement.
This is required to release you patch with Mixxx
Please sign https://docs.google.com/a/mixxx.org/spreadsheet/viewform?formkey=dEpYN2NkVEFnWWQzbkFfM0ZYYUZ5X2c6MQ
And comment here when done.
Thank you very much.

[JaviVilarroig]

Done :) El lun, 10-05-2021 a las 09:33 -0700, Daniel Schürmann escribió:

…

Hi @JaviVilarroig, I have just noticed that we are missing your contributor agreement. This is required to release you patch with Mixxx Please sign https://docs.google.com/a/mixxx.org/spreadsheet/viewform?formkey=dEpYN2NkVEFnWWQzbkFfM0ZYYUZ5X2c6MQ And comment here when done. Thank you very much. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[daschuer]

Thank you. That was quick :-)