[06:22:53] <_joe_> eoghan / jelto are we able to auto-upload debs from gitlab to a staging repo or is there something still blocking that? [07:22:18] Jelto is off until next week [07:23:35] _joe_: I'm actually planning to test my last change from that today. Let me grab you when I'm done getting the kids to school [07:23:46] <_joe_> eoghan: <3 [14:05:40] hello oncallers! As FYI I am merging https://gerrit.wikimedia.org/r/c/operations/puppet/+/1087421 to add a new port for the maps' TLS nginx config, it should be a no-op from the client side but in case something looks weird ping me [14:35:51] ACK, thanks! [16:34:42] https://www.puppet.com/blog/open-source-puppet-updates-2025 [16:38:25] o_O [16:40:21] I used to work at a company that had a strong open-source culture...it took private equity about 3 years to ruin that. How many years has it been since Puppet was bought out by private equity? ;P [16:44:51] I think my favorite paragraph is “As a team of engineers and builders, we need to prioritize innovation and acceleration of the delivery of our product direction. One of the ways we know we can do that is by reducing the frequency of commits to open source code.” [16:45:23] wat [16:46:40] :| [16:48:04] :facepalm: [16:55:13] If it's anything like my situation, they already laid off most of their "engineers and builders" and they'll try and coast off of locked-in Enterprise customers from here on out [17:00:54] <_joe_> perforce is probably 100x the size of puppet in terms of engineering teams [17:48:33] I think the best we can hope for at this point is passive neglect. More likely, they will continue to undermine the OSS product and alienate the community. Hard for me to imagine a scenario where things improve or even stay in their current state [19:33:08] I think that is likely, unfortunately it is a beast of a product, to "just fork"