Too much discussion in JIRA apparently...

[Bertrand Delacretaz <bd...@apache.org>]

Hi,

I haven't followed the DMAP jira in detail recently, but it looks like
discussions are happening there.

Except for details related to a specific issue, t's much better for
"important" discussions to happen on this list so that everybody can
follow without having to look at each and every jira issue. We can
always use issue IDs like DMAP-1234 to make it clear what we are
talking about.

In Apache projects, all "important" discussions and decisions must
happen on the project's dev list - or they didn't happen.

Of course this depends on the meaning of "important"...I'd say as soon
as something is more than a specific detail about a specific issue.

-Bertrand

Re: Too much discussion in JIRA apparently...

[Werner Keil <we...@gmail.com>]

Hi,

That's a good point, and referring to a "side-comment" which came up in a
mentioned JIRA ticket where Volkan and I found it would be better for the
Classifier to separate the "admin console" (for various reasons, security
and being more "hacker-proof" as one of the most important to corporate
users I'd say;-) the actual separation should also be discussed here (we
can of course mention the JIRA task)

Thanks,
Werner

On Tue, Jan 6, 2015 at 3:18 PM, Bertrand Delacretaz <bd...@apache.org>
wrote:

> Hi,
>
> I haven't followed the DMAP jira in detail recently, but it looks like
> discussions are happening there.
>
> Except for details related to a specific issue, t's much better for
> "important" discussions to happen on this list so that everybody can
> follow without having to look at each and every jira issue. We can
> always use issue IDs like DMAP-1234 to make it clear what we are
> talking about.
>
> In Apache projects, all "important" discussions and decisions must
> happen on the project's dev list - or they didn't happen.
>
> Of course this depends on the meaning of "important"...I'd say as soon
> as something is more than a specific detail about a specific issue.
>
> -Bertrand
>