spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hamstra <m...@clearstorydata.com>
Subject Re: Keeping users mailing list with Google groups
Date Tue, 20 Aug 2013 19:52:46 GMT
Is Google groups email formatting completely compatible with Apache lists?



On Tue, Aug 20, 2013 at 11:43 AM, Henry Saputra <henry.saputra@gmail.com>wrote:

> We'll let the other mentors chime in and give their thoughts.
> I have been looking at the Apache policy about public listing [1] and could
> not find anything about cross posting.
>
> Yeah, like Andy proposed before I am thinking about just subscribing the
> user@spark.i.a.o to Google groups and allow Google groups email to send
> email to the mailing list.
> Not sure what permission Chris set when creating the list but I did allow
> the JIRA emails to sent to other Apache list without actually subscribe to
> it.
>
> - Henry
>
>
>
> [1] http://www.apache.org/foundation/public-archives.html
>
>
> On Tue, Aug 20, 2013 at 11:37 AM, Matei Zaharia <matei.zaharia@gmail.com
> >wrote:
>
> > Hi Henry,
> >
> > I'd be happy to do this as long as Apache is okay with it! It will save a
> > lot of hassle for our users. Does it basically just require subscribing
> > user@spark.i.a.o to the Google Group?
> >
> > Matei
> >
> > On Aug 20, 2013, at 11:34 AM, Henry Saputra <henry.saputra@gmail.com>
> > wrote:
> >
> > > Hi Guys,
> > >
> > > I am thinking about keeping the users list with Google groups and
> mirror
> > > the messages to user@spark.i.a.o.
> > >
> > > This way users can communicate via Google groups forum style rather
> than
> > > Apache mailing list,
> > >
> > > Most developers contributing to Spark have to use Apache way to
> > communicate
> > > but as for users, we could always let them communicate via Google
> groups
> > > but mirror the emails (or subscribe user@spark.i.a.o as member of
> Spark
> > > users Google group).
> > >
> > > Thoughts?
> > >
> > > - Henry
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message