i just don't buy the hardening line

I say that's marketing BS :D

and i think p4 is not being frank about their intentions here, and it's a bit frustrating

yeah

anyways, i'm happy to jump on a call and play the game where a free software activist rips his shirt open or whatever

or play the 'how could we really help you accomplish your goals while being in synergy with the free software community' line

but i feel that p4 has shipped out of that lane when they cut off people from slack

and now are waving from the open sea "bye bye suckers"

nah, they're trying to be closed source while keeping up the facade of open source for the goodwill

and this point I don't have faith they'll keep spending time on open source and they're just trying to do damage control

@David - I really hope you will reconsider and publish the point releases as gems. no one will use them for production anyway, but they are very important for testing and integration

ewoud: that's exactly why I'm concerned about more bad news in the future. corporate is clearly moving away from the free software community and does not want to keep spending that money

it sounds like Perforce is trying to pull a Broadcom

I appreciate for now I can only offer words and reassurances which are empty without actions but if you take me at my word that I believe Perforce and I do want to make this work and come to the townhall and EAB sessions to highlight issues (like the gems) and we can work out where we can support / invest / do things differently to make this a success.

What I keep thinking is, if I never got another new feature in puppetserver/agent/db I'd be fine (just security patches and agents-on-OSes). All the things I care about in the ecosystem are modules. Feels like the same moneygrab as Broadcom, but with less penalty if I just don't uptake their new world.

David: I don't blame you personally and I know you're just taking the blame. just want to make that obvious

ewoud: +1

it's a shitty situation, in shitty times

"we're letting you go but we hope you can work with us to make this a success"

I'm sorry that you don't have more to work with, its indeed a shitty situation

+1 thanks David to be here to talk with us

+1

just as I got a question on "note the gems like the packages won't be release at this point by Puppet" for clarity the gems like the packages will be published under the EULA

do you know how the EULA will effect CI runs?

and will we have to run CI jobs for EULA-packages/gems and open source packages/gems. that would be a lot.

it's too bad that the announcement didn't mention that gems on rubygems were also going away

I do wonder how do you enforce a eula on package or code repositories, besides managing credentials

I'm also worried about the contents of the EULA itself, I'm not expecting "community people" to have much input in this...

what a wild rollercoaster this week has been. And it's only Thursday!