You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm one of the authors of Nova (https://novaframework.org) and we have evaluated boss_db to be used within our framework. The problem is that parts of the code is very old and do not always work in newer versions of Erlang.
With this in mind we forked the repository and applied fixes to boss_db (And removed some really old adapters that we saw problems with). We are very much committed to bring boss_db to its former glory and would be happy to contribute to it.
One major question we have now is if it would be okay for us to release our fork of boss_db to hex.pm? We can of course change the name of the application, but want your input to this whole thing.
Another potential solution is to include us as maintainers of boss_db. But right now you have 18 open pull requests and 41 open issues (and last commit to master 2years ago) and the project feels dead. Correct me if I'm wrong here.
that project is not actively maintained, yet used in some running project, which do not require new features. If you are willing to improve it directly, it will great and I don't mind to add you or your team as maintainers.
Thanks for the reply @danikp. Was not my intention to out this project as dead, but were curious about the state and future of it. As I said - we are currently looking to include boss_db as the ORM in Nova and have made quite a lot of changes to it on our fork.
It would be very interesting to talk with you about your view of boss_db and its future. If you're on slack (Erlang or Elixir space) please send me a message, I'm called burbas there, and perhaps we can have a quick discussion.
I really love this project and it would be really cool to perhaps collaborate on it.
Hi,
I'm one of the authors of Nova (https://novaframework.org) and we have evaluated boss_db to be used within our framework. The problem is that parts of the code is very old and do not always work in newer versions of Erlang.
With this in mind we forked the repository and applied fixes to boss_db (And removed some really old adapters that we saw problems with). We are very much committed to bring boss_db to its former glory and would be happy to contribute to it.
One major question we have now is if it would be okay for us to release our fork of boss_db to hex.pm? We can of course change the name of the application, but want your input to this whole thing.
Another potential solution is to include us as maintainers of boss_db. But right now you have 18 open pull requests and 41 open issues (and last commit to master 2years ago) and the project feels dead. Correct me if I'm wrong here.
To the ones that still looks for a Erlang ORM - please have a look on our fork (https://github.com/novaframework/boss_db)
The text was updated successfully, but these errors were encountered: