question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improving issue management

See original GitHub issue

Recently I’ve commented to issues here related with Jitsi camera / microphone / recording / integration with Dropbox, anything with the error message such as “all recorders are busy”, “grabación”, “ocupados”, everything that should be redirected to https://community.jitsi.org, not here.

Basically almost all of them is like one liner without useful information from a user, whose account was only created to leave a meaningless post like those. Dozens of duplicate are pilling up per day without a comment from a team member.

Though I am not related with the team in any way and just trying to help them as far as I could, I think a team member should engage with the stuff here in order to moderate this repository. Otherwise there would be no order and even a spam like https://github.com/jitsi/jitsi-meet/issues/6154 keep happening. It’s no good not only for the team (in terms of public image, public relations) but also for users here who submit legit bug reports.

I see 8x8 is not a large company but as long as you keep this place open, you are expected to engage with issues here. Who are in charge of that job at 8x8?

I would like to recommend you to consider how to manage this place. Here is just my proposal: a) keep this place open and moderate to maintain the order, b) make it only open to contributors from the repo’s setting menu and guide other users to https://community.jitsi.org (this should also have a category for foreign users who don’t speak English), etc. If the team would engage with users, I would happily like to keep helping. However, if the team is going to let the thing including spam happen as it does currently and let the bot close the issues after six month of inactivity, please let me know. Otherwise what I am doing is nothing more than a waste of time and energy.

Thank you very much for your consideration.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:6
  • Comments:16 (8 by maintainers)

github_iconTop GitHub Comments

3reactions
luixxiulcommented, May 12, 2020

I confirmed the request just now 😃

3reactions
l3d00mcommented, Apr 18, 2020

I think adding some interested users like you to help with moderating duplicates, adding labels etc. should already help a lot.

Not letting people report seems like a last resort option to me. That the devs don’t answer in a day or so doesn’t mean they couldn’t trace the issues at a later date. Especially considering how good Jitsi works despite the huge influx says a lot of how much work they probably have do to.

Having presorted issues from the community should a) help to get more dev responses as they don’t have to read through all the low effort and b) help to get higher quality issue reporting if done right.

Read more comments on GitHub >

github_iconTop Results From Across the Web

8 Steps for Better Issue Management - ProjectManager
Project issues are bound to happen; our 8 steps to better issue management will show you how to identify and manage those issues...
Read more >
Issue Management: 5 Steps for Creating an Effective Process
By conducting issue assessments, project managers and issue managers can reach better decisions about how to anticipate future challenges. This ...
Read more >
5 Tips to Improve Your Issue Management - Pmo365
5 Tips to Improve Your Issue Management · 1. Report issues early and check them frequently · 2. Use a cloud-based real-time issue...
Read more >
How a Solid Issue Management Process Can Help Your Team
Risk management: Assess risks to predict issues · 1. Identify the risk · 2. Analyze the risk · 3. Prioritize the risk ·...
Read more >
12 Best Practices for Effective Project Issue Management
12 Best Practices for Effective Project Issue Management · 1. Report The Issues Immediately · 2. Virtual Or Physical Log · 3. Setup...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found