Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preamble #378

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Preamble #378

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
86d75f8
add maint-mode preable
Dec 29, 2023
aa08f17
format
Dec 29, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,15 @@
puppetdb
=========

Statement of Support - Maintenance Mode
---------------------------------------

> This module is maintained by Puppet, but we have no plans for future feature development. We
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry but this must be a joke. Why doesn't Perforce want to provide puppet modules for their own software?
And what about the puppetdb specific code in pe-modules rpm/deb package? That's probably still maintained? Why can't Puppet Enterprise eat their own dogfood and use the puppetlabs/puppetdb module instead?

You put us now in a situation where open source users are treated like second class citizens and I fail to understand why.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another thought: There even is a whole team dedicated to manage puppet modules. They manage a bunch of modules for third party software. Why don't they maintain the PuppetDB module (or one for Puppetserver and Puppet Agent)? I asked that a few times during office hours but never got a proper answer.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GSPatton I have suggested we talk about this at the next VOX sync and it might be good for your product area to be aware and to help discuss

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added this PR as a talking point to the agenda (https://github.com/voxpupuli/community-triage/wiki)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Puppetlabs's own puppetserver team having to work around the lack of maintenance of this module makes this preamble even more puzzling:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was discussed at length: https://github.com/voxpupuli/community-triage/wiki#february-13-2024

The short summary is:

  • Historically there exists an internal version to support PuppetDB in PE
  • Puppet uses this module for CI
  • This preamble is intended to clarify the existing situation
  • By the next community meeting (2024-02-13) we should have more clarity on the path forward

> will keep it working with current versions of Puppet, but new feature development will come
> from community contributions. It does not qualify for Puppet Support plans.

[tier:maintenance-mode]

#### Table of Contents

1. [Overview - What is the PuppetDB module?](#overview)
Expand Down