Looking for co-maintainer

[mhfs]

Hi guys, I'm looking for someone to join me as co-maintainer of devise-async.

I cannot devote the amount of time I'd like to take proper care of this project and having someone to help me would make things quicker and better for everyone.

Desirable characteristics:

• active use of devise-async in live production apps
• history of contributions for OSS

Things I value:

• good test coverage
• good docs in the readme
• backward compatibility
• maintainers consensus on big code refactoring
• maintainers consensus on api changes

Please get in touch.

[baschtl]

@mhfs What are your future plans - if any - for devise-async since Active Job is out for Rails 4.2?

[mhfs]

@baschtl that's part of what I'd want to figure out. I have not worked with latest versions of rails or devise for a while now.

[baschtl]

@mhfs Hmm, I also have not looked into Active Job specifically. But I have seen that the supported backends (http://api.rubyonrails.org/classes/ActiveJob/QueueAdapters.html) match with few differences. I also saw this one yesterday: https://github.com/ushu/devise-async-activejob.

[baschtl]

@mhfs As mentioned in https://github.com/mhfs/devise-async/pull/60 it seems to be pretty easy to use Active Job with devise.

[baschtl]

@mhfs Could you push a new release (0.10.0-alpha) to rubygems if possible? That would be great!

[mhfs]

hey @baschtl, thanks for all the help with device-async. I'm still super busy and still neglecting open source so it seemed the best idea was to make you an owner at rubygems and let you work freely. let me know if it works.

[baschtl]

@mhfs Works like a charm. Thanks!

[baschtl]

I will close this issue as there is apparently no further interest in it.