You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We talked a lot about it between Vox Pupuli members and some Puppet employees. We (Vox Pupuli) have some gems to structure our tooling, for example:
voxpupuli-test
voxpupuli-acceptance
voxpupuli-release
Those map to unit tests and static code validation, acceptance testing, releasing a module.
Describe the Solution You Would Like
I think we should work out a plan to more align the Vox Pupuli and Puppet tooling and what's templated. We try to provide as little boilerplate as possible in our modulesync_config (our pdk-templates equivalent). That makes updates way easier. I think that's something we should work towards to for Puppet as well. I think we should have a talk in zoom or slack about the differences and what we can unite.
Describe Alternatives You've Considered
A clear and concise description of any alternative solutions or features you've considered.
Additional Context
For the whole ecosystem it makes ense when the two biggest module maintainers, Vox Pupuli and Puppet, work together. That also makes it easier for pdk for calling the different tasks.
CC: @davidsandilands I think you mentioned similar ideas at the beginning of the year.
The text was updated successfully, but these errors were encountered:
Hi @bastelfreak . Just wanted to let you know that we've got an eye on this. This would be a major change and as such we need to discuss and review impact before making any formal decision.
Use Case
We talked a lot about it between Vox Pupuli members and some Puppet employees. We (Vox Pupuli) have some gems to structure our tooling, for example:
Those map to unit tests and static code validation, acceptance testing, releasing a module.
Describe the Solution You Would Like
I think we should work out a plan to more align the Vox Pupuli and Puppet tooling and what's templated. We try to provide as little boilerplate as possible in our modulesync_config (our pdk-templates equivalent). That makes updates way easier. I think that's something we should work towards to for Puppet as well. I think we should have a talk in zoom or slack about the differences and what we can unite.
Describe Alternatives You've Considered
A clear and concise description of any alternative solutions or features you've considered.
Additional Context
For the whole ecosystem it makes ense when the two biggest module maintainers, Vox Pupuli and Puppet, work together. That also makes it easier for pdk for calling the different tasks.
CC: @davidsandilands I think you mentioned similar ideas at the beginning of the year.
The text was updated successfully, but these errors were encountered: