[Qgis-psc] Modifications and updates to plugins.qgis.org

[ElPaso]

Il 12/06/2015 13:48, Richard Duivenvoorde ha scritto:
> On 12-06-15 13:25, Anita Graser wrote:
>> ​Thanks!
>>
>> We were also discussing if it would be possible to enable a trusted user
>> group to edit the plugin descriptions displayed at the top of each
>> plugin pag
>> e, e.g. http://plugins.qgis.org/plugins/AccurAssess/ "Carry out the
>> accuracy assessment of a thematic categorical map taking into account
>> the sampling design.
>> ​" This would enable us to improve the plugin description without having
>> to ask each plugin author to update their description and upload a new
>> version of the plugin zip file.
> Not sure if that is an easy one Anita. As the descriptions normally
> comes from the metadata in the plugin zip.
> So a nice rewrite at the website would be overridden if the original
> author uploads a new version of the plugin (with the short version of
> the description...)
>
> One idea (Alessandro shoot me if it is a bad idea), is to have another
> 'field' for every plugin, which is part of the website, and not of the
> plugin... So the website should show an description item from the
> 'staff' and one from the author next to each other or so?? This
> 'description' maybe could also be used for this 'quality'-score we
> proposed to make the good plugins boil up?
>
> Regards,
>
> Richard
>

Preparing the bullets :)

They are probably two distinct things, the last one is about staff's 
picks, we have some mechanisms already in place for this purpose
* the 'popularity' is calculated with a simple algorithm, currently:
'popularity': 'plugins_plugin.downloads * (1 + 
(rating_score/(rating_votes+0.01)/3))'
* then we have 'average_vote' that is the average "stars".
* finally, there is a 'featured' flag that is supposed to highlight most 
important/valuable plugins.

I believe this is enough if the staff wants to highlight some plugins, 
maybe we can just change the default view to order by 'featured' instead 
of showing all plugins orderd by name as it is now.

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.

Adding another field (say 'staff_notes') is possible, but I suspect you 
might think it twice: it's another piece that needs somebody for editing 
and maintainance.

BTW I'm concerned about adding more stuff to this relatively small job, 
I estimated 4 hours but the update to django 1.8 is causing some 
troubles with third party apps we are using and I've already spent more 
hours than I expected.

I'd stick to the original plan and leave this for a future update.

-- 
Alessandro Pasotti
w3: www.itopen.it