On 24-05-17 20:05, Radim Blazek wrote:
> Hi.
>
> On Thu, Jan 26, 2017 at 9:04 PM, Andreas Neumann wrote:
>
>> What is already done:
>> Python plugin update helper 2 to 3
>
> Does it mean a doc? Can you point me to the website? I am looking for
> a python plugin upgrade guide.
Not a guide, but
Hi.
On Thu, Jan 26, 2017 at 9:04 PM, Andreas Neumann wrote:
> What is already done:
> Python plugin update helper 2 to 3
Does it mean a doc? Can you point me to the website? I am looking for
a python plugin upgrade guide.
Radim
___
QGIS-Developer mai
Hi,
QGIS is cutting edge when it comes to data interoperability. It consumes
all kinds of data. It is amazing!
But when it comes to style interoperability, it is not so good. I know
there are a lot of different style languages and libraries, and they
keep changing. Urh!
This SLD compatibility en
I think is really important SLD compatibility work (crowdfunding) by
GeoSolution... QGIS->SLD/SE 1.1
In this moment SLD read back is not correctly done by QGIS, e.g.
SLD/SE1.1->QGIS but almost few people are working on this without a
structured road map (I should say that is not an attractive task)
Hi Regis,
Yes - we already publish our financials. Although in textual form:
see
http://www.qgis.org/en/site/getinvolved/governance/finance/index.html
I will perhaps cross-reference the financial reports on the page
explaining the sponsorship. Makes sense.
The report for 2016 will soon be p
>
> It was my argument to "sell" the sponsorship to our users.
>
Good to know ! I probably could have sold that to my previous employer that
way. So displaying a diagram explaining the average proportion of fund
destinations on the sponsoring page could be great. Could be something like
that "spons
Hi Régis,
No, we did not change our policy regarding earmarked sponsoring.
However, looking at our expenses, bug fixing is the biggest item
(usually around 2/3 of the expenses). So you can easily claim that
someones sponsorship covers that ;-) In reality, of course, everything
goes into the poo
ed when we are still documenting
3.0 features.
my2cts,
Harrissou
Envoyé depuis mon HTC
- Reply message -----
De : "Andreas Neumann"
Pour :
Objet : [Qgis-developer] Status of QGIS3
Date : jeu., janv. 26, 2017 21:04
Hi Paolo, Hi all,
We just had the annual Swiss QGIS user group
Hi Andreas,
thanks for sharing, this is very valuable to other user groups and QGIS
community!
Just a question, up to now, sponsoring could not be oriented and I see that
gold sponsor is dedicacted to bugfixing and QA. Did we change our policy?
If yes, that needs to be wide spread, we might gain s
Il 27/01/2017 09:27, Neumann, Andreas ha scritto:
> Hi Paolo,
>
> Here are the slides from our annual
> meeting:
> https://docs.google.com/presentation/d/1d1ott7W5agb2vvUB8xSfv7x6gE843H-JLw4_OWqyTmc/edit?usp=sharing
>
> However, only a small nr of slides on QGIS 3 itself.
>
> Feel free to re-us
Hi Paolo,
Here are the slides from our annual meeting:
https://docs.google.com/presentation/d/1d1ott7W5agb2vvUB8xSfv7x6gE843H-JLw4_OWqyTmc/edit?usp=sharing
However, only a small nr of slides on QGIS 3 itself.
Feel free to re-use, if you need something.
Andreas
On 2017-01-27 08:05, Paolo C
Hi,
Well, things are going so fast that even for developpers, it's hard to
start a work not already being worked on somewhere else.
Can I ask for all devs to use the WIP (Work in Progress) label in
https://github.com/qgis/qgis3.0_api issues?
We in fact started to work on issues that became Pull R
Il 26/01/2017 21:04, Andreas Neumann ha scritto:
> Some good news:
>
> The Swiss QGIS user group decided yesterday to fund a few of the above
> "what still needs to be worked on" list:
>
> * Print composer refactoring (Nyall)
> * Porting core of Processing to C++ (Nyall)
> * Redesign of GU
Il 27/01/2017 07:42, Nyall Dawson ha scritto:
> On 27 January 2017 at 16:30, Neumann, Andreas wrote:
>
>>
>> Obviously I missed a lot. I apologize. I was trying to be brief and
>> concentrate on the very essential work necessary for QGIS 3. Every version
>> obviously has plenty and numerous impro
On 27 January 2017 at 16:30, Neumann, Andreas wrote:
>
> Obviously I missed a lot. I apologize. I was trying to be brief and
> concentrate on the very essential work necessary for QGIS 3. Every version
> obviously has plenty and numerous improvements, regardless if it is a major
> version change
Hi Nyall,
On 2017-01-27 05:27, Nyall Dawson wrote:
> This is quite an incomplete list ;)
>
> Check https://gist.github.com/nyalldawson/95738ec265c7f9bdb64b15672c210bb7
> for a better (albeit somewhat raw) list!
>
> Nyall
>
> What is already done:
>
> Migration to qt5 and Python 3
> Python pl
On 27 January 2017 at 06:04, Andreas Neumann wrote:
> Hi Paolo, Hi all,
>
> We just had the annual Swiss QGIS user group meeting yesterday. Obviously we
> had to tell our users a little bit about what is already finished, what is
> currently being worked on and what still has to be worked on. So I
Hi Paolo, Hi all,
We just had the annual Swiss QGIS user group meeting yesterday.
Obviously we had to tell our users a little bit about what is already
finished, what is currently being worked on and what still has to be
worked on. So I had to compile a list:
What is already done:
* Migrat
Hi all,
I have to give a short talk on the current status of QGIS3 and the
outlook for the future. The main aim is to grow interest, and ultimately
attract testers, developers, and sponsors.
Topics I thought of are:
* current development state
* what's new for the user
* what's new for the develo
19 matches
Mail list logo
