Roadmap for rumqtt?

[ryanwinter]

Hi,

We currently use this client in one of our product SDKs, however we havent had much traction with PR's being integrated from our fork.

Is there a plan to continue to support this repository?
What would be the best way to integrate our forked changes?

Thanks
Ryan

[tekjar]

Hi @ryanwinter

Here's a roadmap we've setup for rumqttc

• Memory stable and fast
• Should run on devices with <10MB memory
• Features
  • Returns pkid/tokens or other identifier to clients
  • Ability to shutdown
  • Full MQTT 5
  • Ack after processing
  • Synchronous publish with broker (next publish after previous ack)
  • High level client
• Python, C and Javascript wrappers
• Tests
  • Stability and perf test suite with mock broker
  • 100% code coverage
  • Throughput and memory stability tests
  • Comparison between clients
  • Conformance test suite

The primary reason for delay is redesign and bandwidth within the team. We've gone through a list of all the issues and are now iterating on the design for next (major) release. However bandwidth is still a challenge. I'm happy to collaborate with companies/teams using this library or create a sponsorship page to help fund this project for dedicated resources to push the roadmap forward

[ryanwinter]

Thanks @tekjar!

Completely understand the bandwidth challenges :) Let me follow up with the team and we can respond on this thread if this is the easiest way to communicate?

[tekjar]

Thanks @ryanwinter . [email protected] is my email if you prefer to communicate over there. I could also invite you to an internal slack channel if that works. We are proactive there :)