Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle opened issues 馃梼 #507

Closed
sbernard31 opened this issue Nov 30, 2020 · 4 comments
Closed

Handle opened issues 馃梼 #507

sbernard31 opened this issue Nov 30, 2020 · 4 comments

Comments

@sbernard31
Copy link
Contributor

I did some clean-up in opened issue.

First I tried to define if opened issues are enhancement, bug or question and labelled it in consequence.
For question, I tried to get some feedback from users and If I didn't get any answer after something like 1 month, I close and invite to reopen if needed.

For old issue, maybe the team should have a look, especially the ones which are labelled as "bug" to see if bugs still exists or should be fixed. (But I guess this should be done after we merge all PR ? 馃)

For recent issues, it would be good if the team could answer in "short" delay most of the time.
This shows that project is active and rewards user which takes time to give us feedback.
Generally there is not so much issue by days, so maybe taking few minutes by days is a good way and avoid to accumulate too many issues. I talked about answering not fixing or implementing user request immediately.
For easy to fix bug, being reactive could worth as those also show that project is really active and bring confidence.
Of course this is a open source project and so this is best effort and by the way I encourage to keep a rhythm that you could keep at long term.

@sbertin-telular, @rettichschnidi, @tuve, @qleisan Does it sounds good to you ? This is just advice so of course feel free to do as you can or prefer. 鈽猴笍

@qleisan
Copy link

qleisan commented Nov 30, 2020

Sounds good and my ambition is to be very active/responsive here. Putting a serious effort into specs and codebase to be able to deliver on that promise!

@sbernard31
Copy link
Contributor Author

I tried to flag some issues using label (enhancement, bug ...)
Do not hesitate to correct me if needed. 馃檹

@sbernard31
Copy link
Contributor Author

I feel we are back on track with this, all remaining issue are real one.
So maybe there is nothing more to do than just classic issue handling, in this case we can probably close this issue right ?

@qleisan
Copy link

qleisan commented Apr 1, 2021

yes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants