Levi McGranahan, design system lead, hosted a call last week in which he summarized the progress the Rivet team has made toward the goals we laid out for Q1 2019 in the roadmap.

This blog post recaps the key takeaways from Levi’s Q1 progress report.

Goal: Hire a new front-end developer

Status: Done

Rachel O’Connor, formerly of the User Experience Office engineering team, has transitioned into the role of front-end developer for Rivet.

Rachel is still getting up to speed, but since joining the team she has closed a significant number of bugs and maintenance issues. Next quarter, she hopes to shift her focus to the feature requests in the backlog.

Goal: Establish a team project management process

Status: Done

Last year, developers made it clear that Rivet needed a consistent release schedule that they could plan their own workflows around. We resolved to implement a monthly release process, and we’re happy to say that we’ve done so — the end of March saw our third monthly release of 2019.

In addition, we’ve created a comprehensive new wiki that lays out our development, release, and issue tracking processes.

Goal: Increase backlog visibility and engagement

Status: Done

The new project management processes and contribution guidelines we put into place all center around the Rivet public backlog.

A new part of our process this year is soliciting upvotes from the community on feature requests in the backlog. We were encouraged to see more engagement with the backlog than we were expecting when we put out the first call for upvotes, and we hope engagement continues to increase as people become accustomed to this part of the process.

Goal: Establish and document a QA process

Status: Ongoing

On the back of Rivet’s migration to GitHub.com and Rachel’s hiring, we’ve been exploring ways we can leverage continuous integration (CI) tools to run automated tests on any code pushed to Rivet repos.

We’re currently testing a repeatable CI process with Rivet add-on repos like Rivet collapsible.

We’re also continuing to work on documentation on how we carry out manual testing of new or updated components. This documentation will be added to the Rivet wiki when completed.