Config/data reorganization

[nmlorg]

Right now, at the bare minimum, bot runners need to manually create a config/ directory to store multibot.json. To use the /events module (via metabot.calendars.multicalendar.MultiCalendar), they also need to manually create a calendars/ directory and a config/calendars.json file.

• At minimum, metabot should create config/ (and calendars/) for the user automatically.
• When run outside of a virtualenv, the bot should probably default to something like ~/.metabot/ or ~/.config/metabot/. It might make sense to always use this, even inside a virtualenv. It probably makes sense to allow a directory to be the first argument (python -m metabot ~/mybotdata), and might further make sense to prompt for the config/data directory rather than default to config/ or ~/.config/metabot/.
• I chose to use JSON for the config format exclusively because a JSON module has been included in base Python since 2.6. I think it's probably fine to depend on PyYAML.

This might also be a good time to consolidate multibot.json and calendars.json, so:

# config/multibot.json
{
    "firstbot": {
        "admins": {
            "admins": [
                12345, 
                23456
            ]
        }, 
        "moderator": {
            "-10020002000": {
                "greeting": "Another Greeting"
            }, 
            "-10010001000": {
                "greeting": "Example Greeting"
            }
        }, 
        "telegram": {
            "running": true, 
            "token": "1111:XXXX"
        }
    }, 
    "secondbot": {
        "admins": {
            "admins": [
                34567
            ]
        }, 
        "telegram": {
            "running": true, 
            "token": "2222:YYYY"
        }
    }
}

# config/calendars.json
[
    {
        "calid": "[email protected]",
        "name": "An Example Calendar"
    },
    {
        "calid": "[email protected]",
        "name": "Another Example"
    }
]

might look something like:

# ~/.config/metabot/conf.yaml
bots:
  firstbot:
    admins:
      admins:
      - 12345
      - 23456
    moderator:
      -10020002000:  # Note that YAML allows keys to be numeric types!
        greeting: Another Greeting
      -10010001000:
        greeting: Example Greeting
    telegram:
      running: true
      token: 1111:XXXX
  secondbot:
    admins:
      admins:
      - 34567
    telegram:
      running: true
      token: 2222:YYYY
calendars:
  [email protected]:
    name: An Example Calendar
  [email protected]:
    name: Another Example

However, it might also be worth first working out an actual UI for adding new calendars, and change the format of the calendar cache files to include metadata like "title" (or even separate it entirely into per-bot configs) so the configuration process is just scanning the cache directory (~/.config/metabot/calendars/).

[nmlorg]

	sys.prefix	sys.base_prefix	sys.real_prefix
Python 2.7.15rc1	'/usr'	unset	unset
Python 3.6.6	'/usr'	'/usr'	unset
Python 2.7.15rc1 virtualenv	BASE	unset	'/usr'
Python 3.6.6 virtualenv	BASE	BASE	'/usr'
Python 3.6.6 venv	BASE	'/usr'	unset

[nmlorg]

• Add a cleanup filter to the converter logic to convert BOTNAME.moderator.'GROUPID' to BOTNAME.moderator.GROUPID.
• Convert config/calendars.json to config/calendars.yaml.
• Have BotConf expose its current data (bots.yaml) under a new 'bots' level (so BOTNAME.moderator -> bots.BOTNAME.moderator), and pull in any other config/*.yaml files (such as calendar.yaml) too.
• Move all group state (but not group configuration) out of bots.BOTNAME.groups into a new top-level 'groups' (groups.yaml).

[nmlorg]

(See #93.)