Page Comparison

...

Restructure the current and future SIMP modules and RPM (metadata) names to match community standardsutilized structure, making our repositories and RPMs easier to manage, maintain, and understand.

...

Github repositories will be re-named to fit a more standardizedreadable, community recognized utilized structure. The words word ‘pupmod’ and ‘rubygem’ will be removed, and replaced per the structure below. The word ‘simp’ will also be removed unless absolutely necessary.

...

• All puppet modules will be renamed named ‘puppet-<module_name>’
• All rubygems will be renamed ‘rubynamed ‘rubygem-<module_name>’
• All other types will be renamed named ‘simp-<module_name>’
• OPTIONAL: All repositories will contain only one dash, with longer names containing underscores; i.e 'puppet-<extra_long_name>'

...

• ‘rubygem-simp-cli’ would become either ‘ruby-cli’ or ‘ruby'rubygem-simp_cli’ or stay the same
• ‘pupmod-simp-simp’ would become ‘puppet-simp’
• ‘pupmod-simp-simp_apache’ would become ‘puppet-simp_apache’
• ‘pupmod-simp-auditd’ would become ‘puppet-auditd’
• ‘simp-doc’ would stay the same

...

This plan will result in a minor version bump for all updated modules since we would be changing the metadata.json or .spec file to update the names, as well as changing any dependencies to match the new naming scheme, adding obsoletes to prevent issues with the name change. If no changes are needed (such as simp-doc)to the name, metadata or spec, or obsoletes, no version bump would be necessary. 

Options considered

Action items

•  Update SIMP Repositories to match naming scheme if necessary
•  Update metadata.json or .spec file to match naming scheme if necessary
•  Add necessary obsoletes
•  Update code to fix references to old names
•  Minor version bump for Repositories that had metadata.json or .spec file updates
•  Update documentation to match the new naming scheme

...