JIRA notifications, where? (was: [jira] Created: (STANBOL-1) Website: check branding requirements)

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

Hi,

On Wed, Nov 24, 2010 at 10:34 AM, Fabian Christ
<ch...@googlemail.com> wrote:
> 2010/11/23 Isabel Drost <is...@apache.org>:
>> On Tue, 23 Nov 2010 Fabian Christ <ch...@googlemail.com> wrote:
>>> Personally, I don't like dev lists where you have to filter out the
>>> JIRA mails to find the real discussions.
>> I can only speak from my own experience - but with those Apache
>> projects I have been involved with, most "real discussions" as in
>> design discussions for features or code changes actually do happen in
>> the issue tracker.
>
> ...If it is best practice to have most "real" discussions in the JIRA
> ticket threads, then I agree that it is good to see JIRA notification
> mails about discussions that take place there....

> ...So as a consequence ticket related discussions should always be in
> JIRA?...

It's hard to find a balance between discussing things in JIRA or on
the dev list.

My opinion is that short discussions that are very specific to an
issue can happen in JIRA, but the rest belongs on the dev list.

> ...And just for my understanding: Do we open JIRA issues for topics
> like "Review the architecture". I just would like to understand which
> kind of things become an issue and which kind of things are discussed
> via the list. IMO this should be clear for everyone otherwise people
> might miss discussions....

I'm perfectly ok with "review the architecture" as a JIRA task if that
helps coordinate things, especially with sub-tasks that can be
dispatched to different people.

The discussion about the architecture, however, belongs on the dev
list - what might be discussed in such a JIRA task is details of how
the review is supposed to happen, for example, or short progress
reports, but not the review discussion itself.

All IMO of course.

-Bertrand

Re: JIRA notifications, where? (was: [jira] Created: (STANBOL-1) Website: check branding requirements)

[Fabian Christ <ch...@googlemail.com>]

Hi,

2010/11/24 Bertrand Delacretaz <bd...@apache.org>:
>> ...And just for my understanding: Do we open JIRA issues for topics
>> like "Review the architecture". I just would like to understand which
>> kind of things become an issue and which kind of things are discussed
>> via the list. IMO this should be clear for everyone otherwise people
>> might miss discussions....
>
> I'm perfectly ok with "review the architecture" as a JIRA task if that
> helps coordinate things, especially with sub-tasks that can be
> dispatched to different people.

Okay I understand that it will be a mixture. Issues are naturally good
to coordinate things. Mailings are better for broader discussions in
the whole group and to find consensus between people. In the end the
whole work ends in issues to control what's going on.

> The discussion about the architecture, however, belongs on the dev
> list - what might be discussed in such a JIRA task is details of how
> the review is supposed to happen, for example, or short progress
> reports, but not the review discussion itself.

Yes, I like this view. IMO new people, like me, will learn how to use
which channel by practice ;)

Thank you!

-- 
Fabian