[Qgis-developer] Report 5 - QGIS Symbology Sharing Tools

[Régis Haubourg]

Hi,
I tend to think that git / github workflow could be too high technician for
most users that have not developer's culture. This is how I see it for
processing script sharing today.. but processing is mostly concerning devs
when styling is a lot wider.
Why not combine both? Gist or equivalent for static files and git for the
main repo where or and collaborative work is required?
Cheers Regis

Le 27 juin 2016 21:20, "Richard Duivenvoorde" <rdmailings at duif.net> a
écrit :
>
> On 27-06-16 18:28, Vincent Picavet (ml) wrote:
> > On 27/06/2016 12:41, Matthias Kuhn wrote:
> >> > On 06/27/2016 11:32 AM, Akbar Gumbira wrote:
> >>> >> Thanks for the feedback. Unfortunately raw URL is only provided
for a
> >>> >> single file, not a directory.
> >> >
> >> > Couldn't all the files be downloaded individually?
> >> > This will result in a couple of additional requests, but I'm not sure
> >> > this is something to worry about.
> >> > The main question would then be, where the client could retrieve the
> >> > file list (paths relative). Generating this list could be part of the
> >> > upload script.
> > I may be late to the party, but I really do not get the point of using
> > git here for data retrieval.
> > And furthermore, I wouldn't want QGIS to have a hard dependency on git,
> > which is a developer tool users are not supposed to have installed by
> > default.
>
> Hi Vincent,
>
> There has been some (a lot of) discussion indeed already :-)
>
> But the main idea of using git was to have lively updated
> style/symbol/data repositories: by keeping users repo's as
> personal/named style repo's they would get credit for their work. They
> could 'just' do this by starting a repo on Github/Bitbucket/Gitlab. So
> somebody could clone a repo, add one individual icon to it, and maybe
> one updated style and do a pull request.
> Using git then we would have an 'easy' way to update the users local
> repo's with only those files that were updated.
> If I'm correct we would not need a git install, there is also a native
> python-git version which could be used as module.
>
> But thinking about this more, your options is also valid: another
> strategy would be split up the work in:
> -1- serving static files (with a version number in the metadata?) to
> serve out the stuff on a http server
> -2- have the files in git repo's for the administration of it: add stuff
> via pr's etc...
>
> Off course a lot of possible solutions are ok :-(
>
> Regards,
>
> Richard
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20160627/a5e03ddb/attachment.html>