Ansible Lockdown Community Updates

[Jonathan Davila]

Hi everyone,

We (lockdown maintainer) have been hard a work recently trying to lay the foundation toward making this project easier to maintain, easier to use, and just better all around. With that, I'd like to make a few formal announcements. If you take issue/concern with anything mentioned, have an idea, suggestion, etc, please feel free to start a new mailing list thread, propose an agenda topic (instructions below), or open an GitHub issue in the Ansible Lockdown repo.

Announcements:

1. New maintainer: James Cassell, jamescassel on GitHub, is a new (as of a few weeks ago) maintainer to Ansible Lockdown. His contributions both in terms of code and opinion have been very helpful in helping the maturity and progression of this project.
2. New landing page for Lockdown. There is a landing page for the lockdown project that can be seen at https://ansiblelockdown.io. Issues/comments/edits desired for that page should be filed as GitHub issues at https://github.com/ansible/ansible-lockdown
3. Project Merger Pending. The incredible folks over at OpenStack (via Rackspace) have agreed to work toward collapsing the Ansible Hardening project into Ansible Lockdown in order to consolidate efforts. This includes things like making better docs, leveraging the OpenStack test infrastructure to provide better and wider test coverage among other excellent things. 
1. Meeting notes from our first discussion are in the public domain and can be found here.
4. New permanent logging for IRC. All discussions in the #ansible-lockdown IRC channel are now logged in real time and stored publicly here. 
5. New scheduled meeting as an official working group. Starting Nov 1st at 4pm UTC (12pm US Eastern), and every other week after that, we will begin to have regular IRC meetings on Freenode at #ansible-lockdown. 
1. Working Group details can be found here https://github.com/ansible/community/tree/master/group-lockdown
2. Desired Agenda items can be added by anyone by opening up an issue at https://github.com/ansible/community/issues
3. An iCal file can be grabbed from https://github.com/ansible/community/blob/master/meetings/ical/lockdown.ics
6. New project tracking. Maintainer driven projects/tasks/features/etc will be managed via Github Projects in the main Ansible Lockdown repo here https://github.com/ansible/ansible-lockdown/projects This doesn't have much as of the time of this post, but you should start seeing some activity over the coming weeks.
7. Code of Conduct As a formal sub-project of Ansible itself we fall fully under scope of Ansible's Code of Conduct. This project has had nothing but great contributors thus far, I'm leaving this here as a point of reference should any issues ever arise in the future (**crosses fingers**).

Cheers,

- Jonathan <@defionscode>