Skip to content

Home

Jump to bottom Edit New page
Robert Waffen edited this page Mar 15, 2024 · 23 revisions

⚠️ please use the project to add talking points

Monthly sync agenda and notes

March 12, 2024

Agenda:

Notes:

  • @rwaffen will clean up the plumbing issues and create a project. We'll start going through the board with each sync, next month.
  • @binford2k will investigate https://www.puppet.com/docs/bolt/latest/bolt_inventory_reference#features to identify what "features" are.
  • @rwaffen will work on a project & board to replace this wiki.
  • @binford2k will investigate the puppetdb_cli situation
  • PuppetDB v. 8.4.0 release was not published.
  • @binford2k to check with Cas about restarting Bolt office hours
  • Forge content cleanup will go as planned.
    • Modules without updates in more than four years will be contacted via email.
    • In six months time, modules without an update (even just metadata, like supported Puppet/OS versions) will be deprecated.
    • Deprecation only means that it doesn't show up in the UI & search. No content is ever deleted except for legal reasons.
    • @saurabh will share a list of modules scheduled for deprecation with this group for a human safety check.
  • OSS project features like Bolt plans are sort of the test bed for PE projects. Features won't make it to PE unless there's demonstrable customer value. The best way to ensure that features bubble up is to file tickets or talk to TAMs to make sure that Product knows about the customer demand.
  • @davidsandilands will ping the content team for https://github.com/puppetlabs/puppetlabs-stdlib/pull/1418
  • On the PDK and other tools topic:
    • Biggest current blocker for adoption of usage of these tools is the use of opt-out analytics, opt-in is the ideal way to move forward.
    • PDK itself should provide better options for package compatibility, an option was make building from source more accessible.

February 13, 2024

Agenda:

  • Update to puppetlabs/puppetdb situation. [#6]
  • Talk about a process to figure out how/when/whom we sponsor conference trips (by bastelfreak, rwaffen)
  • Elections kickoff

Notes:

  • PuppetDB module will be supported, but we don't have the full timeline for it yet.
    • We are working on a shared ownership model between PuppetDB team and Content team and expect that to be more sustainable.
    • Content is expert at module maintenance and engineering teams are subject matter experts
  • Tim noted that the shared model is similar to how Vox Pupuli works
    • discussion about converging maintenance patterns and common workflow
    • example is modulesync
    • Gavin D is following up with overlaps and convergence opportunities
  • Ewoud talked about moving boilerplate (like modulesync) out of the module and into shared tooling gems and workflows.
  • We need a process for handling money, such as conference selection and swag
  • It's hard to build interest in conference speaking. Nobody has yet requested funding.
    • along with funding, we should work on messaging
    • encourage people to participate, even through imposter syndrome
  • Testing ecosystem improvement opportunities
    • More prescriptive
    • Converge tooling and workflows
  • PMC elections
    • we need to promote it more. Each of us should talk to our peers to get word of mouth out there.
    • @rwaffen will work on a couple blog posts about the specialized roles and experiences we are looking for. @binford2k will help get them published.

January 9, 2024

Agenda:

Notes:

  • Ben provided the history of why Puppet Enterprise Modules were forked and continue to be forked.
    • Back in 3.x days, we started with the OSS modules, but customers upgraded or installed different versions from the Forge. This often ended up with weird failures and made it difficult to support. The root cause of this is that PE management modules are conflated with customer code and third party dependencies often force the upgrade of something like puppetlabs/stdlib.
    • Jon reminds us that the internal forks allow us to develop new features in private.
  • Ewoud points out that hiding work is the antithesis of the Open Source ethos.
    • he says that internal work is the opposite of building trust -- it erodes trust in the company and makes him want to look for alternatives.
  • Robert reminds us that open source licenses must be followed and that copying OSS code into proprietary modules likely violates the license.
  • Gavin wants to know -- what does Community want?
    • the puppetlabs/puppetdb module must be maintained and current.
    • it doesn't matter if it's "supported," but it must be maintained.
    • would be nice if the commercial Puppet Enterprise product used the same modules since it would ensure that both were most reliable and best maintained.
  • Ewoud explains the Foreman / Satellite / etc model:
    • periodically they take upstream projects and harden them for commercial release.
    • branding is always a challenge
    • they sometimes end up with temporary internal forks for security or other reasons
    • but overall everything is OSS first and downstream is just veneer on top
  • Saurabh will will look into the possibility of the Content team maintaining the module.
    • this would be interesting because CAT currently maintains only Supported modules, so it brings up the question about whether the module would end up supported. This doesn't make sense on its face since it's not used for PE, but we are starting to do OSP service engagements.
  • We talked about clarity about what "supported" means and who maintains what modules.
    • In context of our modules, "supported" means that a customer with an active support license can file a support ticket.
    • Just being in the puppetlabs namespace doesn't actually mean much.
    • The Content team maintains some of the Supported modules, but not all. They don't currently maintain anything that's not Supported.
    • (the best way to identify the team owning a module is the CODEOWNERS file)
    • Modules that are not marked as Supported are "best-effort" at best. Any employee who wants to step up and maintain a module can do the work.
    • The current work prompting this discussion is marking modules clearly with README preambles indicating what their support levels are.

December 12, 2023

Agenda:

  • What would be useful to see on Forge user profiles?
    • A list of all the module’s you’ve downloaded?
    • Which of the modules you use that need to be updated?
  • Is there a better home for this doc?
    • Github wiki page?
    • I’d like collaborative real time editing, but could live without it

Notes:

  • We decided to trial moving the agenda/notes doc to this Wiki space

    • actionable items will be tracked as tickets
    • @binford2k will write a simple bookmarklet making it quick to file the tickets

  • What are some things that people are looking at for the Forge?

    • @bastelfreak could not make it it but he has some questions:
      • there's no concept of orgs, just users. and that creates some problems, is there a plan to introduce orgs
        • This would make account management a lot easier. People wouldn't have to juggle different accounts and risk losing a shared account when someone left the company.
        • Not currently on the committed roadmap, but high on the list of possibilities.
      • I think it's an important metric how often a module is used by others (a reverse dependency tree). This was also discussed in the past. Are there plans to implement this?
        • This would help people understand the usage patterns of a module and know how trusted it is.
        • We have the tooling to do it now, so the ask is to expose this on the Forge.
        • Not currently on the committed roadmap, but high on the list of possibilities.
      • Quality checks got disabled some time ago. Will they come back and will there be more puppet-lint plugins used to validate the code?
        • We turned off the display of quality checks because the raw output of puppet-lint is kind of intimidating and misleading to inexperienced users. The Forge still uses them to calculate the quality score, we just don't display them.
        • This was an intentional regression, but the plan was to improve the output of puppet-lint and the like, then turn back on an improved version.
        • The second half of this project didn't actually happen due to org changes, including the acquisition.
    • Module ratings? We tried that in the past, but few people bothered to use it.
      • Are there ways to make a ranking more useful and get more people consistently rank modules?
      • If it was available several of the people on the call would use it, but maybe not consistently.
      • One reason why people don't use it is probably that it's hard to reduce the idea of quality to a star ranking. Often "fit for my purpose" is more important.
      • Usage is probably more important -- how many people actually choose to use a module.
        • When we add subscriptions to the forge, we should expose the number of subscriptions a module has
        • Usage telemetry will show how many people are using the module in production
        • Stars and Followers on Github

  • Discussion around dependency management

    • We discussed the idea of a reverse dependency, essentially how many modules depend on my module. It helps us understand how good my module is
    • We also discussed how Forge can help us perform dependency resolution - I start with a list of modules and Forge can create a Puppetfile for me with the required modules
    • Another use case we discussed was that If I have a underlying module which has had a new release and the upstream module is incompatible with the new release, I can look into upgrading the dependent module

  • What would be most useful to Forge profiles and logged in user accounts

    • Ease of access - Forge should be able to help me access certain modules faster
    • Watch Module - Forge should keep me posted about certain modules
    • I can subscribe to issues e.g. open issues once closed, let me know so I can upgrade to the recent version

  • Quick walkthrough of the Forge user profile page

    • table of modules used with the version you have installed, latest version, release date, notes, etc.
    • Long very quick moving conversation about ideas -- I couldn't keep up!
    • an individual might be involved in multiple org infrastructures so tracking individual module lists isn't helpful. Would be nice to have org profiles too.
    • Should use Puppetfiles to indicate my own module usage.
    • This requires the use of a token to track r10k downloads.
    • Whatever we do, don't break existing usage!!!

  • Would be nice to encourage authors to follow semver

    • a checkbox on publish? Nice, but only accounts for manually published modules.
    • Maybe metadata.json should have a follows_semver = true setting.

November 14, 2023

Agenda:

  • Rspec-puppet and puppet-lint status
  • Process for communicating and making decisions like ^^
  • Razor project interest?
  • puppetlabs-testing “9-arm” architecture

Notes:

  • Follow up with the SDP lists? What is going on with them now.
  • We need to publish a platform support roadmap – even without dates

October 10, 2023

Agenda:

  • What's the status of the Puppetdb module
  • Puppet is forking and renaming tools like puppet-lint, etc

Notes:

  • The puppetdb module has a few very old pull requests that need to be reviewed.
  • Is Puppet changing names? The marketing endorsed name is now "Puppet by Perforce" but there's not a good reason to change namespaces or the like.
  • When we do disruptive things like changing tool names, we need to do so with more community input. Propose a plan with a timeline and share it with the community with plenty of time for feedback and refinement. This could be posted as an issue on the repo and then shared via slack and all the mailing lists. puppet-users@, voxpuli@, etc.
  • Some Puppet partner emails and support accounts seem to have been lost.
  • Can we share quarterly commits and roadmap with partners (and maybe Vox PMC?)
  • The support lifecycle is STILL confusing. We should do a lifecycle graph like the ones on https://access.redhat.com/support/policy/updates/errata/ that highlight PE, Puppet, PDK, etc. lifecycles.
  • Vox Pupuli is now maintaining docker images for puppetdb and puppetserver.

August 8, 2023

Agenda:

  • The three deprecated windows modules (6/26/2023)
    • puppet-windows_env
    • puppet-sslcertificate
    • Puppet-windows_eventlog
  • More conversation about puppetlabs-kubernetes vs puppet-k8s *

Notes:

  • puppetlabs-kubernetes vs puppet-k8s
    • Puppet-k8s is better maintained and more current
    • Doesn't need docker installed
  • Can the Forge add a visual indicator for "stale" modules?
    • Automatic / human generated / community suggested
    • Should this be exposed on the quality score tab
  • What's the deal with Jira? Where do tickets get filed?
    • Long rambling story about how we got where we are.
    • Our Jira admin is testing a sync solution
    • Should have public issues turned back on this or next week 🤞
  • When will the new Ubuntu packages hit?
    • No roadmap changes
    • Late august or so

July 11, 2023

Agenda:

Notes:

  • Modules should maintain the "principle of least surprise" with regards to how they manage features across different OS. Behaviours should be the same regardless of of the OS and config files should be as similar as possible, without violating OS file layout expectations. Romain will write up a style guide update as a PR and share it on the mailing list for conversation.
  • Repo labels should be standardized across the community (vox, puppetlabs) again. Tim and Romain are looking at reviving the Vox Pupuli Tasks tool that can help maintain this. In the meantime, we'll start consolidating differences.
  • David's going to work on definitions and policy for helping to decide which versions of a piece of software our modules will support.
  • Our CONTRIBUTING.md doc needs updated to cover different teams' policies for accepting PRs.

June 13, 2023

Agenda:

May 9, 2023

Agenda:

  • May the Source Be With You recap
    • Can we get Vox more involved in future events?
    • Biannual events, this and Hacktoberfest
  • Pupptoberfest?
  • Public Jira vs. GitHub
    • Ben is proposing moving to public github instead of jira
    • Closer to code
    • Devs already have github accounts
    • Puppet engineers have to sync to internal tracking tickets anyway
    • Validating that this matches community interest – it does.
  • Mass modulesync for Puppet 8?
    • Some housekeeping to go before updating
    • A ton of open PRs to go
    • GitHub is gonna think that Tim is a bot again
    • Tim will send email to vox list and puppet-users
  • Vox may be deprecating several windows modules
    • See the windows modules on this email
    • They don't use Windows, don't have interaction, and don't have the infra to test
    • Can Puppet adopt them like we did IIS?
    • We will look and evaluate them.
    • Robert will also get a list of the windows modules that betadot is using
    • Most of these modules have broken tests and have been quite for more than a year.
  • Should we create "special interest" github groups, eg for windows, on the vox pupuli github group?
    • Maybe send out an email to judge interest
  • What happened to the conversation about consolidating module|pdk sync process to simplify and unify again?
    • Craig and Tim have been talking, but are still in evaluation stage
  • Puppet 8 broke things again
    • Can we get Vox directly in the Product - Eng Leadership release planning meetings?
    • The email Josh sent was useful, but it didn't have specifics like a release date or an rc for testing.
    • **Can we get rubygem release candidates for majors? **
      • It would be really helpful to highlight how valuable the CAT release candidates have been.
  • Community would like to be able to help with new OS platform testing. Can we enable that somehow?

April 11, 2023

Agenda:

March 14, 2023

Agenda:

  • Discuss PR approval within Puppet GitHub Org
    • Each person not being a Puppet member needs their PR approved before CI runs, until at least one of their changes is merged.
    • For Vox Pupuli, this is only required for new GitHub accounts
  • RubyGems and Puppet 8 (Ruby 3.2) - especially the ones needed for testing. (tuxmea)
  • Legacy facts testing etc. (afisher)
    • Should we add an option to facter/puppet 7 to "preview"
  • Stdlib ensure_packages function fix (afisher)
  • PMC election update? (or did I miss something!?)
  • Puppetlabs-apt module release with bugfix for apt::pin? (tuxmea)
  • Any recommendations on how to deal with unresponsive git owners? (e.g. https://github.com/dgolja/golja-gnupg) (tuxmea)

February 14, 2023

Agenda:

Notes:

December 13, 2022

Agenda:

  • Sponsoring travel for Puppet Champions
  • CfgMgmtCamp
    • Community Day
    • Vox Pupuli elections?
  • Nigel

Notes:

  • to order more hoodies and tshirts for cfgmgmtcampt
    • Look into fingerpuppets
  • Can we get a PE / SA / Support engineer at cfgmgmtcamp?
  • Workshop session: content/module support strategies
    • to send proposal to mailing list
  • Can Dimitri and/or Edwin attend cfgmgmtcamp?
  • to check with about being election officer
  • Get Martin a list of platform engineering events

December 13, 2022

Agenda:

  • Sponsoring travel for Puppet Champions
  • CfgMgmtCamp
    • Community Day or Contributor Summit
    • Vox Pupuli elections?
  • R10k maintenance
  • Puppet-module-gems
  • Puppet 8 changes and deprecations
  • Docker hub images

Notes:

  • to work on community budget for Puppet Champion sponsorships for conference presentations and such.
  • Blog posts and content about vox and the duties of the PMC to set the stage for potentially kicking off elections at CfgMgmtCamp
  • The difference between Community Day and Contributor Summit would be mostly in branding. They'd share the same core of content (workshops, upcoming features/changes, Q&A, etc) but if we did Summit, we'd also do community recognition, VIP awards for the year, and such.
  • The r10k incident was clumsily handled, but well intended. Puppet has been tightening our focus for some years, such that we can do fewer things better instead of spreading ourselves out too thinly. The feature-freeze of r10k was intended as a transparency attempt to try to convey that we would not be developing more non-PE features. This has been walked back, and decisions on that project will be delayed until Q1-2 after a Product review.
  • Container discussion https://groups.io/g/voxpupuli/topic/docker_hub_images/95647628?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,95647628,previd%3D1670947882205059555,nextid%3D1602699896869404675&previd=1670947882205059555&nextid=1602699896869404675

October 11, 2022

Agenda:

  • Module gems
  • Webhook queuing
  • SPI application
  • hacktoberfest

Notes:

  • Content team should have synced with Vox about the implementation of the puppet-module-gems improvements
    • Paula and/or Craig will be attending syncs in the future, that should help convey some of the nuances
  • The webhook queue issue has been filed, but it's not on the project board.
    • Alex will talk with David about getting it prioritized
    • Ben's considering learning some Go and contributing an implementation as part of Hacktoberfest, lol
  • Don't necessarily need to wait on SPI to send swag
    • Send tshirts and stickers to Tim for cfgmgmtcamp
      • Ship some directly to the university, some to Tim's house
    • Order puppets, maybe Ben can bring them along?
  • Can Puppet pay for GCP credits for Vox? Can we let vox run integration tests on our GCP?
  • Ben will post an invitation to run a hackathon in #voxpupuli
    • None of the PMC has bandwidth to run an event, but we could coach a bit
  • Ben to share link to community council recording

September 13, 2022

Agenda:

  • Community Council
  • Non profit status
  • elections

Notes:

  • Working on SPI application – time is the blocker
  • We'll plan on kicking off elections at CfgMgmtCamp (fingers crossed)
  • If Puppet does Hacktoberfest hackathon, we'll include Vox

Action items

  • Alex will file an issue on the webhook project starting conversation about what's needed before we can adopt it as default.
  • Ewoud will suggest the systemd queue
  • Ben to investigate the possibility of a Puppet engineer contributing a queuing mechanism to the webhook
  • Ben to follow up on [MODULES-11161] and puppetlabs_spec_helper PRs

Aug 9, 2022

Agenda:

Notes:

  • Puppet lookup broken – scope from node classifier no longer available

Jun 14, 2022

Agenda:

  • Deferred functions shortcomings

Notes:

  • Follow up with Josh and see if we can close
  • Developer ecosystem needs support
    • Tools like facterdb, puppet lint, etc are getting hairy
    • Puppet should invest more dev resources into these tools
    • Current challenge is that the same team supports both tooling and content
    • Puppet is investigating options for freeing up dev time for tooling
  • https://github.com/puppetlabs/puppetlabs-stdlib/pull/1244
    • May cause subtle changes in containment
    • Long discussion about whether that's appropriate or not
    • We don't want to -change- behaviour, but we also don't want to be held back by trying to maintain undefined behaviour.
    • Ben to add a comment to the PR

May 10, 2022

Agenda:

  • Puppet & packaging version mismatch
    • The mismatch was accidental. It's only happened ~4 times since we did the full vendored ruby package.
    • Internal conversation about it, but no updates yet.
  • Forge IP change
    • Happened too fast, Community and Enterprise customers need more time to adapt.
  • Github stale bot
    • The bot closing open PRs feels antagonistic to community.
    • We see the point of keeping things orderly and lot leaving things in a grey indeterminate state, but this is too abrupt.
    • Can the bot set a label instead of closing? That leaves it available to filter.
  • Unsupported module repositories
    • Our puppet module repositories don't make it clear which are supported, which are actively maintained, which have no owners etc.
    • Working on a proposal to clean this up
    • Module repositories will be labeled with their actual support
    • Relay workflow will audit them to ensure that the Forge page matches, the labels are consistent, and the README has the comment explaining it's support.

Notes:

April 12, 2022

Agenda:

Notes:

March 8, 2022

Agenda:

Notes:

  • Puppetserver metrics in prometheus; can DIO do some blogs posts about it or share their configurations?

February 8, 2022

Agenda:

  • Raphink moving on; let's send him a gift.
  • Software in the Public Interest status
  • Language style guide steering committee
  • Elections update
  • Puppet-lint update

Notes:

  • SPI application in, they should be considering us next week
  • Puppet-lint release coming this/next week.
    • If we include the pr to drop ruby 2.3, then we should do a major version
    • Should we do a 2.6 with GHA annotations so that older ruby users benefit from the annotations, and also a 3.0 with the ruby version bump?
  • We should decouple developer tooling from test/ci tooling. If we standardize on the test framework and scaffolding that the PDK generates, then we don't need the full PDK to do the testing in CI – can use the shared github actions or anything else.
  • Check on the client id/secret in puppet–blacksmith. Can they be removed?

January 11, 2022

Agenda:

Notes:

December 14, 2021

Agenda:

Notes:

  • Support KB articles on https://puppet.com/blog/puppet-response-to-remote-code-execution-vulnerability-cve-2021-44228/ are behind the paywall. They probably should not be!
  • SPI is almost done. They can pay invoices or reimburse payments. They probably won't be able to do monthly stipends for PMC members, so we'll have to come up with another solution for that.
    • Swag, conference attendance, etc
    • Issue bounty – is it a conflict of interest for the PMC to assign values and also benefit from them?
    • Put together a proposal for a bounty process and discuss in July
    • Will need some legal review for the bounty payment process
  • Vox Puppet lint checks list is in a pretty good state
    • strict indent plugin should be fixed

November 9, 2021

Agenda:

  • Software in the Public Interest status
  • Module "quality" definition

Notes:

  • Send survey to Test Pilot list and Vox Pupuli list
  • Once we have a standard set of puppet-lint checks, they should be rolled into puppet-lint proper
    • Improve configuration for puppet-lint so that checks can be more easily configured and can be set to not be on by default
    • Improve the indentation check

October 12, 2021

Agenda:

Notes:

  • We will release a ruby3 packaged pdk, but not officially support it yet
  • puppet-module-gems to be deprecated as the problem that it solves hasn't been relevant for years
  • Collaborative design doc for PDK architecture and module "setup" frameworks
  • Containerized approach is valid & worthwhile, but perhaps maybe not required.
  • Trusted Contributors
    • Need more/better review guidelines -- especially on different repos
    • Better responsiveness when reviews are requested
    • How can trusted contributors request a review from Puppet teams?
    • Better major release planning and execution
    • Support lifecycle discussion

September 14, 2021

Agenda:

  • Puppetize checkin -- anyone need anything?
  • Revive non-profit conversation
  • CLA update

Notes:

  • Put zoom link in doc
  • Tim may have applied to github sponsorship as the vox org.
  • OSI might be an option for non-profit funding too
  • 80 members in 2016 -> 162 members today
  • Swag for new contributors
  • Thank Maggie for r10k patch on friday (https://github.com/puppetlabs/r10k/pull/1216)
  • Follow up with Tim's security report and see why it's not getting to the list
    • First send attempt was last october!

July 13, 2021

Agenda:

  • Puppetize
  • CLA update
  • Razor / r10k / attic
  • Lauren's news

Notes:

  • Can Puppet adopt Puppetfile resolver?
  • Check on whether prerecorded talks are required for Puppetize
  • Should we migrate binford2k/node_encrypt to vox?
  • Can we use Github actions or templates to remind folks to submit PRs and issues to the puppetlabs forks of lint / rspec?

July 13, 2021

Agenda:

  • Open for feedback on the new Puppet Content Templating system and how it can help Vox with module creation
  • Start a conversation about scoping/designing a pdk update/pdksync for Vox based on the Puppet Content Template system
  • rspec-puppet/puppet-lint
  • David S
  • Vox Pupuli recruiting

Notes:

  • rspec-puppet/puppet-lint conversation - about how to maintain moving forward

    Could Puppet internal team take ownership? privileges to tag releases moving on (fewer ppl in this group) should we fork (hoping to be able to add more collaborators)?

  • Option 1 - reconfigure pipeline and release under a different name?

  • Option 2 - fork repo (not ideal but perhaps necessary) to be able to continue working on it.

  • Currently: leaving it until we can’t any longer

    Perception - is community surprised that it isn’t owned by Puppet? Baked into PDK (but a lot are)

  • Let’s find ways to build awareness around templating system (PCT) -- the best place to share the news Google User Groups, slack announcement channel (stagger these to be more timezone friendly), IRC, PRs in repos ppl monitor, in person demos of ppl using something!

    • (blog, twitch, office hours, casual chat via Slack) vs. formal marketing effort
    • It would be nice if we could combine code bases to avoid confusions
    • Goal - to be less difficult to get started and avoid the multiple ways of doing something but allowing for those if need be
    • Telemetry and tracking concern
    • The work to move over to PDK is a blocker in itself

  • Recruitment - how to encourage _active _membership… plan to execute

    • The amount of modules we have is massive, impossible to know what all of them are
    • It’s hard to encourage that participation to someone who is _new _
    • Direct feedback of not understanding website at the beginning

  • Trusted Contributor Program: When get stuck, who to reach out to?

    • List of folks who are owners or subject matter experts

Action items:

  • Set a timeline for when to decide what to do about rspec/lint
  • Does David have any repos that we need to transfer?
  • Vox folks - play with PCT and give feedback to James as he designs and builds future iterations
    • How would folks prefer to provide this sort of feedback as James’ team builds this out? Surveys and direct feedback with users
  • Idea - review guide for PRs
  • Ben to follow up with Tim for Vox blog post
  • Ben to write PR review guide for https://voxpupuli.org/docs/reviewing_pr/
  • Ben to follow up with Ewoud about Trusted Contributors process
  • Lauren to follow up with Tim about twitch streams

Jun 8, 2021

(unrecorded)

May 11, 2021

Agenda:

  • We are exploring Community ownership for Razor. Does Vox have advice for building a maintainers group for it? Does Vox want to participate?
    • Coordinate knowledge transfer
    • RFC for vox community coordination
  • Introduce Lauren (new Director of Community)
  • 2021 PDK user study results
  • We should talk about that election thing…
    • Pick back up at the end of 2021
  • Trusted Contributors program

Notes:

  • Recruiting and sustainability conversation
    • CFP review committee for community day of Puppetize
    • Community member spotlight in the community newsletters?
    • Cool module or tool that we want to shout about?

Action items:

  • Ben: The vox homepage should probably have a "click here to get involved" call to action button
  • Ben: Add info about getting the fox logo on your github profile by making membership public
  • Ben: Read IRC backlog about Rangefinder -- should it be put into the GH marketplace? Can we publish the data usage info?
  • Ben: Update validate puppet versions
  • Nick: RFC for Vox / Razor community efforts

April 13, 2021

Agenda:

  • Trusted Contributor agreement
  • Puppet 5 support fully EOL by May 1
  • QA scores tab on Forge?
  • GitHub global maintainer summit (Kara's new gig)
  • We are exploring Community ownership for Razor. Does Vox have advice for building a maintainers group for it? Does Vox want to participate?
  • Vox is picking up a few major projects (Beaker, etc). Should we start talking about building in-org maintainer groups for these projects?
  • Short update about puppet_webhook
  • Quick question on CLA blog shout out (Lucy)
  • Discussions board

Notes:

  • Trusted Contributor agreement is getting run past Puppet legal, so may change text a bit, but then is ready for publication + communication (!!)
  • Took away QA scores on the Forge because they can be confusing or misleading, errors can be difficult for new module authors to parse, etc. But QA scoring metrics have improved since they were removed, so are being experimentally re-added.
    • It’d be nice if they had some info about how to become an approved module - seems like it’s not just all 5’s in module score, some other process
    • Approved has some meaning for the Puppet module team, so perhaps a new badge (like Community Supported) would not put burden on the Puppet module team but does indicate approval and support from a third party. The badge would be removed if users complain that it’s not actually being supported.
    • One possible flow Step one: community supported step two: community approved step three: puppet approved?
    • Don’t have the head count on the Puppet module team to do everything we want to here :(
    • The more of the badging process we can automate the better
  • in charge of Github maintainer summit, pretty much single handedly
    • Most folks don’t have bandwidth for a talk / have hit talk quota for the year
    • But most folks also planning on attending
    • Tim might do a talk on Vox (Do it Tim!!!), Ben might do one on CI?
  • CLA blog post call to action, want to encourage people to contribute, what’s the best way to point to Vox?
    • Sounds like Ben might already have a blog post in the works, and similarly might want to direct people to Vox. Is the webpage the best place?
    • More contributors always a good idea, how to get them always hard
    • Joining slack channel is a good place to start (puppet community #voxpupuli)
    • Github search query to apply filters to filter out a good amount of the PRs that don’t need active attention, to get to the PRs that do need review
    • People can ask in the slack channel what they can contribute (reviews, prs, etc.)
    • No intro-to-vox page on the vox website
  • Update about Puppet webhook
    • Tim talked to David, currently working fine no major issues, low maintenance at the moment
    • David will keep working on it
    • Tim published puppet module that deploys puppet webhook, now able to install the latest version of the webhook
    • Decommission ruby script in R10K module to use this instead (I think? Did I get that right?)
  • Razor!!!
    • Jeffery Miller of National Labs asked if Vox wanted to own it
    • Nick does not mind contributing, fixing bugs, etc. but doesn’t have bandwidth to manage other contributors, be full time maintainer on the project.
    • Nick and Jeff would work on the tool itself, if it was part of Vox then maybe someone like Trevor could just contribute more easily without as much overhead
    • Tim doesn’t know anyone within Vox that uses Razor, but if Nick is ok with kind of managing it within Vox that seems fine (Vox has definitely adopted similar tools successfully in the past)
    • Put together RFC
  • Maintainer orgs
    • Dedicated group for Beaker folks, and he’s on it
    • If anyone needs more perms on things related to Beaker, let Vox know in the slack channel
    • Bumping topic to next session
  • Using Zenhub for velocity, is Vox interested?
    • Maybe once we’ve set it up within Puppet can set it up for Vox as well
    • Use case: you have 10 repos, a bunch of issues that span repos are related (for example are part of an epic), and Zenhub allows you to see all the cross-repo issues and how those issues are proceeding
  • Heads up from Ben
    • We hired a community director, Lauren Lee. Very exciting! Her first day was yesterday, but hopefully she’ll be at the next meeting

Action items:

  • Tim will update the website to include a new getting-started-with-Vox page
    • Ben will help with copy
  • Someone (Lucy? Nick?) will write a quick RFC and run it past the Vox mailing list and ensure that there isn’t broad non-support
  • Ben will try to ask some folks with Razor knowledge to do a knowledge transfer to Nick (but not promises)

March 9, 2021

Agenda:

  • Should we open monthly sync to the public via Office Hours?
  • Content support policy published at forge.puppet.com/supported
  • What's going on with Vanagon? Can we get it documented?
  • Is David going to continue maintaining puppet-webhook?
    • Hope you all are having a good weekend. In case it hasn't been obvious, I have less and less time to focus on VP work, so while I intend to continue being a part of the community and maintain puppet-rsyslog and get back to puppet_webhook, I feel it is time to step down as a member of the PMC and let someone more involved take my place
  • Bintray is stopping free plans; how do we host packages?

Notes:

  • Bintray options:
    • Opensuse build services
    • Github packages
    • Puppet provides repository space
    • Puppet pays the Bintray bill
  • Bump minimum supported versions of Ruby to 2.4
  • Proposed new puppet-lint and rubocop checks

Action items:

  • Ben to set up Office Hours and share this agenda doc
  • Tim to talk to David about puppet-webhook
  • Ben to ask marketing about shop.puppet.com; can we improve international shipping?
  • Gene to chat with IT; Can we get our Jira behind a CDN to improve latency?

Jan 12, 2021

Agenda:

  • Introduce to Vox Pupuli folks
  • Gene and Jenkins module, testing, and Puppet 5 fun

Notes:

  • Talked about OS EoL issues along with Puppet 5 EoL
  • Alex is going to put together a list of Windows and Solaris modules they have but don’t test
  • Tim is getting a list BSD too

Action items:

Dec 8, 2020

Agenda:

  • Puppetize recap
  • CentOS 6 and Puppet 5
  • I18n

Notes:

Action items:

Nov 10, 2020

Agenda:

Notes:

  • More beaker repos to transition to vox
  • Puppetize booth
  • PMC elections

Action items:

  • Ben to follow up with Heather about possibility of a vendor booth
    • Too late, but we can add a bit to the developer experience booth
Add a custom footer

This agenda is a living document to record agenda items for upcoming meetings and notes or action items for past meetings. If you have a thing you'd like to talk about, add it as a comment on the relevant day, or if you have edit rights just add it directly to the agenda list.

Search for Vox Pupuli monthly sync on the Community Office Hours calendar to find the event time and then join this Zoom session.

Open to-do items are tracked as issues on this repository. A bookmarklet can make it quick and easy to submit issues from selected text. Create a bookmark and set its address or location to the javascript snippet below. Then select text directly on the notes page and open the bookmark.

javascript:var txt=window.getSelection().toString();window.open('https://github.com/voxpupuli/community-triage/issues/new?body='+txt,'_blank','popup');
Clone this wiki locally