Re: gitlab.apache.org

Thanks for the info David, I'll keep it in mind. The force is pulling cloudstack to the github-side strong at the moment. I thought of gitlabs as the closest, easiest, cheapest alternative but am open to any. I'll find time to have a look at those pointers. On Sun, Jan 10, 2016 at 7:08 AM, David

Re: gitlab.apache.org

I've seen some of the conversations on dev@cloudstack- but I'll respond in both lists. We've had requests for Gitlab, Gerrit, and a few others. Sometimes (including our own PMC) we've had requests for several different, somewhat competing solutions for the same project. We aren't shutting the

gitlab.apache.org

We, cloudstack-dev-list-users have been talking about moving more functionality to github. This is being rejected by the foundation so far for (in my view obvious) reasons of governance. The functionality is however missed dearly so speaking with an ex-member he suggested we install a machine with

Re: gitlab.apache.org

On 08-01-16 09:25, Daan Hoogland wrote: > We, cloudstack-dev-list-users have been talking about moving more > functionality to github. This is being rejected by the foundation so far > for (in my view obvious) reasons of governance. The functionality is > however missed dearly so speaking with

Re: gitlab.apache.org

This has been discussed rather intensively on the infra ML previously. Here's an answer from David: http://markmail.org/message/msxi7bhkfijydckq It's about half years old, so "short term" might have changed. -- Erik On Fri, Jan 8, 2016 at 2:36 PM, Daan Hoogland

Re: gitlab.apache.org

Wido, you are touching on the point of governance there. The maintenance is the price for keeping the goods under your control. Apache wants to make sure force pushes are not garbage collected but tagged for audit purposes, I understand. Btw, let's include infra in the discussion. On Fri, Jan 8,