We should put an end to merge requests. We have them enabled on gitorious, but we have a workflow outlined on our ​git workflow wiki page: people make a feature branch and post them to a relevant ticket for review. Having two places to look at this makes keeping track of tickets really hard. Since we don't officially support merge requests, this means they are just piling up. This isn't fair to contributors either: if people submit code, we should be looking at it.

So we should disable merge requests and move them over to our workflow.

• Document more clearly on the gitorious page that we do NOT use merge requests.
• Figure out what happens if we just press "disable merge requests" with existing merge requests open. We don't accidentally want to destroy contributions. (Note: I asked about this on #gitorious on irc.freenode.net at one point and got an unclear seeming answer. It's probably worth asking again.)
• Disable merge requests and close them out. This could happen one of several ways:
  1. We could blast through and review them in sets and then merge or close them.
  2. We could convert them to tickets and, if necessary, create "proxy" git repositories for them.

Plugins also want to be able to specify defaults and do type checking for their own section. We should allow this.

In theory, this involves that the user's config file must have a "short reading" first to determine what plugins are actually being loaded before we extent the config specification.

The plugin author's guide needs to be expanded to explain the new tooling we're putting in place for plugins.