We'd be happy to add Discovery support into libmaple. More users means a more robust library, as far as we're concerned, and we're very glad that you've found libmaple useful enough to take the trouble to port it.
If you want to make it easy on us to get your work merged in, the steps to follow are: (1) start with the current LeafLabs libmaple master branch, then (2) commit your changes on top of it into a separate "Discovery support" branch, (3) push that branch to your GitHub libmaple repo, and (4) send us a pull request.
I imagine you've probably got a 'leaflabs' remote in your local libmaple clone that points to the LeafLabs libmaple repo on GitHub. If so, then you can follow this recipe:
First, make sure you're up to date with our master branch:
$ git fetch leaflabs
Next, create a branch called "discovery-support" where you'll put your changes, starting from the current LeafLabs master:
$ git checkout -b discovery-support leaflabs/master
At this point, your current branch should be discovery-support. You can now add your commits however you like, possibly using rebase or cherry-pick.
Please sign your commits with a developer certificate of origin. I believe you're already familiar with this from your last pull request, but just in case, this just means adding the line "Signed-off-by: Your Full Name <firstname.lastname@example.org>" at the end of your commit messages. (We've started doing this for non-LeafLabs staff commits into the libmaple core. It's important to do so because it leaves a "paper trail" which helps us ensure that libmaple stays open source).
Once you're done, push your work into your libmaple fork on GitHub:
$ git push origin discovery-support
At that point, you can send us a pull request and we can get things merged in.