Great to hear the Rainmeter team addresses all issues, even those with just a single confirmation ![:)]( "Smiler")
Unfortunately, that certainly isn't the norm - many many project teams tend not to address issue reports until they get sufficient traction. Indeed a super common response is to the effect of "this isn't affecting enough people to prioritize," thus users are actually encouraged to '+1" issues to indicate that they're affecting many.
Given that Github issues without responses are overwhelmingly an indication that they haven't been seen / are unplanned / etc, and that and there's no way for users to infer something has indeed been seen/considered, it might be worth someone from the team at least giving a quick confirmations, similar to this forum response. Otherwise the natural assumption is likely to be similar to above. Communication is key.
Unfortunately, that certainly isn't the norm - many many project teams tend not to address issue reports until they get sufficient traction. Indeed a super common response is to the effect of "this isn't affecting enough people to prioritize," thus users are actually encouraged to '+1" issues to indicate that they're affecting many.
Given that Github issues without responses are overwhelmingly an indication that they haven't been seen / are unplanned / etc, and that and there's no way for users to infer something has indeed been seen/considered, it might be worth someone from the team at least giving a quick confirmations, similar to this forum response. Otherwise the natural assumption is likely to be similar to above. Communication is key.
Statistics: Posted by ritary — Yesterday, 11:10 pm