First off, what is Issue Bash?

[ishanijerin1]

FANSHIP engineers' initiative to address the health of systems, teams, and individuals - Issue Bash
Hello, this is nonask from the PR team.

This is an interview series to help you get to know the people behind the fan development platform FANSHIP. Today, we spoke with the two top members, Sugii and Ueki, about "Issue Bash," which they say is the secret to the teamwork of FANSHIP's engineering team.

The talk will provide some useful tips for team teacher database building for both engineers and non-engineers, so be sure to read it.



──

Sugii:
One of the tools we use in development is called GitLab, and the issues registered there are called "issues."
We raise not only important issues, but also small bugs, so we end up with a lot of small issues. Issue Bash
was started with the goal of spending a whole day once a month tackling these small issues and cleaning them up.

Ueki:
"Bash" seems to mean something like a lively party, so I guess it's like an issue-busting festival.
It started about three years ago as a place to regularly clear low-priority tasks that were forever put off.
At first, we often competed to see how many tasks we could do in a day.

Sugii:
We've tried various things, such as renting a coworking space and holding meetings outside, but after about a year we started to run out of small issues and the number of people increased, so it started to become a bit stale, so we are now changing our purpose and methods.