Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [DISCUSS] Move to Github
From: Sebastien Goasguen <runseb@gmail.com>
In-Reply-To: <CEAA2F46-B0ED-469A-A8EB-F5FA46CF8ED7@gmail.com>
Date: Sun, 3 Jan 2016 12:25:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F0C16CA-EBDF-4B4F-BC50-E9F6C788421C@gmail.com>
References: <00DF88E2-CE99-4886-88B6-3152CDEDF3AB@gmail.com>
 <567577A3.2020903@renemoser.net>
 <1A8C5FE0-D658-4FB6-8AAE-86EF139FB905@gmail.com>
 <903CE4AD-8908-4B5C-9A61-BA1B8A4AB71B@gmail.com>
 <CAGQtxvZ2e-rJVxZFM8pNOcNo32xjar_av1P9RKX3cwW-qbNmBQ@mail.gmail.com>
 <CEAA2F46-B0ED-469A-A8EB-F5FA46CF8ED7@gmail.com>
To: dev@cloudstack.apache.org

Bringing this one discuss thread to the top of the ML to get stronger =
consensus.

We need it if we want to request a move to GitHub.

Note that this is not about leaving the ASF, it is about using GitHub to =
its full potential.

The ASF board is investigating ways for a project to use Github and =
still maintain strong provenance of commits to keep the high quality and =
provenance standards of ASF code.

If we get consensus we can request to the board to be part of the =
=E2=80=9Ctrial=E2=80=9D and move to Github.

> On Dec 21, 2015, at 11:37 AM, Sebastien Goasguen <runseb@gmail.com> =
wrote:
>=20
>=20
>> On Dec 21, 2015, at 11:34 AM, Daan Hoogland <daan.hoogland@gmail.com> =
wrote:
>>=20
>> Sebastien, This will create a github repo under the apache =
organisation
>> right? one that we can not merge to.
>>=20
>=20
> Yes , that=E2=80=99s how I created all the docs repo and the repos for =
ec2stack and gstack.
>=20
>=20
>=20
>> On Mon, Dec 21, 2015 at 10:51 AM, Sebastien Goasguen =
<runseb@gmail.com>
>> wrote:
>>=20
>>> BTW
>>>=20
>>> Anyone can ask for a new git repo which will be mirrored on github =
at:
>>>=20
>>> =
https://issues.apache.org/jira/servicedesk/customer/portal/1/create/8
>>>=20
>>> Not sure if the link will work, but it=E2=80=99s available through =
issues.
>>>=20
>>>> On Dec 19, 2015, at 7:03 PM, Sebastien Goasguen <runseb@gmail.com>
>>> wrote:
>>>>=20
>>>>=20
>>>>=20
>>>>> On 19 Dec 2015, at 16:28, Rene Moser <mail@renemoser.net> wrote:
>>>>>=20
>>>>> Hi Seb
>>>>>=20
>>>>>> On 12/19/2015 10:12 AM, sebgoa wrote:
>>>>>>=20
>>>>>> Late October I started thread [1] about moving our repo to =
GitHub, I
>>> would like to re-open this discussion.
>>>>>>=20
>>>>>> Now that we have stabilized master and release 4.6.0, 4.6.1, =
4.6.2 and
>>> 4.7.0 we need to think about the next steps.
>>>>>>=20
>>>>>> To me Git and GitHub has become an essential tool to any software
>>> development, not using it to its full potential is hurting us.
>>>>>>=20
>>>>>> Just as an example I would like to point you to [2], this a PR I =
made
>>> to Kubernetes (a container orchestrator), it literally added 14 =
characters
>>> in a json file.
>>>>>> This was really a very minor change.
>>>>>>=20
>>>>>> The PR automatically triggered 3 bots which created 7 labels, it =
ran
>>> end to end testss, Jenkins jobs and triggered third part builds.
>>>>>> It was automatically merged.
>>>>>=20
>>>>> I am fine moving to github.
>>>>>=20
>>>>> But IMHO the git hosting is not the problem, the problem is how =
far do
>>>>> we trust the current tests and how we can them improve.
>>>>>=20
>>>>> Moving to github doesn't improve testing. Doing manual tests is =
okay and
>>>>> hard work, it does not speed up things.
>>>>>=20
>>>>> We need fully automated unit _and_ integration tests that we =
trust. I do
>>>>> not trust in mocking and simulating infrastructure.
>>>>>=20
>>>>> We discovered most of the major problems running cloudstack on =
real
>>>>> hardware in real world scenarios. Race conditions, unexpected VR
>>>>> reboots, VMs not getting IPs from DHCP, etc.
>>>>>=20
>>>>> Rating complexity of changes: easy_fix, minor_change, major_change
>>>>>=20
>>>>> Running tests according complexity:
>>>>>=20
>>>>> - easy_fix: just merge it.
>>>>> - minor_change: unit and simulator test passed
>>>>> - major_change: the full blown integration testing
>>>>>=20
>>>>> IMHO we should work on solid testing and development is fun, =
merging a
>>>>> click and releasing a breath.
>>>>>=20
>>>>> Just my 2 cents.
>>>>=20
>>>> Fully agree
>>>>=20
>>>> I do think moving to github would allow us to run tests on real =
systems
>>> more easily.
>>>>=20
>>>>=20
>>>>>=20
>>>>> Regards
>>>>> Ren=C3=A9
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>> --=20
>> Daan
>=20