You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Henryk Konsek <he...@gmail.com> on 2012/08/13 13:27:27 UTC

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

> You could move the code to Apache hardware; have the PMC disown it (and
> then it can't be released as an Apache release, etc); or ask board@ for
> other options.

I don't get such Apache politics nuances :) . So simply speaking -
Apache infra guys won't let us to send Google notifications to our
mailing list? :)

If so, anybody got an idea for the workaround? My idea would be to
create dedicated Google Mailing Group for Camel-Extra commits and then
send the notifications there.

Any further thoughts?

-- 
Henryk Konsek
http://henryk-konsek.blogspot.com

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Henryk Konsek <he...@gmail.com>.
> It's not me who will decide. We (the community) will decide...
> But I'm +1 if we can hide/disable the issue button and provide an easy to
> find/read link to the Apache Camel JIRA to log issues.

Yes we can hide issues tab easily. And yes we can add readable link on
the home page.

I'll raise a voting for this issue later this weekend. Actually that's
all I can do since my vote is not binding :) .

--
Henryk Konsek
http://henryk-konsek.blogspot.com

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Christian Müller <ch...@gmail.com>.
It's not me who will decide. We (the community) will decide...
But I'm +1 if we can hide/disable the issue button and provide an easy to
find/read link to the Apache Camel JIRA to log issues.

Best,
Christian

On Fri, Sep 14, 2012 at 9:13 AM, Henryk Konsek <he...@gmail.com> wrote:

> > We do not receive many issues via Google. If the notification mechanism
> > works, we will get a mail at issues@ and could create an JIRA issue at
> > Apache, link them together and update the Apache JIRA issue until it is
> > resolved. Than we can close both issues.
>
> Actually I see no point in maintaining both Jira and Google Issues.
> Google Issues do not provide any value added IMHO. And somebody will
> have to link issue to Jira after notification has been sent.
>
> The another thing I don't like in Google Issues at Camel Extra is that
> they create the illusion that Camel Extra issues are handled
> separately from the regular Camel (what is not true, since we create
> camel-extra issues in Jira as well).
>
> In case you decided to close the Google Issues on behalf of Jira -
> just let me know. I'll migrate the existing issues and hide the issues
> tab.
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>



--

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Br...@toyota-europe.com.
+1

Bruno Barin
Purchasing/Warranty Business Support
Toyota Motor Europe 
60 Avenue du Bourget, 
1140 Brussels, Belgium
Ph: +32 (0) 2 745 5606
www.toyota-europe.com









Henryk Konsek <he...@gmail.com> 
14/09/2012 09:13
Please respond to
dev@camel.apache.org

To
Christian Müller <ch...@gmail.com>
cc
dev@camel.apache.org
Subject
Re: Accept mails on committs@camel.apache.org from 
camel-extra.apache-extras.org@codespot.com






> We do not receive many issues via Google. If the notification mechanism
> works, we will get a mail at issues@ and could create an JIRA issue at
> Apache, link them together and update the Apache JIRA issue until it is
> resolved. Than we can close both issues.

Actually I see no point in maintaining both Jira and Google Issues.
Google Issues do not provide any value added IMHO. And somebody will
have to link issue to Jira after notification has been sent.

The another thing I don't like in Google Issues at Camel Extra is that
they create the illusion that Camel Extra issues are handled
separately from the regular Camel (what is not true, since we create
camel-extra issues in Jira as well).

In case you decided to close the Google Issues on behalf of Jira -
just let me know. I'll migrate the existing issues and hide the issues
tab.

--
Henryk Konsek
http://henryk-konsek.blogspot.com


Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Henryk Konsek <he...@gmail.com>.
> We do not receive many issues via Google. If the notification mechanism
> works, we will get a mail at issues@ and could create an JIRA issue at
> Apache, link them together and update the Apache JIRA issue until it is
> resolved. Than we can close both issues.

Actually I see no point in maintaining both Jira and Google Issues.
Google Issues do not provide any value added IMHO. And somebody will
have to link issue to Jira after notification has been sent.

The another thing I don't like in Google Issues at Camel Extra is that
they create the illusion that Camel Extra issues are handled
separately from the regular Camel (what is not true, since we create
camel-extra issues in Jira as well).

In case you decided to close the Google Issues on behalf of Jira -
just let me know. I'll migrate the existing issues and hide the issues
tab.

--
Henryk Konsek
http://henryk-konsek.blogspot.com

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Christian Müller <ch...@gmail.com>.
We do not receive many issues via Google. If the notification mechanism
works, we will get a mail at issues@ and could create an JIRA issue at
Apache, link them together and update the Apache JIRA issue until it is
resolved. Than we can close both issues.

Best,
Christian

On Thu, Sep 13, 2012 at 10:10 PM, Henryk Konsek <he...@gmail.com> wrote:

> > I created a issue at Camel extra and did a commit a few minutes ago.
> Until
> > now, no message received on our mailing list. Will ping INFRA again...
>
> Great. Apparently soon there will be no further need to create extra
> commits notification manually :) .
>
> While we talking about the Google Project issue tracker - I suggest
> that we should disable it in Camel Extra. Instead we should provide
> link to the Apache Jira and tell people to report issues there. We
> host extra code on Google due to the licensing constrains - we do not
> need to maintain separated issue tracker for this reason. Google
> issues suck comparing to Jira and probably nobody checks them :) .
> Can't we stick to the Jira like in the case of the regular Camel?
>
> Laters.
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>



--

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Henryk Konsek <he...@gmail.com>.
> I created a issue at Camel extra and did a commit a few minutes ago. Until
> now, no message received on our mailing list. Will ping INFRA again...

Great. Apparently soon there will be no further need to create extra
commits notification manually :) .

While we talking about the Google Project issue tracker - I suggest
that we should disable it in Camel Extra. Instead we should provide
link to the Apache Jira and tell people to report issues there. We
host extra code on Google due to the licensing constrains - we do not
need to maintain separated issue tracker for this reason. Google
issues suck comparing to Jira and probably nobody checks them :) .
Can't we stick to the Jira like in the case of the regular Camel?

Laters.

--
Henryk Konsek
http://henryk-konsek.blogspot.com

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Christian Müller <ch...@gmail.com>.
I created a issue at Camel extra and did a commit a few minutes ago. Until
now, no message received on our mailing list. Will ping INFRA again...

Best,
Christian

On Thu, Sep 13, 2012 at 12:24 AM, Christian Müller <
christian.mueller@gmail.com> wrote:

> Here is the INFRA ticket: https://issues.apache.org/jira/browse/INFRA-5268
>
> Best,
> Christian
>
>
> On Wed, Sep 12, 2012 at 9:37 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> Hello Henryk!
>>
>> Today I asked INFRA again how we can proceed here.
>> I configured notifications for commits and issues, which are send from
>> one account each. It should be easy to allow receiving mails from this
>> accounts...
>> I will keep you posted.
>>
>> Best,
>> Christian
>>
>>
>> On Mon, Aug 13, 2012 at 1:27 PM, Henryk Konsek <he...@gmail.com>wrote:
>>
>>> > You could move the code to Apache hardware; have the PMC disown it (and
>>> > then it can't be released as an Apache release, etc); or ask board@for
>>> > other options.
>>>
>>> I don't get such Apache politics nuances :) . So simply speaking -
>>> Apache infra guys won't let us to send Google notifications to our
>>> mailing list? :)
>>>
>>> If so, anybody got an idea for the workaround? My idea would be to
>>> create dedicated Google Mailing Group for Camel-Extra commits and then
>>> send the notifications there.
>>>
>>> Any further thoughts?
>>>
>>> --
>>> Henryk Konsek
>>> http://henryk-konsek.blogspot.com
>>>
>>
>>
>>
>> --
>>
>>
>>
>
>
> --
>
>
>


--

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Christian Müller <ch...@gmail.com>.
Here is the INFRA ticket: https://issues.apache.org/jira/browse/INFRA-5268

Best,
Christian

On Wed, Sep 12, 2012 at 9:37 PM, Christian Müller <
christian.mueller@gmail.com> wrote:

> Hello Henryk!
>
> Today I asked INFRA again how we can proceed here.
> I configured notifications for commits and issues, which are send from one
> account each. It should be easy to allow receiving mails from this
> accounts...
> I will keep you posted.
>
> Best,
> Christian
>
>
> On Mon, Aug 13, 2012 at 1:27 PM, Henryk Konsek <he...@gmail.com> wrote:
>
>> > You could move the code to Apache hardware; have the PMC disown it (and
>> > then it can't be released as an Apache release, etc); or ask board@ for
>> > other options.
>>
>> I don't get such Apache politics nuances :) . So simply speaking -
>> Apache infra guys won't let us to send Google notifications to our
>> mailing list? :)
>>
>> If so, anybody got an idea for the workaround? My idea would be to
>> create dedicated Google Mailing Group for Camel-Extra commits and then
>> send the notifications there.
>>
>> Any further thoughts?
>>
>> --
>> Henryk Konsek
>> http://henryk-konsek.blogspot.com
>>
>
>
>
> --
>
>
>


--

Re: Accept mails on committs@camel.apache.org from camel-extra.apache-extras.org@codespot.com

Posted by Christian Müller <ch...@gmail.com>.
Hello Henryk!

Today I asked INFRA again how we can proceed here.
I configured notifications for commits and issues, which are send from one
account each. It should be easy to allow receiving mails from this
accounts...
I will keep you posted.

Best,
Christian

On Mon, Aug 13, 2012 at 1:27 PM, Henryk Konsek <he...@gmail.com> wrote:

> > You could move the code to Apache hardware; have the PMC disown it (and
> > then it can't be released as an Apache release, etc); or ask board@ for
> > other options.
>
> I don't get such Apache politics nuances :) . So simply speaking -
> Apache infra guys won't let us to send Google notifications to our
> mailing list? :)
>
> If so, anybody got an idea for the workaround? My idea would be to
> create dedicated Google Mailing Group for Camel-Extra commits and then
> send the notifications there.
>
> Any further thoughts?
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>



--