Hi Michael,

Sorry to hear that you couldn't find your way in the docs.
Do not worry about all the markup codes, they indeed are easier to apply than 
it may look, and we have tools and people ready to help fix anything. Most of 
the times, following what is already used in the file you are modifying makes 
you quickly learn the syntax. No worries for that.
If you found this page: 
https://docs.qgis.org/testing/en/docs/documentation_guidelines/first_contribution.html#using-the-github-web-interface/
 and was able to go through, then I'd say that you are ready to jump in. 

Yes, we do not expose priorities, I don't know if we have features that we'd 
like to prioritize; discussion on this subject did not go that far.
However, for first time contributors, there's a selection of issue reports 
labeled as "easy" that can be of a good start: 
https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aissue+label%3AEasy+is%3Aopen
 (we should triage the list and tag more)
They, most of the times, are fixed within a single file, or are some kind of 
repeating tasks. 
About your issue with the PG setting "Only look in the public schema", if it's 
a default setting, I'd consider that a bug than a feature to document but we 
are open to discuss whatever you feel is worth knowing in the doc, for less 
user frustration. Everything is welcome.
No special background is required to contribute imho; as a QGIS user, you 
probably know things that others do not and not yet documented. Not all the 
matters are cartographic-centered. Also, while there still are some efforts to 
do in this area, developers try to clearly detail their changes so that 
updating the docs becomes easy for anyone. Some other helps one can provide, 
which are important but not always mentioned:
- update screenshots (obsolete screenshot can be confusing for beginners)
- Or review the docs to fix English (not all the writers are fluent English 
speakers - I'm not.)

Sorry for the length. All I want to say is that, if you want to help in 
documentation, you are more than welcome. We are happy to "mentor" you on the 
technical aspects while you could mentor us on the writing ones. And we provide 
a more complete docs to QGIS users.

Looking forward,
Harrissou

Le sam. 11 juil. 2020 à 23:02, Michael Goldstein <
michael.goldste...@gmail.com> a écrit :

> Thanks for reaching out to me.  I did spend some time yesterday on GitHub 
> trying to puzzle out how to get started.  There's a fairly daunting set of 
> editing conventions and mark-up codes to learn, though I imagine it's 
> easier than it looks once you get going.
>
> A bigger issue for me is that I couldn't figure out where to start, i.e. I 
> didn't find a list of topics or chapters or sections that the QGIS-team has 
> prioritized as needing updating.  Also, while I've been a member of GitHub 
> for years, I've never used it as a contributor, only as someone who was 
> downloading code (typically JavaScript libraries from developers). Another 
> thing to learn....
>
>  
> I'm also trying to figure out the best way for me to "fit in".  My 
> background is a little unusual in that I have no formal training in GIS or 
> cartography, and am totally self-taught, which means I've been an avid 
> consumer of QGIS documentation over the years.  So I'm probably better 
> suited to work on introductory materials than cartographic-intensive ones.  
> The good news is that I still remember a lot of the issues I dealt with.
>
> In May, I started using Postgres with QGIS.  I installed it using 
> PostgreSQL 12, and pgAdmin 4.  Frankly, I thought the documentation could 
> have been a lot better, especially working on a Mac.  Still, I managed to 
> get everything running in about a day until I started defining multiple 
> Schema instead of dumping everything into the Public schema.  It was 
> mystifying why these views and tables would show up in the DBManager but 
> not in the browser.  After 3 days of frustration, I nearly abandoned 
> PostGIS.  Then, purely by accident,  I noticed that the PostGIS  connection 
> dialog has a checkbox specifying "Only look in the 'public' schema", 
> checked by default.  Unchecked the box, and my schema appeared!  
>
> If improving that aspect of the documentation is of interest, it's 
> something I would love to work on.  
>
> That said, I'm open to suggestions.
>
> Regards,
> Michael
>  
>
>
>
> DelazJ wrote on 7/11/20 3:38 PM:
>
> Hi Michael,
>
> Thanks for offering your help. Happy to welcome more experimented writers. 
> Documentation sources are available at 
> https://github.com/qgis/QGIS-Documentation, with a list of features to 
> document at  https://github.com/qgis/QGIS-Documentation/issues. You can 
> find some contribution guidelines at 
> https://docs.qgis.org/testing/en/docs/documentation_guidelines/index.html 
> but feel free to ask if anything is unclear.
> As Andreas mentioned, you can also join the qgis-community-team list (
> https://lists.osgeo.org/mailman/listinfo/qgis-community-team) where we 
> sometimes hold "meta" discussion on the future of the documentation.
>
> Greetings,
> Harrissou
>
> Le ven. 10 juil. 2020 à 16:05, Andreas Neumann <a.neum...@carto.net> a 
> écrit :
>
>> Hi Michael,
>>
>> Or you could buy a used Intel Mac that is only 1-3 years old. I would 
>> assume that many Apple afficionados are eager to jump to new hardware and 
>> would give away the old Intel stuff for a bargain. If QGIS is important to 
>> you, that might be a better deal than becoming an early adopter of arm 
>> hardware and suffer from all the early problems. Over the years - after all 
>> the major problems are solved, I would agree that a more energy efficient 
>> processor sounds compelling.
>>
>> About documentation: documenter are always welcome. The introduction can 
>> be found at https://www.qgis.org/en/site/getinvolved/document.html - 
>> there is a dedicated mailing list for documenters and you need a github 
>> account.
>>
>> Thanks in advance for your efforts in joining the documentation team!
>>
>> Greetings,
>>
>> Andreas
>>
>>
>> On 2020-07-10 15:51, Michael Goldstein wrote:
>>
>> Thanks to everyone who responded to my email.
>>
>> I'm currently running a 27" late-2013 iMac, whose life I extended by 
>> upgrading the boot drive to SSD.  While it's still a capable machine, I 
>> don't think it has 2+ more years left in it.  Sigh.  So I may be forced to 
>> make the ARM transition sooner rather than later, unless I decide to 
>> upgrade to an Intel iMac instead (which is not so desirable given my other 
>> commitments to the Apple eco-system)..
>>
>> I've been running QGIS on Macs since 1.x.  Over the years Mac support has 
>> been spotty even into the 3.xx era.  For example, a few months ago I had to 
>> run the Windows version in a VM to export a georeferenced PDF. That was a 
>> python issue, I think... QGIS 3.8 needed a later version of phython which 
>> didn't then exist for Mac.  That said, a sincere thanks to kyngchaos making 
>> it possible to run on Mac at all for many of those years!
>>
>> Good news that the port to ARM should be straight-forward.  I do hope it 
>> becomes a priority because the inherent energy efficiency of the ARM 
>> chipsets should make for some compelling hardware, particularly for laptop 
>> users.
>>
>> Finally, I would like to volunteer to write some documentation.  What's 
>> the best way to do that?
>>
>> Michael
>>
>>
>>
>> qgis-user-requ...@lists.osgeo.org wrote on 7/10/20 2:33 AM: 
>>
>> Send Qgis-user mailing list submissions to
>>     qgis-user@lists.osgeo.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>     https://lists.osgeo.org/mailman/listinfo/qgis-user
>> or, via email, send a message with subject or body 'help' to
>>     qgis-user-requ...@lists.osgeo.org
>>
>> You can reach the person managing the list at
>>     qgis-user-ow...@lists.osgeo.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Qgis-user digest..."
>>
>>
>> Today's Topics:
>>
>>     1. export a composite image to kmz format (carlos h)
>>     2. Re: New Apple Macintosh ARM Chipsets
>>        (Priv.-Doz. Dr. Maria Shinoto)
>>     3. Re: export a composite image to kmz format (Nicolas Cadieux)
>>     4. Re: Closest Distance of a point within a polygon to the
>>
>>        closest part of that polygon and the name of the adjacent    polygon
>>        with the common boarder (David Kabay)
>>     5. Re: New Apple Macintosh ARM Chipsets (Saber Razmjooei)
>>     6. Re: New Apple Macintosh ARM Chipsets (Andreas Neumann)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 9 Jul 2020 17:07:14 -0600
>> From: carlos h <carloslda...@gmail.com>
>> To: qgis-user <qgis-user@lists.osgeo.org>
>> Subject: [Qgis-user] export a composite image to kmz format
>> Message-ID:
>>     <CAKrv22yPfr=btxtpsfpmgvkumsumruqjyjbpvuxh2zkrlhq...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello! I am with QGis version 3.10.x.
>>
>> How can I export a composite image to kmz format?
>>
>> Thank you
>> --
>> CA
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.osgeo.org/pipermail/qgis-user/attachments/20200709/2ee2982f/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 9 Jul 2020 23:34:00 +0000
>> From: "Priv.-Doz. Dr. Maria Shinoto"
>>     <maria.shin...@zaw.uni-heidelberg.de>
>> To: Michael Goldstein <michael.goldste...@gmail.com>
>> Cc: "qgis-user@lists.osgeo.org" <qgis-user@lists.osgeo.org>
>> Subject: Re: [Qgis-user] New Apple Macintosh ARM Chipsets
>> Message-ID:
>>     <1b8a9ddb-c742-4b5a-a674-19bb1661a...@zaw.uni-heidelberg.de>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Hi,
>>
>>
>> earlier posts said that a port to ARM architecture should not be too big of 
>> a problem.
>>
>>
>> I do not remember the details, but my conclusion was: Just wait, no problems 
>> to expect.
>>
>>
>> But I have to admit that I own a MacBook Pro from 2019 and do not plan to 
>> change in the next five or more years. I would hesitate to buy ARM 
>> architecture in the next 12 months anyway.
>>
>> Best,
>> Maria
>>
>> Am 09.07.2020 um 22:57 schrieb Michael Goldstein <
>> michael.goldste...@gmail.com>:
>>
>>
>>
>> I've just joined this email list, so if this has been covered earlier, I 
>> apologize.  Also, let me know if I should be directing this question to a 
>> different mailing list (Developer list?).
>>
>> Do plans exist to port QGIS to the new Apple Mac ARM architecture?
>>
>>
>> While I am not technical enough to help with the coding/re-compiling, I am a 
>> good documentation writer and would be happy to help document a new Mac 
>> release.  How should I volunteer?
>>
>> Michael
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 9 Jul 2020 20:08:15 -0400
>> From: Nicolas Cadieux <njacadieux.git...@gmail.com>
>> To: carlos h <carloslda...@gmail.com>
>> Cc: qgis-user <qgis-user@lists.osgeo.org>
>> Subject: Re: [Qgis-user] export a composite image to kmz format
>> Message-ID: <2ee34401-012d-46de-9234-0bb0f55c2...@gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi,
>> I believe only Vector layers are supported. Kmz is a zipped kml.
>> Nicolas
>>
>>
>> https://gdal.org/drivers/vector/kml.html
>>
>>
>> Keyhole Markup Language (KML) is an XML-based language for managing the 
>> display of 3D geospatial data. KML has been accepted as an OGC standard, and 
>> is supported in one way or another on the major GeoBrowsers. Note that KML 
>> by specification uses only a single projection, EPSG:4326. All OGR KML 
>> output will be presented in EPSG:4326. As such OGR will create layers in the 
>> correct coordinate system and transform any geometries.
>>
>>
>> At this time, only vector layers are handled by the KML driver. (there are 
>> additional scripts supplied with the GDAL project that can build other kinds 
>> of output)
>>
>>
>> Nicolas Cadieux
>> Ça va bien aller!
>>
>> Le 9 juill. 2020 à 19:07, carlos h <carloslda...@gmail.com> a écrit :
>>
>>
>>
>> Hello! I am with QGis version 3.10.x.
>>
>> How can I export a composite image to kmz format?
>>
>> Thank you
>> --
>> CA
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.osgeo.org/pipermail/qgis-user/attachments/20200709/6f7ebf34/attachment-0001.html
>> >
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Mon, 10 Aug 2020 12:19:23 +0800
>> From: "David Kabay" <dka...@iinet.net.au>
>> To: <Qgis-user@lists.osgeo.org>
>> Subject: Re: [Qgis-user] Closest Distance of a point within a polygon
>>     to the    closest part of that polygon and the name of the adjacent
>>     polygon with the common boarder
>> Message-ID: <008501d66ecd$6e40a650$4ac1f2f0$@net.au>
>> Content-Type: text/plain; charset="utf-8"
>>
>>          Hi
>>   I have a challenge.  I have 2 vector data sets.  One is point vectors
>> (Occurrence of a soil fungus  Pc at a point  +red  with a year of sampling
>>
>> as a label)  and polygon vectors that show the various surface geologies in
>> an area ( the name is on the boundary (purple)  Inside of the one it is
>> e.g. S10, S8 Mc1 etc.
>>     QGIS can give me the number of Pc sample points in each polygon which 
>> I have
>> done.  I want to be able to get the distance from the point to the NEAREST
>>
>> boundary and the other name of the surface geology of the closest adjoining
>> polygon I want it for all Pc points
>> How do I do that in QGIS ??
>>             Thanks Dave
>>   Dave Kabay
>> 19A Priestley Street
>> Embleton WA  6062
>>   Phone 08 6142 6756  Mob 0417 950 508
>>   -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <
>> http://lists.osgeo.org/pipermail/qgis-user/attachments/20200810/6ab731f1/attachment.html
>> >
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Fri, 10 Jul 2020 06:49:22 +0100
>> From: Saber Razmjooei <saber.razmjo...@lutraconsulting.co.uk>
>> To: "Priv.-Doz. Dr. Maria Shinoto"
>>     <maria.shin...@zaw.uni-heidelberg.de>
>> Cc: Michael Goldstein <michael.goldste...@gmail.com>,
>>     "qgis-user@lists.osgeo.org" <qgis-user@lists.osgeo.org>
>> Subject: Re: [Qgis-user] New Apple Macintosh ARM Chipsets
>> Message-ID:
>>     <CAH=WbRAaoAYRyerVJcUNqok2ryNeAt7Z1XNE=tuvfpoyw0m...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi
>>
>> We have already ported QGIS to iOS for Input app (https://inputapp.io and
>> https://github.com/lutraconsulting/input-sdk/tree/master/ios). iOS is ARM
>> based architecture. Hence, it should be possible and straightforward to
>> support the new mac ARM too. It also depends on the upstream support from
>> Apple, Qt, Python...
>>
>> Kind regards
>> Saber
>>
>> On Fri, 10 Jul 2020 at 00:33, Priv.-Doz. Dr. Maria Shinoto <
>> maria.shin...@zaw.uni-heidelberg.de> wrote:
>>
>> Hi,
>>
>> earlier posts said that a port to ARM architecture should not be too big
>> of a problem.
>>
>> I do not remember the details, but my conclusion was: Just wait, no
>> problems to expect.
>>
>> But I have to admit that I own a MacBook Pro from 2019 and do not plan to
>> change in the next five or more years. I would hesitate to buy ARM
>> architecture in the next 12 months anyway.
>>
>> Best,
>> Maria
>>
>> Am 09.07.2020 um 22:57 schrieb Michael Goldstein <
>>
>> michael.goldste...@gmail.com>: 
>>
>>
>> I've just joined this email list, so if this has been covered earlier, I
>>
>> apologize.  Also, let me know if I should be directing this question to a
>> different mailing list (Developer list?). 
>>
>> Do plans exist to port QGIS to the new Apple Mac ARM architecture?
>>
>> While I am not technical enough to help with the coding/re-compiling, I
>>
>> am a good documentation writer and would be happy to help document a new
>> Mac release.  How should I volunteer? 
>>
>> Michael
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>>
>>
>> _______________________________________________
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
> -- 
> *************************
>  Michael Goldstein
>  609-638-3250 (m)
>
>

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Reply via email to