Allow a person submitting feature request / bug information and other person with more experience fixing it

[bekicot]

• [x] This is not a usage question.
• [x] This is not a security issue.
• [x] I am committed to implementing this feature in a reasonable amount of time, and responding promptly to feedback.

Current Behavior

User: inexperience developer when submitting bug / feature request user is obligated to committed on implementing a the fixes in reasonable amount of time. However, it is not possible for inexperience developer who found bugs and don't know how to fix it.

Proposed Behavior

Inexperience developer may submit valid, usefull for common user, and fully described bug / feature request information but not obligated to fix it. Inexperience developer encouraged to write test to to the bugs / feature request, but not required.

Proposed Solution

remove

I am committed to implementing this feature in a reasonable amount of
  time, and responding promptly to feedback.

from issue template.

[jaredbeck]

Proposed .. Inexperience developer may submit valid, usefull for common user, and fully described bug / feature request information but not obligated to fix it. Inexperience developer encouraged to write test to to the bugs / feature request, but not required.

Hi Yana, Thanks for the suggestion. I'll explain why we have this policy, and we can discuss how the policy could change in the future.

This project has two active committers, Tieg and myself. Both of us started working on Authlogic because we used it at work. Neither of us use Authlogic at work anymore. We have time to review PRs, and update dependencies, but we don't have time to triage issues. That is why we have the policy that you must fix your own issue. We'll help as much as we can, though, so don't be afraid to try!

If we had another committer who wanted to triage issues, this policy could change. If that's something you're interested in, or if you want to nominate someone, please tell us!

[bekicot]

Hi @jaredbeck thank you for the explainations. Also thank you for your time & effort to manage this awesome open source software. I also don't have candidate that is fit & willing to manage this project.

However, I do believe that people are willing to spend their time to help with valid Issue, especially if they use this project in their production systems. One of the easiest way to split between valid & non valid issue is if there is no activity on the issue itself. And there is bots that can automatically tag issue with stale, and later close it.