You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Tommaso Teofili <to...@gmail.com> on 2010/11/23 10:43:22 UTC

Re: [jira] Created: (STANBOL-1) Website: check branding requirements

Hi Bertrand,
Just a quick comment: I received this JIRA notification on
stanbol-commits, shouldn't they be notified on stanbol-dev?
Cheers,
Tommaso

2010/11/23 Bertrand Delacretaz (JIRA) <ji...@apache.org>

> Website: check branding requirements
> ------------------------------------
>
>                 Key: STANBOL-1
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1
>             Project: Stanbol
>          Issue Type: Task
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
>
> Check http://apache.org/foundation/marks/pmcs#checklist and include
> results in our board report.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Re: [jira] Created: (STANBOL-1) Website: check branding requirements

Posted by Isabel Drost <is...@apache.org>.
On Wed, 24 Nov 2010 Fabian Christ <ch...@googlemail.com> wrote:
> So as a consequence ticket related discussions should always be in
> JIRA?

Just for clarification: In the end the way you organise development is
up to the project. Just wanted to share some information on how some
other projects are using their bug tracker.

I personally tend view anything that might once turn into a patch as
potentially good candidate for JIRA tickets. Topics of broader scope
belong on the dev list (see also Bertrand's comments on that).

Isabel



Re: [jira] Created: (STANBOL-1) Website: check branding requirements

Posted by Fabian Christ <ch...@googlemail.com>.
Hi,

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.

Hmm okay that is another point. Perhaps, I have to say that my
experience comes from following mailing lists and its the first time
to be directly involved as a developer in an open source project.

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? 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.

-- 
Fabian

Re: [jira] Created: (STANBOL-1) Website: check branding requirements

Posted by 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 agree with you that JIRA in particular can be very chatty. Especially
when looking at corporate projects that also have time tracking
notifications sent out to everyone. However if used wisely it is
possible to limit notifications from JIRA to an extend that makes
following design discussions on the issue tracker from the mailing list
very easy.

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.

Just my 2'ct

Isabel



Re: [jira] Created: (STANBOL-1) Website: check branding requirements

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Tue, Nov 23, 2010 at 4:33 PM, Fabian Christ
<ch...@googlemail.com> wrote:
>... please no. Can we leave the JIRA tickets on stanbol-commit?
> Personally, I don't like dev lists where you have to filter out the
> JIRA mails to find the real discussions....

I don't really mind...you might need to filter in any case.

-Bertrand

Re: [jira] Created: (STANBOL-1) Website: check branding requirements

Posted by Fabian Christ <ch...@googlemail.com>.
Hi,

please no. Can we leave the JIRA tickets on stanbol-commit?
Personally, I don't like dev lists where you have to filter out the
JIRA mails to find the real discussions.

Best,
 - Fabian

2010/11/23 Tommaso Teofili <to...@gmail.com>:
> Hi Bertrand,
> Just a quick comment: I received this JIRA notification on
> stanbol-commits, shouldn't they be notified on stanbol-dev?
> Cheers,
> Tommaso
>
> 2010/11/23 Bertrand Delacretaz (JIRA) <ji...@apache.org>
>
>> Website: check branding requirements
>> ------------------------------------
>>
>>                 Key: STANBOL-1
>>                 URL: https://issues.apache.org/jira/browse/STANBOL-1
>>             Project: Stanbol
>>          Issue Type: Task
>>            Reporter: Bertrand Delacretaz
>>            Priority: Minor
>>
>>
>> Check http://apache.org/foundation/marks/pmcs#checklist and include
>> results in our board report.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>



-- 
Fabian