<div dir="ltr"><div>Hi, <br></div><div>thanks for your inputs. My concern was that we are not resilient enough to detecting regressions or failures. I get your point of finding resources to create a dashboard, and responsibility dilution risks if we don't clarify who is responsible for what. <br></div><div><br></div><div>Let's stay as is concerning the QGIS server performance and OGC compliance suites. We'll forward tools failures only to Paul and me as a backup. <br></div><div><br></div><div>However there was another question about regressions detected concerning OGC compliancy. We are currently not able to wire those to Travis directly (that would be way tooo long), so how can we advertise for regressions to developpers? That is why I was asking to post on developper's list or another list. Unlike Plugin approval's messages, we expect a lot less messages. (something between 1 an 10 maybe?). <br></div><div><br></div><div>Best regards</div><div>Régis<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le dim. 19 mai 2019 à 11:10, Matthias Kuhn <<a href="mailto:matthias@opengis.ch">matthias@opengis.ch</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hi Régis,</p>
<p>I like the idea. It's an easy solution to have an archive of past
notifications and discussions on particular events.</p>
<p>The main risk is, that the "responsibilities" of different lists
is no longer clear and cross list threads are started. I don't
know what's best, but it could even be "read only", so that only
the check results are posted but any discussion shall be triggered
on other channels.</p>
<p>If someone is able to setup a dashboard with advanced
functionality, filtering etc. that would of course be even nicer,
but initial effort is higher and maintenance effort will be higher
too, so it's a question if someone is willing to take on that job.<br>
</p>
<p>Best regards</p>
<p>Matthias<br>
</p>
<p><br>
</p>
<div class="gmail-m_818919395318845532moz-cite-prefix">On 5/17/19 5:54 PM, Régis Haubourg
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi all, <br>
</div>
<div>A gentle relaunch here. Our infrastructure is already
monitored somewhere? <br>
</div>
<div>Or do we stick to having mail received by individual
maintainers? <br>
</div>
<div>Best regards</div>
<div>Régis<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le ven. 10 mai 2019 à 15:47,
Régis Haubourg <<a href="mailto:regis.haubourg@gmail.com" target="_blank">regis.haubourg@gmail.com</a>> a
écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hi all, <br>
</div>
<div>at Oslandia we are currently pushing the OGC compliance
test suite, the performance test suite and some demo
stuff QWC2 on qgis officiel servers. <br>
</div>
<div>We need to monitor those tools that produce daily
reports and send mails in case of failure of the tools<br>
</div>
<div><br>
</div>
<div>We don't want to flood the developper's mailing list
with such messages, so we are wondering what would be the
best place to send those notifications? <br>
</div>
<div><br>
</div>
<div>For the particular case of the OGC compliance test, we
also now have messages in case of regressions. Those
messages should are not wired with Travis PR workflow, so
we need to raise the information probably on the
developper mailing list. <br>
</div>
<div><br>
</div>
<div>Is there anything already set up somewhere we are not
aware of? <br>
</div>
<div><br>
</div>
<div>I think centralizing notification and having a
dashbooard to monitot the status of all the infrastructure
would be nice. <br>
</div>
<div><br>
</div>
<div>Thanks for your hints!</div>
<div><br>
</div>
<div>Best regards <br>
</div>
<div>Régis <br>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="gmail-m_818919395318845532mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_818919395318845532moz-quote-pre">_______________________________________________
QGIS-Developer mailing list
<a class="gmail-m_818919395318845532moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="gmail-m_818919395318845532moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="gmail-m_818919395318845532moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>