<div dir="ltr">Passed with +1 from DanielM, ThomasB, StephanM, MikeS, SteveL, JeffM and -0 from SteveW, UmbertoN(retired)<div><br></div><div>Stephan will be running the script during this code-sprint, once we've tweaked the message to include as a comment.</div><div><br></div><div>Regards,</div><div>Thomas</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 27 March 2014 at 19:24, Stephan Meißl <span dir="ltr"><<a href="mailto:stephan@meissl.name" target="_blank">stephan@meissl.name</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Bart,<br>
<br>
I think it would be possible to add a Cc but I also think that this<br>
wouldn't help if you configured to not get notifications. Additionally<br>
it won't help with all the tickets that were imported to GitHub from<br>
Trac as the opener there is always mapserver-bot.<br>
<br>
cu<br>
<span class="HOEnZb"><font color="#888888">Stephan<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 03/25/2014 09:52 AM, Bart van den Eijnden wrote:<br>
> Hi Stephan,<br>
><br>
> I’ve heard people complain that they don’t always get github notifications on a ticket they have opened (because of their settings), would it be possible to do an explicit<br>
><br>
> cc @opener in the description text?<br>
><br>
> where opener is the github user that opened up the ticket.<br>
><br>
> Best regards,<br>
> Bart<br>
><br>
> On 24 Mar 2014, at 19:03, Stephan Meißl <<a href="mailto:stephan@meissl.name">stephan@meissl.name</a>> wrote:<br>
><br>
>> Hi Jukka,<br>
>><br>
>> valid points. Just a quick note, the script adds the special label "No<br>
>> Recent Activity" as well as a comment before closing any issue. At the<br>
>> moment the text of the comment is the following:<br>
>><br>
>> ### This is an automated comment<br>
>><br>
>> This issue has been closed due to lack of activity. This doesn't mean<br>
>> the issue is invalid, it simply got no attention within the last year.<br>
>> Please reopen if still valid.<br>
>><br>
>><br>
>> Would this comment address your concerns? Would you like me to add<br>
>> something to it?<br>
>><br>
>> cu<br>
>> Stephan<br>
>><br>
>><br>
>> On 03/24/2014 05:52 PM, Rahkonen Jukka (Tike) wrote:<br>
>>> Hi,<br>
>>><br>
>>> Please remember that Mapserver in not only developer community but there are still some users hanging around here.<br>
>>> 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.<br>
>>> - There are real issues and feature requests which are still valid.<br>
>>> - 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.<br>
>>> - Nobody will go through the +4200 closed tickets and check if there are some which should be re-opened.<br>
>>> - Especially because there is not an issue class "probably still valid, but unfortunately no one had time to work on it".<br>
>>> - 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".<br>
>>> - At least the message should encourage the creator of the ticket to check if the issue is still valid and re-open it.<br>
>>> - Much better if there is some human touch: During ticket closing sprint is was concluded that this ticket should be closed because...<br>
>>> - If the issue is valid, isn't it better to keep it open than to try to forget that it exists?<br>
>>> - 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".<br>
>>><br>
>>><br>
>>> With kind regards,<br>
>>><br>
>>> -Jukka Rahkonen-<br>
>>><br>
>>> Lime, Steve D (MNIT) wrote:<br>
>>>><br>
>>>> How many tickets are we talking about?<br>
>>>><br>
>>>> -----Original Message-----<br>
>>>> From: <a href="mailto:mapserver-dev-bounces@lists.osgeo.org">mapserver-dev-bounces@lists.osgeo.org</a> [mailto:<a href="mailto:mapserver-dev-">mapserver-dev-</a><br>
>>>> <a href="mailto:bounces@lists.osgeo.org">bounces@lists.osgeo.org</a>] On Behalf Of Daniel Morissette<br>
>>>> Sent: Monday, March 24, 2014 10:43 AM<br>
>>>> To: 'MapServer Dev List'<br>
>>>> Subject: [mapserver-dev] MOTION: Run script to close tickets more than one<br>
>>>> year without activity<br>
>>>><br>
>>>> Hi MapServer PSC<br>
>>>><br>
>>>> MOTION:<br>
>>>><br>
>>>> To adopt the practice of automatically closing issues in the MapServer Github<br>
>>>> repository that have had no activity for more than one year.<br>
>>>><br>
>>>> And I start with my +1<br>
>>>><br>
>>>><br>
>>>> Context:<br>
>>>><br>
>>>> This came up again at the Vienna Code Sprint today and there was general<br>
>>>> agreement to go ahead with this mass closing since tickets that have seen no<br>
>>>> activity in over a year are either invalid, no longer relevant, or lacking<br>
>>>> information or a champion to address them. If a ticket is automatically closed by<br>
>>>> the script but is still relevant then someone can reopen it and provide an update<br>
>>>> on its status.<br>
>>>><br>
>>>> Stephan Meissl and Thomas Bonfort have created a script to automatically<br>
>>>> execute this mass closing and tested it at the sprint last year. If this motion<br>
>>>> passes, this script would be run manually at regular interval every few months.<br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Daniel Morissette<br>
>>>> T: <a href="tel:%2B1%20418-696-5056%20%23201" value="+14186965056">+1 418-696-5056 #201</a><br>
>>>> <a href="http://www.mapgears.com/" rel="noreferrer" target="_blank">http://www.mapgears.com/</a><br>
>>>> Provider of Professional MapServer Support since 2000<br>
>>>> _______________________________________________<br>
>>>> mapserver-dev mailing list<br>
>>>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>>>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> mapserver-dev mailing list<br>
>>>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>>>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
>>> _______________________________________________<br>
>>> mapserver-dev mailing list<br>
>>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
>>><br>
>><br>
>> _______________________________________________<br>
>> mapserver-dev mailing list<br>
>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
><br>
<br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</div></div></blockquote></div><br></div>