Re: [Qgis-developer] Re: Complicate the plugin situation
2012/1/20 Denis Rouzaud denis.rouz...@gmail.com: Hi Paolo, hi all Hi Denis, I'm the unlucky guy who spent a lot of time doing, undoing, redoing the new Plugins website. My frustration is at his top and I couldn't agree more with you, there are a couple of issues here: 1 - specifications on py plugins are changing very often and there is not a clear unique authoritative source of specifications for plugins, or peharps I just couldn't find it 2 - there is no agreement on important topics, the main was if plugins without a tracker and a public code repository and a public homepage can be accepted on plugins.qgis.org 3 - there is not a single place for documentation 4 - I cannot do everything by myself, I'a a python-Django coder and I try to keep updated the specifications for the application I write, I I'm not going to do any CSS/styling work and I will not take care of updating the CMS pages or other end-user documentatio, somebody else has to do that 5 - the plugins website has nothing to do with Redmine instance running on hub.qgis.org and there is no bridge between the two (except for authentication) 6 - there is not an approval workflow for plugins: I'm not going to approve any plugin anymore, somebody else must do that IMHO the main source of confusion comes from the lack of agreement on the following topics * all plugins *must* have a public issue (bug) tracker on hub.qgis.org * all plugins *must* have a SNV/GIT core repository on hub.qgis.org * all plugins *must* have a public homepage after endless emails we agreed on * all plugins should have a public issue tracker * all plugins should should a SNV/GIT core repository * all plugins should have a public homepage this means that if the author doesn't supply those informations a warning (not an error!) is issued by the plugins app. Only staff members and authors see the warnings. The warning says: Some important informations are missing from the plugin metadata (homepage, tracker or repository). Please consider creating a project on hub.qgis.org and filling the missing metadata. this is a suggestion, not an order, if the red color of the text disturbs you, we can easily change, also, if you have some proposals on a better message, please let us know. As I wrote recently, I'm strongly against forcing authors to create projects on Redmine, I myself will not do it for my plugins, suggesting authors to do so, it's a good compromise: the idea is if you (author) dont' know where to host your code or your tracker, hub is here to help you. If hub doesn't work as expected (and I'm pretty sure it doesn't), please add a comment to one of the tickets already opened about the same sub-project issue. The source of specifications for the plugins application which I maintain is here: https://github.com/qgis/qgis-django/blob/master/qgis-app/plugins/docs/introduction.rst Also, at this time, metadata.txt is not (yet) mandatory your plugin will be accepted even if there is only __init__.py -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
On Fri, Jan 20, 2012 at 09:40:26AM +0100, Alessandro Pasotti wrote: after endless emails we agreed on * all plugins should have a public issue tracker * all plugins should should a SNV/GIT core repository * all plugins should have a public homepage FWIW: I'll stack my agreement over that :) The source of specifications for the plugins application which I maintain is here: https://github.com/qgis/qgis-django/blob/master/qgis-app/plugins/docs/introduction.rst Very useful! Permision rules 3 and 4 seem identical to me, are them ? Also, at this time, metadata.txt is not (yet) mandatory your plugin will be accepted even if there is only __init__.py Is a warning and red-widget also shown for this case ? Keep up the good work ! --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
after endless emails we agreed on * all plugins should have a public issue tracker * all plugins should should a SNV/GIT core repository * all plugins should have a public homepage this means that if the author doesn't supply those informations a warning (not an error!) is issued by the plugins app. Only staff members and authors see the warnings. The warning says: Some important informations are missing from the plugin metadata (homepage, tracker or repository). Please consider creating a project on hub.qgis.org and filling the missing metadata. this is a suggestion, not an order, if the red color of the text disturbs you, we can easily change, also, if you have some proposals on a better message, please let us know. Hi Ale I like very much the approach of the plugin Django application, so I really hope that the QGIS developers community will stick with it. A very nice add-on you could easily implement isre a comment system, by using the django-threadedcomments. I also recommend you to give a look to the OpenComparison project [1], the platform on which the DjangoPackages portal [2] (and other ones) is based: there are very good ideas all around there, specially the integration with the APIs provided by PyPI, Github, BitBucket, Launchpad, and SourceForge ;) Thanks again for your excellent work! P [1] http://opencomparison.readthedocs.org/en/latest/index.html [2] http://djangopackages.com/ -- Paolo Corti Geospatial software developer web: http://www.paolocorti.net twitter: @capooti skype: capooti ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
2012/1/20 Paolo Corti pco...@gmail.com: after endless emails we agreed on * all plugins should have a public issue tracker * all plugins should should a SNV/GIT core repository * all plugins should have a public homepage [...] Hi Ale I like very much the approach of the plugin Django application, so I really hope that the QGIS developers community will stick with it. A very nice add-on you could easily implement isre a comment system, by using the django-threadedcomments. I also recommend you to give a look to the OpenComparison project [1], the platform on which the DjangoPackages portal [2] (and other ones) is based: there are very good ideas all around there, specially the integration with the APIs provided by PyPI, Github, BitBucket, Launchpad, and SourceForge ;) Thanks again for your excellent work! P [1] http://opencomparison.readthedocs.org/en/latest/index.html [2] http://djangopackages.com/ -- Paolo Corti Geospatial software developer web: http://www.paolocorti.net twitter: @capooti skype: capooti Thanks Paolo, there are already many new proposed features! Comments is certainly one of those. Plugin rating was also proposed and plugins app i18n support is also very important. rpc4django is already in place and a tighter integration between QGIS client GUI and the web application would allow the user to rate a plugin directly from QGIS interface. Good to know that there are github apis available, but the official choice is Redmine here... anyway I will give a closer look to that. -- Alessandro Pasotti w3: www.itopen.it ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
Hi all, On Fri, Jan 20, 2012 at 9:40 AM, Alessandro Pasotti apaso...@gmail.com wrote: 2 - there is no agreement on important topics, the main was if plugins without a tracker and a public code repository and a public homepage can be accepted on plugins.qgis.org IMHO they must have both a tracker and a repository, instead a public homepage I think shouldn't be mandatory. 3 - there is not a single place for documentation The main documentation source for creating/uploading a python plugins is the pyQGis cookbook, of course it has to be updated but remember that the new plugin repo is available since few months only. 5 - the plugins website has nothing to do with Redmine instance running on hub.qgis.org and there is no bridge between the two (except for authentication) sites doesn't need a really strong integration IMHO, but of course some kind of joining points between the two would make life easier to plugin authors. 6 - there is not an approval workflow for plugins: I'm not going to approve any plugin anymore, somebody else must do that In this moment the new repo is available only from QGis master, and also the plugins site is under testing. If there isn't a workflow then it's time to define it. * all plugins should have a public issue tracker * all plugins should should a SNV/GIT core repository IMOH all plugins *must* have a public tracker and repository. * all plugins should have a public homepage Instead a public page should be strongly recommended. Some important informations are missing from the plugin metadata (homepage, tracker or repository). Please consider creating a project on hub.qgis.org and filling the missing metadata. I've seen that warning, but the link should point to a new project creation (not the hub homepage) and the form should be populated yet (name, description, set as subproject of User plugins) Regards. -- Giuseppe Sucameli ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
Hi all, I also tried to upload my simple plugin to the new plugin repository using only available information. Here is my experience. Plugin code hosted at GitHub, I decide to use bugtracker at hub.qgis.org. I have no problems with creating subproject under User plugins project, only little puzzled with Identifier field. Then I create package with my plugin and tried to upload it on plugins.qgis.org and here I have one issue. My plugin have both files __init__.py and metadata.txt. Metadata.txt file has all required fields including links to source code repository and bugtracker. But when I try to upload plugin I get message There were errors reading plugin package (please check also your plugin's metadata). qgisMinimumVersion is set to less than 1.8 (1.0.0) and there were errors reading metadata from the __init__.py file. This can lead to errors in versions of QGIS less than 1.8, please either set the qgisMinimumVersion to 1.8 or specify the metadata also in the __init__.py file. Reported error was: Cannot find metadata qgisMinimumVersion in metadata source (__init__.py). Please bear in mind that the current implementation of the __init__.py validator is based on regular expressions, check that your metadata functions directly return metadata values as strings. This is confusing for me, because my __init__.py contains def qgisMinimumVersion(): return 1.0.0 and metadata.txt contains under general section qgisMinimumVersion = 1.0.0 And I was able to upload plugin only when change qgisMinimumVersion in both files to 1.8.0. That's all. A little waiting and plugin approved and available for download. 2012/1/20 Giuseppe Sucameli brush.ty...@gmail.com: 1.a. In section How to add your plugin to this repository I can see: - register your plugin at http://hub.qgis.org/projects/qgis-user-plugins, to show plugin info, add issues/tickets and to have just ONE repository for all qgis plugins. Shouldn't it be this optional as the user can choose any tracker? I agreed with Giuseppe. As I remember in previous discussions we decide that plugin author can use not only hub.qgis.org but any other bugtracker and code repository. I under stand that using hub.qgis.org as bugtracker has some advantages (single login and single place for all QGIS releated bugs), but someone may don't like redmine. I think we should create some policy regarding bugtracker and source code repository. At least bugtracker and code repo URL should be mandatory. 2. About the PyQGIS cookbook: 2.a. The section Release a plugin into the cookbook needs to be update with the new procedure, It also contains a link to the old plugins repo site. 2.b. There isn't a section about metadata.txt, what information it contains, where put the file, ... Already fixed. But because auto updates for CookBook at qgis.org was broken for a while we have outdated version on site. As I say this already fixed, thanks to Otto and Werner. -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
Just playing around plugin web-app and have some additional questions. 1. What message This plugin has no public version yet. means and how I can made plugin public? 2. When after approving plugin I want to update already uploaded archieve I again see unchecked checkbox Approved that I can't change. Maybe it is better to hide it from regular developers? Thanks -- Alexander Bruy ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
Il 19/01/2012 17:07, 3nids ha scritto: I have to say it is not a trivial task and might discourage people as it is right now. Agreed. There are inconsistencies in the page http://plugins.qgis.org : - the linked wiki http://hub.qgis.org/wiki/quantum-gis/Writing_Python_Plugins has moved removed. - As already stated, it tells you to register your plugin at http://hub.qgis.org/projects/qgis-user-plugins where you cannot create a project Can someone fix this please? Also, when submitting the plugin, I needed to give a metadata file, which I did not heard about. When I looked in PyQGIS cook book at writting plugins ( http://www.qgis.org/pyqgis-cookbook/plugins.html#writing-a-plugin ), the info about metada is unclear and tells you to register the plugin at another repo http://pyqgis.org/ So the cookbook has to be fixed. The warnings when you upload the plugin are somehow discouraging also Can you please fill appropriate tickets suggesting better messages etc? Thanks a lot for the effort. With your help, the process can be streamlined. All the best. -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
Il 19/01/2012 17:24, Paolo Cavallini ha scritto: So the cookbook has to be fixed. Also fixed - Thanks Alex Bruy! -- Paolo Cavallini - Faunalia www.faunalia.eu Full contact details at www.faunalia.eu/pc ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Re: Complicate the plugin situation
Hi Paolo, hi all I am not understanding what you mean by fiiling appropriate tickets. My point with these messages was: I did what I read I should do, and when I uploaded my plugin, I got error/warning messages... These are too big and flashy regarding to their importance (homepage, tracker, repo, etc.) Also having to set sub-project and plugins is weird, as you have to fill the info twice. I tried to look for the page where you set tracker, repo etc. and cannot find it anymore. It's not clear if it's possible or not to give the repo and that it is automatically included in the hub/projects. Why not having only one of the two for the plugins? I also think that having developers to validate plugins is a useless job. Because having number of downloads and users rating (via QGIS?) and comments is imho far the best way of evaluating a plugin. Second, I don't like very much the delay for the plugin to be available (although I am known to be very impatient ;) Well, to finish I'll say I am a little sad regarding to the amount of work that has been done on these website for the plugins. All these stuff seems great on its own. But it does look like there used to be a lack of aggreement / concertation. (I noticed the discussion on the wiki). I would suggest to have a single page for howto publish a plugin (1) and a single gateway to browse plugins, instead of many (2) and without any link from qgis home page (!!!) I see that the discussion in the wiki http://hub.qgis.org/projects/quantum-gis/wiki/Python_Plugin_Repositories is going in that way and it's great. I know that this king of work is not very sexy for developers, but the gain for users and user-developers is huge! (1) now: http://plugins.qgis.org/ http://www.qgis.org/pyqgis-cookbook/plugins.html#releasing-the-plugin (2) I could find these on the website: http://hub.qgis.org/projects /sub-sprojects http://plugins.qgis.org/plugins/ http://pyqgis.org/ http://pyqgis.org/repo/official http://pyqgis.org/repo/contributed http://hub.qgis.org/projects/quantum-gis/wiki/Python_Plugin_Repositories (all the external) On 01/19/2012 05:24 PM, Paolo Cavallini wrote: Il 19/01/2012 17:07, 3nids ha scritto: I have to say it is not a trivial task and might discourage people as it is right now. Agreed. There are inconsistencies in the page http://plugins.qgis.org : - the linked wiki http://hub.qgis.org/wiki/quantum-gis/Writing_Python_Plugins has moved removed. - As already stated, it tells you to register your plugin at http://hub.qgis.org/projects/qgis-user-plugins where you cannot create a project Can someone fix this please? Also, when submitting the plugin, I needed to give a metadata file, which I did not heard about. When I looked in PyQGIS cook book at writting plugins ( http://www.qgis.org/pyqgis-cookbook/plugins.html#writing-a-plugin ), the info about metada is unclear and tells you to register the plugin at another repo http://pyqgis.org/ So the cookbook has to be fixed. The warnings when you upload the plugin are somehow discouraging also Can you please fill appropriate tickets suggesting better messages etc? Thanks a lot for the effort. With your help, the process can be streamlined. All the best. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
