"But I know nothing about the module!", you say. Well, maintaining a module is not strictly an undertaking of coding. Much of the responsibility involves empowering others to introduce improvements and fixes. Having a solid knowledge of JavaScript or PHP is helpful to triage issues and determine priority. But no one is an island in this community and I find at least that responsibility is the best teacher. And I am always available to consult on issues as well. I probably know the code as much as one can know it. I'm very nice, I promise and I'm always happy to walk through an issue on a hangout or over Skype. What would you do exactly? Well, I'll borrow some of xjm's points to enumerate the tasks:

What you'd do

Check for RTBC 8.x toolbar issues (it's empty right now!) every few days, and help the core maintainers by ensuring that our RTBCs have clear, up-to-date issue summaries and that they meet basic requirements like the core gates.

Keep an eye on major and critical toolbar issues: Make sure their summaries are up to date, that the next step is clear, and that they are actually major or critical. Consulting with others to determine criticality is ok.

As you can see, not a lot of coding! Of course, you're more than welcome to work on patches for the module as well.

What you'd get out of it

xjm identifies these benefits of being a core maintainer

Insight into Drupal core process.

Direct exposure to what's new and exciting in Drupal 8.

Karma! People who work on core will recognize your contributions, and so that makes it easier for them to help and support you in return.

Seriously, is there anything more awesome than having your name in every copy of Drupal that gets downloaded?

That's a pretty good list! I've certainly gained a lot of insight being one of the JavaScript maintainers.

How do I "apply"?

The word apply is wrapped in quotation marks because maintainership of toolbar is not something I will personally grant. Not at all. We are discussing the maintainership in an issue. I encourage you to announce your interest in that issue. If you have questions about maintainership before you make your intentions known in the issue, I am glad to answer them through my contact form.

Plain text

Filtered HTML

Use [acphone_sales], [acphone_sales_text], [acphone_support],
[acphone_international], [acphone_devcloud], [acphone_extra1] and
[acphone_extra2] as placeholders for Acquia phone numbers. Add class
"acquia-phones-link" to wrapper element to make number a link.

To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.