spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matei Zaharia <>
Subject Re: Discussion on strategy or roadmap should happen on dev@ list
Date Fri, 07 Feb 2014 02:27:56 GMT
Henry (or anyone else), do you have any preference on sending these directly to “dev" versus
creating another list for “issues”? I guess we can try “dev” for a while and let people
decide if it gets too spammy. We’ll just have to advertise it in advance.


On Feb 6, 2014, at 9:55 AM, Henry Saputra <> wrote:

> HI Matei, yeah please subscribe it for now. Once we have ASF JIRA
> setup for Spark it will happen automatically.
> - Henry
> On Wed, Feb 5, 2014 at 2:56 PM, Matei Zaharia <> wrote:
>> Hey Henry, this makes sense. I’d like to add that one other vehicle for discussion
has been JIRA at Right now the dev list
is not subscribed to JIRA, but we’d be happy to subscribe it anytime if that helps. We were
hoping to do this only when JIRA has been moved to the ASF, since infra can set up the forwarding
automatically. But most major discussions (e.g., happen there. I think this is the model
we want to have in the future — most other projects I’ve participated in also used JIRA
for their discussion, and mirrored to either the “dev” list or an “issues” list.
>> Matei
>> On Feb 5, 2014, at 2:49 PM, Henry Saputra <> wrote:
>>> Hi Guys,
>>> Just friendly reminder, some of you guys may work closely or
>>> collaborate outside the dev@ list and sometimes it is easier.
>>> But, as part of Apache Software Foundation project, any decision or
>>> outcome that could or will be implemented in the Apache Spark need to
>>> happen in the dev@ list as we are open and collaborative as community.
>>> If offline discussions happen please forward the history or potential
>>> solution to the dev@ list before any action taken.
>>> Most of us work remote so email is the official channel of discussion
>>> about stuff related to development in Spark.
>>> Github pull request is not the appropriate vehicle for technical
>>> discussions. It is used primarily for review of proposed patch which
>>> means initial problem most of the times had been identified and
>>> discussed.
>>> Thanks for understanding.
>>> - Henry

View raw message