yeah

i will make a PR

https://github.com/voxpupuli/puppet-ipset/pull/105 changed the label on the original MR to

enhancement

oops I meant https://github.com/voxpupuli/puppet-ipset/pull/109

Zhenech: once the recording is there, I challenge you to take a shot every time democratic or some variation of that word is used

I… ugh… nope

It's always DNS: https://github.com/theforeman/puppet-pulpcore/pull/364#issuecomment-2548217621

binford2k: thanks

we need a write up on what perforce is actually doing and what it means

i end up getting the same questions over and over again

anarcat i certainly would like an easy TL;DR; to share with my execs in laymans terms what it actually means for OSS Puppet

The meeting had marketing speak which basically said, "Perforce no longer wishes to spend money supporting open source anything. The community is welcome to do that"

OSS Puppet as it existed a couple months ago is dead

BTW. Is there a concrete date at which puppet will not provide OSS packages anymore?

this is the only official statement that I know of https://www.puppet.com/blog/open-source-puppet-updates-2025 and "early 2025" is all they seem to commit to

@TheMeier I think they already said that they won't publish new packages

you cant trust what they say anyway, assume its dead is the safest approach

asomerset: don't use Perforce tools anymore, switch to the forks

Also what RI says

I'll trust them on the negative things like "we don't do X (anymore)"

Although I'm a Puppet employee, I would like to ask a question from a personal standpoint. There's a lot of commentary about Puppet not providing "free" binaries and so, therefore, it's no longer OSS. My understanding of OSS, having been in the Unix/Linux industry since the early 90s, doesn't include anything about providing binaries. Only that source code is available, users can compile their own, can modify it themselves, can redistribute those binaries and/or changes, and (preferably) has a mechanism for contributing those modifications back (not that there's any guarantee those changes will be accepted). Back in the days when I was getting started all you ever got was source code and you always had to compile it yourself. In fact, to this day, as far as I'm aware you cannot download a binary Linux kernel from the Linux Foundation. Is the Linux kernel not OSS?

I think a bigger issue is that Perforce also indicated that the released gems wouldn't be accessible and I also wonder if releases will be published to https://downloads.puppet.com/

or at least, not without signing some EULA

it was always great that Puppet tarballs were signed with GPG signatures so you could verify it, quite crucial in today's world of supply chain attacks

also, for CI I think most people use those gems so it's entirely unclear to me how a development workflow would even work

i missed a lot of those messages because they were clipped

the problem is partly the binaries, but it's also the source code

from what i understand, the actual source code with security fixes (!) will be hidden behind a EULA

and while perforce claims that this code is still opensource, under the current license, that's rather irrelevant if you need to agree (and pay for) a EULA before accessing it