That is what I am saying. Apache can (and does) handle donations, and there
have been discussions about donations that can be directed to projects at
the donation time (someone that knows about the topic could provide some
help here?).
So, the foundation part looks covered for meI think we ne
Rafael,
I agree. I am not saying move away from Apache.. I am saying setup a
"foundation" to handle donations and even development management..
Regards,
Marty Godsey
Principal Engineer
nSource Solutions, LLC
-Original Message-
From: Rafael Weingärtner [mailto:rafaelweingart...@gmail.co
ACS is an Apache project, not a foundation per se; donation goes to Apache.
I know that there is some discussion/work to create a way for donating
things (not just money) to projects, but I do not know how that is going.
I do not think we need to create other foundation and move away from Apache
(
Alex,
I agree.. The only "good" way that we will get more adoption is to treat it
like an Enterprise product. But that would require investment. Investment with
money, not just time.
As an example, I use pfSense alot in my projects. If I put in a pfSense router,
I take 2-5% (depends on scope)
For small fixes that do not affect functionality the value of a JIRA may
be questioned.
The main advantages that I see:
- if 2 people find the same bug and both fix it without raising a JIRA,
you may end up with 2 different patches
- if an end-user finds the bug and searches the JIRA to see if
If it isn't being treated as a product it will be very impossible to market it
as enterprise ready.
I know we all know this.
Similar sized projects under the Apache banner must have the same issue, what
is the best way to gather experience of these projects? See how they handle
these growing
I understand that it is a volunteer organization.
I do not know how many (if any) of the committers and PMC members are
funded by their organizations (allowed or ordered to work on Cloudstack
during company time) which is often the way that Apache projects get
staffed.
Clearly it is hard to t
Hello guys..
I do work for a company in Silicon Valley. The company also uses a free project
to build its commercial project to make money. This project, like ACS, has no
funding. The project is FreeNAS. However, IXSystems, the company, uses FreeNAS
to build a "supported, commercial version" ca
I personally don't know how Jira solves any of this, but assuming it does,
fine...
The bigger problem which you have raised is that CloudStack has zero
funding. So we can't hire a project manager, or a release manager or
someone whose job it is to maintain documentation. I have been trying to
find
As a real outsider, IMHO Paul is right.
At times it seems that Cloudstack is a coding hobby rather than a
project or a production quality product.
Who decides what goes into a release? How does this affect the release
schedule?
Who is responsible for meeting the "published" roadmap (of which
Agreed Alex
On Jun 29, 2017 5:34 AM, "Alex Hitchins" 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.
>
Why are we still using jira instead of the PRs for that communication? Can
we not use issues in github now instead of jira if someone needs to open an
issue but does not yet have code to contribute. If not, jira could still be
used for that.
I think duplicating data between jira and the PR is kind
Hi Paul
On 06/29/2017 11:06 AM, Paul Angus wrote:
> Hi, Mr Grumpy here!
>
> I was looking the commits and I'm seeing commits going in with no Jira Issue
> assigned.
> My understanding is that there must be a Jira ticket for EVERY
> fix/enhancement/feature, so that we have a way to search and
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
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 A
On Thu, Jun 29, 2017 at 11:06 AM, Paul Angus 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 th
Hi, Mr Grumpy here!
I was looking the commits and I'm seeing commits going in with no Jira Issue
assigned.
My understanding is that there must be a Jira ticket for EVERY
fix/enhancement/feature, so that we have a way to search and track these
things.
+ Release notes will be impossible to cr
17 matches
Mail list logo
