I don’t frequent that world much these days, but I personally preferred the agent/pull model when I did. I can’t really articulate why, I think I feel comfortable knowing that the agent will run with the last known config on the machine, potentially correcting any misconfiguration even if the central host is down.

The big debate back in the day was Puppet vs. Chef (before Ansible/SaltStack). Puppet was more declarative, Chef more imperative.

I also admit, I don’t like YAML, other than for simple, mostly flat config and serializing.

I further admit that Ansible just has a bigger community these days, and that’s worth something. When I need to do a bit of CM these days, I use Ansible.

So wait… Did Puppet have a license change as well recently? Is this just preemptive because it looks like Perforce is starting to change things?

The Free Software Foundation requires “CLAs” as well. I have no fear that they’re going to rug-pull. I don’t think we can use that as the indicator. IMO, it’s even a good idea to have a CLA so that’s no conflict that the project owns the code.

The warning for me is if the project is run by a company, especially a VC-backed company. Joplin isn’t, so I would be comfortable using it (although I don’t).

JIRA Data Center: What am I? Chopped liver‽

https://www.atlassian.com/enterprise/data-center/jira

Agreed that JIRA is… not the greatest tool.