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

Tue Feb 23 08:08:19 PST 2016

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry if you're receiving quite some GitHub notifications right now. We
tried to figure out how to temporarily disable notifications but didn't
find a way.

cu
Stephan

On 02/23/2016 01:14 PM, thomas bonfort wrote:
> Passed with +1 from DanielM, ThomasB, StephanM, MikeS, SteveL, JeffM a
nd
> -0 from SteveW, UmbertoN(retired)
> 
> Stephan will be running the script during this code-sprint, once we've
> tweaked the message to include as a comment.
> 
> Regards,
> Thomas
> 
> On 27 March 2014 at 19:24, Stephan Meißl <stephan at meissl.name
> <mailto:stephan at meissl.name>> wrote:
> 
>     Hi Bart,
> 
>     I think it would be possible to add a Cc but I also think that thi
s
>     wouldn't help if you configured to not get notifications. Addition
ally
>     it won't help with all the tickets that were imported to GitHub fr
om
>     Trac as the opener there is always mapserver-bot.
> 
>     cu
>     Stephan
> 
> 
>     On 03/25/2014 09:52 AM, Bart van den Eijnden wrote:
>     > Hi Stephan,
>     >
>     > 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
>     >
>     > cc @opener in the description text?
>     >
>     > where opener is the github user that opened up the ticket.
>     >
>     > Best regards,
>     > Bart
>     >
>     > On 24 Mar 2014, at 19:03, Stephan Meißl <stephan at meissl.name
>     <mailto:stephan at meissl.name>> wrote:
>     >
>     >> 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 las
t
>     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 ol
d
>     tickets automatically.
>     >>> - There are real issues and feature requests which are still v
alid.
>     >>> - Many of them are created by not so active developers or user
s.
>     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 sti
ll
>     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-closin
g
>     sprints for advanced users like me for giving a helping hand for t
he
>     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 ol
d
>     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>
>     [mailto:mapserver-dev- <mailto:mapserver-dev->
>     >>>> bounces at lists.osgeo.org <mailto: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 th
at
>     have seen no
>     >>>> activity in over a year are either invalid, no longer relevan
t,
>     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 a
nd
>     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.
>     
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJWzIPzAAoJEKNQXeNWi+qtrjsP/AxqkhBbOQvthAledj4I2m/W
jjGk5v+sJFqkA9EAQTg5dUHa1l/mL8rPF6/+YIUhBt4d1d3iNCbFZ8fmRhAK7hbq
yxBv9HfU51vKMwtGxoFkcPXvqY8D3iveSryT8gT2H7IlMDkbEKlG9o183bqkHEC1
RP/+9Agq9Hvo7M98ie3+L5o3vP6kLjZsnqps7PCyphHvjUPH1EtpHIe+5dHXPDQQ
BxPmrRzwqsZwLk6pIYISQRhSi0E+HkXo6VVM5rs7erD1Ab8qJO7nxqW+gPVMrq6f
rGKIsPX+HN8IjLLcCZQLxoSuvBiN7a6JY2djhZTCw4xzB4g/84QWOeau+U9ySgBq
SIB4BGu8JKHXN6x5bHyoUkCGiELkre74lXLrtvdKqOGeRGW151AYlkb2BkI6QXRV
aGGzP7tLHo14inn6WClcxWBpqpjBhC47Hnoh3Y+vW6V9rnOGcpj/SLDBH+PEesqY
QT+r7DTuoCB8+RXPCaalH50wMcqif0KQ3X/cs0Eh1XHZSSJqVfn2GcCeRoxW37OG
1S9PIG0jXWbgmKUerEYozJ4e2fdJwvoCT++tld4iZlfyfCITNN6oCq1A/spp0X6N
twDwjP3ADLH9qpiZQnBKy8xLvh/UKHS6cLYTdSt5dvBMqYOOkUHHpWR74axJ6yWA
il3i8HJLCCuD3b0v3BYs
=rYuf
-----END PGP SIGNATURE-----