Puppet Community

maybe 'vox' or 'voxpupuli' should be in the gem name somewhere?

voxpupuli-puppet-lint-plugins is our metagem

We _could_ add them there if you update the license to match the incoming code (since the meta gem doesn't really contain anything other than a short list of gems at the moment, updating changing its license wouldn't be an issue)

Do we need to mark our gem as 'conflicting' somehow with the originals?

are you suggesting to vendor the lint checks?

so probably voxpupuli-puppet-lint-plugin-forks with Apache is best. that's what the plugins from mmckinst use as well

I would like to pull in the checks from <https://github.com/mmckinst/puppet-lint-top_scope_facts-check/> and <https://github.com/mmckinst/puppet-lint-legacy_facts-check/>  into a new gem

ewoud: vendor the ones we need to fix but where we can't get hold of the original maintainer.

just another thought: perhaps do it in puppet-lint itself?

because they have open bugs and the maintainer is MIA and we cant release the fixes

I think getting a puppet-lint release out is more complex

<https://github.com/puppetlabs/puppet-lint/tree/main/lib/puppet-lint/plugins> are there and these are according to the Puppet style guide

things like whitespace are more opionated, but using current (non-legacy) facts should be in the Puppet style guide since it prepares for Puppet 8

I tend to agree about the velocity of releases though.

fwiw its not hard to release puppet-lint :slightly_smiling_face:

license may be tricky there, but IMHO we should get back to the principle that puppet-lint has all the checks for the official Puppet best practices