[Qgis-developer] Where to release a plugin
tech_dev at wildintellect.com
Thu Apr 2 16:02:12 EDT 2009
I've only heard mumbles on the side, so I'll try to explain where I'm
going with this. I think it would be good for fostering plugin
development if we had a more collective place where new developers could
put together their stuff.
I'm particularly looking at examples like http://trac-hacks.org/ where
plugin developers all share a code repo and have their own page/folder
for development. All the other developers could technically help on any
plugin hosted there, and releases can be hosted from one unofficial
Right now, I've got a plugin I want to release but it was a team effort
and will continue to be. We used sourceforge to collaborate but it's not
a good platform for a qgis repo to be hosted. In fact I can't figure out
how to do it without violating sourceforge rules.
Moving the release to another server at my lab or the qgis contributed
or official will work short term, but it would rely on me to be the
person who always packages a new version for release. I worry that's not
robust enough of solution.
Any ideas, thanks,
Alex Mandel wrote:
> So while not done, I'd like to start getting more people involved with
> the Metadata editor plugin my colleagues and I started. We have a
> sourceforge trac/svn instance and mailing for managing additional
> contributors which we now openly welcome.
> The question in this email though is where is the best place to put the
> plugin so it can be installed via the python plugin manager. Sourceforge
> isn't conducive to setting up a qgis style plugin repo, unless someone
> can show me how to do this in trac and since it's a community project I
> don't really want to stick it on my personal server.
> Is this an appropriate thing to add to the Contributed plugins?
> And yes it's only Alpha at this point, it's a metadata reader but it's a
> good start.
More information about the Qgis-developer