Merge with devise-i18n-views about devise-i18n HOT 2 CLOSED

Yes, I'd be happy to work on it myself.

from devise-i18n.

I totally agree with you that a single I18n solution for devise would be best all round.

However, I have absolutely zero time at the moment to dedicate to this, is this something you would be willing to work on (more than happy to give you access to this repo)?

On 12 Oct 2015, at 21:48, Jason Barnabe [email protected] wrote:

I'm currently a maintainer of devise-i18n-views gem. I would like to propose that the functionality of that gem be merged into devise-i18n. I've read the comment in #13 #13, but I'd like to present my case.

The purpose of any gem (or software in general) is to be useful to users. The purpose of both devise-i18n and devise-i18n-views is to provide i18n for devise. The fact that some of this i18n is done simply with locale files and some requires views included isn't of much consequence to the gem users. In fact, having them separate causes confusion for users and requires both projects to tell people to use the other.

The same confusion arises for contributors to the gems (mcasimir/devise-i18n-views#68 mcasimir/devise-i18n-views#68 #92 #92). These contributors will also either only contribute to one project, or need to keep track of two separate projects. Having them as one will mean an easier job for contributors and likely more complete translations.

Finally, having one project will make it easier for me and you (the maintainer of this gem). Having additional people to look at pull requests or sync from localeapp will make us more responsive.

—
Reply to this email directly or view it on GitHub #131.

from devise-i18n.