Maintainer Preferred Path: PR or Discussion First? + Long-Term Plan Inquiry

1

Hello everyone,

I’m a big fan of this project, I use this code heavily, I have three gateways running seamlessly for years with Bluetooth and RF, all communicating with my Home Assistant instance.

As a former developer, I often make custom changes, but I struggle to contribute them upstream because I’m not sure if they align with the project’s direction.

What is the current best way for community members to propose changes?

  • Should we open a discussion thread first, or is a Pull Request the preferred method?

  • Do you have a clear long-term maintenance plan, or specific release strategies in mind?

  • Is there a public To-Do or ‘wish list’ of features you’d like help with?

I’m keen to contribute and align with the established strategy. Thanks for your guidance!

2

Hello Odyno,

Thanks for your proposals.

For big PR I would suggest to discuss it first here or send me an email.

In term of To Do list I have the following:

  • Decrease RAM usage
  • Decrease flash footprint
  • Allow a better handling of the certificates and secure options through the onboarding and the WebUI
  • Dynamically build the WebUI settings from the list of parameters from each module
  • Modernize the documentation

Also it would be great to add some automated testing where we can.

3

Very good! Therefore, all activities carried out to maintain the state of the art and reduce technical debt.

In fact, there would be much to discuss about each of these; personally, I think that testing is one of the most important things to introduce, but I realise that, given the way the code is structured at present, it is really difficult to isolate a unit test, even if only on a native platform.

Thank you