<div dir="ltr">Hi all,<div><br></div><div>Just wanted to give my opinion on using a external service as source code repository, I think there is no problem using github because:</div><div><br></div><div>- Source Code is protected by the license,</div><div>- If github service stops to address the project needs then port it to other repository. I remember sourceforge starting to be a really bad service (having a bunch of ads and bad practices) and people just migrated to other repositories.</div><div>- Having a internal source repository service needs human resources and hardware, it costs money and time. Having a semi-working service will also impact project efficiency.</div><div>- Migrating a project to other repository is not a problem if the entry point is always the same: the project website. Most people that look for releases are going to search them on the project website or on their operating system software center. For developers they can be warned with a message on source code project description or readme file.</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 28, 2015 at 8:23 AM, María Arias de Reyna <span dir="ltr"><<a href="mailto:delawen+osgeo@gmail.com" target="_blank">delawen+osgeo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Sep 28, 2015 at 9:17 AM, Julien Michel <span dir="ltr"><<a href="mailto:julien.michel@cnes.fr" target="_blank">julien.michel@cnes.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi all,<br>
<br>
I am a fairly new charter member, so maybe the two following
comments here will be irrelevant.<br>
<br>
From my perspective, having Orfeo ToolBox as an incubating project
definitively helped us to move in the right direction. I am not
saying that it would not have occured without OSGeo, but the
organization gives the momentum and defines the standards to
reach. As such, it is useful and somehow efficient. The fact that
the process is long is mostly on the project side in our case.<br>
<br>
I think that the Github move is hazardous. Sure, it is easy, free
for open-source projects, and really really cool. Granted, it
helps a lot in getting fluid contributions to open-source
projects. But ... in two years, they may start shipping sponsors
links at the end of the Readme files, and in a moments notice you
have to watch 20 seconds ads before cloning. At this point, you
will want to bail out, only to find out that in fact you can not,
because you can not delete the project anymore, or the issue
tracker database can not be exported ...<br>
<br>
My point is, OSGeo should care about long-term protection of GIS
open-source, and if this goal aligns for now with services that
Github provides, it may no longer be the case in the future .Of
course we need to be on Github: it is a public place to be, like
twitter & co. But completely giving up code hosting and
developers exchanges to a private company is the opposite of what
I think the organization should do. <br>
<br>
I know proper hosting services requires time and money, I do not
have the solution to that, but for me OSGeo should provide a
sustainable alternative, up-to-date and tailored for its purpose.</div><div><br></div></div></blockquote><div><br></div></span><div>Completely agree with you, Julien. Avoid openess and advance towards freedom :)</div><div><br></div><div>The easiest solution is to have our own git repository+dashboard on our own server, like with gitlab: <a href="https://about.gitlab.com/" target="_blank">https://about.gitlab.com/</a> </div></div></div></div>
<br>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br></blockquote></div><br></div>