{"id":3580,"date":"2017-02-12T19:24:53","date_gmt":"2017-02-12T18:24:53","guid":{"rendered":"https:\/\/www.devco.net\/?p=3580"},"modified":"2017-02-12T19:32:35","modified_gmt":"2017-02-12T18:32:35","slug":"choria-update","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2017\/02\/12\/choria-update.php","title":{"rendered":"Choria Update"},"content":{"rendered":"

Recently at Config Management Camp I’ve had many discussions about Orchestration, Playbooks and Choria, I thought it’s time for another update on it’s status.<\/p>\n

I am nearing version 1.0.0, there are a few things to deal with but it’s getting close. Foremost I wanted to get the project it’s own space on all the various locations like GitHub, Forge, etc.<\/p>\n

Inevitably this means getting a logo, it’s been a bit of a slog but after working through loads of feedback on Twitter and offers for assistance from various companies I decided to go to a private designer called Isaac Durazo<\/a> and the outcome can be seen below:<\/p>\n


\n 
\n<\/center><\/p>\n

The process of getting the logo was quite interesting and I am really pleased with the outcome, I’ll blog about that separately.<\/p>\n

Other than the logo the project now has it’s own GitHub organisation at https:\/\/github.com\/choria-io<\/a> and I have moved all the forge modules to it’s own space as well https:\/\/forge.puppet.com\/choria<\/a>.<\/p>\n

There are various other places the logo show up like in the Slack notifications and so forth.<\/p>\n

On the project front there’s a few improvements:<\/p>\n