<p dir="ltr">Hmm I thought the whole point of using github etc was so we don't have to run our own setup and can just deal with making the software? </p>
<br><div class="gmail_quote"><div dir="ltr">On Mon, 29 Aug 2016 5:33 pm Vincent Picavet (ml) <<a href="mailto:vincent.ml@oslandia.com">vincent.ml@oslandia.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Just a note to say that SAC is currently testing an OSGeo GitLab<br>
instance. It is on a temporary server, but may be used freely and can be<br>
used for testing and migration purpose.<br>
<br>
What is currently lacking is not setup time, but instead :<br>
* a decision from OSGeo's community on what we do want to use as a<br>
modern software hosting platform<br>
* a maintainance team<br>
* a better server for the definitive setup<br>
<br>
I think that if QGIS is willing to migrate to GitLab, using this<br>
opportunity to join forces with current SAC effort would be great.<br>
CCed to Bjorn and Sandro who currently lead the testing effort.<br>
<br>
You can already give it a try here (latest GitLab version) :<br>
<a href="https://git.osgeo.org/gitlab/" rel="noreferrer" target="_blank">https://git.osgeo.org/gitlab/</a><br>
<br>
Vincent<br>
<br>
Just a On 27/08/2016 13:47, Tudor Barascu wrote:<br>
> Hi all,<br>
><br>
> I am volunteering to install, do maintenance if you'll go the gitlab<br>
> way. I would have said this from the start but I didn't notice that such<br>
> a discussion was taking place. I am positive that I would manage this I<br>
> have good enough experience with system administration and I'm actually<br>
> maintaning a gitlab private instance for about 2 years now.<br>
> Although I can manage it on my own it would be very nice if somebody<br>
> else would also be involved.<br>
> I can also help with migrating the issues from redmine to gitlab.<br>
><br>
> Regards,<br>
> Tudor<br>
><br>
> PS. I think gitlab would be the better option<br>
><br>
><br>
> On Saturday, August 27, 2016 12:00 PM, Andreas Neumann<br>
> <<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a>> wrote:<br>
><br>
><br>
> Hi Denis,<br>
> We had a look at hosted solutions (for Gitlab and for Redmine) - but<br>
> most of them had been too expensive for our case - they have a limit on<br>
> the number of users that can be associated with a project, or other<br>
> limits like file sizes/total project size, etc.<br>
> Running our own gitlab instance would have been an option, but no one<br>
> volunteered to take on the task of permanently maintaining the<br>
> infrastructure, e.g. dealing with security issues/patching/upgrading,<br>
> spammers, deal with the evil guys out on the web. Maybe if we can find<br>
> someone who wants to take on the task (ideally more than one person), we<br>
> could reconsider to use a self-hosted gitlab.<br>
> Note that the new Redmine instance has some integration with github.<br>
> Jürgen, Richard or Pirmin can tell you the details.<br>
><br>
> What is so bad with Redmine? And exactly what integration with github<br>
> are you missing? Maybe Redmine can do this integration.<br>
><br>
> Andreas<br>
><br>
> Am 26.08.2016 um 23:03 schrieb Denis Rouzaud:<br>
>> Hi all,<br>
>> Being part of the unhappy, I would like to ask if you have considered<br>
>> running our own gitlab instance or using a gitlab service?<br>
>> To me integrated solution should be a hard requirement.<br>
>> If we have to maintain something like Redmine, why not gitlab. It<br>
>> seems you can categorize issues.<br>
>> Denis<br>
>><br>
>> Le ven. 26 août 2016 22:24, Andreas Neumann <<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a><br>
>> <mailto:<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a>>> a écrit :<br>
>><br>
>> Hi,<br>
>><br>
>> The issue tracker was discussed almost 1.5h at the board meeting - and<br>
>> it wasn't a clear and unanimous decision. Some board members<br>
>> (including<br>
>> me) also changed their minds during the discussion. Apparently not all<br>
>> core devs were happy with the quite limited filtering and structuring<br>
>> options that github offers. The issue tracker is certainly quite<br>
>> limited, compared to other issue tracker offerings. Offering only<br>
>> labels<br>
>> is quite limited. In addition, migrating all the existing tickets from<br>
>> Redmine to Github turned out to be non-trivial - and we don't want to<br>
>> loose the old issues.<br>
>><br>
>> Finally, it is probably good that we are in control of the issues and<br>
>> that it runs on free software. The board knows that not all people are<br>
>> happy with this decision but one cannot make everyone happy ... we<br>
>> hope<br>
>> that the "unhappy" people can still live with the renewed (and faster)<br>
>> Redmine.<br>
>><br>
>> The issues are migrated to the newest Redmine version and on a<br>
>> dedicated<br>
>> machine rented by <a href="http://QGIS.ORG" rel="noreferrer" target="_blank">QGIS.ORG</a> <<a href="http://qgis.org/" rel="noreferrer" target="_blank">http://qgis.org/</a>> to ensure good<br>
>> performance. This should make<br>
>> dealing with issues much more pleasant and more performant.<br>
>><br>
>> Big thanks to Jürgen, Richard and Pirmin for dealing with the Redmine<br>
>> migration.<br>
>><br>
>> Andreas<br>
>><br>
>> Am 26.08.2016 um 22:08 schrieb Marco Bernasocchi:<br>
>> > .<br>
>> ><br>
>> ><br>
>> >> I was under the impression that we were leaning towards to<br>
>> migrating<br>
>> >> to GH issues tracker.<br>
>> >> What was the main reason behind choosing Redmine again? technical<br>
>> >> issues? lack of time to solve them? Will the migration to a new<br>
>> >> Redmine version be effortless?<br>
>> >><br>
>> > Me too. I'm still convinced that this is a _very_ sub optimal<br>
>> solution for everybody.<br>
>> > Pity we really want to stick with something that forces us<br>
>> continuing having two different, non integrated tools where one<br>
>> could have done it in a great way.<br>
>> ><br>
>> > Cheers Marco<br>
>><br>
>> _______________________________________________<br>
>> Qgis-developer mailing list<br>
>> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a> <mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a>><br>
>> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a> <mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a>><br>
> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></blockquote></div>