Le 23/07/2014 16:29, AntonioLocandro a écrit :
Just a thought here but if billion dollar company having thousands of
workers releases just one major version (with actual new features and
refactoring) and one or two minor releases (mainly bug fixes) why should
QGIS try to do something like the
Il 22/07/2014 21:27, Andrew ha scritto:
Also, I was just looking at the QGIS homepage and found it quite
difficult to figure out how to contribute to documentation.
Agreed: please make suggestions, even better pull requests, so we can improve
in this
regard.
Thanks.
--
Paolo Cavallini -
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
Why QGIS is in such a need to release every 4/6 months? It's obvious the
project doesn't have enough resources and I find a bit troublesome that
developers in the period add tons of new features yet bug squashes are
relatively small and left basically for the last week to be covered by
funding.
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
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
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
Am 22.07.2014, 12:16 Uhr, schrieb Derek Hohls dho...@csir.co.za:
Is it not possible to require an absolutely minimum entry, at the
correct place in the docs, for a new feature? For example, if a
developer adds a new function X to a list of existing functions,
already documented in
Hi,
I don't think splitting development resources to maintain an LTS branch is
going to solve the real issues. In fact, it will probably just cause more.
It seems to me that it all boils down to needing more time between releases:
* Documentation and development teams need to work more together
Hi All,
It is hard to figure out where in the conversation to interject but
Victors counter-suggestion appears appropriate to me.
Being involved in several open source projects, creating tutorials for
these and having in the past been involved with trying to contribute to
the main
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,
Hi,
I'm also a trainer for QGIS software (I have 2-week-courses every 3 month)
and I fully agree with Lene's concerns about the (new) release time
schedule.
And - in my opinion - it is not only much more work for QGIS trainers to
keep their papers up-to-date.
I think it also confuses the QGIS
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
17 matches
Mail list logo
