Feature request #3138
Add plugin autopackaging script
Status: | Closed | ||
---|---|---|---|
Priority: | Low | ||
Assignee: | Borys Jurgiel | ||
Category: | Python plugins | ||
Pull Request or Patch supplied: | No | Resolution: | worksforme |
Easy fix?: | No | Copied to github as #: | 13198 |
Description
The current situation with plugins is rather confusing for the user: many repos, not all of them available all the time, often no easy way to understand ahow they work.
For developers the situation is also not optimal: it is difficult to notifiy bugs, easy to miss them, and difficult to fix problems in plugins other than its own.
I suggest to put all them on a trac (either a separate instance or a brach of the main QGIS trac).
A set of useful functions would then be:
For developers the situation is also not optimal: it is difficult to notifiy bugs, easy to miss them, and difficult to fix problems in plugins other than its own.
I suggest to put all them on a trac (either a separate instance or a brach of the main QGIS trac).
A set of useful functions would then be:
- a script for automatic packaging after any commit; this will solve the frequent problems with plugins with wrong XML data being asked to be upgraded any time, and make the dev life easier
- a rating system, so users can tell which ones to trust more
- download statistics, for the same purpose
- an info page, better if open to coments
History
#1 Updated by Andreas Neumann about 14 years ago
I will list here some of my expectations regarding the new centralized plugin repository - and related to it - some extensions on the Python plugin installer:
Central Repository
- Quality Assurance (poor plugins are bad for QGIS reputation)
- Status (experimental, production)
- trac-like option to report bugs and enhancement requests
- category
- documentation:
- where in the UI can the plugin be found (menu, toolbar, dialogue)
- initial check-in date, last updated date
- contact information - how to reach the plugin author (developer and organization/company)
- purpose of the plugin
- URL to further information/manual/howto
- support options (if any)
- what language is supported
- reveal metadata listed above
- way for users to comment, rate or report bugs (could also be provided by a separate web-based tool, but the plugin-installer should show a link to this other system)
- plugins could be grouped by category
- plugin installer could display external documentation webpage within a qtwebkit embedded in the installer
- plugin-installer could show screenshots of the plugin
#2 Updated by Paolo Cavallini about 14 years ago
I would add:
- we need cooperative platform to let one or more maintainer group plugins under a reasonable number of submenus: now it is very difficult to find a plugin when installed
#3 Updated by Borys Jurgiel almost 14 years ago
- Status changed from Open to In Progress
#4 Updated by Giovanni Manghi almost 13 years ago
- Target version changed from Version 1.7.0 to Version 1.7.4
#5 Updated by Giovanni Manghi over 12 years ago
- Target version changed from Version 1.7.4 to Version 2.0.0
#6 Updated by Pirmin Kalberer about 12 years ago
- Target version changed from Version 2.0.0 to Future Release - Nice to have
#7 Updated by Giovanni Manghi over 11 years ago
- Resolution set to fixed
- Pull Request or Patch supplied set to No
- Status changed from In Progress to Closed
it seems it was everything implemented, right?
#8 Updated by Paolo Cavallini over 11 years ago
- Status changed from Closed to In Progress
- Subject changed from Add plugin trac + svn to Add plugin autopackaging script
Most of the features have been implemented; the autopackaging script is still missing.
#9 Updated by Alexander Bruy over 8 years ago
- Resolution deleted (
fixed)
Do we really need autopackaging script for 3rd party plugins? What is the purpose of this script? For me it looks quite useless, I can not think of any reason why I may need to create plugin package on each commit to my GitHub or local repo.
BTW, Plugin Builder already generates makefile which allows create plugin package by running make.
#10 Updated by Giovanni Manghi over 7 years ago
- Easy fix? set to No
#11 Updated by Paolo Cavallini almost 7 years ago
- Status changed from In Progress to Closed
- Description updated (diff)
- Resolution set to worksforme
Plugin builder solves the issue IMHO