Papercuts

What is a Papercut?
A Papercut is a tiny issue - usually UI or UX - that is never a high priority but causes lots of pain to users. It might be a small bug or a missing bit of UI. It might be issues we tend to always hear about from users but do not have direct implications on the actual functionality and thus never make it into the bug priority list. It might be things that we look at and think “Ergh is this still not fixed?” or “%^&* that is SO ANNOYING”. We might have been looking at it for years.

We want to start fixing some of these so that we start bringing real joy to our users. Particularly as we work on performance and tech debt - features that users cannot see but are high priority. Fixing Papercuts is designed to bring sparkles in a world that often has few.

Process Trial [Edited 05.11 v1.2]

  1. Everyone can contribute issues to the Papercuts list by adding an issue to the ‘Potential Papercuts’ column of the Papercuts project.
    Before adding your Papercut please make sure it fits the following criteria:
  • The issue must be clearly specified using the appropriate Github templates
  • The issue must have a clear proposed solution.
  • If you are not sure, add it anyway. :slight_smile:
  1. @sauloperez @lin_d_hop and @Kirsten will meet to do a quick run through of all the Proposed Papercuts. A Papercut will be excluded off the list if:
  • It is not XS - it will take more than 1/2 day to complete
  • It is not obvious what the solution is - if we need to chat for more than 5 mins to decide on the solution
  • It is not specified using one of the templates (making it hard to read and follow).

If a Papercut is accepted for voting we will move it to ‘Next Up Papercuts’
If a Papercut is rejected we will move to ‘Rejected Papercuts’
Rejected papercuts will generally have a comment that explains why. If you make the necessary changes (or ask someone to help you) then afterwards feel free to move back to Potential Papercuts column.

  1. Every active* instance will be given the option to choose one Papercut from the list of Next Up Papercuts. These will be moved onto the Papercuts Backlog in Zenhub for the Devs to be able to choose from.
    Choose a papercut by adding your instance label to the papercut issue (as we did for s3 bugs).

  2. Each release one Papercut will be completed. The order in which this happens may well be random unless someone else suggests something better.

  3. If we like this trial then we’ll do it again :slight_smile:

This is an experiment. Please add your thoughts on what you like and don’t like below so that in the New Year we can improve the process.

Currently we have defined active* instances as: Australia, UK, France, Belgium, Katuma, Canada, US.
We have based this on who is contributing and who is trading.
If anyone thinks that their instance should also be on this list please say so. We can expand this list on the next iteration of this process.

2 Likes

I have a papercut! And 2 requests!

Can you add the US as an active instance? Our papercut can obvs wait.

Could you link to the bug and story templates? I think I know what you’re referring to but for future reference?

I guess I also need to be educated about Zenhub.

Hi @lauriewayne1

It’s pretty hard to miss the templates :slight_smile: If you create an issue you’ll have to choose one of them.

Before creating an issue it’s important to check if the issue already exists by searching Github. Perhaps the #bugs channel in Slack might be a good place to chat this through if it’s all new.

US is now part of the list :slight_smile:

I created labels in Github for each active instance to put on their selected papercut (will be using these for sev 3 bugs too).

Let’s kill those annoying things :metal: ! I’m sooo looking forward to this

Hoping I have put this in the right place.

Hi @lbwright22. Thanks!
No need to post the issue here. You can add to the Papercuts ‘Pipline’ when you create the issue:

I don’t think anyone other than gardener’s can move things along the pipeline @lin_d_hop, so someone with full access will need to do this. Ran into this same problem with the S3 bugs :frowning_face:

Hi everyone,
Just so you know the process has been updated and the next round of papercuts is ready for selection.
See the edited process above for more info…
Or just go here.

An important note… we only have 7 papercuts this round to choose from. If you aren’t fussed about the papercut that is selected for your instance feel free to not choose one and we’ll get to the next round of proposals faster :slight_smile: