HI, Yes, I am trying to explore Dulwich now (which is a pure Python implementation of GIT). There is no need to add git dependency added to QGIS or that user needs to have git in their computer (if Dulwich works nicely).
And as Ale said, we would like to have 2 designs implemented here: - Repository handler. This should be independent to the protocol of the repository. In the case of filesystem, it would be just to copy the repository to the plugin working directory and extract the collections inside. I made handlers classes quite general and will be refactoring time to time if it's needed (now I am still working on git protocol though). - Resources handler. This part of the system should handle how the resources in the collection being imported into QGIS. The focus on this GSoC phase is to fetch and import the collections (not the sharing part). With this goal, it would be easier for users if we implement in a way that they don't need to make a list of the resources in the collections. That's why I am still looking for a solution other than listing all the resources and fetch them one by one using HTTP request to the git host. Cheers On Tue, Jun 28, 2016 at 11:09 AM, Alessandro Pasotti <[email protected]> wrote: > 2016-06-27 21:45 GMT+02:00 Régis Haubourg <[email protected]>: > >> 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 >> > > The designed architecture of the resource sharing system is protocol > independent: handlers for different repository protocols can be easily > added. > > The idea is to have at least: > - filesystem (symbol repository is on filesystem, for example a network > share), this is the simplest case: a copy command is all we need to fetch > resources and update them > - git > > So, git is just one of the possible handlers for remote repositories and > the idea is that the average user will never know that git is used under > the hood, it should be completely transparent. > > If the general design will be respected during the implementation, it will > be really easy to expand the system to handle different remotes and > different shared resources. > > The idea comes from the flexibility of python pip: it can fetch and > install resources (python packages in this case) from many different URIs, > git included. > > Cheers > > > > -- > Alessandro Pasotti > w3: www.itopen.it > > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > -- *-------------------* *Akbar Gumbira * *www.akbargumbira.com <http://www.akbargumbira.com>*
_______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
