I´ve now been using-, bug reporting- and making tutorials for QGIS since 1.7
and I still find it difficult to make stable contributions in several ways: In
this tread everyone write ‘more money’ or ‘Work together’
I want to donate time – but find it difficult to find a limited project. As
Il 23/07/2014 08:58, Lene Fischer ha scritto:
I´ve now been using-, bug reporting- and making tutorials for QGIS since 1.7
and I
still find it difficult to make stable contributions in several ways: In this
tread
everyone write ‘more money’ or ‘Work together’
I want to donate time –
Hi Simon,
this sounds like a very good idea to me.
At the moment documenters look at the commit logs for a [FEATURE] comment
and add it to a wiki list. Then search through all mls, wikis and blogs, if
there is some howto available or at a least a short discussion or
description about that
We could make a script to just pull out everything with [FEATURE] in the
commit between a date range if that will help. Maybe we could create stubs
in Tims changelog system using something like this.
- Nathan
On Wed, Jul 23, 2014 at 5:28 PM, Otto Dassau das...@gbd-consult.de wrote:
Hi Simon,
Hi Nathan,
thanks for the offer, but this is not the problem. After feature freeze we
currently do a git log --since=date --grep='FEATURE', that's ok. And Tims
changelog is also very helpful and often already fine as a beginning.
The result is in the wiki: http://hub.qgis.org/wiki/17/ManualTasks
I think stubs from github to the visual changelog would be great.
Also, it would be great if the visual changelog could some day be hosted
under a qgis.org address. The visual changelog is very useful and I
always point users to it after a new version was released. It looks a
bit strange if the
+1
2014-07-23 10:18 GMT+02:00 Andreas Neumann a.neum...@carto.net:
Also, it would be great if the visual changelog could some day be hosted
under a qgis.org address. The visual changelog is very useful and I
always point users to it after a new version was released. It looks a
bit strange
Hi,
I would prefere another solution instead of changing the releases. The
documentation team is in the same situation. We are always behind the
releases, but the problem I see is that there are not enough people working
on the documents. At the moment we were not even able to start updating the
+1 with Otto, many many trainers do still almost all material from scratch,
we loose a lot of good contributors, and we loose money also (as a funder).
We started courses last year and pushed the will to have teachers contribute
to bugtracking and contribute to open source version of the docs.
Hi Otto,
You make some excellent points. Just to follow on one of them:
But usually customers and developers don't think about also spending
an additional
little amount to document the feature in the QGIS docs and training
material.
I think that's a QGIS problem. I know when I get quotes for
+1 to what Otto said. Very good point. Those creating training materials
should coordinate and help the core QGIS documentation (both the manual and
the training manual) improve.
The solution is very simple: Require up to date, accurate documentation
for all commits of new features. This is
+ 1 to Otto and Victor.
Developers should develop, the can document some aspects of
code/feature (and they
already do this!) but we can not ask them to write manuals
2014-07-22 13:01 GMT+03:00 Victor Olaya vola...@gmail.com:
+1 to what Otto said. Very good point. Those creating training
Except that self-evidently the current solution doesn't work well. Of the
three projects I listed, QGIS has by far the worst documentation; as Otto
noted, they've not even started updating for 2.4 yet.
Just looking now, not a single one of the QGIS Geoalgorithms that I've
ever looked at (which
Just looking now, not a single one of the QGIS Geoalgorithms that I've
ever looked at (which are I think is what Victor is referencing) have
anything in the help tab. And these are a core part of the software.
Yes that's what I mean. But, IMHO, it's better to have that functionality
there
Il 22/07/2014 12:41, Victor Olaya ha scritto:
...
I am not saying that this is ideal, and that developers should not write
docs. I am
saying that time is limited and, if we put those restrictions, we might end up
rejecting a lot of interesting functionality.
Sorry for jumping in late. These
Hi all,
On Tue, Jul 22, 2014 at 10:10 AM, Otto Dassau das...@gbd-consult.de wrote:
a) Trainers could combine their forces and prepair general training
materials
together that everybody can use and extend. All tools and the document
basis
is available and provided by QGIS project in the
Is it a common practice for developer to fill feature requests for
Documentation and help whenever they create new features? This would still
free developers to keep creating good stuff, and help others to keep track
of what needs attention in Docs. Using the visual changelog and scrolling
Hi Lene,
Does Your proposal mean that those universities, which start to
use QGIS and QGIS based material for education, start to support
QGIS development financially and with other resources like man
power for testing, fixing etc. ?
Cheers,
I also do some short training courses
using QGIS, and I fully understand and support Lene's idea.
On 21/07/2014 18:35, Lene Fischer wrote:
Hi,
This is not a mail
about bugs or issues on a
19 matches
Mail list logo
