[mapserver-dev] [EXTERNAL] Re: MOTION: Run script to close tickets more than one year without activity

Mon Mar 24 15:14:56 PDT 2014

Hi,

There seems to be 21 pages of open tickets. More than one year old issues seem to start from page 3
https://github.com/mapserver/mapserver/issues?page=3&state=open
Everything starting from page 5 they are at least two years old and they are imported from the Trac by mapserver-bot.
https://github.com/mapserver/mapserver/issues?page=5&state=open
How about to close the imported trac issues now and follow the situation with the remaining issues for half a year or so? The issues which are created in the trac are unlikely to receive activity from the creators because they may not even have Github accounts and it would require quite a lot of interest to show activity in Github.

Somehow I feel that great deal of the problem is that ticket handling routine went broken on the developer side when it was moved from Trac into Github. Developers have fixed whole lot of issues which have never been closed. There are lots of cases like this https://github.com/mapserver/mapserver/issues/4017
Perhaps the routine works now again with the issues which have been living in Github all the time.

-Jukka Rahkonen-

Smith, Michael ERDC-RDE-CRREL-NH wrote:

> Jukka,
> 
> I don¹t think there is a limit of the number that can be open, but there are a lot
> of old tickets that really should be closed. Some of them should legitimately still
> be open but I think (personal opinion here) that there are far more of the ³need
> to be closed² variety than ones that need to be reopened.
> 
> It should be noted that having the automated script close the ticket is not an
> indication that the ticket is not valid. It just means that the devs don¹t know that
> this is still valid/important and there has not been activity on it for some time.
> Users should not take it in any kind of negative way. Its just a way to trying to
> determine what is still relevant and what might no longer be. Anyone interested
> in keeping a ticket from being closed via the script has a very simple means of
> doing so, just post some (any) activity to the ticket.
> 
> In my opinion, I think this is a good thing.
> 
> +1
> 
> Mike
> 
> --
> Michael Smith
> 
> US Army Corps
> Remote Sensing GIS/Center
> 
> 
> 
> On 3/24/14, 5:52 PM, "Rahkonen Jukka  (Tike)" <jukka.rahkonen at mmmtike.fi>
> wrote:
> 
> >Hi,
> >
> >Please remember that Mapserver in not only developer community but
> >there are still some users hanging around here.
> >I was fast browsing through ten pages of more than 1 year old tickets
> >and I do not ultimately like the idea about closing all old tickets
> >automatically.
> >- There are real issues and feature requests which are still valid.
> >- Many of them are created by not so active developers or users. They
> >have once found a real issue but they perhaps don't come back with it
> >after the ticket is closed.
> >- Nobody will go through the +4200 closed tickets and check if there
> >are some which should be re-opened.
> >- Especially because there is not an issue class "probably still valid,
> >but unfortunately no one had time to work on it".
> >- For someone who creates a ticket it would feel impolite to hear next
> >time about the issue after one year by getting a message: "Issue
> >automatically solved because no one has solved the issue".
> >- At least the message should encourage the creator of the ticket to
> >check if the issue is still valid and re-open it.
> >- Much better if there is some human touch: During ticket closing
> >sprint is was concluded that this ticket should be closed because...
> >- If the issue is valid, isn't it better to keep it open than to try to
> >forget that it exists?
> >- Another alternative would be to try to organize issue-closing sprints
> >for advanced users like me for giving a helping hand for the busy
> >developers. The result would be a list of suggested actions: "Close as
> >resolved (check if I remember right)", "Close with kind message to
> >creator", "Ask developer what to do" and "Keep open".  I do understands
> >that issues do not get solved be keeping them in a queue forever.
> >Perhaps PSC could give us a limits: Only max 200 old tickets can be
> >left open, the rest must be dropped at least to category "Close with
> >kind message to creator".
> >
> >
> >With kind regards,
> >
> >-Jukka Rahkonen-
> >
> >Lime, Steve D (MNIT) wrote:
> >>
> >> How many tickets are we talking about?
> >>
> >> -----Original Message-----
> >> From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-
> >>bounces at lists.osgeo.org] On Behalf Of Daniel Morissette
> >> Sent: Monday, March 24, 2014 10:43 AM
> >> To: 'MapServer Dev List'
> >> Subject: [mapserver-dev] MOTION: Run script to close tickets more
> >>than one  year without activity
> >>
> >> Hi MapServer PSC
> >>
> >> MOTION:
> >>
> >> To adopt the practice of automatically closing issues in the
> >>MapServer Github  repository that have had no activity for more than
> >>one year.
> >>
> >> And I start with my +1
> >>
> >>
> >> Context:
> >>
> >> This came up again at the Vienna Code Sprint today and there was
> >>general  agreement to go ahead with this mass closing since tickets
> >>that have seen no  activity in over a year are either invalid, no
> >>longer relevant, or lacking  information or a champion to address
> >>them. If a ticket is automatically closed by  the script but is still
> >>relevant then someone can reopen it and provide an update  on its
> >>status.
> >>
> >> Stephan Meissl and Thomas Bonfort have created a script to
> >>automatically  execute this mass closing and tested it at the sprint
> >>last year. If this motion  passes, this script would be run manually
> >>at regular interval every few months.
> >>
> >>
> >> --
> >> Daniel Morissette
> >> T: +1 418-696-5056 #201
> >> http://www.mapgears.com/
> >> Provider of Professional MapServer Support since 2000
> >> _______________________________________________
> >> mapserver-dev mailing list
> >> mapserver-dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> >>
> >>
> >> _______________________________________________
> >> mapserver-dev mailing list
> >> mapserver-dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
> >_______________________________________________
> >mapserver-dev mailing list
> >mapserver-dev at lists.osgeo.org
> >http://lists.osgeo.org/mailman/listinfo/mapserver-dev