Re: [QGIS-Developer] Documentation repository looking for developers

[Tim Sutton via QGIS-Developer]

Great, thanks!

On Mon, Nov 7, 2022 at 12:38 PM DelazJ  wrote:

> Hi Tim,
> Yes, I'm in touch with Anita. And yes, I'll try to join the meeting
> tomorrow (I may be late, sorry in advance).
>
> Harrissou
>
> Le lun. 7 nov. 2022 à 09:50, Tim Sutton  a écrit :
>
>> Hi Harrisou
>>
>>
>>
>> On Mon, Nov 7, 2022 at 6:40 AM Delaz J  wrote:
>>
>>> Hi Tim,
>>>
>>> Thanks for replying. I appreciate.
>>>
>>> OK, if no one steps up meanwhile, let's see how we can collaborate with
>>> the new recruit. But I feel that, at the beginning, he will be more skilled
>>> for general coding matters ("Code/Setup" section) than QGIS specific issues
>>> as reported in sections "Writing" and "Triage". No?
>>>
>>
>> Yes their help would be in the context of section #1 in your list. I do
>> know that Anita has been looking at how to use QGIS funds to get you more
>> support which hopefully provides some mechanism to address some of your
>> other items.
>>
>> How about you come and join the PSC call tomorrow evening - we regularly
>> discuss how we can help you and the docs team, but it might be more useful
>> if you are actually in the conversation!
>>
>> Regards
>>
>> Tim
>>
>>
>>
>>
>>> Kind regards,
>>>
>>> Harrissou
>>> Le 05/11/2022 à 23:54, Tim Sutton a écrit :
>>>
>>> Hi Harrisou!
>>>
>>> Top posting here since I cannot address the items individually. We are
>>> in the last stages of hiring a QGIS Jr Web Developer for one year under
>>> funding from QGIS.org. I think quite a few of the things on your list below
>>> are things we might be able to assign to the person we appoint. So I warmly
>>> invite you to maybe do some collaboration with the person when they
>>> 'arrive' and we can assign them tasks that will help you.
>>>
>>> One specific point on #3 below, Mathias Kuhn was working on some
>>> Transifex cleverness at the Firence hackfest for the web site - maybe some
>>> of this logic can also be ported to pull instead of push for the docs.
>>> https://github.com/qgis/QGIS-Website/blob/master/.github/workflows/tx_push.yml
>>>
>>>
>>> Regards
>>>
>>> Tim
>>>
>>>
>>> On Thu, Oct 20, 2022 at 10:07 AM DelazJ via QGIS-Developer <
>>> qgis-developer@lists.osgeo.org> wrote:
>>>

 Hi dear devs,

 With feature freeze/bug fixes period almost finished, and before you
 get busy with pushing cool and nice features for the next 3.30 branch, I'd
 like to share with you a few cool features the documentation repo will also
 be really happy to get from your skills.

 *Code/Setup*

 1. Create a github action to automatically assign labels to issue
 reports generated from merged pull requests in code repo, to help us
 quickly triage. See #50562 
 and #7826 

 2. To the generated issue reports, we also have to assign the
 milestone, that is the next LTR we will document it in... An automatic
 assignment would also be great. See #7828
 

 3. If the move away from Transifex is not yet on the radar, a github
 action to regularly pull unfinished translation files would be welcome. See
 #7827 

 4. Help setup the release branches to allow automatic merge when tests
 pass. See #7837
 

 5. Fix text frame width in the pyQGIS API documentation. See #36
 

 *Writing*

 If you instead feel like writing , there are some outdated, confusing
 instructions in the docs for beginners in coding:

 1. how to configure python path
 
 from within QGIS or custom application: See #6179
  and attempts
 to fix it at #6306
 , #7139
  and #7140
 

 2. methods and tools to debug code/plugins: see #7836
 

 3. as usual, review of current pull requests
  is still welcome

 *Triage*

 If you don't feel like coding nor writing, you can just tell us whether
 you think that any of these reports is worth documenting and how we could
 address it: ToDocOrNotToDoc
 

 As you can see, the needs are diverse; it is about coding, setup,
 triaging and writing so you probably will find something for you (I hope)
 and do it faster than in my unsuccessful

Re: [QGIS-Developer] QGIS attribute form - changing values with Python of disabled widgets

[Andreas Neumann via QGIS-Developer]

Hi Matthias,

Do you mean disabling them with a Python init code and 
QgsWidget.setEnabled(False) - right?


Just tried it - and it seems to work ;-)

Thanks for the hint!

Andreas

On 2022-11-07 15:46, Matthias Kuhn wrote:


Hi Andreas,

How about going the other way around and leaving them as editable in 
the config and disabling the widget via python instead?


Matthias

On Mon, Nov 7, 2022 at 3:42 PM Andreas Neumann via QGIS-Developer 
 wrote:



Hi,

I have a QGIS form with a number of widgets that are set to 
"disabled". I don't want the user to change these values manually, but 
they should be updated by a Python action "on demand". Hence I set the 
editable state of these widgets to False.


Now I noticed that while I can change values in the widgets with my 
Python action, the values are not stored when the editable state is 
set to "False". As soon as I set the editable state to "True", then my 
Python action works fine and the values are correctly stored.


I tried with two approaches:

QgsAttributeForm.changeAttribute()

and

QgsWidget.setValue()

Both of these work fine when editable state is enabled, but not, when 
they are disabled.


Is there any way to also change attribute values when the editable 
state of a widget is set to False?


Thanks,

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


[1]

Best of Swiss Enterprise App-Award for QField [1] - Hold the power of 
QGIS in your hand - get it now [2]




Links:
--
[1] 
https://www.opengis.ch/2022/11/03/best-of-swiss-enterprise-app-award-for-qfield/

[2] https://qfield.org/get___
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 attribute form - changing values with Python of disabled widgets

[Matthias Kuhn via QGIS-Developer]

Hi Andreas,

How about going the other way around and leaving them as editable in the
config and disabling the widget via python instead?

Matthias

On Mon, Nov 7, 2022 at 3:42 PM Andreas Neumann via QGIS-Developer <
qgis-developer@lists.osgeo.org> wrote:

> Hi,
>
> I have a QGIS form with a number of widgets that are set to "disabled". I
> don't want the user to change these values manually, but they should be
> updated by a Python action "on demand". Hence I set the editable state of
> these widgets to False.
>
> Now I noticed that while I can change values in the widgets with my Python
> action, the values are not stored when the editable state is set to
> "False". As soon as I set the editable state to "True", then my Python
> action works fine and the values are correctly stored.
>
> I tried with two approaches:
>
> QgsAttributeForm.changeAttribute()
>
> and
>
> QgsWidget.setValue()
>
> Both of these work fine when editable state is enabled, but not, when they
> are disabled.
>
> Is there any way to also change attribute values when the editable state
> of a widget is set to False?
>
> Thanks,
>
> Andreas
> ___
> 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
>

-- 
 


Best of Swiss Enterprise App-Award for QField 

 
- Hold the power of QGIS in your hand - get it now 
___
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 attribute form - changing values with Python of disabled widgets

[Andreas Neumann via QGIS-Developer]

Hi,

I have a QGIS form with a number of widgets that are set to "disabled". 
I don't want the user to change these values manually, but they should 
be updated by a Python action "on demand". Hence I set the editable 
state of these widgets to False.


Now I noticed that while I can change values in the widgets with my 
Python action, the values are not stored when the editable state is set 
to "False". As soon as I set the editable state to "True", then my 
Python action works fine and the values are correctly stored.


I tried with two approaches:

QgsAttributeForm.changeAttribute()

and

QgsWidget.setValue()

Both of these work fine when editable state is enabled, but not, when 
they are disabled.


Is there any way to also change attribute values when the editable state 
of a widget is set to False?


Thanks,

Andreas___
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] Documentation repository looking for developers

[DelazJ via QGIS-Developer]

Hi Tim,
Yes, I'm in touch with Anita. And yes, I'll try to join the meeting
tomorrow (I may be late, sorry in advance).

Harrissou

Le lun. 7 nov. 2022 à 09:50, Tim Sutton  a écrit :

> Hi Harrisou
>
>
>
> On Mon, Nov 7, 2022 at 6:40 AM Delaz J  wrote:
>
>> Hi Tim,
>>
>> Thanks for replying. I appreciate.
>>
>> OK, if no one steps up meanwhile, let's see how we can collaborate with
>> the new recruit. But I feel that, at the beginning, he will be more skilled
>> for general coding matters ("Code/Setup" section) than QGIS specific issues
>> as reported in sections "Writing" and "Triage". No?
>>
>
> Yes their help would be in the context of section #1 in your list. I do
> know that Anita has been looking at how to use QGIS funds to get you more
> support which hopefully provides some mechanism to address some of your
> other items.
>
> How about you come and join the PSC call tomorrow evening - we regularly
> discuss how we can help you and the docs team, but it might be more useful
> if you are actually in the conversation!
>
> Regards
>
> Tim
>
>
>
>
>> Kind regards,
>>
>> Harrissou
>> Le 05/11/2022 à 23:54, Tim Sutton a écrit :
>>
>> Hi Harrisou!
>>
>> Top posting here since I cannot address the items individually. We are in
>> the last stages of hiring a QGIS Jr Web Developer for one year under
>> funding from QGIS.org. I think quite a few of the things on your list below
>> are things we might be able to assign to the person we appoint. So I warmly
>> invite you to maybe do some collaboration with the person when they
>> 'arrive' and we can assign them tasks that will help you.
>>
>> One specific point on #3 below, Mathias Kuhn was working on some
>> Transifex cleverness at the Firence hackfest for the web site - maybe some
>> of this logic can also be ported to pull instead of push for the docs.
>> https://github.com/qgis/QGIS-Website/blob/master/.github/workflows/tx_push.yml
>>
>>
>> Regards
>>
>> Tim
>>
>>
>> On Thu, Oct 20, 2022 at 10:07 AM DelazJ via QGIS-Developer <
>> qgis-developer@lists.osgeo.org> wrote:
>>
>>>
>>> Hi dear devs,
>>>
>>> With feature freeze/bug fixes period almost finished, and before you get
>>> busy with pushing cool and nice features for the next 3.30 branch, I'd like
>>> to share with you a few cool features the documentation repo will also be
>>> really happy to get from your skills.
>>>
>>> *Code/Setup*
>>>
>>> 1. Create a github action to automatically assign labels to issue
>>> reports generated from merged pull requests in code repo, to help us
>>> quickly triage. See #50562 
>>> and #7826 
>>>
>>> 2. To the generated issue reports, we also have to assign the milestone,
>>> that is the next LTR we will document it in... An automatic assignment
>>> would also be great. See #7828
>>> 
>>>
>>> 3. If the move away from Transifex is not yet on the radar, a github
>>> action to regularly pull unfinished translation files would be welcome. See
>>> #7827 
>>>
>>> 4. Help setup the release branches to allow automatic merge when tests
>>> pass. See #7837 
>>>
>>> 5. Fix text frame width in the pyQGIS API documentation. See #36
>>> 
>>>
>>> *Writing*
>>>
>>> If you instead feel like writing , there are some outdated, confusing
>>> instructions in the docs for beginners in coding:
>>>
>>> 1. how to configure python path
>>> 
>>> from within QGIS or custom application: See #6179
>>>  and attempts
>>> to fix it at #6306
>>> , #7139
>>>  and #7140
>>> 
>>>
>>> 2. methods and tools to debug code/plugins: see #7836
>>> 
>>>
>>> 3. as usual, review of current pull requests
>>>  is still welcome
>>>
>>> *Triage*
>>>
>>> If you don't feel like coding nor writing, you can just tell us whether
>>> you think that any of these reports is worth documenting and how we could
>>> address it: ToDocOrNotToDoc
>>> 
>>>
>>> As you can see, the needs are diverse; it is about coding, setup,
>>> triaging and writing so you probably will find something for you (I hope)
>>> and do it faster than in my unsuccessful attempts.
>>> *The docs needs the devs*.
>>>
>>> Kind regards and looking forward,
>>> Harrissou
>>> ___
>>> QGIS-Developer mailing list
>>> QGIS-Developer@l

Re: [QGIS-Developer] QGIS python action with Expression problem

[Alessandro Pasotti via QGIS-Developer]

On Mon, Nov 7, 2022 at 11:59 AM Andreas Neumann  wrote:
>
> Hi Ale,
>
> Thanks for the hint!

You're welcome!

the formScope adds another feature: the "form" feature which
represents a virtual feature with the values taken from the current
form status.

>
> With
>
> expContext.setFeature(form.feature())
>
> it seems to work.
>
> I was assuming that adding the formScope would also add the feature context 
> ... but apparently not.
>
> Now I can continue adding the more complex expression.
>
> Thank you for your help!
>
> Andreas
>
> On 2022-11-07 11:46, Alessandro Pasotti wrote:
>
> You need to set the feature if you want to access the feature fields.
>
> QgsExpressionContext::setFeature( const QgsFeature &feature )
>
> If you want the form feature values you need to use the current_value
> or the current_feature functions.
>
> Regards.
>
> On Mon, Nov 7, 2022 at 11:27 AM Andreas Neumann via QGIS-Developer
>  wrote:
>
>
> Hi,
>
> I am trying to implement a Python action in "form" and "feature" action scope 
> that uses a QGIS expression, but fail to get a valid expression calculation.
>
> Here is my code so far:
>
> from qgis.PyQt.QtWidgets import *
> from qgis.core import QgsMessageLog
>
> expContext = QgsExpressionContext()
> expContext.appendScopes(QgsExpressionContextUtils.globalProjectLayerScopes(form.layer()))
> expContext.appendScope(QgsExpressionContextUtils.formScope(form.feature(),'SingleEditMode'))
>
> exp = QgsExpression('t_id')
>
> expResult = exp.evaluate(expContext)
> QgsMessageLog.logMessage('Expression Result=' + str(expResult))
>
>
> So even the most basic expression (getting a field value) will not work in my 
> code. I always get "None" as a result.
>
> Any idea what is missing? Am I missing a certain scope or an import statement?
>
> Thank you very much for any hints what might be wrong here ...
>
> Andreas
>
> ___
> 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
>
>
>
>


-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 python action with Expression problem

[Andreas Neumann via QGIS-Developer]

Hi Ale,

Thanks for the hint!

With

expContext.setFeature(form.feature())

it seems to work.

I was assuming that adding the formScope would also add the feature 
context ... but apparently not.


Now I can continue adding the more complex expression.

Thank you for your help!

Andreas

On 2022-11-07 11:46, Alessandro Pasotti wrote:


You need to set the feature if you want to access the feature fields.

QgsExpressionContext::setFeature( const QgsFeature &feature )

If you want the form feature values you need to use the current_value
or the current_feature functions.

Regards.

On Mon, Nov 7, 2022 at 11:27 AM Andreas Neumann via QGIS-Developer
 wrote:


Hi,

I am trying to implement a Python action in "form" and "feature" 
action scope that uses a QGIS expression, but fail to get a valid 
expression calculation.


Here is my code so far:

from qgis.PyQt.QtWidgets import *
from qgis.core import QgsMessageLog

expContext = QgsExpressionContext()
expContext.appendScopes(QgsExpressionContextUtils.globalProjectLayerScopes(form.layer()))
expContext.appendScope(QgsExpressionContextUtils.formScope(form.feature(),'SingleEditMode'))

exp = QgsExpression('t_id')

expResult = exp.evaluate(expContext)
QgsMessageLog.logMessage('Expression Result=' + str(expResult))

So even the most basic expression (getting a field value) will not 
work in my code. I always get "None" as a result.


Any idea what is missing? Am I missing a certain scope or an import 
statement?


Thank you very much for any hints what might be wrong here ...

Andreas

___
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] Issue with qgis Docker images starting from qgis:final-3_22_10

[DelazJ via QGIS-Developer]

Hi,

I also confirm this issue for the QGIS 3.22 documentation (
https://github.com/qgis/QGIS-Documentation/issues/7858) but afaict, tests
were still passing mid october (hence with 3.22.11).

Regards,
Harrissou

Le lun. 7 nov. 2022 à 11:15, Paolo Tormene via QGIS-Developer <
qgis-developer@lists.osgeo.org> a écrit :

> Hello. I use qgis docker images to run tests for a plugin. Recently my
> tests started to fail when attempting to import qgis ("ModuleNotFoundError:
> No module named 'qgis'").
> I normally run tests using images qgis/qgis:latest and
> qgis/qgis:release-3_22, in order to check compatibility with both the
> latest release and the current LTR.
> With qgis/qgis:latest everything works, but with qgis/qgis:release-3_22 it
> produces the error described above.
> While investigating the problem, I also tried to use older versions:
> qgis:final-3_22_12 -> KO
> qgis:final-3_22_11 -> KO
> qgis:final-3_22_10 -> KO
> qgis:final-3_22_9 -> OK (it seems to work as expected until this version)
> Were there any significant changes between 3_22_9 and 3_22_10 that might
> have caused this? Do you have any suggestions?
> Thank you,
> Paolo
>
> --
>
> *PAOLO TORMENE* senior software developer +39 0382 5169882
>
> *GLOBAL EARTHQUAKE MODEL * working together to assess risk
>
> *GEM -* globalquakemodel.org  *T -*
> @GEMwrld  *F -* GEMwrld
> 
> ___
> 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] QGIS python action with Expression problem

[Alessandro Pasotti via QGIS-Developer]

You need to set the feature if you want to access the feature fields.

QgsExpressionContext::setFeature( const QgsFeature &feature )

If you want the form feature values you need to use the current_value
or the current_feature functions.

Regards.

On Mon, Nov 7, 2022 at 11:27 AM Andreas Neumann via QGIS-Developer
 wrote:
>
> Hi,
>
> I am trying to implement a Python action in "form" and "feature" action scope 
> that uses a QGIS expression, but fail to get a valid expression calculation.
>
> Here is my code so far:
>
> from qgis.PyQt.QtWidgets import *
> from qgis.core import QgsMessageLog
>
> expContext = QgsExpressionContext()
> expContext.appendScopes(QgsExpressionContextUtils.globalProjectLayerScopes(form.layer()))
> expContext.appendScope(QgsExpressionContextUtils.formScope(form.feature(),'SingleEditMode'))
>
> exp = QgsExpression('t_id')
>
> expResult = exp.evaluate(expContext)
> QgsMessageLog.logMessage('Expression Result=' + str(expResult))
>
>
> So even the most basic expression (getting a field value) will not work in my 
> code. I always get "None" as a result.
>
> Any idea what is missing? Am I missing a certain scope or an import statement?
>
> Thank you very much for any hints what might be wrong here ...
>
> Andreas
>
> ___
> 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



-- 
Alessandro Pasotti
QCooperative:  www.qcooperative.net
ItOpen:   www.itopen.it
___
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 python action with Expression problem

[Andreas Neumann via QGIS-Developer]

Hi,

I am trying to implement a Python action in "form" and "feature" action 
scope that uses a QGIS expression, but fail to get a valid expression 
calculation.


Here is my code so far:

from qgis.PyQt.QtWidgets import *
from qgis.core import QgsMessageLog

expContext = QgsExpressionContext()
expContext.appendScopes(QgsExpressionContextUtils.globalProjectLayerScopes(form.layer()))
expContext.appendScope(QgsExpressionContextUtils.formScope(form.feature(),'SingleEditMode'))

exp = QgsExpression('t_id')

expResult = exp.evaluate(expContext)
QgsMessageLog.logMessage('Expression Result=' + str(expResult))

So even the most basic expression (getting a field value) will not work 
in my code. I always get "None" as a result.


Any idea what is missing? Am I missing a certain scope or an import 
statement?


Thank you very much for any hints what might be wrong here ...

Andreas___
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] Issue with qgis Docker images starting from qgis:final-3_22_10

[Paolo Tormene via QGIS-Developer]

Hello. I use qgis docker images to run tests for a plugin. Recently my
tests started to fail when attempting to import qgis ("ModuleNotFoundError:
No module named 'qgis'").
I normally run tests using images qgis/qgis:latest and
qgis/qgis:release-3_22, in order to check compatibility with both the
latest release and the current LTR.
With qgis/qgis:latest everything works, but with qgis/qgis:release-3_22 it
produces the error described above.
While investigating the problem, I also tried to use older versions:
qgis:final-3_22_12 -> KO
qgis:final-3_22_11 -> KO
qgis:final-3_22_10 -> KO
qgis:final-3_22_9 -> OK (it seems to work as expected until this version)
Were there any significant changes between 3_22_9 and 3_22_10 that might
have caused this? Do you have any suggestions?
Thank you,
Paolo

-- 

*PAOLO TORMENE* senior software developer +39 0382 5169882

*GLOBAL EARTHQUAKE MODEL * working together to assess risk

*GEM -* globalquakemodel.org  *T -*
@GEMwrld  *F -* GEMwrld

___
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] Documentation repository looking for developers

[Tim Sutton via QGIS-Developer]

Hi Harrisou



On Mon, Nov 7, 2022 at 6:40 AM Delaz J  wrote:

> Hi Tim,
>
> Thanks for replying. I appreciate.
>
> OK, if no one steps up meanwhile, let's see how we can collaborate with
> the new recruit. But I feel that, at the beginning, he will be more skilled
> for general coding matters ("Code/Setup" section) than QGIS specific issues
> as reported in sections "Writing" and "Triage". No?
>

Yes their help would be in the context of section #1 in your list. I do
know that Anita has been looking at how to use QGIS funds to get you more
support which hopefully provides some mechanism to address some of your
other items.

How about you come and join the PSC call tomorrow evening - we regularly
discuss how we can help you and the docs team, but it might be more useful
if you are actually in the conversation!

Regards

Tim




> Kind regards,
>
> Harrissou
> Le 05/11/2022 à 23:54, Tim Sutton a écrit :
>
> Hi Harrisou!
>
> Top posting here since I cannot address the items individually. We are in
> the last stages of hiring a QGIS Jr Web Developer for one year under
> funding from QGIS.org. I think quite a few of the things on your list below
> are things we might be able to assign to the person we appoint. So I warmly
> invite you to maybe do some collaboration with the person when they
> 'arrive' and we can assign them tasks that will help you.
>
> One specific point on #3 below, Mathias Kuhn was working on some Transifex
> cleverness at the Firence hackfest for the web site - maybe some of this
> logic can also be ported to pull instead of push for the docs.
> https://github.com/qgis/QGIS-Website/blob/master/.github/workflows/tx_push.yml
>
>
> Regards
>
> Tim
>
>
> On Thu, Oct 20, 2022 at 10:07 AM DelazJ via QGIS-Developer <
> qgis-developer@lists.osgeo.org> wrote:
>
>>
>> Hi dear devs,
>>
>> With feature freeze/bug fixes period almost finished, and before you get
>> busy with pushing cool and nice features for the next 3.30 branch, I'd like
>> to share with you a few cool features the documentation repo will also be
>> really happy to get from your skills.
>>
>> *Code/Setup*
>>
>> 1. Create a github action to automatically assign labels to issue reports
>> generated from merged pull requests in code repo, to help us quickly
>> triage. See #50562  and #7826
>> 
>>
>> 2. To the generated issue reports, we also have to assign the milestone,
>> that is the next LTR we will document it in... An automatic assignment
>> would also be great. See #7828
>> 
>>
>> 3. If the move away from Transifex is not yet on the radar, a github
>> action to regularly pull unfinished translation files would be welcome. See
>> #7827 
>>
>> 4. Help setup the release branches to allow automatic merge when tests
>> pass. See #7837 
>>
>> 5. Fix text frame width in the pyQGIS API documentation. See #36
>> 
>>
>> *Writing*
>>
>> If you instead feel like writing , there are some outdated, confusing
>> instructions in the docs for beginners in coding:
>>
>> 1. how to configure python path
>> 
>> from within QGIS or custom application: See #6179
>>  and attempts to
>> fix it at #6306 ,
>> #7139  and #7140
>> 
>>
>> 2. methods and tools to debug code/plugins: see #7836
>> 
>>
>> 3. as usual, review of current pull requests
>>  is still welcome
>>
>> *Triage*
>>
>> If you don't feel like coding nor writing, you can just tell us whether
>> you think that any of these reports is worth documenting and how we could
>> address it: ToDocOrNotToDoc
>> 
>>
>> As you can see, the needs are diverse; it is about coding, setup,
>> triaging and writing so you probably will find something for you (I hope)
>> and do it faster than in my unsuccessful attempts.
>> *The docs needs the devs*.
>>
>> Kind regards and looking forward,
>> 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
>>
>
>
> --
>
> --
>
> Tim Sutton
> Visit http://kartoza.com to find out about o