Ben Cotton

5063 points

Lafayette, Indiana

Ben Cotton is a meteorologist by training, but weather makes a great hobby. Ben works as the Fedora Program Manager at Red Hat. He is the author of Program Management for Open Source Projects. Find him on Twitter (@FunnelFiasco) or at FunnelFiasco.com.

Open Sourcerer People's Choice Award Moderator's Choice Award 2017 Comment Gardener Cloud Linux Open science Python SysAdmin Community Manager Creative Commons Developer Fedora Contributor Club Author Open Organization Ambassador

Authored Content

Improve your DevOps security game with Ansible Vault

10 articles to enhance your security aptitude

Whether you're learning the first steps or looking to add to your skills, there's something for you in Opensource.com's top 10 security articles of 2019.

How to use CherryTree for note taking

CherryTree is an open source alternative to OneNote for keeping track of the things you need to know.

How Kubernetes became the solution for migrating legacy applications

Will your organization change itself to death?

Open organizations are adaptable, but the way they adapt to changing conditions can define (or destroy) them.

Managing changes in open source projects

Here's how to create a visible change process to support the community around an open source project.

IRC vs IRL: How to run a good IRC meeting

Internet Relay Chat meetings can be a great way to move a project forward if you follow these best practices.

Why your employees should be calling you out

If members of your organization are sharing their concerns about your behavior with everyone but you, they may no longer trust you're doing the right thing.

Authored Comments

bcotton

30 Sep 2020

Is it time to revise the Open Source Definition?

This is a really thoughtful article. I think the other thing that we would want to consider is data. We've focused on software for so long and it turns out that maybe the data is more important than the software. It's a mistake to assume that free software automatically protects user data.

bcotton

8 Sep 2020

How to install software with Ansible

> The logic used in the solution so far assumes that all hosts being configured by Ansible run the same OS

This is exactly why (also laziness) I haven't Ansible-ized the few non-Fedora machines I have. But your example assumes the packages are named identically between OSes. What do you recommend for handling cases where they're not?