From a user perspective, I would like to suggest something like:

“Leaving an issue on the QGIS issue tracker might help, but there is no 
guarantee that this will be timely solved as our volunteered resources are 
limited. If you or your organization need something to be quickly fixed, there 
is the possibility to hire someone (link to the list of QGIS commercial support 
providers) ”.

In this way, users are aware that there is the intention in solving issues, 
just limited resources, and how a particular issue can move forward.

Regards,
Rosa

-----------------------------------------------------------------
MSc Rosa Aguilar - PhD Candidate
University of Twente
Faculty of Geoinformation Science and Earth Observation
Connect with me on 
LinkedIn<https://www.linkedin.com/in/rosamaguilar/?locale=en_US>
https://rosaguilar.github.io<https://rosaguilar.github.io/>
-----------------------------------------------------------------
The essential is invisible to the eye. Saint-Exupéry

From: QGIS-Developer <qgis-developer-boun...@lists.osgeo.org> On Behalf Of 
Charles Dixon-Paver
Sent: 08 January 2021 07:44
To: Alexandre Neto <senhor.n...@gmail.com>
Cc: qgis-developer <qgis-developer@lists.osgeo.org>
Subject: Re: [QGIS-Developer] Stale bot and older requests/issues - possible 
enhancement

How about something like:

Unfortunately this issue has not been addressed by the QGIS community for some 
time. If you would like to expedite the resolution of this issue and more like 
it, please refer to the <a 
href="https://qgis.org/en/site/getinvolved/facilitation.html";>facilitating 
development</a> guide for information on how to sponsor the development of this 
functionality.

And make a facilitation page that explains the various resolution options 
nicely.

Not sure if that's OK for non-native speakers

On Fri, 8 Jan 2021 at 02:51, Alexandre Neto 
<senhor.n...@gmail.com<mailto:senhor.n...@gmail.com>> wrote:

On Thu, Jan 7, 2021 at 11:44 PM Nyall Dawson 
<nyall.daw...@gmail.com<mailto:nyall.daw...@gmail.com>> wrote:


What I'm trying to convey here is that there's a chance the ticket
will be addressed without sponsorship, but if they DO sponsor it will
get addressed immediately. So "fast track" here means something a
little like "short cut".  Is there better wording you think may convey
this same meaning?

Nyall


Maybe "Speed up" or "accelerate"

But maybe it's just my limited vocabulary.

Alexandre

>
> Other than that +1
>
> Alexandre Neto
>
> A quinta, 7/01/2021, 08:33, Matthias Kuhn 
> <matth...@opengis.ch<mailto:matth...@opengis.ch>> escreveu:
>>
>> Hi Nyall,
>>
>> I would also appreciate a hint like this.
>> Maybe it could be done even more subtle by shortening this text and adding a 
>> link to a page "learn how to make things progress"?
>>
>> I'd also very much appreciate the voices of users on this topic (that's a 
>> classical "we don't only want to hear the dev side" topic).
>>
>> Matthias
>>
>> On Thu, Jan 7, 2021 at 1:42 AM Nyall Dawson 
>> <nyall.daw...@gmail.com<mailto:nyall.daw...@gmail.com>> wrote:
>>>
>>> Hi list,
>>>
>>> I've a small request to consider for stale bot and issues/feature
>>> requests. I think that if a ticket remains open for say > 90 days
>>> since the last comment, it would be nice if stale bot added a comment
>>> like:
>>>
>>> "Unfortunately this bug/feature request has not seen any solution in
>>> the recent QGIS release. If this fix/feature is important to you or
>>> your organisation, you can help to fast-track its development by
>>> sponsoring this work. To do so, contact one of the QGIS commercial
>>> support providers listed at ... to discuss how you could fund this
>>> functionality".
>>>
>>> I think it's a non-threatening, non-begging way to advise bug
>>> reporters on the alternative ways they can fast track development in
>>> QGIS.
>>>
>>> Thoughts?
>>>
>>> Nyall
>>> _______________________________________________
>>> QGIS-Developer mailing list
>>> QGIS-Developer@lists.osgeo.org<mailto:QGIS-Developer@lists.osgeo.org>
>>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org<mailto:QGIS-Developer@lists.osgeo.org>
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org<mailto:QGIS-Developer@lists.osgeo.org>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to