Room for a Co-maintainer?

Going to mark this critical, have been hearing similar comments from others.

Just to give a quick heads up on this topic:

The situation with adding co-maintainers is special for Dreditor, since it is a user script and not a module.

This means that every commit immediately ends up in the "release", because there is no release, or rather, the HEAD revision of the .js file in the git repository is what is being linked from the project page and what everyone installs.

This inherently means that, in addition to the well-known best practices, every change has to be extensively tested manually before commit. (Fact is, most changes I'm committing have been running and tested in production on my local machine for weeks upfront. ;))

I'm perfectly happy and open to add co-maintainers though. Just a bit scared myself by the sheer amount of people who're using the script meanwhile... ;)

I agree on @all :p

I want to work on dreditor too. Some patches are great to have applied while my big triage patch would be awesome to to have in dreditor.

Having a stable branch next to a bleeding edge is great for both dreditor users and developers.

I am very interested in this. I'm primarily a front end developer, would be glad to contribute what I can. +1 for making a release branch.

Both neochief and I are maintainers now.

Awesome!