Help us decide the future of thechangelog/infrastructure

[gerhard]

In 2016 we open-sourced the code behind the new changelog.com, Changelog.com is Open Source, and we spoke about the related infrastructure work in Episode 254 but never open-sourced this code. The primary reason was that making it open-source friendly was low in the backlog and never made the cut. While good commit messages were used, and user stories with the right amount of what and why were written, the high level context remained diluted and fragmented.

Today, we are open-sourcing the code behind changelog.com infrastructure as is, and are giving you the opportunity to influence the way we continue investing our time. We need your help to decide on one of the following directions:

[gerhard]

Respond with 👍 if you would like us to make the current approach in thechangelog/infrastructure easy to understand and re-use.

[gerhard]

Respond with 👍 if you would like us to start from the beginning, with today's best tools, services and practices. All code will be public, developed iteratively, open and available to everyone willing to follow along. It's a fresh start with your involvement at every step.

[gerhard]

If you want to understand the big picture, read The code behind Changelog's infrastructure.

All your comments are welcome, I'll be hanging out in the #dev channel today if you prefer Slack over GitHub comments.

I am especially interested to hear from you if you think that this is a silly idea. At least one of us is bound to learn a great deal from that discussion 🙂

[phillipsj]

Nice move!

[jerodsanto]

I think we got the answers we were looking for here, thanks all! 💚💚💚