It is not and never has been the case that folks have been working on third-party software integration into Nethserver just for the fun of it–it’s been driven by a perceived need. That’s why I built my acme-dns and self-service-password RPMs, as well as automx. That’s why I wrote up the installation process for Phabricator, and documented using acme.sh and DNS validation to get Let’s Encrypt certs for internal servers.
If there’s a particular package you want, but don’t have the ability to package it up, suggest it. Do what you can on it. Are there instructions for installing it under CentOS 7 (that don’t require Docker)? If so, that’s a good start, and you’ll probably be able to get the app up and running with only minor modification. Or is it pretty much just a web app, using the standard LAMP stack? It’s likely pretty straightforward to install. Write that up.
Next, how is the app configured? Are there configuration files? Are there standard things that need to be defined, and can be expected (e.g., things like domain names)? Are there others that the user will want to configure? Work on templates for those.
Packaging the nethserver-appname RPM is probably the fiddliest part of the procedure, but one doesn’t need to know the app well in order to do that.
Now, of course, all this depends on there being an existing app that could be packaged for Nethserver and would do what you want done, and at least two of the three things you mention as examples really aren’t in this category. The “proper CA” may be, though I’m not really aware of a good candidate application (BounCA at https://www.bounca.org/ could be, though the last commit to the code was a year and a half ago, and its installation instructions claim to require nginx).
As you know, much of the development is community-driven. If you want something done, the best way to make it happen is to do it yourself. If you’re unable to do that, a detailed request (identifying the use case where it would be beneficial, the specific capabilities desired, and ideally a specific package that would provide them) is much more likely to get a favorable response than a one-liner that provides none of that information and just says, e.g. “can you add a map server to Nethserver?”. The goal is to get someone else who can do the work to see the value in doing it. Using the examples you gave, I don’t see any value at all in the first two, and thus would be unlikely to put much work into making them happen. I might have a go at getting BounCA or openxpki running just for the fun of it, but I don’t see me building packages and putting them in my repo. But I’m open to being convinced, as I’m sure are others more capable than I.
@stephdl and I, at least, include update notifications as part of our repo RPMs.