Re: [QGIS-Developer] Long filename/filepath causing git issues

2022-11-24 Thread Greg Troxel via QGIS-Developer 

"Alexis R.L. via QGIS-Developer" 
writes:

> I'm not sure it warranted a bug report but some control image now have
> names that are frankly too long and are causing issues in git if the local
> report folder is located some level down.
>
> Would it be too crazy to shrink down some offending name to prevent error
> when switching to more recent branches? I can submit a PR if needed.
>
> Here's one of the error I got
> 'tests/testdata/control_images/labelingengine/expected_label_curved_line_allow_upside_down_hint_reversed_right_positive_offset/expected_label_curved_line_allow_upside_down_hint_reversed_right_positive_offset.png':
> Filename too long

I am not objecting to shrinking, and don't really have standing to, but
can you explain the platform and what you think is going on?

That filename is 210 bytes long, which doesn't seem that big.  Do you
know what limit is being hit, in which program or the OS kernel, and
what properties the file name needs to have to avoid the problems?

I just checked on the box I am reading mail on (NetBSD), and it looks
like PATH_MAX is 1024 bytes.  That actually seems like a low limit these
days.   I am unclear on what the values are on other systems, only that
I have ~never run into this.


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

[QGIS-Developer] Long filename/filepath causing git issues

2022-11-24 Thread Alexis R.L. via QGIS-Developer 
Greetings everyone,

I'm not sure it warranted a bug report but some control image now have
names that are frankly too long and are causing issues in git if the local
report folder is located some level down.

Would it be too crazy to shrink down some offending name to prevent error
when switching to more recent branches? I can submit a PR if needed.

Here's one of the error I got
'tests/testdata/control_images/labelingengine/expected_label_curved_line_allow_upside_down_hint_reversed_right_positive_offset/expected_label_curved_line_allow_upside_down_hint_reversed_right_positive_offset.png':
Filename too long

Thanks,

Alex
___
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] [Qgis-psc] QGIS budget 2023 RFC

2022-11-24 Thread Bernd Vogelgesang via QGIS-Developer 

sneaking in from the ouside ...

Hey guys and girls,

you are providing the world (including million-$€-companies) with an
awesome "product" with a budget worth maybe 50 ESRI-licenses!!!

There has to be a way to grab those big players by the balls! THEN such
discussions about payment rates would start to make sens.

Maybe investing some money in marketing psychologists who can help
developing a campaign for that? Obviously different abilities apart from
software development are needed for this.

Just my two micro-cents
Bernd



Am 24.11.22 um 16:09 schrieb Andreas Neumann via QGIS-Developer:

Hi Vincent,

Thank you for joining the discussion.

We did not really discuss the hourly rates at the budget meeting. From
2021 to 2022 we raised the hourly dev rates from 100 to 110 - and the
hourly documentation rates from 40 to 44. I know that both rates are
low. We can discuss raising them again.

The plan for the two positions was not to have direct employees of
QGIS.ORG , but to use a proxy company, in our case
Kartoza, to act as the employer. Also - our budget does not allow
regular European or North-American salaries. With these limitations at
hand, we can use Kartoza as a proxy to hire employees in certain parts
of the world where the salaries we can offer can be attractive - and
where they have talented people to work on some of our issues
(sysadmin, documentation, etc.)

For the documentation part: Tim and Harrissou are involved in the
selection process of the candidates.

I agree that the grant budget with 10k is not very attractive. We also
discussed skipping it for one year. Not sure what is better ...

BTW: you can all help to find new sustaining members ... that would
increase our budget and would allow us to pay better hourly rates ...

I wish we had a larger budget at hand than the +/- 200k € we seem to
be able to attract each year. From certain countries where we know we
have a lot of QGIS users (France, Italy - just to name two of them)
there are not a lot of sustaining members or donations other than from
a few private persons and very small companies. Maybe companies like
yours could help us to get in touch with the larger companies with a
lot of QGIS users that could become new sustaining members ... Do you
think that would be possible?

Andreas

On Thu, 24 Nov 2022 at 15:05, Vincent Picavet (ml) via QGIS-Developer
 wrote:

Hello,

Thanks for sharing the budget with the community.

A few questions / remarks :
- in most countries, we can see a general inflation, having
consequences on every kind of costs ( hosting, salaries…). Did you
take this context into account when preparing the budget,
especially when basing planned 2023 costs on actual 2022 costs ?
- the cut on Grant budget is really hard. With a "reasonable" mean
budget of 5K per grant, this would mean 2 grants only this year.
It sounds more or less like the end of the grant program. Who
would candidate if chances to be selected are really low ?
Wouldn't there be a way to mitigate it a bit, through various
smaller budget reductions to other budget lines ? The increase in
documentation contribution is huge compared to the grant decrease.
I fear that we loose grants as a mean to attract new core developers.

My most important remark is about "allow for a regular small
salary .. for one person on each item". Disclaimer : I am quite
strongly against QGIS.org having employees. If we are in the
process of having "regular workers" for qgis.org
, then we really have to work hard on :
- having a clear, written and transparent process for how to
select these people
- .. process including a fair way for anyone to candidate
I may have missed some communications, but I have not seen this in
place up to now. This is definitely something we have to put in
place before having some internal troubles.

Best regards,
Vincent

On 24/11/2022 12:07, Marco Bernasocchi wrote:
> Hi all, we prepared the QGIS budget for 2023 and would like to have
> feedback before submitting it to the voting members for
approval. You
> can directly leave comments in the file [1].
>
> Please let us have any Feedback until December 4th. On december 7th
> we'll send the budget for vote.
>
> Cheers Marco
>
> [1]
>

https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing
>


>
>  -- Marco Bernasocchi
>
> QGIS.org Chair OPENGIS.ch CEO http://berna.io 
>
> ___ Qgis-psc mailing
> list qgis-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc

___
QGIS-Developer mailing list

Re: [QGIS-Developer] [Qgis-psc] QGIS budget 2023 RFC

2022-11-24 Thread Peter Petrik via QGIS-Developer 
Hi all,

re the "QGIS packaging work, incl. OSGeo4W, Ubuntu/Debian and Mac builds"
item - I am listed as community manager, but MacOS builds are not under
openGIS/Denis. Maybe you change it in the docs?

Thanks,
Peter





On Thu, Nov 24, 2022 at 4:09 PM Andreas Neumann via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi Vincent,
>
> Thank you for joining the discussion.
>
> We did not really discuss the hourly rates at the budget meeting. From
> 2021 to 2022 we raised the hourly dev rates from 100 to 110 - and the
> hourly documentation rates from 40 to 44. I know that both rates are low.
> We can discuss raising them again.
>
> The plan for the two positions was not to have direct employees of
> QGIS.ORG, but to use a proxy company, in our case Kartoza, to act as the
> employer. Also - our budget does not allow regular European or
> North-American salaries. With these limitations at hand, we can use Kartoza
> as a proxy to hire employees in certain parts of the world where the
> salaries we can offer can be attractive - and where they have talented
> people to work on some of our issues (sysadmin, documentation, etc.)
>
> For the documentation part: Tim and Harrissou are involved in the
> selection process of the candidates.
>
> I agree that the grant budget with 10k is not very attractive. We also
> discussed skipping it for one year. Not sure what is better ...
>
> BTW: you can all help to find new sustaining members ... that would
> increase our budget and would allow us to pay better hourly rates ...
>
> I wish we had a larger budget at hand than the +/- 200k € we seem to be
> able to attract each year. From certain countries where we know we have a
> lot of QGIS users (France, Italy - just to name two of them) there are not
> a lot of sustaining members or donations other than from a few private
> persons and very small companies. Maybe companies like yours could help us
> to get in touch with the larger companies with a lot of QGIS users that
> could become new sustaining members ... Do you think that would be possible?
>
> Andreas
>
> On Thu, 24 Nov 2022 at 15:05, Vincent Picavet (ml) via QGIS-Developer <
> qgis-developer@lists.osgeo.org> wrote:
>
>> Hello,
>>
>> Thanks for sharing the budget with the community.
>>
>> A few questions / remarks :
>> - in most countries, we can see a general inflation, having consequences
>> on every kind of costs ( hosting, salaries…). Did you take this context
>> into account when preparing the budget, especially when basing planned 2023
>> costs on actual 2022 costs ?
>> - the cut on Grant budget is really hard. With a "reasonable" mean budget
>> of 5K per grant, this would mean 2 grants only this year. It sounds more or
>> less like the end of the grant program. Who would candidate if chances to
>> be selected are really low ? Wouldn't there be a way to mitigate it a bit,
>> through various smaller budget reductions to other budget lines ? The
>> increase in documentation contribution is huge compared to the grant
>> decrease. I fear that we loose grants as a mean to attract new core
>> developers.
>>
>> My most important remark is about "allow for a regular small salary ..
>> for one person on each item". Disclaimer : I am quite strongly against
>> QGIS.org having employees. If we are in the process of having "regular
>> workers" for qgis.org, then we really have to work hard on :
>> - having a clear, written and transparent process for how to select these
>> people
>> - .. process including a fair way for anyone to candidate
>> I may have missed some communications, but I have not seen this in place
>> up to now. This is definitely something we have to put in place before
>> having some internal troubles.
>>
>> Best regards,
>> Vincent
>>
>> On 24/11/2022 12:07, Marco Bernasocchi wrote:
>> > Hi all, we prepared the QGIS budget for 2023 and would like to have
>> > feedback before submitting it to the voting members for approval. You
>> > can directly leave comments in the file [1].
>> >
>> > Please let us have any Feedback until December 4th. On december 7th
>> > we'll send the budget for vote.
>> >
>> > Cheers Marco
>> >
>> > [1]
>> >
>> https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing
>> > <
>> https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing
>> >
>> >
>> >  -- Marco Bernasocchi
>> >
>> > QGIS.org Chair OPENGIS.ch CEO http://berna.io 
>> >
>> > ___ Qgis-psc mailing
>> > list qgis-...@lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>
>> ___
>> 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
>>
>
>
> --
>
> --
> Andreas Neumann
> QGIS.ORG board member (treasurer)
>

Re: [QGIS-Developer] [Qgis-psc] QGIS budget 2023 RFC

2022-11-24 Thread Andreas Neumann via QGIS-Developer 
Hi Vincent,

Thank you for joining the discussion.

We did not really discuss the hourly rates at the budget meeting. From 2021
to 2022 we raised the hourly dev rates from 100 to 110 - and the hourly
documentation rates from 40 to 44. I know that both rates are low. We can
discuss raising them again.

The plan for the two positions was not to have direct employees of QGIS.ORG,
but to use a proxy company, in our case Kartoza, to act as the employer.
Also - our budget does not allow regular European or North-American
salaries. With these limitations at hand, we can use Kartoza as a proxy to
hire employees in certain parts of the world where the salaries we can
offer can be attractive - and where they have talented people to work on
some of our issues (sysadmin, documentation, etc.)

For the documentation part: Tim and Harrissou are involved in the selection
process of the candidates.

I agree that the grant budget with 10k is not very attractive. We also
discussed skipping it for one year. Not sure what is better ...

BTW: you can all help to find new sustaining members ... that would
increase our budget and would allow us to pay better hourly rates ...

I wish we had a larger budget at hand than the +/- 200k € we seem to be
able to attract each year. From certain countries where we know we have a
lot of QGIS users (France, Italy - just to name two of them) there are not
a lot of sustaining members or donations other than from a few private
persons and very small companies. Maybe companies like yours could help us
to get in touch with the larger companies with a lot of QGIS users that
could become new sustaining members ... Do you think that would be possible?

Andreas

On Thu, 24 Nov 2022 at 15:05, Vincent Picavet (ml) via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hello,
>
> Thanks for sharing the budget with the community.
>
> A few questions / remarks :
> - in most countries, we can see a general inflation, having consequences
> on every kind of costs ( hosting, salaries…). Did you take this context
> into account when preparing the budget, especially when basing planned 2023
> costs on actual 2022 costs ?
> - the cut on Grant budget is really hard. With a "reasonable" mean budget
> of 5K per grant, this would mean 2 grants only this year. It sounds more or
> less like the end of the grant program. Who would candidate if chances to
> be selected are really low ? Wouldn't there be a way to mitigate it a bit,
> through various smaller budget reductions to other budget lines ? The
> increase in documentation contribution is huge compared to the grant
> decrease. I fear that we loose grants as a mean to attract new core
> developers.
>
> My most important remark is about "allow for a regular small salary .. for
> one person on each item". Disclaimer : I am quite strongly against QGIS.org
> having employees. If we are in the process of having "regular workers" for
> qgis.org, then we really have to work hard on :
> - having a clear, written and transparent process for how to select these
> people
> - .. process including a fair way for anyone to candidate
> I may have missed some communications, but I have not seen this in place
> up to now. This is definitely something we have to put in place before
> having some internal troubles.
>
> Best regards,
> Vincent
>
> On 24/11/2022 12:07, Marco Bernasocchi wrote:
> > Hi all, we prepared the QGIS budget for 2023 and would like to have
> > feedback before submitting it to the voting members for approval. You
> > can directly leave comments in the file [1].
> >
> > Please let us have any Feedback until December 4th. On december 7th
> > we'll send the budget for vote.
> >
> > Cheers Marco
> >
> > [1]
> >
> https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing
> > <
> https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing
> >
> >
> >  -- Marco Bernasocchi
> >
> > QGIS.org Chair OPENGIS.ch CEO http://berna.io 
> >
> > ___ Qgis-psc mailing
> > list qgis-...@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
> ___
> 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
>


-- 

--
Andreas Neumann
QGIS.ORG board member (treasurer)
___
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] [Qgis-psc] QGIS budget 2023 RFC

2022-11-24 Thread Vincent Picavet (ml) via QGIS-Developer 

Hello,

Thanks for sharing the budget with the community.

A few questions / remarks :
- in most countries, we can see a general inflation, having consequences on 
every kind of costs ( hosting, salaries…). Did you take this context into 
account when preparing the budget, especially when basing planned 2023 costs on 
actual 2022 costs ?
- the cut on Grant budget is really hard. With a "reasonable" mean budget of 5K 
per grant, this would mean 2 grants only this year. It sounds more or less like the end 
of the grant program. Who would candidate if chances to be selected are really low ? 
Wouldn't there be a way to mitigate it a bit, through various smaller budget reductions 
to other budget lines ? The increase in documentation contribution is huge compared to 
the grant decrease. I fear that we loose grants as a mean to attract new core developers.

My most important remark is about "allow for a regular small salary .. for one person on each 
item". Disclaimer : I am quite strongly against QGIS.org having employees. If we are in the 
process of having "regular workers" for qgis.org, then we really have to work hard on :
- having a clear, written and transparent process for how to select these people
- .. process including a fair way for anyone to candidate
I may have missed some communications, but I have not seen this in place up to 
now. This is definitely something we have to put in place before having some 
internal troubles.

Best regards,
Vincent

On 24/11/2022 12:07, Marco Bernasocchi wrote:

Hi all, we prepared the QGIS budget for 2023 and would like to have
feedback before submitting it to the voting members for approval. You
can directly leave comments in the file [1].

Please let us have any Feedback until December 4th. On december 7th
we'll send the budget for vote.

Cheers Marco

[1]
https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing


 -- Marco Bernasocchi

QGIS.org Chair OPENGIS.ch CEO http://berna.io 

___ Qgis-psc mailing
list qgis-...@lists.osgeo.org 
https://lists.osgeo.org/mailman/listinfo/qgis-psc


___
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] QGIS budget 2023 RFC

2022-11-24 Thread Andreas Neumann via QGIS-Developer 
Hi all,

Maybe we should a few explanations to the budget draft - since there are
some substantial changes compared to the last year budget.

We increased two budget items:

   - Maintenance / Sysadmin QGIS.ORG server infrastructure
   - QGIS documentation contribution

The intention is to allow for a regular small salary on these two items for
one person on each item. It is an experiment next year - and if it works
out well, we may continue in 2024.

In exchange for these two increases we had to decrease other items. We
slightly decreased the "bug fixing" positions, and unfortunately also the
"QGIS grant" section had to be reduced to 10k.

If there is additional income, we can again increase the bug fixing items.
We'll also monitor the 2022 income and if it increases substantially until
the end of the year, we will probably increase the bug fixing items.

Do you have any questions or remarks on the budget draft for 2023?

Thank you for your feedback,
Andreas

On Thu, 24 Nov 2022 at 12:07, Marco Bernasocchi via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi all,
> we prepared the QGIS budget for 2023 and would like to have feedback
> before submitting it to the voting members for approval. You can directly
> leave comments in the file [1].
>
> Please let us have any Feedback until December 4th. On december 7th we'll
> send the budget for vote.
>
> Cheers
> Marco
>
> [1]
> https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing
>
> --
> Marco Bernasocchi
>
> QGIS.org Chair
> OPENGIS.ch CEO
> http://berna.io
> ___
> 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
>


-- 

--
Andreas Neumann
QGIS.ORG board member (treasurer)
___
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] QGIS budget 2023 RFC

2022-11-24 Thread Marco Bernasocchi via QGIS-Developer 
Hi all,
we prepared the QGIS budget for 2023 and would like to have feedback before
submitting it to the voting members for approval. You can directly leave
comments in the file [1].

Please let us have any Feedback until December 4th. On december 7th we'll
send the budget for vote.

Cheers
Marco

[1]
https://docs.google.com/spreadsheets/d/1WyoZCKOehNhU5YB4pFPOuiJbie1mUmMPiq8YW7qyez0/edit?usp=sharing

-- 
Marco Bernasocchi

QGIS.org Chair
OPENGIS.ch CEO
http://berna.io
___
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] API websites do not build

2022-11-24 Thread Jürgen E . Fischer via QGIS-Developer 
Hi Harrissou,

On Thu, 24. Nov 2022 at 11:42:02 +0100, DelazJ wrote:
> I wanted to preview some recent changes in API documentation and found that
> the C++ (2 days ago) and PyQGIS (last night) API websites failed to update
> lastly.

The C++ API site is updated near to the end of the debian "nightly" builds.
Last round started Wed Nov 23 00:03:05 UTC 2022 and is still underway.

The previous started Sat Nov 19 21:26:11 UTC 2022 (manually triggered some time
after the still running "nightlies" from before the release finished) and ended
Tue Nov 22 12:11:18 UTC 2022 (long "night": 2d14h41m26s).

So the current state is from back then and will be updated once the "nightly"
finishes.

pyqgis however is updated independantly.



Jürgen

-- 
Jürgen E. Fischer
Dipl.-Inf. (FH)   norBIT GmbH   Tel. +49-4931-918175-31
Software Engineer Rheinstraße 13Fax. +49-4931-918175-50
Geschäftsführer   D-26506 Norden  https://www.norbit.de


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/
___
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] API websites do not build

2022-11-24 Thread DelazJ via QGIS-Developer 
Hi,
I wanted to preview some recent changes in API documentation and found that
the C++ (2 days ago) and PyQGIS (last night) API websites failed to update
lastly.

Regards,
Harrissou
___
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