[erlang-questions] erlang-bcrypt status

Aaron France aaron.l.france@REDACTED
Tue Jun 18 09:02:12 CEST 2013


My advice would be to fork it, merge the patches where applicable and
maintain and advertise that fork. If all goes well, the original
maintainers will want that fork.


On Tue, Jun 18, 2013 at 4:33 AM, Jeremy Ong <jeremy@REDACTED> wrote:

> Hi all,
> The highest profile implementation of the bcrypt algorithm is currently
> the smarkets fork of erlang-bcrypt at
> https://github.com/smarkets/erlang-bcrypt.
> However, activity on this fork has not existed for a year now and I think
> we should reach a consensus on where this library should be officially
> maintained so everybody's patches can coalesce cohesively.
> The issues I see now are build problems on various nixes, a very outdated
> bundled rebar, and a potentially thread safety issue mentioned here:
> https://github.com/smarkets/erlang-bcrypt/pull/9/files.
> I am willing to do this and the fork would be actively maintained at the
> company I work at (Quark Games). However, I want to open up this
> opportunity in case somebody has already done significant work on the
> library and wants to curate it that I am unaware of.
> Cheers,
> Jeremy
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130618/7e2ff108/attachment.htm>

More information about the erlang-questions mailing list