Preparing reps.mozilla.org for continuous delivery

The Mozilla Reps web development team is starting to move toward continuous delivery so that we can deliver features faster while maintaining or increasing the quality of code deployed to reps.mozilla.org.

Continuous deployment is the holy grail of application development. It reduces bottlenecks between stages of the development process, allowing the team to move faster and be pretty confident in the quality of the code. Once in place, it can also reduce the work to test and release new functionality. We think it’s a win for everyone.

It also means pushing every code change to a production environment (that’s the deployment part). Our team is interested in a variation of this called continuous delivery, which means that we have the ability to push to production at any time. This will give us more flexibility, since we’ll be able to separately make code changes and update the site when it is most convenient for the team.

What do we need to build to move to continuous delivery?

  • Continuous integration server
  • Source control commit check
  • Simple deployment script
  • Real-time alerting
  • Root cause analysis
  • Dark Launch and Feature Flipping
  • Redefine relationship between QA and WebDev
  • Re-evaluate branch management and staging environments
  • Higher standards for code reviews

Giorgos has provided more information about each of these, and I will publish another post that goes into detail about each one.

This is a big undertaking, and it will take us several months to fully implement continuous delivery. If you’d like to give feedback or ask questions about this project, please post in the discussion forum or stop by #remo-dev on IRC. You can also follow along with the project by watching our tracking bug.

A new homepage for mozillians.org

[This is a re-post of a post that originally appeared on the Mozilla about:community blog]

There are two big changes to mozillians.org, our community directory, this week. We launched a new design for the homepage and we also updated the style across the whole site.

The new Mozillians homepage allows you to search for Mozillians with public profiles.

The new Mozillians homepage allows you to search for Mozillians with public profiles.

A redesigned homepage

Public search: A few months ago we rolled out the ability to have public profiles, and now you can search for those profiles without logging into the site. If you haven’t already, now is a good time to edit your profile so it shows up in public search results. This will make it easier for Mozillians as well as your friends and family to see your profile.

Better browsing: Browsing through groups and functional areas is improved, including the option to sort groups in different ways.

Announcements: To better share future changes to mozillians.org, we have added an announcements section on the homepage for logged-in users. When there aren’t any announcements to show, you’ll see some fun facts about Mozillians based on information in the database.

    The new logged-in view lets you browse groups more easily and also shows announcements.

The new logged-in view lets you browse groups more easily and also shows announcements.

A new look

As we were redesigning the homepage, it also made sense to update the styles on the whole site. We worked with the fantastic Brand Engagement team on the visuals and direction. We especially love their Style Guide, which made the styling much easier for us.

Take it for a spin

As with many site redesigns, this is a large release with big changes to our codebase. If you see anything that looks weird, we’d like to make it better. Please file a bug and we’ll look into it.

Mozillians, this site is for you. All 3,500+ Mozilla volunteers and paid staff. We hope you enjoy the new homepage and styles for the site. And we’ve just begun. We’ll be fixing minor UI bugs and giving profiles some attention in a redesign soon.

Thanks

A round of applause to Kaustav Das Modak, MichaƂ Frontczak, Sambit Roy, Vuyisile Ndlovu, John Kim, and Tomer Cohen as well as the Community Tools team who helped with this release.