You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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!
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 ?
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.鈽猴笍
The text was updated successfully, but these errors were encountered: