[Qgis-developer] [Qgis-psc] QGIS Resource Sharing Plugin in core?

[Matthias Kuhn]

Hi Tim,

> Just to emphasize again that anyone is welcome to post here, so
> thanks for sharing your thoughts.

Thanks for reassuring, I always appreciate that the PSC is open about this!

> I'm ok with anyone asking the PSC for input if they feel the need for it.

Sure, everyone is free to ask the PSC for input at any time!
My point is just that I think there is still the need for a more public
discussion where everybody can bring their thoughts to the table and we
should at the moment stick to looking for input and not yet decisions.

All the best
Matthias


On 02/01/2017 12:02 PM, Matthias Kuhn wrote:
> Hi all,
> 

> 
> I think the whole "issue" is based on a series of misunderstandings and
> I would be very glad if we could flatten the waves and take this
> decision based on arguments instead of escalating it by requesting a PSC
> decision.
> 
> First off, as far as I could see, everybody liked the outcome of the
> GSOC and everyone is happy with the outcome. I don't think the plugin or
> the project is at risk wherever it may live, be it in core or as a
> separate plugin. The job done by Akbar and Alesandro is of great
> importance and it's going to be even more important the more resources
> are in there. Thank you very much for the amazing job!
> 
> Apparently, the clearance to 1) port this to a core plugin and 2) which
> parts of it and 3) the future of core plugins per se has not been
> understood the same way by all parties. A merge which was done in an
> unfortunately quick timeframe caused different parties to react just as
> quickly.
> 
> From what I can see, there was a lot of personal investment by Alesandro
> done into the plugin. This was done under the clear assumption that it
> is to bring this plugin to core. I am absolutely convinced, that this
> work was very valuable for the plugin wherever it may live. It's a pity
> to read now, that you feel like the work has been done in vain which I'm
> convinced it's not.
> 
> On the other hand I have noticed a lot of python code / core plugins
> disappear from the qgis repo recently which was not only also a lot of
> work but also makes it easier to update to QGIS 3 (for api changes).
> Everyone involved with api changes knows that python code in the repo is
> particularly hard to handle here. Not to forget that we still not
> recommend that developers start to update their python plugins.
> 
> I would propose to take a step back, discuss what parts of the code
> should be merged and then revisit this discussion, when the general
> porting of plugins starts.
> 
> All the best
> Matthias
> 
> 
> On 02/01/2017 11:30 AM, ElPaso wrote:
>> Hi,
>>
>> I've always been convinced that this plugin for "sharing" was a
>> fundamental feature to share symbology assets (and not only them!!!), so
>> fundamental that having it as a core plugin was taken for granted.
>>
>> If the problem is the lack of quality of the plugin, well I can take it
>> and admit that we've failed the GSOC. No problems with that.
>>
>>
>> But now I start thinking that I might have completely misunderstood the
>> importance of the plugin in the first place.
>>
>>
>> Can I ask the PSC to take (or confirm) position on this topic?
>>
>> See: https://github.com/qgis/QGIS/pull/4087
>>
>> There is already enough nonsense in that thread that I don't want to
>> reply more, but of course it's not a +34000 lines of code PR, well, it
>> is if you count jquery.js, *.css, *.html and all Python ext-libs and tests.
>>
>> As for the responsibility: I take it for granted that if you commit a
>> feature you also "commit" to maintain it, but we are a community and we
>> agree to work together for the good of the project, this means that we
>> also agree to cooperate and help each other if needed.
>>
>>
>> Thanks!
>>