Accept mails on [e-mail] from [e-mail]

[Christian Mueller]

The Apache Camel team also develop/maintain components at Apache extra [1].
We would like to receive mail notifications for changes done at Camel extra
which are sent by [hidden email].
I already configured this at the Camel extra site, but we do not receive
the commit mails.
What have we to do else?

[1] http://code.google.com/a/apache-extras.org/p/camel-extra

Thanks in advance,
Christian

[Daniel Shahaf]

Christian Müller wrote on Thu, Jul 12, 2012 at 21:38:54 +0200:
> The Apache Camel team also develop/maintain components at Apache extra [1].
> We would like to receive mail notifications for changes done at Camel extra
> which are sent by [hidden email].
> I already configured this at the Camel extra site, but we do not receive
> the commit mails.
> What have we to do else?
>

The above scenario is not supported.  Code for Apache projects must live
on Apache hardware.

That said, the answer to your question is "Read the bounce email the
sender will have received, or show us an SMTP transcript where
MX(apache.org) accepted the mail so we can investigate further".

> [1] http://code.google.com/a/apache-extras.org/p/camel-extra
>
> Thanks in advance,
> Christian

[Christian Mueller]

Thanks Daniel for the quick answer.

I would like to show you the bounce email, but I didn't get one (I SUPPOSE
Google/Codespot doesn't forward the bounce mail to the project admins).
And because the mail doesn't received our mailing list, I ASSUME it wasn't
accepted.

I did not think our project is the first one which such a request, because
there are many more projects at code.google.com/a/apache-extras.org/
Do we have another option how we can proceed?

Best,
Christian

On Thu, Jul 12, 2012 at 9:53 PM, Daniel Shahaf <[hidden email]>wrote:

> Christian Müller wrote on Thu, Jul 12, 2012 at 21:38:54 +0200:
> > The Apache Camel team also develop/maintain components at Apache extra
> [1].
> > We would like to receive mail notifications for changes done at Camel
> extra
> > which are sent by [hidden email].
> > I already configured this at the Camel extra site, but we do not receive
> > the commit mails.
> > What have we to do else?
> >
>
> The above scenario is not supported.  Code for Apache projects must live
> on Apache hardware.
>
> That said, the answer to your question is "Read the bounce email the
> sender will have received, or show us an SMTP transcript where
> MX(apache.org) accepted the mail so we can investigate further".
>
> > [1] http://code.google.com/a/apache-extras.org/p/camel-extra
> >
> > Thanks in advance,
> > Christian
>

[Marvin Humphrey]

On Sat, Jul 14, 2012 at 3:43 PM, Christian Müller
<[hidden email]> wrote:
> I did not think our project is the first one which such a request, because
> there are many more projects at code.google.com/a/apache-extras.org/
> Do we have another option how we can proceed?

I wonder if the Maven PMC made such a request.

    http://markmail.org/message/irqi7rtn3vhcxzf6

    If the Maven project had not deliberately ignored an order by the board
    regarding use of our own version control system, it would not have been in
    this position today.  We have no control over the policies applied to
    software in apache-extras.  We will not allow external repositories to be
    used as an end-run around our policies.  We will not tolerate any further
    deviances in this regard from Maven.  Do it right or don't do it at all.

Marvin Humphrey

[Daniel Shahaf]

Christian Müller wrote on Sun, Jul 15, 2012 at 00:43:23 +0200:

> Thanks Daniel for the quick answer.
>
> I would like to show you the bounce email, but I didn't get one (I SUPPOSE
> Google/Codespot doesn't forward the bounce mail to the project admins).
> And because the mail doesn't received our mailing list, I ASSUME it wasn't
> accepted.
>
> I did not think our project is the first one which such a request, because
> there are many more projects at code.google.com/a/apache-extras.org/
> Do we have another option how we can proceed?
>

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.

> Best,
> Christian
>
> On Thu, Jul 12, 2012 at 9:53 PM, Daniel Shahaf <[hidden email]>wrote:
>
> > Christian Müller wrote on Thu, Jul 12, 2012 at 21:38:54 +0200:
> > > The Apache Camel team also develop/maintain components at Apache extra
> > [1].
> > > We would like to receive mail notifications for changes done at Camel
> > extra
> > > which are sent by [hidden email].
> > > I already configured this at the Camel extra site, but we do not receive
> > > the commit mails.
> > > What have we to do else?
> > >
> >
> > The above scenario is not supported.  Code for Apache projects must live
> > on Apache hardware.
> >
> > That said, the answer to your question is "Read the bounce email the
> > sender will have received, or show us an SMTP transcript where
> > MX(apache.org) accepted the mail so we can investigate further".
> >
> > > [1] http://code.google.com/a/apache-extras.org/p/camel-extra
> > >
> > > Thanks in advance,
> > > Christian
> >

[hekonsek]

> 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

[Christian Mueller]

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 <[hidden email]> 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
>

--

[Christian Mueller]

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 <
[hidden email]> 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 <[hidden email]> 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
>>
>
>
>
> --
>
>
>

--

[Christian Mueller]

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 <
[hidden email]> 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 <
> [hidden email]> 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 <[hidden email]>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
>>>
>>
>>
>>
>> --
>>
>>
>>
>
>
> --
>
>
>

--

[hekonsek]

> 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

[Christian Mueller]

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 <[hidden email]> 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
>

--

[hekonsek]

> 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

[Bruno.Barin]

+1

Bruno Barin
Purchasing/Warranty Business Support
Toyota Motor Europe
60 Avenue du Bourget,
1140 Brussels, Belgium
Ph: [phone]
www.toyota-europe.com









Henryk Konsek <[hidden email]>
14/09/2012 09:13
Please respond to
[hidden email]

To
Christian Müller <[hidden email]>
cc
[hidden email]
Subject
Re: Accept mails on [hidden email] from
[hidden email]






> 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

[Christian Mueller]

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 <[hidden email]> 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
>

--

[hekonsek]

> 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