[Qgis-psc] Fwd: QGIS Usage survey

[Andreas Neumann]

The survey looks good.

I discovered one small typo and have two suggestions:

Typo:
QGIS does not enable me to carry out the critical tasks I need, I need 
so use other GIS packages
--> ..., I need to use ...

Suggestion 1:
For the question "How often do you use the QGIS documentation":

Add an option: "Occasionaly" - so we have something in between "Monthly" 
and "Never" - I consider myself to be in that group.

Suggestion 2:
Ask for domain/industry - like:

I work for

- private consulting company
- government (federal level)
- government (province level)
- government (municipal level)
- education (university level)
- education (other)
- military/intelligence
- NGO
- private (hobby)
- anything else?

Thanks,
Andreas

On 14.10.2015 09:44, Tim Sutton wrote:
> Apologies I sent this the the gmail PSC group earner by mistake:
>
> @andreas I incorporated some changes to the form to include your ideas
> @paolo I also added some fields to incorporate your ideas
>
> Regards
>
> Tim
>
>> Begin forwarded message:
>>
>> *From: *Tim Sutton <tim at qgis.org <mailto:tim at qgis.org>>
>> *Subject: **QGIS Usage survey*
>> *Date: *14 October 2015 at 06:49:29 SAST
>> *To: *psc at qgis.org <mailto:psc at qgis.org>
>>
>> Hi all
>>
>> I guess you have all been following along on the discussion started 
>> by Andreas about release frequency etc. I was thinking that one issue 
>> we have with these types of discussions is that we lack any 
>> meaningful data - all the arguments are based on anecdotal usage. I 
>> was thinking that it would be good to run a survey like this:
>>
>> http://goo.gl/forms/FPvlBzkquQ
>>
>> We could do an embed of it into our website and market it to the 
>> user, dev, community, ux, twitter etc. mailing lists.
>>
>> I agree that things can be improved and I am thinking that we should 
>> apply basic supply and demand theory: when we have an ‘over supply’ 
>> of patches to QGIS, we should make it ‘more expensive’ to contribute 
>> them by increasing the minimum criteria for submission for example:
>>
>> * requiring tests (for GUI changes too)
>> * requiring complete API documentation (for C++ and Python)
>> * requiring complete end user documentation (the doc team can then 
>> focus on editing docs rather than composing them)
>> * requiring a changelog when appropriate
>> * requiring existing tests all pass
>> * requiring coding standards adherance
>> * requiring bug fixes be supported with a regression test wherever 
>> possible
>>  *etc.
>>
>> (Yes I realise some items in my list are already in place). Of course 
>> this will add more bureaucracy to the process of applying changes to 
>> QGIS and we would need to figure out how to manage that cleanly. I 
>> think another thing high on our agenda at the project level should be 
>> looking to employ one or more developers full time to actually manage 
>> this process. Perhaps we can hold a campaign to fund 1 year salary 
>> for such a person and try to make that happen?
>>
>> But first lets get some real data about who uses QGIS and what their 
>> concerns are. If the PSC is in general agreement, can we put out the 
>> survey to do that? Feel free to suggest additions / changes to the 
>> survey before I send it out….
>>
>> Regards
>>
>> Tim
>>
>>
>>
>>
>>
>>
>>
>> Tim Sutton
>> QGIS Project Steering Committee Member
>> tim at qgis.org <mailto:tim at qgis.org>
>>
>>
>>
>>
>
>
>
> Tim Sutton
> QGIS Project Steering Committee Member
> tim at qgis.org <mailto:tim at qgis.org>
>
>
>
>
>
>
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-psc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20151014/698df110/attachment.html>