Good news everyone!
The Babelfish project now has an official mailing list 🎉!
After 2 years of active development using GitHub and Slack as a main communication tools for the project, we think it's ready and now it seems like a good time to put some dedicated effort toward bringing Bbflsh to the next level. We are looking forward to the public, open discussions, especially regarding documenting and sharing a high-level roadmap and upcoming features as well as growing overall community involvement in the day to day development work.
Here are the basic tools that core developers working on bblfsh use to date:
Code/Issues: https://github.com/bblfsh
Public Slack: https://sourced-community.slack.com/#babelfish
Code Reviews: https://git.io/vHGM4 (points to GitHub pull requests)
Now there is also this bblfsh-dev@ mailing list, available at both
We plan to use it for both developer support and discussion of longer-term directions, proposals, planning, etc. We hope that this work will ultimately lead to a more clear roadmap and steering of this project. Meanwhile, we still expect most of the small day-to-day discussion to happen in IM on Slack.
This means we would be very happy to hear from you—please, do not hesitate to ask questions, share your use cases and missing features, and so on. This is one of the simplest useful ways of contributing back to the project!
--
Alex,
on behalf of core bblfsh maintainers