Woring on Mavlink Platform

[nikolaevarius]

I am looking at doing some work on the mavlink code base (primarily investigating upgrading it to v2)

I somewhat wish to fork the current mavlink protocol specific codebase in

https://github.com/hybridgroup/gobot/tree/dev/platforms/mavlink and then reimport it as a dependency and expose its functionality as an adaptor This is because I think there is value to trying to have a protocol like mavlink as its own separate library so that other projects can use it and make it easier to keep compliant with different mavlink versions.

What are the opinions of the community on forking out generic protocols into their own library