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

[Stephan Meißl]

Hi Jukka,

valid points. Just a quick note, the script adds the special label "No
Recent Activity" as well as a comment before closing any issue. At the
moment the text of the comment is the following:

### This is an automated comment

This issue has been closed due to lack of activity. This doesn't mean
the issue is invalid, it simply got no attention within the last year.
Please reopen if still valid.


Would this comment address your concerns? Would you like me to add
something to it?

cu
Stephan


On 03/24/2014 05:52 PM, Rahkonen Jukka (Tike) 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
>