Re: [QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Andreas Neumann]

Hi Tim,

The developer map in the about box works fine. I don't see anything 
wrong. What would be the problem?


Thanks for the fixes. One can even learn from the styling of this easter 
egg ;-) like the continuous updates, shadow effects, etc.


And of course the funny details of the hackfests ;-)

Andreas


Am 27.08.2018 um 22:50 schrieb Tim Sutton:
I merged Mathieu’s fix (thanks!) but I think there may still be an 
issue with the developer map in the about box. I can’t test this on 
Mac since we don’t get that tab in Mac so could someone on Linux confirm?


@Richard for Easter egg details see

https://github.com/qgis/QGIS/pull/7714

Regards

Tim Sutton
Co-founder of Kartoza
Ex-QGIS project chairman

On 27 Aug 2018, at 22:31, Richard Duivenvoorde > wrote:



On 08/27/2018 07:58 PM, Andreas Neumann wrote:

Eager to try out the new easter eggs ;-)


Tell us, Tell us :-)

Richard
___
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



___
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


___
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

Re: [QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Tim Sutton]

I merged Mathieu’s fix (thanks!) but I think there may still be an issue with 
the developer map in the about box. I can’t test this on Mac since we don’t get 
that tab in Mac so could someone on Linux confirm?

@Richard for Easter egg details see

https://github.com/qgis/QGIS/pull/7714

Regards 

Tim Sutton 
Co-founder of Kartoza 
Ex-QGIS project chairman 

> On 27 Aug 2018, at 22:31, Richard Duivenvoorde  wrote:
> 
>> On 08/27/2018 07:58 PM, Andreas Neumann wrote:
>> Eager to try out the new easter eggs ;-)
> 
> Tell us, Tell us :-)
> 
> Richard
> ___
> 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
___
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

[QGIS-Developer] HiRe: RES: Do we really need experimental and non-experimental plugins?

[Borys Jurgiel]

Hi,

Thanks for all your answers. It clearly seems there is no common demand to 
drop it ;) Frankly speaking, I didn't expect it's considered so useful.
Especially thanks to Martin and Paolo for explaining your use cases.

I'm also against restricting the time to be experimental - to keep this 
function as simple and unambiguous as possible. 

Best regards,

Borys

HiDnia poniedziałek, 27 sierpnia 2018 15:38:03 CEST Jorge Almerio pisze:
> Hi devs,
> 
> I agree with Andreas. I think we need experimental and non-experimental
> flags to plugins as it is. And I think that we can NOT restrict the time to
> be experimental. Because it depends on the author available time to make
> his plugin stable. Restrict the experimental plugins would reduce the
> number of plugins been uploaded. To mark as experimental is important for
> the users and for the authors too, because one can help the other to fix
> bugs.
> 
> Jorge Almerio
> 
> 
> -Mensagem original-
> De: QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] Em nome
> de Andreas Neumann Enviada em: segunda-feira, 27 de agosto de 2018 09:42
> Para: qgis-developer@lists.osgeo.org
> Assunto: Re: [QGIS-Developer] Do we really need experimental and
> non-experimental plugins?
> 
> Hi Borys,
> 
> Personally, I think there is a need for the differentiation of
> experimental or not experimental.
> 
> I'd like to keep it as it is.
> 
> Andreas
> 
> Am 27.08.2018 um 02:06 schrieb Nyall Dawson:
> > On Mon, 27 Aug 2018 at 04:11, Borys Jurgiel  wrote:
> >> Hi Lists,
> >> 
> >> Before I make a QEP I'd like to know your general thoughts.
> >> 
> >> After I removed the deprecated plugins filter from the Plugin manager
> >> (and
> >> make them always visible) [1], Alex suggested doing the same with the
> >> Experimental status.
> > 
> > I'm -1 on this. Experimental plugins can be dangerous (some result in
> > crashes, data corruption, etc), and shouldn't be shown by default.
> > 
> >> However, I'm not sure if it makes much sense nowadays. Releasing 'stable'
> >> and 'experimental' versions seems a bit overscaled to me. And there is a
> >> simpler solution: If the recent version is buggy, users can just
> >> download the last working one from the repo and install from zip.
> > 
> > I think that's overestimating some of our user's abilities -- it would
> > take a lot of knowledge that:
> > 1. a plugin is at fault
> > 2. they can overwrite a plugin manually with an earlier version
> > and
> > 3. they can download earlier versions of plugins.
> > 
> > Then, they'd also need to know *which* older plugin version is "good"
> > and should be downloaded.
> > 
> >> The former case, when the
> >> whole plugin is experimental, seems to be often misused: authors can use
> >> it to hide some specialised of localised plugisn from majority of users.
> >> In fact even I committed such clear misuse, marking the Plugin Reloader
> >> as experimental just to not clutter the list for normal users... Another
> >> reason could be a shyness. But again, we have the rating stars now and
> >> don't need to rely on the author's shyness anymore.
> >> 
> >> So... Do you see important reasons to keep this tag? Maybe we should
> >> completely drop it? Or just remove the option to hide them from manager,
> >> leaving the flask icon on the plugin details page?
> > 
> > I think it should be kept. I know of one buggy plugin which recently
> > got marked as experimental, and I'm *very* glad to see this particular
> > plugin hidden from the majority of our users by default.
> > 
> > Nyall
> > ___
> > 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
> 
> ___
> 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
> 
> ___
> 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




___
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

Re: [QGIS-Developer] Do we really need experimental and non-experimental plugins?

[Borys Jurgiel]

Dnia poniedziałek, 27 sierpnia 2018 06:21:17 CEST Paolo Cavallini pisze:
> I agree with Nyall. Furthermore, I'm also -1 on showing deprecated
> plugins. These are mosty useless, sometimes dangerous. I ask to revert
> the change ASAP.

Don't worry, it's still a PR (and there are no deprecated 3.x plugins yet ;)
Richard, do you want to defend this idea or shall we close the ticket? :)

Borys


___
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

Re: [QGIS-Developer] QgsProcessingParameterFile - Multiple extensions

[C Hamilton]

That's too bad. It would be useful. I will need to not use an extension in
this case because it need to import more than one.

Calvin

On Sun, Aug 26, 2018 at 9:41 PM, Nyall Dawson 
wrote:

> On Fri, 24 Aug 2018 at 05:42, C Hamilton  wrote:
> >
> > Does QgsProcessingParameterFile support more than one extensioin ie
> *.kml, *.kmz? I've tried various things but none have worked.
>
> That's not currently supported, unfortunately.
>
> Nyall
>
> >
> > self.addParameter(
> > QgsProcessingParameterFile(
> > self.PrmInputLayer,
> > tr('Import KML/KMZ file'),
> > extension='kml')
> > )
> >
> > Thanks,
> >
> > Calvin
> > ___
> > 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
>
___
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

Re: [QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Richard Duivenvoorde]

On 08/27/2018 07:58 PM, Andreas Neumann wrote:
> Eager to try out the new easter eggs ;-)

Tell us, Tell us :-)

Richard
___
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

Re: [QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Tim Sutton]

Yes please stand by - a fix is in the works….if the internet lets me….

Apologies…..

Tim

> On 27 Aug 2018, at 20:58, Andreas Neumann  wrote:
> 
> Thanks - then I wait for Tim to merge this into master.
> 
> Eager to try out the new easter eggs ;-)
> Greetings,
> 
> Andreas
> 
> Am 27.08.2018 um 19:45 schrieb Etienne Trimaille:
>> There is a PR to fix it from Mathieu: https://github.com/qgis/QGIS/pull/7722 
>> 
>> 
>> Le lun. 27 août 2018 à 13:05, Andreas Neumann > > a écrit :
>> Hi,
>> 
>> After compiling QGIS I can't install QGIS. When i run "ninja install" I
>> get the following error message:
>> 
>> ---
>> 
>> CMake Error at doc/cmake_install.cmake:41 (file):
>>file INSTALL cannot find "/home/an/dev/QGIS/doc/contributors.json".
>> Call Stack (most recent call first):
>>cmake_install.cmake:58 (include)
>> 
>> 
>> FAILED: CMakeFiles/install.util
>> cd /home/an/dev/QGIS/build && /usr/bin/cmake -P cmake_install.cmake
>> ninja: build stopped: subcommand failed.
>> --
>> 
>> Seems like the download/update/install of the contributors.json doesn't
>> work?
>> 
>> Thanks for any hints on how to fix this!
>> 
>> Andreas
>> 
>> ___
>> 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 
>> 
> ___
> 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

—








Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
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

Re: [QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Andreas Neumann]

Thanks - then I wait for Tim to merge this into master.

Eager to try out the new easter eggs ;-)

Greetings,

Andreas


Am 27.08.2018 um 19:45 schrieb Etienne Trimaille:
There is a PR to fix it from Mathieu: 
https://github.com/qgis/QGIS/pull/7722


Le lun. 27 août 2018 à 13:05, Andreas Neumann > a écrit :


Hi,

After compiling QGIS I can't install QGIS. When i run "ninja
install" I
get the following error message:

---

CMake Error at doc/cmake_install.cmake:41 (file):
   file INSTALL cannot find "/home/an/dev/QGIS/doc/contributors.json".
Call Stack (most recent call first):
   cmake_install.cmake:58 (include)


FAILED: CMakeFiles/install.util
cd /home/an/dev/QGIS/build && /usr/bin/cmake -P cmake_install.cmake
ninja: build stopped: subcommand failed.
--

Seems like the download/update/install of the contributors.json
doesn't
work?

Thanks for any hints on how to fix this!

Andreas

___
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



___
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

Re: [QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Etienne Trimaille]

There is a PR to fix it from Mathieu: https://github.com/qgis/QGIS/pull/7722

Le lun. 27 août 2018 à 13:05, Andreas Neumann  a
écrit :

> Hi,
>
> After compiling QGIS I can't install QGIS. When i run "ninja install" I
> get the following error message:
>
> ---
>
> CMake Error at doc/cmake_install.cmake:41 (file):
>file INSTALL cannot find "/home/an/dev/QGIS/doc/contributors.json".
> Call Stack (most recent call first):
>cmake_install.cmake:58 (include)
>
>
> FAILED: CMakeFiles/install.util
> cd /home/an/dev/QGIS/build && /usr/bin/cmake -P cmake_install.cmake
> ninja: build stopped: subcommand failed.
> --
>
> Seems like the download/update/install of the contributors.json doesn't
> work?
>
> Thanks for any hints on how to fix this!
>
> Andreas
>
> ___
> 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
___
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

[QGIS-Developer] Can't install QGIS after compile because of contributors.json

[Andreas Neumann]

Hi,

After compiling QGIS I can't install QGIS. When i run "ninja install" I 
get the following error message:


---

CMake Error at doc/cmake_install.cmake:41 (file):
  file INSTALL cannot find "/home/an/dev/QGIS/doc/contributors.json".
Call Stack (most recent call first):
  cmake_install.cmake:58 (include)


FAILED: CMakeFiles/install.util
cd /home/an/dev/QGIS/build && /usr/bin/cmake -P cmake_install.cmake
ninja: build stopped: subcommand failed.
--

Seems like the download/update/install of the contributors.json doesn't 
work?


Thanks for any hints on how to fix this!

Andreas

___
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

Re: [QGIS-Developer] QGIS 3.2 Connection Oracle very slow

[Carlos López PSIG]

Hi,
I opened a ticket because the problem follow,  link


Anybody have comments?

Best regards,


* *
*PSIG*
Implementació, gestió i formació SIG

*Carlos López Quintanilla*

www.psig.es
carlos.lo...@psig.es
+34 699.680.261

Nota legal: Este mensaje y cualquier archivo adjunto está destinado
únicamente a la
persona a quien se dirige y es confidencial. Si usted ha recibido este
mensaje por
error, por favor, comuníqueselo al remitente y bórrelo inmediatamente. La
utilización ,
revelación y/o reproducción del mensaje puede constituir un delito.

Protección de Datos: Le informamos que sus datos de contacto electrónico se
hallan
incorporados a un fichero titularidad de CARLOS LÓPEZ QUINTANILLA, al
objeto de
envío de información, respuesta a consultas y contactos genéricos.
Puede ejercer los derechos de acceso, rectificación, cancelación y
oposición que
establece la LOPD en cualquier momento, mediante escrito, acompañado de
copia de
documento oficial que le identifique, dirigido a CARLOS LÓPEZ QUINTANILLA
CL. P
arellada, 8 E2 de Corbera de Llobregat, 08757-Barcelona.

También podrá oponerse a nuestros envíos de comunicaciones comerciales
(Art.21.2
de la LSSI) a través de la siguiente dirección de correo electrónico:
ad...@psig.es



El mar., 10 jul. 2018 a las 10:51, Carlos López PSIG ()
escribió:

> Hi developers,
> We are testing QGIS 3.2 and we see that the connection to Oracle is very
> slow and the connection did not end ...
> Is this a known error?
>
> if we use QGIS 2.18 the connection is good and fast.
> OS: Windows
>
> Best regards,
>
>
> * *
> *PSIG*
> Implementació, gestió i formació SIG
>
> *Carlos López Quintanilla*
>
> www.psig.es
> carlos.lo...@psig.es
> +34 699.680.261
>
> Nota legal: Este mensaje y cualquier archivo adjunto está destinado
> únicamente a la
> persona a quien se dirige y es confidencial. Si usted ha recibido este
> mensaje por
> error, por favor, comuníqueselo al remitente y bórrelo inmediatamente. La
> utilización ,
> revelación y/o reproducción del mensaje puede constituir un delito.
>
> Protección de Datos: Le informamos que sus datos de contacto electrónico
> se hallan
> incorporados a un fichero titularidad de CARLOS LÓPEZ QUINTANILLA, al
> objeto de
> envío de información, respuesta a consultas y contactos genéricos.
> Puede ejercer los derechos de acceso, rectificación, cancelación y
> oposición que
> establece la LOPD en cualquier momento, mediante escrito, acompañado de
> copia de
> documento oficial que le identifique, dirigido a CARLOS LÓPEZ QUINTANILLA
> CL. P
> arellada, 8 E2 de Corbera de Llobregat, 08757-Barcelona.
>
> También podrá oponerse a nuestros envíos de comunicaciones comerciales
> (Art.21.2
> de la LSSI) a través de la siguiente dirección de correo electrónico:
> ad...@psig.es
>
>
___
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

[QGIS-Developer] RES: Do we really need experimental and non-experimental plugins?

[Jorge Almerio]

Hi devs,

I agree with Andreas. I think we need experimental and non-experimental flags 
to plugins as it is.
And I think that we can NOT restrict the time to be experimental. Because it 
depends on the author available time to make his plugin stable. Restrict the 
experimental plugins would reduce the number of plugins been uploaded. To mark 
as experimental is important for the users and for the authors too, because one 
can help the other to fix bugs.

Jorge Almerio


-Mensagem original-
De: QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] Em nome de 
Andreas Neumann
Enviada em: segunda-feira, 27 de agosto de 2018 09:42
Para: qgis-developer@lists.osgeo.org
Assunto: Re: [QGIS-Developer] Do we really need experimental and 
non-experimental plugins?

Hi Borys,

Personally, I think there is a need for the differentiation of 
experimental or not experimental.

I'd like to keep it as it is.

Andreas


Am 27.08.2018 um 02:06 schrieb Nyall Dawson:
> On Mon, 27 Aug 2018 at 04:11, Borys Jurgiel  wrote:
>> Hi Lists,
>>
>> Before I make a QEP I'd like to know your general thoughts.
>>
>> After I removed the deprecated plugins filter from the Plugin manager (and
>> make them always visible) [1], Alex suggested doing the same with the
>> Experimental status.
> I'm -1 on this. Experimental plugins can be dangerous (some result in
> crashes, data corruption, etc), and shouldn't be shown by default.
>
>> However, I'm not sure if it makes much sense nowadays. Releasing 'stable' and
>> 'experimental' versions seems a bit overscaled to me. And there is a simpler
>> solution: If the recent version is buggy, users can just download the last
>> working one from the repo and install from zip.
> I think that's overestimating some of our user's abilities -- it would
> take a lot of knowledge that:
> 1. a plugin is at fault
> 2. they can overwrite a plugin manually with an earlier version
> and
> 3. they can download earlier versions of plugins.
>
> Then, they'd also need to know *which* older plugin version is "good"
> and should be downloaded.
>
>> The former case, when the
>> whole plugin is experimental, seems to be often misused: authors can use it 
>> to
>> hide some specialised of localised plugisn from majority of users. In fact
>> even I committed such clear misuse, marking the Plugin Reloader as
>> experimental just to not clutter the list for normal users... Another reason
>> could be a shyness. But again, we have the rating stars now and don't need to
>> rely on the author's shyness anymore.
>>
>> So... Do you see important reasons to keep this tag? Maybe we should
>> completely drop it? Or just remove the option to hide them from manager,
>> leaving the flask icon on the plugin details page?
> I think it should be kept. I know of one buggy plugin which recently
> got marked as experimental, and I'm *very* glad to see this particular
> plugin hidden from the majority of our users by default.
>
> Nyall
> ___
> 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

___
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

___
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

Re: [QGIS-Developer] Do we really need experimental and non-experimental plugins?

[Paolo Tormene]

Dear Borys,

for our plugin (the OpenQuake Integrated Risk Modelling Toolkit [1]) we
have been very happy to use the "experimental" flag so far, and we consider
it
a very useful feature.

For us, the ideal workflow would be to release a new
version of the plugin flagged as experimental, then let our scientific team
try
it extensively on real use-cases, and then mark it as stable. If I
understand
correctly, your proposal is to remove the possibility to mark an existing
experimental
version as stable, so we would have to release an identical version of the
plugin
without the "experimental" flag, as soon as we receive the approval from our
scientists.

>From a user perspective, we believe it is important that the user
can actually trust our plugin for "production" purposes, as long as the
plugin
is not flagged as "experimental". Users that are willing to try new
cutting-edge features at their own risk, can still enable experimental
plugins
and download the most recent version.

We also have another important point in favor of keeping two different
versions
of the plugin. Our tool has to interface itself with the OpenQuake Engine
[2],
that is a scientific engine that evolves very quickly. We currently keep the
most recent stable version of our plugin aligned with the latest official
release of the OpenQuake Engine, ensuring compatibility between the two
softwares. Between one official release and the next one, we release new
experimental versions of the plugin, ensuring compatibility with the nightly
builds of the OpenQuake Engine. Therefore, scientists that are interested in
using the most recent features offered by the two softwares can rely on the
nightly builds of the OpenQuake Engine and on the latest experimental
OpenQuake
Integrated Risk Modelling Toolkit.

For the above reasons, our answer to your question is yes, we do really need
this feature. And if you decide to drop it, we will have to significantly
redesign our release workflow.

Paolo Tormene, on behalf of the OpenQuake Team

[1] https://plugins.qgis.org/plugins/svir/
[2] https://github.com/gem/oq-engine/

On Sun, Aug 26, 2018 at 8:11 PM Borys Jurgiel  wrote:

> Hi Lists,
>
> Before I make a QEP I'd like to know your general thoughts.
>
> After I removed the deprecated plugins filter from the Plugin manager (and
> make them always visible) [1], Alex suggested doing the same with the
> Experimental status.
>
> Initially it was designed for two cases: to mark a whole plugin as
> experimental, and to just mark the recent version (so a kind of beta).
> Both
> cases seem to be popular among authors: at the moment we have 215 plugins
> for
> master, from which ~40 are experimental only and ~20 are in both versions.
>
> However, I'm not sure if it makes much sense nowadays. Releasing 'stable'
> and
> 'experimental' versions seems a bit overscaled to me. And there is a
> simpler
> solution: If the recent version is buggy, users can just download the last
> working one from the repo and install from zip. The former case, when the
> whole plugin is experimental, seems to be often misused: authors can use
> it to
> hide some specialised of localised plugisn from majority of users. In fact
> even I committed such clear misuse, marking the Plugin Reloader as
> experimental just to not clutter the list for normal users... Another
> reason
> could be a shyness. But again, we have the rating stars now and don't need
> to
> rely on the author's shyness anymore.
>
> So... Do you see important reasons to keep this tag? Maybe we should
> completely drop it? Or just remove the option to hide them from manager,
> leaving the flask icon on the plugin details page?
>
> Regards,
> Borys
>
> [1] https://github.com/qgis/QGIS/pull/7713
>
>
>
> ___
> 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



-- 

*PAOLO TORMENE* senior software developer +39 0382 5169882

*GLOBAL EARTHQUAKE MODEL * working together to assess risk

*GEM -* globalquakemodel.org  *T -*
@GEMwrld  *F -* GEMwrld

___
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

Re: [QGIS-Developer] Do we really need experimental and non-experimental plugins?

[Andreas Neumann]

Hi Borys,

Personally, I think there is a need for the differentiation of 
experimental or not experimental.


I'd like to keep it as it is.

Andreas


Am 27.08.2018 um 02:06 schrieb Nyall Dawson:

On Mon, 27 Aug 2018 at 04:11, Borys Jurgiel  wrote:

Hi Lists,

Before I make a QEP I'd like to know your general thoughts.

After I removed the deprecated plugins filter from the Plugin manager (and
make them always visible) [1], Alex suggested doing the same with the
Experimental status.

I'm -1 on this. Experimental plugins can be dangerous (some result in
crashes, data corruption, etc), and shouldn't be shown by default.


However, I'm not sure if it makes much sense nowadays. Releasing 'stable' and
'experimental' versions seems a bit overscaled to me. And there is a simpler
solution: If the recent version is buggy, users can just download the last
working one from the repo and install from zip.

I think that's overestimating some of our user's abilities -- it would
take a lot of knowledge that:
1. a plugin is at fault
2. they can overwrite a plugin manually with an earlier version
and
3. they can download earlier versions of plugins.

Then, they'd also need to know *which* older plugin version is "good"
and should be downloaded.


The former case, when the
whole plugin is experimental, seems to be often misused: authors can use it to
hide some specialised of localised plugisn from majority of users. In fact
even I committed such clear misuse, marking the Plugin Reloader as
experimental just to not clutter the list for normal users... Another reason
could be a shyness. But again, we have the rating stars now and don't need to
rely on the author's shyness anymore.

So... Do you see important reasons to keep this tag? Maybe we should
completely drop it? Or just remove the option to hide them from manager,
leaving the flask icon on the plugin details page?

I think it should be kept. I know of one buggy plugin which recently
got marked as experimental, and I'm *very* glad to see this particular
plugin hidden from the majority of our users by default.

Nyall
___
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


___
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