Sorry dude, that sucks. I'll try and open the mailing list to other emails
as well. Can you create a Spark ticket in the ASF
INFRA ticket [1] project so we don't forget?

Cheers,
Chris

[1] http://issues.apache.org/jira/browse/INFRA

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Andy Konwinski <[email protected]>
Date: Friday, June 28, 2013 1:38 PM
To: jpluser <[email protected]>
Cc: "[email protected]"
<[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: A wiki for Spark (on Apache infra)

>There is also the frustrating fact that the Apache email spam filter (for
>the dev list) is bouncing emails from my gmail address since it thinks
>I'm sending spam...
>
>
>Sigh.
>
>On Fri, Jun 28, 2013 at 1:35 PM, Mail Delivery Subsystem
><[email protected]> wrote:
>
>Delivery to the following recipient failed permanently:
>
>     [email protected]
>
>Technical details of permanent failure:
>
>Google tried to deliver your message, but it was rejected by the server
>for the recipient domain spark.incubator.apache.org
><http://spark.incubator.apache.org/> by mx1.us.apache.org
><http://mx1.us.apache.org/>.
> [140.211.11.136].
>
>The error that the other server returned was:
>552 spam score (5.0) exceeded threshold
>(HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_BLACK
>
>
>----- Original message -----
>
>DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>        d=gmail.com <http://gmail.com/>; s=20120113;
>        
>h=mime-version:in-reply-to:references:date:message-id:subject:from:to
>         :cc:content-type;
>
>        bh=JNCvkWn5sku7r9R4cADEwztjnt3on6aUgFuiqVQkVpw=;
>        
>b=g91O9eTNyfAHuyKidHN6AeP6hju9ynxflJruSCsRZFXmZ1MvLKw3oQwyTXeOgKwJEA
>         
>VCEK0wsLqln9o6+Kneu5Dq3x0Maro5Vf0S2ZL67NPPfzvL1csSyXYTT6Bfh0f98trAD3
>         
>3v0jTW96qhIyRXJ0gS6rpXNK8NydSqEZfhyzOdmb4seWsJAyFjmuta7qZgrCFTrtUUPF
>         
>xDaXGsQb3OqirZwarUWszvlQjkJNkeWPGLurPESg5XacB7ztjP1dSV/N0ruXINh5ueix
>         
>yq9FLEvA1HFIN9pdDBb40XE6BJNho8UO7E97qwigkJFK11cyxHxwiBLoiYjhThCG3z+l
>         iBIw==
>MIME-Version: 1.0
>X-Received: by 10.112.142.66 with SMTP id ru2mr7448534lbb.7.1372451727361;
> Fri, 28 Jun 2013 13:35:27 -0700 (PDT)
>Received: by 10.112.75.6 with HTTP; Fri, 28 Jun 2013 13:35:27 -0700 (PDT)
>In-Reply-To: <cdf3356d.ebfb7%[email protected]
><mailto:cdf3356d.ebfb7%[email protected]>>
>References: 
><calezfqxh2ffs-lpbmkk-anjvuw-6g-pzqpvj+ppyxe7axp+...@mail.gmail.com
><mailto:CALEZFQxH2ffS-LpbMkk-anJVuW-6G-pZQpvJ%2BPPyXe7aXp%[email protected]
>.com>>
>        <cdf3356d.ebfb7%[email protected]
><mailto:cdf3356d.ebfb7%[email protected]>>
>Date: Fri, 28 Jun 2013 13:35:27 -0700
>Message-ID: 
><CALEZFQwuQA3OhVwOpDp2aqqo1e796Z1ZagOSzSANXVHasmj=p...@mail.gmail.com>
>Subject: Re: A wiki for Spark (on Apache infra)
>
>From: Andy Konwinski <[email protected]>
>To: "Mattmann, Chris A (398J)" <[email protected]>
>Cc: "[email protected]"
><[email protected]>,
>        "[email protected]" <[email protected]>
>Content-Type: multipart/alternative; boundary=001a11c37aaaae4e2104e03cd142
>
>Thanks for responding Chris! Responses inline.
>
>On Fri, Jun 28, 2013 at 12:45 PM, Mattmann, Chris A (398J) <
>[email protected]> wrote:
>
>> Hi Andy,
>>
>> The mailing lists especially need to be at the ASF. Basically this is
>> because the business needs to be conducted here since if it didn't
>>happen
>> on the ML, it didn't happen. Also MLs help to show the health/activity
>> of the community and if it's not here at the ASF it's not an ASF
>>project.
>>
>> There are some precedents e.g., with things like Maven for them to use
>> other JIRAs, etc., but I really don't like the idea there and it caused
>> a lot of ill will etc.
>>
>> Any particular reason you were wondering? Mainly b/c of the overhead or
>> my lack of replies recently? Sorry about that if it was I was underwater
>> in DC working on a DARPA project, but am back in business now and
>> will try and get some of this stuff moving along. Sorry again.
>>
>
>I asked for a couple of reasons actually. One of the reasons, and why I
>asked on this thread which is supposed to be about our wiki, is because
>one
>of our active developers, Evan Chan, asked in this thread if we have to
>move at all, in his words:
>
>>No matter what, is there any way we could keep the google groups for an
>>Apache project?   I think my least favorite feature of most Apache
>>projects is the mailing list.....  really hard to subscribe, post,
>>search, reply, etc.
>
>
>I actually agree that google groups provides a much easier to use
>interface
>for mailing lists than Apache's mailing list software. However, from what
>I
>know about Apache, I think that keeping our lists on non ASF infra is a
>battle we probably won't win (without accruing a lot of ill will, as you
>point out).
>
>I have a few other thoughts on this topic. However, to keep email subject
>and contents aligned, let's continue this conversation on the email thread
>you created with the subject "Mailing list transition (was Re: Apache
>Spark
>podling: Created!)" instead of here :)
>
>Andy
>
>
>> Cheers,
>> Chris
>
>
>
>
>
>
>
>
>
>
>
>
>On Fri, Jun 28, 2013 at 1:35 PM, Andy Konwinski
><[email protected]> wrote:
>
>Thanks for responding Chris! Responses inline.
>
>
>On Fri, Jun 28, 2013 at 12:45 PM, Mattmann, Chris A (398J)
><[email protected]> wrote:
>
>Hi Andy,
>
>The mailing lists especially need to be at the ASF. Basically this is
>because the business needs to be conducted here since if it didn't happen
>on the ML, it didn't happen. Also MLs help to show the health/activity
>of the community and if it's not here at the ASF it's not an ASF project.
>
>There are some precedents e.g., with things like Maven for them to use
>other JIRAs, etc., but I really don't like the idea there and it caused
>a lot of ill will etc.
>
>Any particular reason you were wondering? Mainly b/c of the overhead or
>my lack of replies recently? Sorry about that if it was I was underwater
>in DC working on a DARPA project, but am back in business now and
>will try and get some of this stuff moving along. Sorry again.
>
>
>
>
>
>I asked for a couple of reasons actually. One of the reasons, and why I
>asked on this thread which is supposed to be about our wiki, is because
>one of our active developers, Evan Chan, asked in this thread if we have
>to move at all, in his words:
>
>
>
>
>
>
>
>>No matter what, is there any way we could keep the google groups for an
>
>
>
>
>>Apache project?   I think my least favorite feature of most Apache
>
>
>>projects is the mailing list.....  really hard to subscribe, post,
>
>
>>search, reply, etc.
>
>
>
>
>
>
>
>I actually agree that google groups provides a much easier to use
>interface for mailing lists than Apache's mailing list software. However,
>from what I know about Apache, I think that keeping our lists on non ASF
>infra is a battle we
> probably won't win (without accruing a lot of ill will, as you point
>out).
>
>
>I have a few other thoughts on this topic. However, to keep email subject
>and contents aligned, let's continue this conversation on the email
>thread you created with the subject "Mailing list transition (was Re:
>Apache Spark podling:
> Created!)" instead of here :)
>
>
>Andy
>
>
>
>
>Cheers,
>Chris
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Chris Mattmann, Ph.D.
>Senior Computer Scientist
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 171-266B, Mailstop: 171-246
>Email: [email protected]
>WWW:  http://sunset.usc.edu/~mattmann/
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Adjunct Assistant Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
>-----Original Message-----
>From: Andy Konwinski <[email protected]>
>
>Date: Tuesday, June 25, 2013 10:32 PM
>To: "[email protected]"
><[email protected]>
>Cc: "[email protected]" <[email protected]>,
>jpluser <[email protected]>
>Subject: Re: A wiki for Spark (on Apache infra)
>
>
>>Chris M., is there any precedent for a project not moving mailing lists
>>to Apache infra? Are there rules about it?
>>Andy
>>On Jun 25, 2013 1:31 PM, "Evan Chan" <[email protected]> wrote:
>>
>>I think a wiki that has plugins for diagrams would be pretty kickass and
>>valuable for documentation.  See:
>>http://ffeathers.wordpress.com/2009/07/04/drawing-diagrams-on-a-wiki-page
>>/
>>
>>
>>No matter what, is there any way we could keep the google groups for an
>>Apache project?   I think my least favorite feature of most Apache
>>projects is the mailing list.....  really hard to subscribe, post,
>>search, reply, etc.
>>
>>
>>
>>On Tuesday, June 25, 2013 10:39:52 AM UTC-7, Andy Konwinski wrote:
>>
>>As part of the migration process to Apache, I think we should request a
>>wiki for the Spark project (and after that we should set up and advertise
>>a long overdue PoweredBy page for Spark on that wiki). My personal
>>preference is for a Confluence wiki but
>> I believe we can alternately ask for a MoinMoin wiki.
>>
>>
>>
>>Do others have thoughts about (1) asking for a wiki, (2) which type we
>>request, or (3) anything else related to this?
>>
>>
>>Andy
>>
>>
>>
>>
>>--
>>You received this message because you are subscribed to the Google Groups
>>"Spark Developers" group.
>>To unsubscribe from this group and stop receiving emails from it, send an
>>email to
>>
>>[email protected]
>><mailto:spark-developers%[email protected]>
>
>
>><mailto:spark-developers%[email protected]
>><mailto:spark-developers%[email protected]>>.
>>For more options, visit
>>https://groups.google.com/groups/opt_out
>
>><https://groups.google.com/groups/opt_out>.
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Reply via email to