I'm wondering if maintainers listened to certain flags on tickets to notice "raised hands" for featues or bugfixes that are handed in for a review and discussion. Is there a special procedure in place for this?
I think it would be nice for all contributors to know how they should act while developing and what actions to take in order to trigger maintainer's attention. Whatever may be agreed upon as a possible procedure, it should allow for maintainers to spend a minimum of time to evaluate "raised hands" and take appropriate action.
What would you suggest?
Now like everybody doing it in own maneer.
I think we need to define approach for bugs and tasks
for bugs is like well described issue and procedure how to reproduce bug or issue
for tasks at least some background on what we trying to achieve with it
i think we should keep feature requests less strict to let people submit their ideas
I agree with your approach on handing in bug reports and feature requests. What I try to figure out is how folks trying to solve these bugs and implement feature requests would best approach maintainers. Since there is very few maintainers and they spend their spare time on VyOS project maintainance, I think there should be guidelines for folks (like me) on how to hand in code for review - and maybe how not to. This, I hope, would allow maintainers to accept more pull requests with less use of their valuable spare time.