[QGIS-Developer] Stale Bot Closed my Pull Request

[TurboGraphxBeige]

Hello fellow QGIS devs!

I had a PR pending in the QGIS repository but unfortunately, the Stale Bot
closed it due to inactivity:

#41906
Custom Label checkbox in the Legend Item Properties (fixes #41384)

Can a commiter re-open it please?


Thank you!





--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Charles Dixon-Paver]

I agree with Jorge and am personally not a fan of a simple "pay a
commercial partner" message, which is why I think a separate link like
Matthias suggested is a great idea, and any message which might be
interpreted as "It's open source, so fix it yourself" could be harmful.

I think a large part of the problem is an awareness issue, where there is a
lack of understanding of the development process and ecosystem at large.
Users should know that donations and sustaining memberships go a long way
to feature development and squashing bugs too, but they also need to know
that it cannot be guaranteed that a specific issue will be addressed unless
they make their own arrangements to address it.

When you factor in community engagement, hackfests, crowd funding, and all
the other initiatives the project is undertaking, I feel like there is a
lot more that users can do besides buying a support contract.

Mostly I think the message would need to be concise but meaningful, and
although it may be frustrating for "seasoned veterans" of the community to
keep seeing it pop-up, I think it is a fair way to engage with users in a
way that supports a healthy ecosystem. I think if it gets too "spammy", the
simple solution is to extend the timeframe before the message is applied.

I made an error in my previous suggested notice and would certainly replace
"how to sponsor the development of this functionality" with "how to support
the development of this functionality".

But that's just my three cents ;-)


On Fri, 8 Jan 2021 at 17:58, Jorge Gustavo Rocha  wrote:

> Hi,
>
> I have a different opinion on this. We should emphasis the community
> component of our QGIS open source project. Just asking to pay if they
> want the issue solved, is what any commercial software project does. It
> does not help to create new contributors.
>
> Reporting and working on issues is (should be) included in our strategy
> to promote participation and get new blood. It is a good place to engage
> new users into QGIS development.
>
> Users should be encourage to know better the community and the people
> behind the software. If a issue is tagged as stale, we should help them
> to identify and know the people related/behind that feature. Without
> knowing the people and without communication, there is no community.
>
> When people know and trust the community behind software, they will
> invest money in. In other words, it is too soon to ask for money for
> someone that just filled an issue in github.
>
> Just my two cents.
>
> Jorge Gustavo
>
> Às 00:42 de 07/01/21, Nyall Dawson escreveu:
> > 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
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> >
>
> J. Gustavo
> --
> Jorge Gustavo Rocha
> Departamento de Informática
> Universidade do Minho
> 4710-057 Braga
> Gabinete 3.29 (Piso 3)
> Tel: +351 253604480
> Fax: +351 253604471
> Móvel: +351 910333888
> skype: nabocudnosor
> ___
> 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
>
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Jorge Gustavo Rocha]

Hi,

I have a different opinion on this. We should emphasis the community
component of our QGIS open source project. Just asking to pay if they
want the issue solved, is what any commercial software project does. It
does not help to create new contributors.

Reporting and working on issues is (should be) included in our strategy
to promote participation and get new blood. It is a good place to engage
new users into QGIS development.

Users should be encourage to know better the community and the people
behind the software. If a issue is tagged as stale, we should help them
to identify and know the people related/behind that feature. Without
knowing the people and without communication, there is no community.

When people know and trust the community behind software, they will
invest money in. In other words, it is too soon to ask for money for
someone that just filled an issue in github.

Just my two cents.

Jorge Gustavo

Às 00:42 de 07/01/21, Nyall Dawson escreveu:
> 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
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

J. Gustavo
-- 
Jorge Gustavo Rocha
Departamento de Informática
Universidade do Minho
4710-057 Braga
Gabinete 3.29 (Piso 3)
Tel: +351 253604480
Fax: +351 253604471
Móvel: +351 910333888
skype: nabocudnosor
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Greg Troxel]

I am not a fan of a bugtracker pushing people to sponsored development
by spamming each issue with it.   It's perfectly reasonable to assign a
label that means basically "this issue appears legitimate but no one has
expressed interest in working on it", and make the pointer to either 1)
maybe you should write the code yourself (that has to be there!) or 2)
you migth wish to sponsor someone once in the top-level README that
explains the labels.


signature.asc
Description: PGP signature
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[r.agui...@utwente.nl]

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  On Behalf Of 
Charles Dixon-Paver
Sent: 08 January 2021 07:44
To: Alexandre Neto 
Cc: qgis-developer 
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 https://qgis.org/en/site/getinvolved/facilitation.html";>facilitating 
development 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 
mailto:senhor.n...@gmail.com>> wrote:

On Thu, Jan 7, 2021 at 11:44 PM Nyall Dawson 
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 
> 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 
>> 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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Charles Dixon-Paver]

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 https://qgis.org/en/site/getinvolved/facilitation.html";>facilitating
development 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  wrote:

>
> On Thu, Jan 7, 2021 at 11:44 PM Nyall Dawson 
> 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 
>> 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 
>> 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
>> >>> 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
>>
> ___
> 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
>
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Alexandre Neto]

On Thu, Jan 7, 2021 at 11:44 PM Nyall Dawson  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 
> 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 
> 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
> >>> 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
>
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Nyall Dawson]

On Fri, 8 Jan 2021 at 09:25, Alexandre Neto  wrote:
>
> As an user and member of a user group, the message does not offend at all. 
> This is something we struggle to explain to users and it's a good opportunity 
> to send the message.
>
>  I prefer a long version instead of just a link (many won't click on it)
>
> I am not a native english speaker, but I think using something like "consider 
> sponsoring" instead of "you can sponsor".
>
> Also the term "fast track" for me is not very clear for me, again as 
> non-native english speaker.

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


>
> Other than that +1
>
> Alexandre Neto
>
> A quinta, 7/01/2021, 08:33, Matthias Kuhn  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  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
>>> 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
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Alexandre Neto]

As an user and member of a user group, the message does not offend at all.
This is something we struggle to explain to users and it's a good
opportunity to send the message.

 I prefer a long version instead of just a link (many won't click on it)

I am not a native english speaker, but I think using something like
"consider sponsoring" instead of "you can sponsor".

Also the term "fast track" for me is not very clear for me, again as
non-native english speaker.

Other than that +1

Alexandre Neto

A quinta, 7/01/2021, 08:33, Matthias Kuhn  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 
> 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
>> 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
>
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Jürgen E . Fischer]

Hi Stefan,

On Thu, 07. Jan 2021 at 12:55:22 +, Stefan Steiger wrote:
> Also, if you use commercial software, 

you probably meant to say proprietary software - as you correctly said free
software is not required to be free of charge and hence can be commercial too.

> As with plugins:
> As long as they are NOT distributed with the software BY DEFAULT, they don’t
> necessarily have to abide by the GPL.

If they are derived from GPL software they also have to be GPL - and most QGIS
plugins have no use without QGIS.


> As long as you only use it internally (e.g. on a WebServer), you don’t have
> to abide by the terms of the GPL (the
> Affero/Application-Service-Provider
> loophole).

You always have to abide the license terms - just if you don't redistribute,
many restrictions don't apply.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[JD L]

My bad, it's a bad translation on my part. I though "gratuit" in French
translated to free (free of charges). I'm totally agree with you. That will
teach me to give my opinion in the language if Shakespeare.

Le jeu. 7 janv. 2021 à 13:55, Stefan Steiger  a
écrit :

> >> As a user and employee of a French administration, I think what is 
> >> proposed would be an excellent reminder. Open source is not free.
>
>
>
> Wrong on so many levels.
>
>
>
> First: GPL = Free Software
>
> So since the license of QGIS is GPL, it’s free software.
>
> “Free Software” means that along with the software, you get the source
> code for free, included in that is the freedom to change and redistribute
> it.
>
> Free as in Freedom. That does not mean it’s gratis.
>
>
>
> Second: “OpenSource” is not the same as 'Free Software'
>
> “OpenSource” merely means you have the source.
>
> It doesn’t mean you’re allowed to change or redistribute it.
>
> It also doesn’t mean it’s gratis.
>
> So “OpenSource” is much worse than GPL./ 'Free Software'.
>
>
>
> Third misconception:
>
> Free (as in freedom) doesn’t mean it’s gratis.
>
> It just means you have the freedom to alter and redistribute the software,
> provided you abide by the license’s requirements, which means granting the
> same right to others.
>
> It also doesn’t mean somebody else does your work for you, or pays
> somebody else to do your work for you.
>
> Therefore QGIS is indeed free, just not gratis.
>
>
>
> What you mean to say is that Free is not Gratis.
>
> That’s a truism/platitude.
>
>
>
> Also, if you use commercial software, you pay far more for the same, and
> you don’t have ANY guarantee that ANY bug is fixed, even if you can pay.
>
> You also cannot usually pay anyone else than the original company to do
> some work on it, even if somebody else could do the same work far cheaper.
>
> With commercial software, you also don’t have any guarantee that the
> product isn’t discontinued tomorrow, or taken into a completely different
> direction.
>
>
>
> As with plugins:
>
> As long as they are NOT distributed with the software BY DEFAULT, they
> don’t necessarily have to abide by the GPL.
>
> As long as you only use it internally (e.g. on a WebServer), you don’t
> have to abide by the terms of the GPL (the Affero
> <https://en.wikipedia.org/wiki/Affero_General_Public_License>/Application-Service-Provider
> loophole).
>
>
>
>
>
>
>
> *Von:* QGIS-Developer  *Im
> Auftrag von *JD L
> *Gesendet:* Donnerstag, 7. Januar 2021 10:10
> *An:* Matthias Kuhn 
> *Cc:* qgis-developer 
> *Betreff:* Re: [QGIS-Developer] Stale bot and older requests/issues -
> possible enhancement
>
>
>
> Hi
>
> As a user and employee of a French administration, I think what is proposed 
> would be an excellent reminder. Open source is not free.
>
>
>
> Le jeu. 7 janv. 2021 à 09:33, Matthias Kuhn  a
> écrit :
>
> 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 
> 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
> 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
>
>
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Giovanni Manghi]

> 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.

yes please!

cheers

-- G --
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Stefan Steiger]

>> As a user and employee of a French administration, I think what is proposed 
>> would be an excellent reminder. Open source is not free.


Wrong on so many levels.

First: GPL = Free Software
So since the license of QGIS is GPL, it’s free software.
“Free Software” means that along with the software, you get the source code for 
free, included in that is the freedom to change and redistribute it.
Free as in Freedom. That does not mean it’s gratis.

Second: “OpenSource” is not the same as 'Free Software'
“OpenSource” merely means you have the source.
It doesn’t mean you’re allowed to change or redistribute it.
It also doesn’t mean it’s gratis.
So “OpenSource” is much worse than GPL./ 'Free Software'.

Third misconception:
Free (as in freedom) doesn’t mean it’s gratis.
It just means you have the freedom to alter and redistribute the software, 
provided you abide by the license’s requirements, which means granting the same 
right to others.
It also doesn’t mean somebody else does your work for you, or pays somebody 
else to do your work for you.
Therefore QGIS is indeed free, just not gratis.

What you mean to say is that Free is not Gratis.
That’s a truism/platitude.

Also, if you use commercial software, you pay far more for the same, and you 
don’t have ANY guarantee that ANY bug is fixed, even if you can pay.
You also cannot usually pay anyone else than the original company to do some 
work on it, even if somebody else could do the same work far cheaper.
With commercial software, you also don’t have any guarantee that the product 
isn’t discontinued tomorrow, or taken into a completely different direction.

As with plugins:
As long as they are NOT distributed with the software BY DEFAULT, they don’t 
necessarily have to abide by the GPL.
As long as you only use it internally (e.g. on a WebServer), you don’t have to 
abide by the terms of the GPL (the 
Affero<https://en.wikipedia.org/wiki/Affero_General_Public_License>/Application-Service-Provider
 loophole).



Von: QGIS-Developer  Im Auftrag von JD L
Gesendet: Donnerstag, 7. Januar 2021 10:10
An: Matthias Kuhn 
Cc: qgis-developer 
Betreff: Re: [QGIS-Developer] Stale bot and older requests/issues - possible 
enhancement


Hi

As a user and employee of a French administration, I think what is proposed 
would be an excellent reminder. Open source is not free.

Le jeu. 7 janv. 2021 à 09:33, Matthias Kuhn 
mailto:matth...@opengis.ch>> a écrit :
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 
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
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[JD L]

Hi

As a user and employee of a French administration, I think what is
proposed would be an excellent reminder. Open source is not free.


Le jeu. 7 janv. 2021 à 09:33, Matthias Kuhn  a écrit :

> 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 
> 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
>> 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
>
___
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

Re: [QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Matthias Kuhn]

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  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
> 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

[QGIS-Developer] Stale bot and older requests/issues - possible enhancement

[Nyall Dawson]

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
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] stale bot :-(

[DIF]

Not to hijack the thread, but that had me thinking about the current Bug report 
template on GitHub. At **QGIS and OS versions**, it's written . However when doing this, the about info is simply pasted line by line 
which make it long and less readable. Instead, could a Copy info button be 
added on the about window that copy the info in the clipboard as a nice 
markdown table ready to paste?





Jean-François Bourdon, ing.f.

Analyste en télédétection

Direction des inventaires forestiers

Ministère des Forêts, de la Faune et des Parcs

5700, 4e Avenue Ouest, local A-108

Québec (Québec) G1H 6R1

Téléphone : 418 627-8669, poste 4304

jean-francois.bour...@mffp.gouv.qc.ca

mffp.gouv.qc.ca



-Message d'origine-
De : QGIS-Developer  De la part de 
Karsten Tebling
Envoyé : 4 janvier 2021 02:40
À : Nyall Dawson 
Cc : qgis-developer 
Objet : Re: [QGIS-Developer] stale bot :-(



Am 22.12.2020 um 23:23 schrieb Nyall Dawson:

> That sounds ideal, but unfortunately things just don't work that way.

> If your bug report is not reproducible there's a very low chance it

> will get fixed.

>

> So if you want your bug fixed, the motivation sits with you to make it

> as easy as possible for the bug triaging team/developers to reproduce.

> Honestly, if we (developers) can't reproduce a bug in <5 minutes,

> we'll just move to the next ticket in the queue and you've missed your

> chance at a fix...

>

> And that's exactly what stale bot and the feedback tag is designed to

> assist with -- it helps push the responsibility back to the bug

> submitter to make sure there's sufficient detail and a reproducible

> test case in the ticket. It's actually in place to avoid frustration

> caused by the "I submitted this ticket 12 months ago, why has nothing

> been done?!?!?" situation.

>

> Nyall





first of all, happy new year!



thanks for the detailed answer!



>From a user-point-of-view I thought the "Copy Report" would contain enough 
>information needed to fix the issue. Knowing that you will skip reports/bugs 
>that can't be reproduced within <5 minutes, I would suggest to change the text 
>of the QGIS-crashed dialog to reflect that. Right now the text is "Include as 
>much information as you can as well as steps to reproduce the issue if 
>possible" - it would be better if the text would say something like "if you 
>can reproduce..." or "if you can provide sample data that crashes..." or "if 
>this crash occured more than once...". You could also remove the "Tell us 
>something about when you got the crash." because it is both above the input 
>field and in the input field - this way you have more room to explain what a 
>helpful report is for you developers. This might help to save time for the 
>developer and the user.



Even if you don't change anything I'm thankful for your answer, because now I 
know when to report and when not, which saves me precious time!



greetz



___

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

Re: [QGIS-Developer] stale bot :-(

[Karsten Tebling]

Am 22.12.2020 um 23:23 schrieb Nyall Dawson:

That sounds ideal, but unfortunately things just don't work that way.
If your bug report is not reproducible there's a very low chance it
will get fixed.

So if you want your bug fixed, the motivation sits with you to make it
as easy as possible for the bug triaging team/developers to reproduce.
Honestly, if we (developers) can't reproduce a bug in <5 minutes,
we'll just move to the next ticket in the queue and you've missed your
chance at a fix...

And that's exactly what stale bot and the feedback tag is designed to
assist with -- it helps push the responsibility back to the bug
submitter to make sure there's sufficient detail and a reproducible
test case in the ticket. It's actually in place to avoid frustration
caused by the "I submitted this ticket 12 months ago, why has nothing
been done?!?!?" situation.

Nyall



first of all, happy new year!

thanks for the detailed answer!

From a user-point-of-view I thought the "Copy Report" would contain 
enough information needed to fix the issue. Knowing that you will skip 
reports/bugs that can't be reproduced within <5 minutes, I would suggest 
to change the text of the QGIS-crashed dialog to reflect that. Right now 
the text is "Include as much information as you can as well as steps to 
reproduce the issue if possible" - it would be better if the text would 
say something like "if you can reproduce..." or "if you can provide 
sample data that crashes..." or "if this crash occured more than 
once...". You could also remove the "Tell us something about when you 
got the crash." because it is both above the input field and in the 
input field - this way you have more room to explain what a helpful 
report is for you developers. This might help to save time for the 
developer and the user.


Even if you don't change anything I'm thankful for your answer, because 
now I know when to report and when not, which saves me precious time!


greetz

___
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

Re: [QGIS-Developer] stale bot :-(

[Nyall Dawson]

On Wed, 23 Dec 2020 at 08:58, Sandro Santilli  wrote:
>
> On Wed, Dec 23, 2020 at 08:23:55AM +1000, Nyall Dawson wrote:
>
> > It's actually in place to avoid frustration
> > caused by the "I submitted this ticket 12 months ago, why has nothing
> > been done?!?!?" situation.
>
> To be honest, I always find these stale bots more frustrating:
>
> "I submitted this ticket 2 months ago, why was it closed?"

That's why the bot has a very descriptive message, giving the
submitter the answer to this question in advance ;)

Nyall

>
> Hey, the OSGeo wiki/LDAP integration ticket survived open
> for 13 years, and it's finally being worked on !
> https://trac.osgeo.org/osgeo/ticket/165
>
> --strk;
___
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

Re: [QGIS-Developer] stale bot :-(

[Sandro Santilli]

On Wed, Dec 23, 2020 at 08:23:55AM +1000, Nyall Dawson wrote:

> It's actually in place to avoid frustration
> caused by the "I submitted this ticket 12 months ago, why has nothing
> been done?!?!?" situation.

To be honest, I always find these stale bots more frustrating:

"I submitted this ticket 2 months ago, why was it closed?"

Hey, the OSGeo wiki/LDAP integration ticket survived open
for 13 years, and it's finally being worked on !
https://trac.osgeo.org/osgeo/ticket/165

--strk;
___
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

Re: [QGIS-Developer] stale bot :-(

[Nyall Dawson]

On Wed, 23 Dec 2020 at 00:14, Karsten Tebling  wrote:
>
> Hello,
>
> could you tell me what is considered weed? In most cases I can't provide
> sample data because I do not own the data or a coworker had the crash
> and "only" saved the report details.
>
> In the "QGIS unexpectedly ended"-dialog it reads "You can also send us a
> helpful bug report using the Copy Report button and opening a ticket at
> QGIS Issue Tracker." - the thing is, the "copy report"-button only
> activates after some text is inserted into "Tell us something about when
> you got the crash" and without knowing that, you just assume the "copy
> report"-button is broken too and close the dialog. In addition some of
> my workmates can't even read english, they just close the dialog
> immediately. I also noticed that one of my reports was closed because I
> only posted the stacktrace and a short sentence about what my coworker
> was roughly doing as far as he could remember and I couldn't provide
> sample data. So I guess posting the stack trace and a short explanation
> is considered weed and not a "helpful bug report"?
>
> Could you add more information to the "QGIS unexpectedly ended"-dialog,
> so it is easier for you to pinpoint the issue without having the user to
> create sample data, a sample project, a new user profile? That would be
> my wish for christmas.

That sounds ideal, but unfortunately things just don't work that way.
If your bug report is not reproducible there's a very low chance it
will get fixed.

So if you want your bug fixed, the motivation sits with you to make it
as easy as possible for the bug triaging team/developers to reproduce.
Honestly, if we (developers) can't reproduce a bug in <5 minutes,
we'll just move to the next ticket in the queue and you've missed your
chance at a fix...

And that's exactly what stale bot and the feedback tag is designed to
assist with -- it helps push the responsibility back to the bug
submitter to make sure there's sufficient detail and a reproducible
test case in the ticket. It's actually in place to avoid frustration
caused by the "I submitted this ticket 12 months ago, why has nothing
been done?!?!?" situation.

Nyall


>
> greetz
>
> Karsten
>
>
> Am 22.12.2020 um 09:37 schrieb Richard Duivenvoorde:
> > I received some "this issue will be closed because of lack of feedback",
> > but I think current 'stale bot implementation' is a little rude on the 
> > edges.
> >
> > (did I miss some discussion about this here?)
> >
> > I received some "this issue will be closed because of lack of feedback", 
> > only because I commented on them. But some are just plain valid:
> >
> > As an example:
> > https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
> > that is just a valid use-case (or maybe feature request?)
> >
> > This one:
> > https://github.com/qgis/QGIS/issues/37984
> > is just valid (I even installed Oracle to check this...)
> >
> > This one: also valid and still needed:
> > https://github.com/qgis/QGIS/issues/37956
> >
> > Weeding the issues is not nice, so removing non-valid, old or non 
> > responding is fine, but now I think the bot is pulling the veggies instead 
> > of the weed :-)
> >
> > Regards,
> >
> > Richard Duivenvoorde
> >
> >
> >
> >
> >
> > ___
> > 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
> ___
> 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
___
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

Re: [QGIS-Developer] stale bot :-(

[Matthias Kuhn]

This one slipped through the cracks of a notoriously understaffed pull
request review team. Sorry for that. I just reopened it, since it looks
reasonable.
If you run into this again, please ask what can be done to continue with
the pull request, a comment will show your interest, likely attract
reviewers - and also snooze the stale bot.

Matthias

On Tue, Dec 22, 2020 at 3:59 PM Ian Turton  wrote:

> Actually it was the PR itself that was closed -
> https://github.com/qgis/QGIS/pull/39231
>
> Ian
>
> On Tue, 22 Dec 2020 at 14:54, Matthias Kuhn  wrote:
>
>> Hi Ian,
>>
>> Can you share a link to this issue?
>>
>> Thanks
>> Matthias
>>
>> On Tue, Dec 22, 2020 at 3:51 PM Ian Turton  wrote:
>>
>>> That's odd to hear as I had one marked stale that had a PR attached
>>>
>>> Ian
>>>
>>> On Tue, 22 Dec 2020 at 10:03, Matthias Kuhn  wrote:
>>>
 Hi Richard,

 Sorry if it was a bit a rough start!
 The stale bot specifically picks only issues which are left with the
 "feedback" label.
 This was the case with these two issues. I notice Giovanni already
 fixed this.

 The assumption is that the veggies don't have open questions on them
 and this way we can filter the weed. Does that sound reasonable to you?

 Best regards
 Matthias

 On Tue, Dec 22, 2020 at 9:38 AM Richard Duivenvoorde <
 rdmaili...@duif.net> wrote:

> I received some "this issue will be closed because of lack of
> feedback",
> but I think current 'stale bot implementation' is a little rude on the
> edges.
>
> (did I miss some discussion about this here?)
>
> I received some "this issue will be closed because of lack of
> feedback", only because I commented on them. But some are just plain 
> valid:
>
> As an example:
> https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
> that is just a valid use-case (or maybe feature request?)
>
> This one:
> https://github.com/qgis/QGIS/issues/37984
> is just valid (I even installed Oracle to check this...)
>
> This one: also valid and still needed:
> https://github.com/qgis/QGIS/issues/37956
>
> Weeding the issues is not nice, so removing non-valid, old or non
> responding is fine, but now I think the bot is pulling the veggies instead
> of the weed :-)
>
> Regards,
>
> Richard Duivenvoorde
>
>
>
>
>
> ___
> 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
>
 ___
 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

>>>
>>>
>>> --
>>> Ian Turton
>>>
>>
>
> --
> Ian Turton
>
___
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

Re: [QGIS-Developer] stale bot :-(

[Giovanni Manghi]

>
> That's odd to hear as I had one marked stale that had a PR attached
>

There was some initial glitch, but I think Matthias already fixed it.
And to answer Richard: each ticket that will be labeled as stale will
be manually reviewed (by me for sure) and if it needs to stay open
(and the feedback label removed) it will.

This bot was added because we **need** to keep the bug queue cleaner
that it is now.

cheers

-- G --
___
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

Re: [QGIS-Developer] stale bot :-(

[Ian Turton]

Actually it was the PR itself that was closed -
https://github.com/qgis/QGIS/pull/39231

Ian

On Tue, 22 Dec 2020 at 14:54, Matthias Kuhn  wrote:

> Hi Ian,
>
> Can you share a link to this issue?
>
> Thanks
> Matthias
>
> On Tue, Dec 22, 2020 at 3:51 PM Ian Turton  wrote:
>
>> That's odd to hear as I had one marked stale that had a PR attached
>>
>> Ian
>>
>> On Tue, 22 Dec 2020 at 10:03, Matthias Kuhn  wrote:
>>
>>> Hi Richard,
>>>
>>> Sorry if it was a bit a rough start!
>>> The stale bot specifically picks only issues which are left with the
>>> "feedback" label.
>>> This was the case with these two issues. I notice Giovanni already fixed
>>> this.
>>>
>>> The assumption is that the veggies don't have open questions on them and
>>> this way we can filter the weed. Does that sound reasonable to you?
>>>
>>> Best regards
>>> Matthias
>>>
>>> On Tue, Dec 22, 2020 at 9:38 AM Richard Duivenvoorde <
>>> rdmaili...@duif.net> wrote:
>>>
 I received some "this issue will be closed because of lack of feedback",
 but I think current 'stale bot implementation' is a little rude on the
 edges.

 (did I miss some discussion about this here?)

 I received some "this issue will be closed because of lack of
 feedback", only because I commented on them. But some are just plain valid:

 As an example:
 https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
 that is just a valid use-case (or maybe feature request?)

 This one:
 https://github.com/qgis/QGIS/issues/37984
 is just valid (I even installed Oracle to check this...)

 This one: also valid and still needed:
 https://github.com/qgis/QGIS/issues/37956

 Weeding the issues is not nice, so removing non-valid, old or non
 responding is fine, but now I think the bot is pulling the veggies instead
 of the weed :-)

 Regards,

 Richard Duivenvoorde





 ___
 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

>>> ___
>>> 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
>>>
>>
>>
>> --
>> Ian Turton
>>
>

-- 
Ian Turton
___
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

Re: [QGIS-Developer] stale bot :-(

[Matthias Kuhn]

Hi Ian,

Can you share a link to this issue?

Thanks
Matthias

On Tue, Dec 22, 2020 at 3:51 PM Ian Turton  wrote:

> That's odd to hear as I had one marked stale that had a PR attached
>
> Ian
>
> On Tue, 22 Dec 2020 at 10:03, Matthias Kuhn  wrote:
>
>> Hi Richard,
>>
>> Sorry if it was a bit a rough start!
>> The stale bot specifically picks only issues which are left with the
>> "feedback" label.
>> This was the case with these two issues. I notice Giovanni already fixed
>> this.
>>
>> The assumption is that the veggies don't have open questions on them and
>> this way we can filter the weed. Does that sound reasonable to you?
>>
>> Best regards
>> Matthias
>>
>> On Tue, Dec 22, 2020 at 9:38 AM Richard Duivenvoorde 
>> wrote:
>>
>>> I received some "this issue will be closed because of lack of feedback",
>>> but I think current 'stale bot implementation' is a little rude on the
>>> edges.
>>>
>>> (did I miss some discussion about this here?)
>>>
>>> I received some "this issue will be closed because of lack of feedback",
>>> only because I commented on them. But some are just plain valid:
>>>
>>> As an example:
>>> https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
>>> that is just a valid use-case (or maybe feature request?)
>>>
>>> This one:
>>> https://github.com/qgis/QGIS/issues/37984
>>> is just valid (I even installed Oracle to check this...)
>>>
>>> This one: also valid and still needed:
>>> https://github.com/qgis/QGIS/issues/37956
>>>
>>> Weeding the issues is not nice, so removing non-valid, old or non
>>> responding is fine, but now I think the bot is pulling the veggies instead
>>> of the weed :-)
>>>
>>> Regards,
>>>
>>> Richard Duivenvoorde
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> 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
>>>
>> ___
>> 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
>>
>
>
> --
> Ian Turton
>
___
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

Re: [QGIS-Developer] stale bot :-(

[Ian Turton]

That's odd to hear as I had one marked stale that had a PR attached

Ian

On Tue, 22 Dec 2020 at 10:03, Matthias Kuhn  wrote:

> Hi Richard,
>
> Sorry if it was a bit a rough start!
> The stale bot specifically picks only issues which are left with the
> "feedback" label.
> This was the case with these two issues. I notice Giovanni already fixed
> this.
>
> The assumption is that the veggies don't have open questions on them and
> this way we can filter the weed. Does that sound reasonable to you?
>
> Best regards
> Matthias
>
> On Tue, Dec 22, 2020 at 9:38 AM Richard Duivenvoorde 
> wrote:
>
>> I received some "this issue will be closed because of lack of feedback",
>> but I think current 'stale bot implementation' is a little rude on the
>> edges.
>>
>> (did I miss some discussion about this here?)
>>
>> I received some "this issue will be closed because of lack of feedback",
>> only because I commented on them. But some are just plain valid:
>>
>> As an example:
>> https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
>> that is just a valid use-case (or maybe feature request?)
>>
>> This one:
>> https://github.com/qgis/QGIS/issues/37984
>> is just valid (I even installed Oracle to check this...)
>>
>> This one: also valid and still needed:
>> https://github.com/qgis/QGIS/issues/37956
>>
>> Weeding the issues is not nice, so removing non-valid, old or non
>> responding is fine, but now I think the bot is pulling the veggies instead
>> of the weed :-)
>>
>> Regards,
>>
>> Richard Duivenvoorde
>>
>>
>>
>>
>>
>> ___
>> 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
>>
> ___
> 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
>


-- 
Ian Turton
___
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

Re: [QGIS-Developer] stale bot :-(

[Karsten Tebling]

Hello,

could you tell me what is considered weed? In most cases I can't provide 
sample data because I do not own the data or a coworker had the crash 
and "only" saved the report details.


In the "QGIS unexpectedly ended"-dialog it reads "You can also send us a 
helpful bug report using the Copy Report button and opening a ticket at 
QGIS Issue Tracker." - the thing is, the "copy report"-button only 
activates after some text is inserted into "Tell us something about when 
you got the crash" and without knowing that, you just assume the "copy 
report"-button is broken too and close the dialog. In addition some of 
my workmates can't even read english, they just close the dialog 
immediately. I also noticed that one of my reports was closed because I 
only posted the stacktrace and a short sentence about what my coworker 
was roughly doing as far as he could remember and I couldn't provide 
sample data. So I guess posting the stack trace and a short explanation 
is considered weed and not a "helpful bug report"?


Could you add more information to the "QGIS unexpectedly ended"-dialog, 
so it is easier for you to pinpoint the issue without having the user to 
create sample data, a sample project, a new user profile? That would be 
my wish for christmas.


greetz

Karsten


Am 22.12.2020 um 09:37 schrieb Richard Duivenvoorde:

I received some "this issue will be closed because of lack of feedback",
but I think current 'stale bot implementation' is a little rude on the edges.

(did I miss some discussion about this here?)

I received some "this issue will be closed because of lack of feedback", only 
because I commented on them. But some are just plain valid:

As an example:
https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
that is just a valid use-case (or maybe feature request?)

This one:
https://github.com/qgis/QGIS/issues/37984
is just valid (I even installed Oracle to check this...)

This one: also valid and still needed:
https://github.com/qgis/QGIS/issues/37956

Weeding the issues is not nice, so removing non-valid, old or non responding is 
fine, but now I think the bot is pulling the veggies instead of the weed :-)

Regards,

Richard Duivenvoorde





___
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

___
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

Re: [QGIS-Developer] stale bot :-(

[Matthias Kuhn]

Hi Richard,

Sorry if it was a bit a rough start!
The stale bot specifically picks only issues which are left with the
"feedback" label.
This was the case with these two issues. I notice Giovanni already fixed
this.

The assumption is that the veggies don't have open questions on them and
this way we can filter the weed. Does that sound reasonable to you?

Best regards
Matthias

On Tue, Dec 22, 2020 at 9:38 AM Richard Duivenvoorde 
wrote:

> I received some "this issue will be closed because of lack of feedback",
> but I think current 'stale bot implementation' is a little rude on the
> edges.
>
> (did I miss some discussion about this here?)
>
> I received some "this issue will be closed because of lack of feedback",
> only because I commented on them. But some are just plain valid:
>
> As an example:
> https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
> that is just a valid use-case (or maybe feature request?)
>
> This one:
> https://github.com/qgis/QGIS/issues/37984
> is just valid (I even installed Oracle to check this...)
>
> This one: also valid and still needed:
> https://github.com/qgis/QGIS/issues/37956
>
> Weeding the issues is not nice, so removing non-valid, old or non
> responding is fine, but now I think the bot is pulling the veggies instead
> of the weed :-)
>
> Regards,
>
> Richard Duivenvoorde
>
>
>
>
>
> ___
> 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
>
___
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

[QGIS-Developer] stale bot :-(

[Richard Duivenvoorde]

I received some "this issue will be closed because of lack of feedback",
but I think current 'stale bot implementation' is a little rude on the edges.

(did I miss some discussion about this here?)

I received some "this issue will be closed because of lack of feedback", only 
because I commented on them. But some are just plain valid:

As an example:
https://github.com/qgis/QGIS/issues/39107#issuecomment-749298135
that is just a valid use-case (or maybe feature request?)

This one:
https://github.com/qgis/QGIS/issues/37984
is just valid (I even installed Oracle to check this...)

This one: also valid and still needed:
https://github.com/qgis/QGIS/issues/37956

Weeding the issues is not nice, so removing non-valid, old or non responding is 
fine, but now I think the bot is pulling the veggies instead of the weed :-)

Regards,

Richard Duivenvoorde





___
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