Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: Alex Hitchins <alex@alexhitchins.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Thu, 29 Jun 2017 10:33:56 +0100
Subject: Re: JIRA - PLEASE READ
Message-Id: <A72D964C-2D2B-4B9D-8FDA-DD8032E20924@alexhitchins.com>
References: <DB5PR07MB13341236AC030D3C6C84D9E48CD20@DB5PR07MB1334.eurprd07.prod.outlook.com> <CAGQtxvYZqk2pbTKPnsCTCc2OZpcw4OX4RjyxHRR8Uqyg2oQceA@mail.gmail.com> <DB5PR07MB133432A1B09BB0863A89438A8CD20@DB5PR07MB1334.eurprd07.prod.outlook.com>
In-Reply-To: <DB5PR07MB133432A1B09BB0863A89438A8CD20@DB5PR07MB1334.eurprd07.prod.outlook.com>
To: dev@cloudstack.apache.org
archived-at: Thu, 29 Jun 2017 09:34:07 -0000

I've saved up enough to chip a tuppence worth of comment in.

In any other project, you would have a project manager, someone at the coalf=
ace ensuring there is a perfect harmony behind the chaos that is software de=
velopment.

=46rom the sidelines, it looks like Cloudstack really needs some project man=
agement love and attention.=20

Comment over, as you were.


> On 29 Jun 2017, at 10:24, Paul Angus <paul.angus@shapeblue.com> wrote:
>=20
> Such a view of CloudStack is what holds CloudStack back.
> It stops users/operators from having any chance of understanding what Clou=
dStack does and how it does it.
> Code for code's sake is no use to anyone.
> Jira is about communication between developers and to everyone else.
>=20
>=20
>=20
> Kind regards,
>=20
> Paul Angus
>=20
> paul.angus@shapeblue.com=20
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Daan Hoogland [mailto:daan.hoogland@gmail.com]=20
> Sent: 29 June 2017 10:14
> To: dev <dev@cloudstack.apache.org>
> Subject: Re: JIRA - PLEASE READ
>=20
>> On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus <paul.angus@shapeblue.com> w=
rote:
>> + Release notes will be impossible to create without a proper Jira histor=
y.
>> And no one will know what has gone into CloudStack.
>=20
>=20
> No they are not mr Grumpy. they should be base on the code anyway, hence o=
n git, not jira. I do not appose to the use of Jira but it is not required f=
or good coding practices and as we are not and will not function as a corpor=
ation, jira is an extra for those that grave for it. not a requirement.
>=20
> --
> Daan