[Qgis-user] Public Repository for plugins...
Sampson, David
David.Sampson at NRCan-RNCan.gc.ca
Mon Jun 8 13:03:47 PDT 2009
Maybe those that are interested can have a little thread and come up
with a temp solutions while the ducks line up...
I would propose sourceforge as that is what I know and I already help
admin a project on sourceforge.
I would say if we can get three plugin groups working together that is a
good start.
Any takers?
Cheers
> -----Original Message-----
> From: qgis-user-bounces at lists.osgeo.org
> [mailto:qgis-user-bounces at lists.osgeo.org] On Behalf Of Alex Mandel
> Sent: Monday, June 08, 2009 15:41
> To: qgis-user at lists.osgeo.org
> Subject: Re: [Qgis-user] Public Repository for plugins...
>
> Sampson, David wrote:
> > Is there a co-ordinated effort o house multiple QGIS plugins in the
> > same place?
> >
> > I am thinking specifically of python plugins that deal with
> OGC type
> > services.
> >
> > Sourceforge is a classic option
> >
> > There is also http://code.google.com/opensource/
> >
> > I am thinking one central place for people that don't want the
> > overhead of housing their own code.
> >
> > The thought would be something like the following in the repo
> >
> > Repo ==>
> > Plugin I ==>
> > trunk
> > branches
> > tags
> > Plugin II ==>
> > trunk
> > branches
> > tags
> >
> >
> > Basicaly housing a bunch of plugins in one place in one repo and
> > different people are responsible for their different plugins and we
> > all follow the "proper" way to package and distribute to the python
> > plugin loader.
> >
> >
> > Thoughts?
> >
> >
> We've discussed it briefly previously and I believe Gary was
> looking into how to do this so it would be integrated with
> the distribution site http://pyqgis.org/
>
> Although that appears to be down at the moment, it's where
> the Official and Contributed Plugins are hosted from.
>
> As I pointed out in a previous thread on this the model you
> wrote is basically like trac-hacks.org, and feasible. There
> is some question as to whether we should go with a DVCS to
> allow for more flexibility in merging and trading pieces. It
> appears that some plugin devs prefer Git or Mercurial over
> svn for this stuff.
>
> Overall though I agree we need a central hub for plugin
> development to make it easier to manage the Official ones and
> allow champions to easily pickup where someone else left off.
>
> Alex
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>
More information about the Qgis-user
mailing list