Get rid of common.

[taoeffect]

As discussed and explained in #18, we need to modularize all of the services provided into individual roles that can be, at the user's discretion, commented out and not run. HT to @PiPeep for suggesting this approach.

So that implies we must get rid of the common role completely and split all of its services out into separate roles.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6710524-get-rid-of-common?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github).

[pkirkovsky]

What's the plan for moving stuff out of common and into separate modules? I'd love to help with this effort but I'm not sure where to start.

[bgw]

@pkirkovsky, pretty much anything that's separated into a different task file in the common role could become a role of it's own. Good things to start with would probably be mariadb and the security (which is really just intrustion-detection) stuff. I'd recommend splitting off one thing at a time.

Other parts, like user setup and ssl might be a bit more iffy. We might want to think more carefully about how roles declare dependencies.

[taoeffect]

Yeah, there's that, and:

• anything with the tarsnap label (they're all sorta related).
• Issue check-rbl.pl doesn't work #63 is causing annoyance and is easy to fix

Pretty much just have a look through the structure of the ansible files, the open issues, the various labels, and then take something and let us know that you're working on it so that we don't duplicate effort.

Thanks for offering to help out @pkirkovsky! 😄 👍

[taoeffect]

@pkirkovsky As far as this issue is concerned, the comments here should help provide some guidance.