S C

Oh great. Thanks!

What happens if the maintainer doesn't like your idea / code? Can they make suggestions? Do maintainers ever feel obliged to include someone's work just out of guilt? Or will they generally come back with suggestions to improve the code ?

I have two questions.

How do I contribute to a ruby gem? Do I just locate it's repo and make a pull request? Or are there more formal procedures?

Also, what if I've made some very useful methods but I know they're not perfect (but they're still very useful and could save others a lot of time). Is it worth submitting changes that are known to be imperfect?

Very cool! Thanks so much. I'll give it a go and report back

I've built authentication a few times now, and every time it's been 99.9% the same (save for a few tweaks in form validations etc). The machinery has been more or less identical to that found in the Michael Hartl tutorial (with 'remember me', account activation and password reset)

I was wondering if there's a command that can build all this for me, so I don't need to do it manually every time?

I know of gems like devise, but have heard they make it harder to configure things. I already find rails hard to configure, so I would like to stick to 'manual' authentication

If the answer is 'no', could I make a rake task that will do everything for me, then just copy that rake task into any new app and run it to build authentication that way?

Thanks in advance for any help