Often times the issue filler has no knowledge or time to actually fix anything. In an ideal world they would provide patches but it's not possible. (Not to mention I had a ton of patches grow stale in the Oracle Bugzilla so even a patch doesn't do much actually).
Maybe we need a NetBUG program similar to the NetCAT program? Specific periods of time when it's all about bug fixing / triaging? Not sure... Bounties was an idea, but depends on scale I think. I have some NetBeans bounties on the CoolBeans site and nobody ever claimed them (1 single person asked some questions but didn't start work). --emi On Mon, Aug 12, 2019 at 5:11 PM Geertjan Wielenga <geert...@apache.org> wrote: > > Hi all, > > There's understandable frustration by people reporting issues ( such as our > issue filer hero Chris Lenz :-) ) about issues being filed and not being > responded to. > > Partly, I think that simply filing issues and then moving on, and then > being upset when no one picks up the issues, is suboptimal (i.e., the filer > should I think go further than that) but at the same time it is > understandable that the filer then becomes increasingly frustrated. > > How can we handle this situation? > > Maybe we can create tribes around certain areas and then have the tribes > work together to respond to issues, create specifications, lead discussions > on the mailing list, and implement the technical solutions together? > > Or, what can be done, what's the right approach to take? > > Thanks, > > Gj --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
