I too would like to be able to have access to the source code to be able to fork it and make custom changes.
Some of those changes could be contributed back of course.
I was hoping to be able to write an inventory management module (managing purchases, and serial numbers assigned to which customers, etc)
So far I had to extract the code from docker images and then reverse engineer most of the stuff you guys did to make it work - very painful
@jsenecal_zap yes, the source code is accessible and anyone can check it or suggest a bugfix or an extension but for now, it's not possible to contribute directly to the source code. In the current state of development, we prefer to listen to your feature requests and suggestions and at the same time, we want to choose the right direction suitable for WISP all over the world.
However, what is possible now and what we additionally want to focus on is to provide you with an interface and API for small add-ons and extensions, like some custom traffic shapers, payments importer, integrations with an external accounting software, etc.
Talking about the Inventory module, that's something we need to integrate ourselves to ensure it's suitable for most of the users and to provide the best integration with UNMS as well. *However, it will be much appreciated if you share your ideas and needs about this module* - You can tell us about the use cases you need to incorporate, attributes and data you need to store and show on the frontend, etc.
Please take a look at this feature request and share your thoughts https://community.ubnt.com/t5/UCRM-Feature-Requests/hardware-inventory/idi-p/1929000
Wednesday - last edited Wednesday
@UBNT-Petr: "yes, the source code is accessible and anyone can check it". Is there any way to check it besides having to fetch it inside docker? It makes it kinda hard to check.