Co-maintainer request

It seems to me that this bug is critical. Any patch won't pass tests. Patch from #1923242: Syntax error in ctools_plugin_example should be applied ASAP.

There's a lot of sandboxes around with patch-sets against ctools. Not sure it's possible to bring sanity in current codebase...
+1 to @podarok as co-maintainer
Also I'd like to take a part in ctools code-sprint :) a-la views-bug-squad

I absolutely welcome CTools co-maintainers.

Since I don't particularly recognize podarok by name, but I do see a significant commit history, I'd like to go with a trial period. You don't need commit access to become highly involved with a project, and I'm going to need to some vetting to make sure that you're able to do things in the ways that I consider best and up to the standards of ctools. Which may not be as high as the standards of core, as there simply has never been the rigorous review that core has. Nonetheless, I consider ctools a higher quality piece of code, despite its warts, than a lot of other code.

1) Help people who file support requests.
2) Help identify bugs.
3) Help with the overgrown needs review queue.
4) I will put a higher priority on RTBC issues that you have marked RTBC.

I recently spent a significant chunk of time trying to reduce the needs review queue, and it's long and thorny and it has lots of stuff in it. Some of them are easy, some of them are very much not so easy. I have to imagine any serious effort at co-maintainership is going to come with a LOT of questions about my intentions and where I think something should go.

I'd also be totally willing to start work on peeling some things out of CTools and putting them in their own modules. stylizer, for example, is kind of rotting because it's now an afterthought. It was a really fun exercise while I was writing it, but the kind of effort that's going to be required to make it more than a cute toy is well beyond what I want to give it. Potentially page_manager can become its own thing, though it's got a pretty awful hard dependency on CTools in includes/context-task-handler.inc, so pulling that out would be a pretty major undertaking.

In any case, once you've gone through all this and I feel comfortable working with you, we can talk about giving you actual maintainer access. I hope you understand my reasoning.

I checked the maintainers list, and you have "Maintain Issues" perm. Proving it by assigning to you :)

Marking duplicate because this is basically looking to fix the bugs also in #2129033: [Meta] CTools 7.x-1.4 release