<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Il 12/06/2015 15:53, Anita Graser ha
scritto:<br>
</div>
<blockquote
cite="mid:CAFFV8Fj0KiLV3jAZRZ41KOJOc0W9CVcipT2DZ+AmMkA_=Oxpvw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Jun 12, 2015 at 2:23 PM,
ElPaso <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:elpaso@itopen.it" target="_blank">elpaso@itopen.it</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="">
<div class="h5"><br>
</div>
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">The
second point is like you said: 'description' and 'about'
come from metadata.txt, they can be altered from the
website (for quick fixes and typos) but they are
overridden when the used uploads a new version. So, to
answer Anita, it is already possible for a staff member to
edit plugin's description and about but it will just last
until the next upload.<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>
<div class="gmail_default" style="font-size:small">Oh I
see! Have to check if I have the rights to alter
descriptions. Then it would be possible to extend some
and also issue pull requests with this new content in
the plugin repos so it's included the next time.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"
class="gmail_quote"><span
style="font-size:12.8000001907349px">I'd stick to the
original plan and leave this for a future update.</span></blockquote>
<div><br>
</div>
<div>
<div class="gmail_default"
style="font-size:small;display:inline">+1</div>
</div>
<div>
<div class="gmail_default"
style="font-size:small;display:inline"><br>
</div>
</div>
<div>
<div class="gmail_default" style="font-size:small">
Thanks and best wishes,</div>
<div class="gmail_default" style="font-size:small">Anita
</div>
<br>
</div>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Hello,<br>
<br>
task completed, this is what I've done:<br>
<br>
* updated to Django 1.8.2<br>
* updated and fixed all third party apps to Django 1.8 compatible
versions<br>
* made "about" "tracker" and "repository" mandatory<br>
* fixed user map<br>
* added bootstrap pagination (cosmetic change)<br>
* added a red asterisk for mandatory fields in plugin forms<br>
* added a new CSV export view for "bad" plugins (those with missing
"about" "tracker" or "repository"):
<a class="moz-txt-link-freetext" href="http://plugins.qgis.org/userexport/export_bad">http://plugins.qgis.org/userexport/export_bad</a>, the link is at the
top right in <a class="moz-txt-link-freetext" href="http://plugins.qgis.org/admin/auth/user/">http://plugins.qgis.org/admin/auth/user/</a> only available
to superadmins<br>
* deployed and tested<br>
<br>
For the techies (migration notes):<br>
* there are some new requirements in REQUIREMENTS.txt and most of
third party apps have been updated also<br>
* there are some new migrations in plugins app, old South migrations
are gone<br>
* there is a SQL migration since the Django core email field is now
max_length=254 instead of original 75: <br>
ALTER TABLE plugins_plugin ALTER email TYPE character varying(254);<br>
<br>
Have a nice weekend!<br>
<br>
-- <br>
Alessandro Pasotti
w3: <a class="moz-txt-link-abbreviated" href="http://www.itopen.it">www.itopen.it</a>
</body>
</html>