Re: [Qgis-developer] github vs hub.qgis.org/projects/.../repository
Il 19/12/2011 10:02, Alessandro Pasotti ha scritto: > I would suggest that you complete/integrate/update the (static) pages > on the new plugin site Yes, please, let's consolidate the info, now a bit difficult to find, especially for newcomers. Thanks. -- 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] github vs hub.qgis.org/projects/.../repository
2011/12/19 Richard Duivenvoorde : > On 2011-12-16 09:48, Richard Duivenvoorde wrote: >> doing some plugins, and working both with plugins from >> hub.qgis.org/projects/.../repository (my own) and plugins living at >> github (wktplugin from Allesandro), it appears to me that github seems >> to work more transparant for me... > > ok, clear. > > So my conclusion for a 'how to publish my plugin'-guideline: > > 1) share your plugin at Qgis plugin repo > http://plugins.qgis.org/plugins/ > > 2) 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. > > 3) depending on your plugin/ideas/capabilities, either > -A- put ALL code in the zip uploaded to Qgis plugin repo > or > -B- put code in git repo at hub > or/and > -C- put code in github (because it just has more features at this moment) > > > - I will update the 'Writing_Python_Plugins' [0] with this. > - Maybe also move the code snippets from that page to the plugins > snippets pages [1] and point to there. > - Also link to Tim's pydev debugging blog [2] in the wiki. > - 'Deprecate' the 'Python_Plugin_Repositories' page [3] > - make note of new metadata format... Allesandro you showed me some page > once...? Yes, this one: https://github.com/qgis/qgis-django/blob/master/qgis-app/plugins/docs/introduction.rst I would suggest that you complete/integrate/update the (static) pages on the new plugin site (you now have staff account at http://plugins.qgis.org/admin/ ) with instructions for plugin users and plugin authors. Once there is a page with instructions about metadata, I could change messages when user uploads a plugin pointing to metadata instructions. Metadata example: https://github.com/qgis/qgis-django/blob/master/qgis-app/plugins/tests/HelloWorld/1.3-full-md-no-init/HelloWorld/metadata.txt There is still one point missing: the new "category" metadata. I'm wating for a final decision about this new metadata and then it can be added to the new repo. -- 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] github vs hub.qgis.org/projects/.../repository
On 2011-12-16 09:48, Richard Duivenvoorde wrote: > doing some plugins, and working both with plugins from > hub.qgis.org/projects/.../repository (my own) and plugins living at > github (wktplugin from Allesandro), it appears to me that github seems > to work more transparant for me... ok, clear. So my conclusion for a 'how to publish my plugin'-guideline: 1) share your plugin at Qgis plugin repo http://plugins.qgis.org/plugins/ 2) 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. 3) depending on your plugin/ideas/capabilities, either -A- put ALL code in the zip uploaded to Qgis plugin repo or -B- put code in git repo at hub or/and -C- put code in github (because it just has more features at this moment) - I will update the 'Writing_Python_Plugins' [0] with this. - Maybe also move the code snippets from that page to the plugins snippets pages [1] and point to there. - Also link to Tim's pydev debugging blog [2] in the wiki. - 'Deprecate' the 'Python_Plugin_Repositories' page [3] - make note of new metadata format... Allesandro you showed me some page once...? Ok? Richard [0] http://hub.qgis.org/wiki/quantum-gis/Writing_Python_Plugins [1] http://plugins.qgis.org/snippets/ [2] http://linfiniti.com/2011/12/remote-debugging-qgis-python-plugins-with-pydev/ [3] http://hub.qgis.org/wiki/quantum-gis/Python_Plugin_Repositories ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] github vs hub.qgis.org/projects/.../repository
Il 17/12/2011 10:02, Alessandro Pasotti ha scritto: > Moreover I don't think we should force plugin users to use a > particular SCM o tracker system. Not *forcing*: easing it up. For most devs, having it for free is a bonus, not an obligation IMHO. 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] github vs hub.qgis.org/projects/.../repository
2011/12/17 Paolo Cavallini : > Il 16/12/2011 20:18, Alex Mandel ha scritto: > >> Hopefully as we start to integrate the plugins site with hub the feature >> set will prove useful when communicating not only with other developers >> but users, especially power users. To me it's the users and power users >> that benefit the most from us hosting our own infrastructure and trying >> to make it more user friendly than github which is clearly only for >> coders in the know. > > Right. I think we should make life easier for new plugin devs, so that they > could > publish the plugin, the source code, and the bugtracker with the minimum > effort > possible. Not all of them know about git, and even redmine can be a bit scary > for > many. I also had several private enquiries about that, of people puzzled > about what > to do to publish their plugin. > All the best. Publishing the plugin on the new repo it is now very easy, and with the new XML-RPC interface [1] it could be even done from QGIS client itself with a suitable plugin (see code example [2]) or from the command line. The plugins source code it's inside the package itself, this implies that the code is always available in any case, even when a code repository does not exists. Of course having a full SCM system (git, svn bzr, place your favourite here) it's advisable for most plugins (perhaps it's not very useful for the simpler 10-lines plugins) but IMHO should not be mandatory, the plugin app now issue some warnings when a tracker and SCM are not available and suggest to create one on hub.qgis.org. Moreover I don't think we should force plugin users to use a particular SCM o tracker system. For the simpler plugins that lack a tracker I would suggest to add a [Send email to developer] button in the plugin web app, kind of poor man's bug tracking system: better than nothing. An RPC method for this could also be added, and integrated in QGIS client. [1] http://plugins.qgis.org/plugins/RPC2/ [2] https://github.com/qgis/qgis-django/blob/master/qgis-app/plugins/utils/plugin_upload.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] github vs hub.qgis.org/projects/.../repository
Il 16/12/2011 20:18, Alex Mandel ha scritto: > Hopefully as we start to integrate the plugins site with hub the feature > set will prove useful when communicating not only with other developers > but users, especially power users. To me it's the users and power users > that benefit the most from us hosting our own infrastructure and trying > to make it more user friendly than github which is clearly only for > coders in the know. Right. I think we should make life easier for new plugin devs, so that they could publish the plugin, the source code, and the bugtracker with the minimum effort possible. Not all of them know about git, and even redmine can be a bit scary for many. I also had several private enquiries about that, of people puzzled about what to do to publish their plugin. 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] github vs hub.qgis.org/projects/.../repository
github has quotas, and lacks a good way to group plugins by independent authors including their wikis and tickets. We also can't guarantee their polcies so hub is a backup to ensure our codebase, wiki and tickets. As others have pointed out there's no reason to not sync your code to both. I just like the idea of hub holding collectively all the bugs for all plugins and the main applications in one place with an osgeo login that enables anyone in the community to file bugs against any part. In some ways we were trying to discourage the trend that everyone had their own plugin server (the goal of the plugin site), the source code was not clearly available (other than releases) and no one knew where to file bugs. Hopefully as we start to integrate the plugins site with hub the feature set will prove useful when communicating not only with other developers but users, especially power users. To me it's the users and power users that benefit the most from us hosting our own infrastructure and trying to make it more user friendly than github which is clearly only for coders in the know. Thanks, Alex On 12/16/2011 02:58 AM, Pirmin Kalberer wrote: > Hi Richard, > > There was never an in-depth discussion about the role of hub.qgis.org vs > github.com. > Since I was involved in the setup of both platforms, here my personal view: > > We want to have direct links between tickets and changesets for QGIS. > Therefore we need the git repository viewer on hub.qgis.org. But for me, > gitosis on hub.qgis.org is only a backup solution to keep a certain > independency from github.com. Due to the nature of a distributed VCS, the > risk > of this dependency is low and we won't be able to compete with github.com in > terms of features. So I suggest people to publish their (plugin) code on > github. And If they don't want that, they have the possibility to use the > OSGEO hosted git repo on hub.qgis.org (with less functionality). > > Regards > Pirmin > > > Am Freitag, 16. Dezember 2011, um 09.48:17 schrieb Richard Duivenvoorde: >> Hi Devs, >> >> doing some plugins, and working both with plugins from >> hub.qgis.org/projects/.../repository (my own) and plugins living at >> github (wktplugin from Allesandro), it appears to me that github seems >> to work more transparant for me... >> >> Eg at github after a couple of days you could see that people forked >> Allesandro's plugin and you could even see what they were doing with it >> (by going to the forkers github repo). I could even contact those people >> to ask to do a pull request etc etc. >> >> I think, this cannot be done at our own hub.qgis.org-repo? >> Or am I missing something in this? >> >> I think it is really helpfull to see what other people are adding/doing >> with a plugin. And it hopefully also minimizes the private >> branching/forking of plugins. >> >> I read something about the old jquery plugins site, which broke down, >> and now there is a message at >> http://blog.jquery.com/2011/12/08/what-is-happening-to-the-jquery-plugins-s >> ite/ that says: "we’ve started converting our plans into action, building >> out an infrastructure that’s backed by GitHub". >> >> Isn't that an ideal situation for QGIS plugin future to? >> >> I am NOT wanting to throw away the infrastructure we have now! It's just >> that I like the jquery plugin idea... >> >> Regards, >> >> Richard Duivenvoorde >> >> ps as a temporary solution I think to fork (is forking actually adding a >> new remote?) my repo's to github too... >> >> ps2 (sorry for too much words on the list from my side I will go in >> stealth mode now) >> ___ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer > > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] github vs hub.qgis.org/projects/.../repository
On Fri, Dec 16, 2011 at 09:48:17AM +0100, Richard Duivenvoorde wrote: > I think it is really helpfull to see what other people are adding/doing > with a plugin. And it hopefully also minimizes the private > branching/forking of plugins. I think it is helpful to see what others are doing when they tell you what they are doing is ready for you. Or it'd be just noise. > ps as a temporary solution I think to fork (is forking actually adding a > new remote?) my repo's to github too... Forking is branching. Remotes are just a way to publish your branches in a place where others can look at, so they can do: $ git log richard/hisThing..HEAD $ git log tim/master..HEAD $ git log jef/topo..HEAD and see what's being done by whom. (syntax is likely wrong, but you get the idea) --strk; ,--o-. | __/ |Thank you for PostGIS-2.0 Topology ! | / 2.0 |http://www.pledgebank.com/postgistopology `-o--' ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] github vs hub.qgis.org/projects/.../repository
Hi Richard, There was never an in-depth discussion about the role of hub.qgis.org vs github.com. Since I was involved in the setup of both platforms, here my personal view: We want to have direct links between tickets and changesets for QGIS. Therefore we need the git repository viewer on hub.qgis.org. But for me, gitosis on hub.qgis.org is only a backup solution to keep a certain independency from github.com. Due to the nature of a distributed VCS, the risk of this dependency is low and we won't be able to compete with github.com in terms of features. So I suggest people to publish their (plugin) code on github. And If they don't want that, they have the possibility to use the OSGEO hosted git repo on hub.qgis.org (with less functionality). Regards Pirmin Am Freitag, 16. Dezember 2011, um 09.48:17 schrieb Richard Duivenvoorde: > Hi Devs, > > doing some plugins, and working both with plugins from > hub.qgis.org/projects/.../repository (my own) and plugins living at > github (wktplugin from Allesandro), it appears to me that github seems > to work more transparant for me... > > Eg at github after a couple of days you could see that people forked > Allesandro's plugin and you could even see what they were doing with it > (by going to the forkers github repo). I could even contact those people > to ask to do a pull request etc etc. > > I think, this cannot be done at our own hub.qgis.org-repo? > Or am I missing something in this? > > I think it is really helpfull to see what other people are adding/doing > with a plugin. And it hopefully also minimizes the private > branching/forking of plugins. > > I read something about the old jquery plugins site, which broke down, > and now there is a message at > http://blog.jquery.com/2011/12/08/what-is-happening-to-the-jquery-plugins-s > ite/ that says: "we’ve started converting our plans into action, building > out an infrastructure that’s backed by GitHub". > > Isn't that an ideal situation for QGIS plugin future to? > > I am NOT wanting to throw away the infrastructure we have now! It's just > that I like the jquery plugin idea... > > Regards, > > Richard Duivenvoorde > > ps as a temporary solution I think to fork (is forking actually adding a > new remote?) my repo's to github too... > > ps2 (sorry for too much words on the list from my side I will go in > stealth mode now) > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Pirmin Kalberer Sourcepole - Linux & Open Source Solutions http://www.sourcepole.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
