Drop the requirement for role owners to write role specifications (for now)

[cbeams]

When the Phase Zero doc was originally written, I laid out a requirement that each role—or at least each bonded role—must have a role specification similar to the one I put together for the Twitter Admin role at https://github.com/bisq-network/roles/blob/master/twitter-admin.adoc. And you can see how that specification is linked from the Twitter Admin role issue description at bisq-network/roles#21.

Here's the thing though: no one else has written any role specifications since then, and I haven't made it a priority to enforce this rule. After 6 months of operating the Bisq DAO under Phase Zero, I think it's safe to say that we're getting by just fine without these specifications for now, and I am therefore proposing that we remove this rule from the Phase Zero doc, and remove the TODOs in each role issue description.

At least for now. As things progress, and as we exit Phase Zero, especially as BSQ becomes real and bonding means that role owners have real skin in the game, it will probably makes sense to have Git-controlled role specifications like I originally laid out. In the meantime, though, I propose that (a) keeping role issue descriptions up to date and (b) doing monthly role owner report comments as described in #13 is enough.

If you agree, please give this a 👍 below, and (assuming consensus) I'll do the following:

• remove all spec-related TODOs from role issue descriptions
• remove the specification column from the roles repository README
• update the Phase Zero document as appropriate

[cbeams]

Closed as approved by bisq-network/bisq-docs#47.