Agreed Alex On Jun 29, 2017 5:34 AM, "Alex Hitchins" <a...@alexhitchins.com> wrote:
> 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 > coalface ensuring there is a perfect harmony behind the chaos that is > software development. > > From the sidelines, it looks like Cloudstack really needs some project > management love and attention. > > Comment over, as you were. > > > > > On 29 Jun 2017, at 10:24, Paul Angus <paul.an...@shapeblue.com> wrote: > > > > Such a view of CloudStack is what holds CloudStack back. > > It stops users/operators from having any chance of understanding what > CloudStack 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. > > > > > > > > Kind regards, > > > > Paul Angus > > > > paul.an...@shapeblue.com > > www.shapeblue.com > > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > > @shapeblue > > > > > > > > > > -----Original Message----- > > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > > Sent: 29 June 2017 10:14 > > To: dev <dev@cloudstack.apache.org> > > Subject: Re: JIRA - PLEASE READ > > > >> On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus <paul.an...@shapeblue.com> > wrote: > >> + Release notes will be impossible to create without a proper Jira > history. > >> And no one will know what has gone into CloudStack. > > > > > > No they are not mr Grumpy. they should be base on the code anyway, hence > on git, not jira. I do not appose to the use of Jira but it is not required > for good coding practices and as we are not and will not function as a > corporation, jira is an extra for those that grave for it. not a > requirement. > > > > -- > > Daan > >
