<puppet news>

< bastelfreak> we prefer forks

I mean… sure?

:-D

open to interpretation

pitchforks?

I'm also good at setting stuff on fire https://p.bastelfreak.de/AnQTj/

what? your car?

ex-car

RIP

a long story :D

it once was my car

now it's my closing slide for presentations

and if you want to find out why, come to my talk at config management camp!

ok, so free access to hardened releases up to 25 nodes, is that PE for 25 nodes basically? or is it that I can't run puppet without paying for more then 25 nodes?

(or I have to build my own binaries)

https://aus.social/@redezem/113405485417259252 - placed here for reasons

if I had a printer I'd print it and put it on my wall

you can have virtual meeting backgrounds

(I solemnly swear, I'm up to no good, etc etc)

"Our technology team will use that focus to invest in projects that drive innovation and accelerate our product vision without sacrificing the stability or security of our commercial offerings. Key areas of investment include reimagining Puppet with the use of AI"

noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo

I really don't have a single customer. Neither PE nor open source, that wants this. they just want that their open issues and PRs are reviewed

+1000

I just want to manage configurations, not have some LLM running on my gear to make decisions without my input

I've read their statement a few times and its still unclear if we'll (debian) still be able to get the source code somewhere and ship it

all of the repos will remain under apache license in their current locations

funny how the main concern expressed by the blog post is about "the security of open source software", but shutting down the public package archives brings absolutely nothing towards security

so this is a new set of builds that are going to be maintained in addition to the existing AIO?

private forks will be made to build the EULA based packages