- #Relax sounds open source app android studio github how to#
- #Relax sounds open source app android studio github code#
You’ll get to it later when you have more time.
If you merge this PR now, you might wind up with even more issues tomorrow, because you broke someone else’s workflow by solving this one person’s (very edge-casey) problem. Or maybe the PR made the project too confusing for new users, because it excessively complicated the API surface. Maybe the tests passed, but the performance degraded by a factor of ten. In the past, you’ve merged a PR without fully evaluating it, and in the end it led to new headaches because of problems you failed to foresee. However, you’ve been burned by that before. The Travis tests passed, and so you’re tempted to just say " LGTM" and merge the pull request. You know that this person put a lot of work into their solution, and it’s probably a reasonable one. Unfortunately the issue is complicated, and so their PR contains many paragraphs of prose explaining it.Īgain, your eye darts to the hundreds of people still waiting in line. They’ve run into a very esoteric issue and have proposed a pull request to fix it. You recognize their name from various community forums and sibling projects. The next person is a regular contributor. Stack Overflow? The wiki? The mailing list? After a few minutes of Googling, you paste a link and close the issue. You know you’ve seen this error a few times before, but can’t quite recall where the solution was posted. The next person has run into a very common error, with an easy workaround. If there’s a bug in the code, please submit a reproducible test case or a PR.” You simply say, “This is an open-source project, and it’s maintained by volunteers. You don’t waste a lot of time on this person. Their vitriol gives you a bad feeling in the pit of your stomach. They spew out complaints about how your project wasted 2 hours of their life because a certain API didn’t work as advertised. The next person in line has a frown on their face. You also cheerfully suggest that they try Stack Overflow or the Slack channel instead. You could spend a half-hour trying to understand this person’s code, or you could just skim through it and offer some links to tutorials and documentation, on the off-chance that it will help solve their problem.
Wearily, you glance at the hundreds of other folks waiting in line behind them. Either way, you struggle to understand the paragraphs of text they’ve posted. Maybe this person doesn’t speak English as a first language, or maybe they have a disability that makes it difficult for them to communicate via writing.
#Relax sounds open source app android studio github code#
But it’s still a lot of code to read.Īlso, their description of the problem is a bit hard to understand. Helpfully, you edit their comment to add a code block, so that it’s nicely formatted.
#Relax sounds open source app android studio github how to#
They’ve pasted their code into a GitHub comment, but they forgot or didn’t know how to format it, so their code is a big unreadable mess. They’re well-meaning enough they tried to use your project but ran into some confusion over the API. When you manage to find some spare time, you open the door to the first person. Maybe you had a hard day at work, or you’re tired, or you’re just trying to enjoy a weekend with your family and friends.īut if you go to /notifications, there’s a constant reminder of how many people are waiting: You want to help all of them, but for now you’re putting it off. They are patiently waiting for you to answer their questions, complaints, pull requests, and feature requests. Outside your door stands a line of a few hundred people.