Apologies for the lateness of the reply.
On Tue, Oct 06, 2015 at 11:38:13AM +0100, James Masson wrote:
Hi list,
I'm writing a helper for the CA in
https://vaultproject.io/
It's written in Ruby, requires a few extra gems, is functional, but a bit
basic right now.
At the moment, it's going to live in Github. I'll post a link when it's
ready for public consumption.
Cool!
If we did want to include the plugin in the Certmonger code-base
& RPM,
what's the process for that?
We haven't really defined one, but my leaning would be toward starting
with patches in trac tickets and/or on the mailing list.
I'm not really familiar with Ruby, but keeping the build and install
requirements list short (i.e., to things that are provided as part of
RHEL and CentOS's main repositories) is a pretty hard requirement, and
so far that's meant implementing in C and being careful about adding
dependencies on new libraries.
Anything that depends on more than that has tended to live in a
different package. For example, the helpers that FreeIPA carries in its
own tree get to be written in Python and make use of FreeIPA's client
framework.
Would we retain commit access to update the plugin and fix bugs?
Probably? More maintainers is a good thing.
If the plugin's going to need frequent updates and fixes, then being in
the same repository means the rate of package updates for RHEL and
CentOS (infrequent), and to an extent Fedora, becomes a limiting factor.
Either way, Fedora's accounts system is the starting point, since that's
where the
fedorahosted.org systems get their idea of who users are, for
both trac ticketing and git.
Do you have specific licence requirements?
In the certmonger package itself, it's GPLv3 or later with an exception
for linking with OpenSSL. I expect that enrollment helpers that live in
other packages will have a license that is appropriate for them.
Cheers,
Nalin