Sure, let's start in the wiki. It should probably be in a more permanent place, but there's a FAQ item I have posted into issues already in the wiki somewhere, so that's probably a good starting place for this one too.
On Fri, Aug 21, 2015 at 3:18 AM, Thomas Andraschko <[email protected]> wrote: > sounds good! > Probably in the wiki or somewhere? > > 2015-08-20 22:31 GMT+02:00 Mike Kienenberger <[email protected]>: >> >> We should probably document our policy of closing issues somewhere and >> refer that that policy in each comment. >> >> - Issues older than 5 years are closed. >> - Issues needing reporter feedback are closed after 1 year >> - Enhancement/improvement Issues without a patch for maintenance mode >> branches are closed. >> >> On Thu, Aug 20, 2015 at 4:15 PM, Thomas Andraschko >> <[email protected]> wrote: >> > 4) i would probably close every ticket without feedback since 1 year. >> > >> > I will do 1-4 first, lets check 5) afterwards. >> > >> > Am Donnerstag, 20. August 2015 schrieb Mike Kienenberger : >> >> >> >> One more comment on 5). I've found that if I specifically ask for a >> >> patch that the reporter often submits one. So I'd prefer we try that >> >> approach first. In fact, we should get in the habit of doing so as >> >> soon as we first read an issue to encourage reporters to become >> >> involved in "scratching their own itch" and joining our community. >> >> >> >> On Thu, Aug 20, 2015 at 4:05 PM, Mike Kienenberger <[email protected]> >> >> wrote: >> >> > On Thu, Aug 20, 2015 at 3:58 PM, Thomas Andraschko >> >> > <[email protected]> wrote: >> >> >> 5) Close issues which are untouched and feedback would be required >> >> >> 5) is a little bit difficult. I will take a look at them as last a >> >> >> step >> >> >> and >> >> >> come back. >> >> > >> >> > Rather than closing these, I'd suggest we state that we need more >> >> > feedback or a patch. > >
