[Board] Travis-CI & OSGeo

Mon Apr 23 07:50:31 PDT 2018

My issue is not that Even shouldn't be given the freedom to manage his project the way he wants.  Of course he should.

The point is that 

1)      He is limited because he is under the OSGEO Project infrastructure on Github.  If he were on his own project space, like PostGIS or QGIS (or Geos used to be), he wouldn't be limited by the 5 worker limit. I fail to see what benefit this Org is doing us when several of aour key projects aren't even on it (e.g. QGIS, GRASS, PostGIS) and even if they are what is the point, people should be lured to the osgeo website, not github.

2)      $5000 or more a year I fair is eventually what you'd need to pay as more projects get added to the GitHub Org

this https://github.com/OSGeo/  the pricier it gets and plus you need to be committed to offer this every year.

-- this extracted from Even's note for those who are not aware

a.  number of 5 concurrent jobs per organization 

b.  I contacted Travis-CI support and they gave me a quote to increase the number of concurrent 

c.  jobs :

d.  10 concurrent jobs: $1925/year

e.  15 concurrent jobs: $3850/year

f.  20 concurrent jobs: $5775/year

g.  (taking into account a 30% discount for non-profit organizations).

3)      I think with $5000, that's almost the size of the osgeo budget for hardware.  I think of all the good we could do with $5000/yr and something that could help all projects not just things hosted on GitHub.

Like building up our own CI infrastructure that would test more than just Ubuntu.

And what about AppVeryor.  How much are you going to have to pay for that?  Is it under the same core limitations or will you have to shell out an additional $5000/yr for that?

So my main concern is that this takes away money from other worthy causes and can be easily ameliorated by projects not falling under the Github OSGeo org, and the github/OsGeo org just listing projects and related repos.

Might I reiterate I find it self-defeating that we have a GitHub Org and projects like QGIS, GRASS, or PostGIS aren't even represented on it.  The list looks cluttered hard to follow and would be better served with a plain old list.

Thanks,

Regina

From: Board [mailto:board-bounces at lists.osgeo.org] On Behalf Of Tim Sutton
Sent: Monday, April 23, 2018 10:27 AM
To: Jeffrey Johnson <ortelius at gmail.com>
Cc: osgeo-board List <board at lists.osgeo.org>; Sandro Santilli <strk at kbt.io>
Subject: Re: [Board] Travis-CI & OSGeo

Hi

On 23 Apr 2018, at 16:14, Jeffrey Johnson <ortelius at gmail.com <mailto:ortelius at gmail.com> > wrote:

How bout we just use what the folks writing the code want to use
rather than being so militant about things?

+1…as project leader for GDAL, Even should be given the freedom to manage his project infrastructure in a way that is comfortable for him….I think it is an overreach to require him to retool his entire workflow.

Regards

Tim

On Mon, Apr 23, 2018 at 7:13 AM, María Arias de Reyna <delawen at gmail.com <mailto:delawen at gmail.com> > wrote:

On Mon, Apr 23, 2018 at 11:01 AM, Sandro Santilli <strk at kbt.io <mailto:strk at kbt.io> > wrote:

On Fri, Apr 20, 2018 at 05:46:12PM -0400, Michael Smith wrote:

I don’t see any reason why we wouldn’t want to provide this for OSGeo projects.

I do: we'd be an OpenSource Software Foundation paying a ClosedSource
Software Company to keep being successful in their business model.

Compare that to giving money to community members willing to provide
build agents to the existing OSGeo build infrastructure (drone.osgeo.org <http://drone.osgeo.org> ).

See https://wiki.osgeo.org/wiki/Drone

Me and Regina are currently the only ones providing build agents.

Or also, compare that to paying the external service to someone
who puts the service code out there as open source, for example
Drone developer himself ( https://drone.io/pricing/ ) or gitlab
people ( https://about.gitlab.com/pricing/ ).

Or also, to paying sysadmin teams to build these things in-house.

What's been asked here is to pay for what is really just marketing:
showing that "OSGeo has a good presence on GitHub", as if doing so
makes it a _serious_ OpenSource player. This is surrendering to
GitHub marketing stating "where software is built!". Are we paying
to be marketing agents ?

You make a good point. Should we reinforce Gitlab then and try to find
a similar service for our projects? How will moving to Gitlab impact
our projects?
_______________________________________________
Board mailing list
Board at lists.osgeo.org <mailto:Board at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/board

_______________________________________________
Board mailing list
Board at lists.osgeo.org <mailto:Board at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/board

—

Tim Sutton

Co-founder: Kartoza

Project chair: QGIS.org <http://QGIS.org> 

Visit http://kartoza.com <http://kartoza.com/>  to find out about open source:

Desktop GIS programming services

Geospatial web development

GIS Training

Consulting Services

Skype: timlinux 

IRC: timlinux on #qgis at freenode.net <http://freenode.net> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20180423/c652dff7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6122 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/board/attachments/20180423/c652dff7/attachment.jpg>