[postgis-devel] is PostGIS ready for git ?

Paragon Corporation lr at pcorp.us
Tue Oct 13 22:30:44 PDT 2015


 

> What about PostgreSQLs git repositories? They don't have "a special place" for extensions?

They have their own which is not github and they have a mirror on github.

http://git.postgresql.org/gitweb/

 

but really it's no better than relying on OSGeo infrastructure and worse cause they still have no issue tracker.  They are still fighting over what to pick.

I think their concerns are closer to strk's.

 

 

> My question is if there is no good alternatives to GitHub when it comes to git (like not propriety host)?

 

Like Paul said there is an inertial benefit of being on github.  In fact as the forces go more and more proprietary companies are giving back by offering special options for open source projects.

Should we look a gift horse in the mouth. Yes, but that does not mean we should refuse it. Many proprietary companies are thankful and just want to say thank you in a meaningful way so why not let them.

http://www.appveyor.com/pricing has free offering for os projects.  I presume that is what Paul meant by taking the medicine without the teaspoon of sugar.

 

The problem with relying on OSGeo infrastructure too much is that we have unpaid volunteers.  And trust me maintaining bots and all that stuff is a big burnout job. Maintenance is way more work than cost of servers.

It's a big janitor job really and for projects you aren't intimately involved with it's well 

pretty thankless with no upside reward.

 

All you get are thankless people whining about this and that and how it doesn't quite work the way they want. I feel like volunteer time could be better spent.  But really that's a discussion for higher up.

Rather than asking for things we should insure our hard-working people get paid or are better rewarded before we start demanding things.

 

>/Nicklas

2015-10-13 skrev Sandro Santilli :

On Tue, Oct 13, 2015 at 04:19:42AM -0700, Paul Ramsey wrote:
>
>> If we’re going to spend the time processing trac entries to match git,
>> why not spend the time migrating them to github and be done w/ it?
>
>That'd mean also asking all PostGIS contributors to get an account on
>a priorietary platform, rather than using the "OSGeo" account to
>partecipate in the development of a full free software gis stack.
>
>Sure it's tempting to just move to a system that, today, works faster
>and is better maintained than the OSGeo infrastructure, but I'd still
>prefer to stick with the official source being on OSGeo.
>
>We're looking at various options to make it even unnecessary to
>process trac entries to match git (by keeping multiple repositories).
>
>--strk;
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20151014/c981c0a1/attachment.html>


More information about the postgis-devel mailing list