| Follow @gregdek
DURHAM
Greg DeKoenigsberg is the Vice President of Community for Ansible, where he leads the company's relationship with the broader open source community. Greg brings to Ansible over a decade of open source product and community leadership, with the majority of this time spent building and leading communities for open source leader Red Hat. While at Red Hat, Greg served in various community leadership roles, including senior community architect, leader of the Fedora project, chair of the first Fedora Project Board, and Red Hat community liaison with the One Laptop Per Child project. More recently, Greg led community and product efforts for open source cloud pioneer Eucalyptus Systems.
Authored Comments
This. Exactly this.
Period.
Mailing lists are not complicated. They're ubiquitous and trivial to set up, and they *must* exist in a *basic* form as a precondition to any "official" community business.
It takes literally two minutes to start a Google Group that provides this functionality.
I agree: *serious* decisions about *ongoing* infrastructure should be delayed until stakeholders have a better idea of what they're trying to accomplish. But if you want transparency from the very beginning, then you should be archiving all important discussions *from the very beginning* -- in a way that allows new participants to come up to speed.
And that means, at the very least, a mailing list.