Do you consider broid to be production ready? #139
Comments
|
Hi m90, I would say you thanks for yours PRs and feedbacks. I looked into your issue/PR, it's more about improvement/security (eg #134) than real bug blocker. Maybe I am wrong and if it's true, please open issues as you want to help us to improve all integrations. We try to follow the Opensource/Linux rules about the versioning number. 2.x.x release introduce a big breaking change on the API side (check #123). Basically, we added the support of external express router in all the integrations. We did that because the community asked us this feature (#71) About the documentation, I am completely agreed with you and we actually working to revamp and rewrite the documentation to make more clear the potential of the broid integrations. We expect to publish something next week. Again all suggestion is welcome about that! We still working on Broid, mostly around the quality and CI improvement (eg. #132), and other dark work (like normalizing the contribution, publishing an official roadmap etc..) This can explain your feeling about the contribution trend. You and all developers can discuss with us about any topic in Slack via http://slackin.broid.ai/, we are always connected and ready to share! Hopefully, I answered all your questions and if it's not, Join us on Slack to continue ;) Edit: I need to check your issue about |
|
Hi and thanks for your response and all the insights sounds good. Just to add on what I was writing, here's what is or was broken for me:
Again: this is no problem. It just feels very alpha. |
I am using broid in a side project. In every integration I used (4 major platforms) I found show stopping bugs (i.e. does not work at all) that required fixing them myself or hacking my way around them (you probably noticed that by now). That is totally fine and actually fun as I am learning new stuff and the side project is totally non-critical.
I think the route this project is trying to take is really amazing and could solve a whole slew of issues the ongoing bot craze is currently facing. It's cool that it is developed as an open source software library and not as the next SaaS thing that exposes yet another API.
What worries me though is: I find it hard to tell what the current state of this library is. It feels like an alpha version when using it (which is perfectly fine for me and a normal state for any software of such scale), but then again I do not find any evidence on that in the documentation or ongoing development. It's a 2.x.x release and the docs look like this is a turn-key solution, commit activity seems to be more or less done. That's not what I experienced.
Which leads me to the question: do you consider broid in its current state to be production ready? Is there any sort of roadmap that you follow on the way to production readyness or whatever your next goal is? From my recent experiences I would not use broid in a production project, but I think that's just a normal stage of software lifecycle: it's in development.
Then again I would much love to use broid in a production project if one came up soonish. But to do that I'd need to know what the agenda and project state is. I feel other users might be interested in your view on that too before they make their bets.
That being said, I'd be more than happy to help out on improving this. Thanks.
The text was updated successfully, but these errors were encountered: