Status of the 99 papercuts project

We are now on day 8 of our project 99 Papercuts, with 7 days to go.

From now until Monday, 19th September, you can participate in our 99 Papercuts Project and make Shopware better - one papercut at a time.

The feedback so far has been pretty good; we've already received several contributions and merged a good amount of pull requests. We also noticed increased activity in our IRC Channel, where you can get in touch with the Community.

You can help by reviewing the open pull requests and providing feedback.

New Pull Request Workflow

If you are a regular contributor to Shopware you may have noticed that we changed the pull request workflow for the time of the papercuts project.

Normally, when you open a pull request we will first schedule it. That means a script fetches the pull request's information and creates a ticket in our Issue Tracker. In one of our next scrum sprints, the team will place the tickets with the status "scheduled" into the sprint and work on it.

When a team member is working on your pull request he imports it from GitHub into our internal git system. We use the excellent Hub tool from the GitHub team for that. The final code review as well as QA will take place in our internal systems. If all of that is fine, the code will be merged into one of the mainline branches (at the time of writing either 5.2, or 5.3).

A cronjob will push the latest changes from our internal git system to GitHub where the pull request is then finally closed.

During the time of the papercuts project we changed that workflow. Pull Requests will be merged directly on GitHub into the dedicated 99-papercuts branch. A team member will perform the code review, test directly on GitHub and provide feedback if changes are necessary.

GitHub released a new feature just in time that supports this workflow quite well: Improved collaboration with Forks.

We use Travis CI to run our automated tests and Style CI to check that all the merged code adheres to our Coding Standards.

Tickets have already been created in our Issue Tracker, and we have no scheduling phase since we are all working on the papercuts project.

Get involved and participate

Now it's your turn. Find a papercut bug that bothers you and try to fix it.

Back to overview