Hi,
a good software developer doesn't need to be a good or even acceptable
documentation writer. It is a completely different set of skills IMHO,
starting with the language skills, ending with the different point of view
to the problem (we developers tend to looks at the algorithm selection,
code
Dear Jürgen,
Thank you very much for your quick reply. I have been struggling from
the past one month, installing multiple times on multiple machines. I
couldn't succeed.
As I understand
1) Use the QGIS version 3.16 repository
2) Use Microsoft Visual Studio 2019 compiler
3) Use the up
Hi Alister
On Wed, Apr 14, 2021 at 8:55 AM Alister Hood wrote:
>
> What I'm suggesting is that a slightly more general solution would be
> useful in more situations. In your words, it would "avoid the need to
> create derived raster files" in a lot more situations.
>
> The only downside is that
Greetings,
Matthias there is one point that you raised that should be a non-issue. The
barrier of entry aspect, I think this is false.
Non-core contributor often need to write more documentation to showcase the
use of their work and its behaviour. In some way documenting properly
things is more o
On Thu, 15 Apr 2021 at 10:15 pm, Alessandro Pasotti
wrote:
> Hi,
>
> I think it would be wise to add a new policy about documentation for
> new features which requires a parallel Documentation PR to be opened
> and approved before we accept and merge new features into master.
>
> This is a common
Hi Raghunath,
On Thu, 15. Apr 2021 at 11:35:30 -0700, rnathre...@sanasw.com wrote:
> I am trying to build the QGIS on windows and followed the instructions given
> at
> https://github.com/qgis/QGIS/blob/release-3_16/INSTALL.md#4-building-on-windows.
That is not up-to-date as current master stopp
Hi,
I am trying to build the QGIS on windows and followed the instructions
given at
https://github.com/qgis/QGIS/blob/release-3_16/INSTALL.md#4-building-on-windows.
When the ConfigOnly.bat command issued from the command prompt I got the
following error. I couldn't understand the error. Can
Hi
Thanks for raising this topic Alessandro. I agree we need better
documentation.
Some questions:
What do we do with interesting feature pull requests and no documentation?
Stale away?
Who decides if the quality of the documentation is good enough?
Who decides if documentation is required?
Will
If there is a large cluster of points obscuring the selected point, even
that method will not work.
Has there been any interest in changing this behavior in QGIS?
On Thu, Apr 15, 2021 at 11:46 AM Nicolas Cadieux <
njacadieux.git...@gmail.com> wrote:
> Hi,
> Indeed... I usually select a thicker l
Hi,
On Thu, 15. Apr 2021 at 14:15:16 +0200, Alessandro Pasotti wrote:
> - most of the times authors have been paid for the new feature and it doesn't
> look fair to me that the documentation is left to volunteers
> Any opinion?
I'd say requiring volunteers to do anything they didn't volunteer
Hi again,
Sorry for the delay.
Julien, thank you for the message I agree with about Alister proposal!
Alister, thank you for the explanation and for the advice!
Concerning the project and so the renderer feature, the first result I would
like to achieve is to style the layer, I agree it would be
Any opinion?
+1
___
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
I have a user complaint with QGIS who explained that when point features
overlap and one is selected from the attribute table but is underneath
other features, you cannot see it highlighted because it is covered by
other points. Is there any way to have it show that there is a highlighted
feature
+1 for me
thanks Ale for raising this
Il 15/04/21 14:15, Alessandro Pasotti ha scritto:
> Hi,
>
> I think it would be wise to add a new policy about documentation for
> new features which requires a parallel Documentation PR to be opened
> and approved before we accept and merge new features into
Hi,
I think it would be wise to add a new policy about documentation for
new features which requires a parallel Documentation PR to be opened
and approved before we accept and merge new features into master.
This is a common policy for other open source projects: documentation
is a first class ci
15 matches
Mail list logo
