As part of Spark's recent move to Apache, we are planning to migrate the mailing lists to Apache infrastructure this month, so that the current Google groups will become read-only on September 1, 2013. To keep receiving updates about Spark or to participate in development discussions, please subscribe to the following lists:
Get help using Spark or contribute to the project on our mailing lists:
Most users will probably want the User list, but individuals interested in contributing code to the project should also subscribe to the Dev list.
After September 1st, we'll try to make the Google Groups mirror the Apache list so you can still read updates on them, but it's not yet clear whether this will be possible. Sorry for the inconvenience and thanks for bearing with us.
Matei
This is a BIG downgrade.--
You received this message because you are subscribed to the Google Groups "Spark Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spark-users...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Can you elaborate?
--
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 spark-develope...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Spark Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spark-users...@googlegroups.com.
I notice that there are still a lot of active topics in this group: and also activity on the apache mailing list (which is a really horrible experience!). Is it a firm policy on apache's front to disallow external groups? I'm going to be ramping up on spark, and I really hate the idea of having to rely on the apache archives and my mail client. Also: having to search for topics/keywords both in old threads (here) as well as new threads in apache's (clunky) archive, is going to be a pain! I almost feel like I must be missing something because the current solution seems unfeasibly awkward!
I'd be fine with one-way mirrors here (Apache threads being reflected in Google groups) -- I have no idea how one is supposed to navigate the Apache list to look for historic threads.
That would be really awesome. I'm not familiar with any Google Groups functionality that supports that but I'll look.
That's an argument for maybe just changing the names of the existing groups to something with mirror in them instead of using newly created ones.
This is great! Could the new *-mirror groups start off with a complete copy of the (closed) original groups and the apache lists? (So as to avoid having to search 3 different sources for historical information.)
--