This would give to this project a lot more visibility and traction, I think.
Steps to do the process are here: https://github.com/arduino/Arduino/wiki/Library-Manager-FAQ
Thanks a lot.

P.S: It would be great if this example sketch (https://github.com/wolfSSL/wolfssl/blob/190d30f336c0ff32aecbf198bd0603b42dcac46a/IDE/ARDUINO/sketches/wolfssl_client.ino ) -or others if exist- come along with the lib

The documentation needs the following improvements:

• Add tutorial on how to use libpull to send updates using Zephyr + nRF52840 + BLE;
• Finish documenting the API to fix the Travis build.

For normal builds, it is helpful to have more specific versions than simply the upcoming version snapshot. 2019.2.MMDD.HHmmSS.0 seems like a reasonable format. It combines the year major and minor open source versions with a timestamp and ending in .0 which follows an internal convention where these are treated specially as development builds.

We should make the creation/sending of error messages a clearer part of the implicit state machine. This means, for example, adding context states for sending error messages, and updating handle_io.