You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Alex North (JIRA)" <ji...@apache.org> on 2011/01/05 03:34:46 UTC
[jira] Created: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Allow any address to post to wave-commits@incubator.apache.org
--------------------------------------------------------------
Key: INFRA-3338
URL: https://issues.apache.org/jira/browse/INFRA-3338
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: Mail (qmail)
Reporter: Alex North
The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin closed INFRA-3338.
------------------------
Resolution: Fixed
Agree
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Alex North (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980531#action_12980531 ]
Alex North commented on INFRA-3338:
-----------------------------------
Ok. I believe it's not possible to configure Reitveld to send all mail from a single address. It might be possible to do something crazy like sign wave-commits@ up as a member of the wave-protocol-code-discuss group (would need a Google account for it, etc), but maybe it's just better to wait and move the code and code reviewing to Apache first.
If you agree, we can close this as won't-fix and concentrate on moving the code.
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977593#action_12977593 ]
Brett Porter commented on INFRA-3338:
-------------------------------------
this will mean a moderator needs to let each address through (and "allow" them to post in future) if they aren't already subscribed. Is that ok?
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978020#action_12978020 ]
Brett Porter commented on INFRA-3338:
-------------------------------------
is the code review tool hosted on 'google apps for your domain'?
As a side note, Gav would like to let you know we have a reviewboard instance at reviews.apache.org :)
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977616#action_12977616 ]
Brett Porter commented on INFRA-3338:
-------------------------------------
I need to check with the other members of infra@, as changing it to moderated still requires @apache.org.
The typical configuration other projects have used is a separate list (e.g. -issues@ or -notifications@), with all discussion on -dev@, so using commits in this way is a bit non-standard.
As for moderators, the moderator on all the lists is currently Upayavira. It'd be good to add more - can I add soren & anorth on all of the lists?
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979944#action_12979944 ]
Brett Porter commented on INFRA-3338:
-------------------------------------
Apologies, I had an extended discussion with Joe and found that it wasn't captured in my IRC logs.
>From what I recall he said that the solution used before was to set up your review system to send to the list via a single address, as the same thing had been done for Shindig in the past. He might add more details if I've got that wrong.
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Alex North (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977597#action_12977597 ]
Alex North commented on INFRA-3338:
-----------------------------------
That sounds fine.
How does one become a moderator for the list? If that's also an infra request, soren@ and anorth@ would be an appropriate start, and I hope some other committers will join us.
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Alex North (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977620#action_12977620 ]
Alex North commented on INFRA-3338:
-----------------------------------
I'm happy for us to do things in a more Apache way, just don't know what that is yet :) I'm definitely ok with there being an -issues@ list for JIRA, but let's talk about that one later.
I don't think code reviews are out of place on the -commits@ list; they're commits waiting to happen (we do pre-commit review). If it's hard to set up I don't mind using another list, but any other list would need to allow non @apache.org addresses too.
Please do add soren and anorth as moderator on all the lists. Can you point me to the moderation interface?
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977623#action_12977623 ]
Brett Porter commented on INFRA-3338:
-------------------------------------
Added - see http://www.apache.org/dev/committers.html#mail-moderate
I'll get back to you on the list itself.
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Alex North (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978053#action_12978053 ]
Alex North commented on INFRA-3338:
-----------------------------------
Yes, the tool is on an apps-for-your-domain AppEngine instance. But thanks for reminding me about review board! We'll definitely consider switching if we can make pre-commit reviews there. I'll start testing it out. Maybe we can move code reviews first and then this request will be unnecessary.
The mail it sends has headers like (some internal routing ones redacted):
Return-Path: <3A...@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com>
Received-SPF: pass (google.com: domain of 3AwElTQkKBnYXUhcfUnimaiiafY.WigUhilnbaiiafY.Wig@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com designates 172.25.149.13 as permitted sender)
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 3AwElTQkKBnYXUhcfUnimaiiafY.WigUhilnbaiiafY.Wig@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com designates 172.25.149.13 as permitted sender) smtp.mail=3AwElTQkKBnYXUhcfUnimaiiafY.WigUhilnbaiiafY.Wig@m3kw2wvrgufz5godrsrytgd7.apphosting.bounces.google.com; dkim=pass (test mode) header.i=@google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=beta;
h=domainkey-signature:mime-version:received:reply-to
:x-google-appengine-app-id:message-id:date:subject:from:to:cc
:content-type;
bh=6biGihTsbQoZUpTQ4fWoBVGcIijDm8u3r/RsDcYR1P0=;
b=XyEq+NtuGH7tUATBrSIf4B89mEzf8jzGwJniYIq1NzxKasLl8IxRtmA7+NsSIZ/uJV
xBCi+8yOm7jw2iBoDv/A==
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=google.com; s=beta;
h=mime-version:reply-to:x-google-appengine-app-id:message-id:date
:subject:from:to:cc:content-type;
b=bReZ+V9dl85/IIFDLEpElEHub8hJ7Za3hllhvzNf6GQObFeH4orWr6gW6zyvAmFFBn
7eMTIeLyIzmZ7NV+KEyA==
MIME-Version: 1.0
Reply-To: danilatos@google.com, anorth@google.com,
wave-protocol-code-discuss@googlegroups.com
X-Google-Appengine-App-Id: wave-codereview
Message-ID: <20...@google.com>
Date: Wed, 05 Jan 2011 23:38:43 +0000
Subject: Initial piece of migration logic
From: danilatos@google.com
To: anorth@google.com
Cc: wave-protocol-code-discuss@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
X-System-Of-Record: true
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-3338) Allow any address to post to
wave-commits@incubator.apache.org
Posted by "Alex North (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978055#action_12978055 ]
Alex North commented on INFRA-3338:
-----------------------------------
After a cursory investigation it looks like it will be much easier to switch reviews to review board after switching the repository to Apache SVN than the other way round. Review Board seems to want to know about the repository being talked about, while our existing Reitveld doesn't care.
Thus, allowing any address to post to our -commits (or a -reviews) list still seems like the best first step.
> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
> Key: INFRA-3338
> URL: https://issues.apache.org/jira/browse/INFRA-3338
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Mail (qmail)
> Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code review requests. The first two come from wave-protocol@googlecode.com but the third are sent by our code review tool as ("From") the logged in user, an arbitrary email address. This is approximately what I think we should use the wave-commits@incubator.apache.org for, but when I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org address".
> Please allow any address to post to wave-commits@ for the time being, at least while we're migrating systems to Apache infra. We may be able to tighten things back up again after source, issues, and code review are all moved to Apache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.