We've had a couple of interesting developments in the codebase this week. Firstly, @jaswilli did an epic PR to switch our promise library from when to Bluebird, which we hope will bring improvements to both performance, and reliability. Secondly, @JoshWillik has refactored the Ghost startup, such that requiring Ghost no longer results in the express server starting. This moves us much closer to being useful as a package to include in other software and to exposing Ghost as express middleware.
0.5.1 Maintenance release
Triaging the backlog
Over the past couple of weeks, there's been an effort to triage and close as many old issues as possible and cleanup our backlog. Moving forward we want to be leaner and cleaner with what issues are open. Issues which are bugs and features or technical improvements we actively want to work on will live in the 0.5.x backlog. Bugs should be a priority, if they are true bugs we don't want them hanging around for longer than 1 release if possible.
Any longer term issues which are not actively ready to work on will live in the future backlog, this list will stay minimal and mostly be old issues with lots of history. Feature requests that aren't likely to be worked on in the near future will be closed in favour of a card on the public roadmap. The aim is to make it much, much clearer what issues are ready to be worked on and make the backlog much easier to digest and become familiar with.
We've been talking for a while now about having a concept of a 'Core Team': a group of contributors who lead development and help us to regularly ship high quality code. I have published an overview of the Core Team on the wiki which covers what it means and what makes someone likely to be considered for the role. In next week's meeting we'll announce who the first members will be.
End of Ghost-UI
Back in March we moved all of Ghost's SASS over to the Ghost-UI repository so that we no longer had a ruby dependency in the main Ghost repo. We hoped to turn the code into a Bootstrap-esque framework with reusable generic components.
Unfortunately this hasn't worked out. Managing issues across the two repositories is an administrative nightmare, and the switch to Ember means there's not really a good way to build components in a separate repo. This week we'll be switching Ghost-UI to use libsass to remove the ruby dependeny, and then move the SASS back to the Ghost repo.
In order to ship another feature release, we need to clean up after the GUI 2.0 design refresh (see
#3810), which in turn depends on us moving Ghost-UI back to the Ghost repo. Once this is done we hope to bash out a couple of the features which are made possible by the new Post Settings Menu design. We'll release 0.5.2 as soon as the bugs are fixed and we have a couple of worthy features ready to go.
What is this?
We hold a public development meeting pretty much every Tuesday at 5:30pm London time in the #ghost channel on freenode. In this meeting we discuss progress, important issues, and what is and isn't on the Roadmap. It's a chance for everyone to get involved and have their say about where Ghost goes next.
Hope to see you at next week's meeting: Tuesday 2nd September, 5:30pm London time.