Looks good to me. Thanks for helping find a common ground everyone, and
Sean for handling the implementation.
On Mon, Jul 20, 2015 at 2:22 AM, Sean Owen wrote:
> This is done, and yes I believe that resolves the issue as far all here
> know.
>
> http://spark.apache.org/downloads.html
> ->
>
> ht
Thanks, Sean.
On Mon, Jul 20, 2015 at 12:22 AM, Sean Owen wrote:
> This is done, and yes I believe that resolves the issue as far all here
> know.
>
> http://spark.apache.org/downloads.html
> ->
>
> https://cwiki.apache.org/confluence/display/SPARK/Useful+Developer+Tools#UsefulDeveloperTools-Ni
This is done, and yes I believe that resolves the issue as far all here know.
http://spark.apache.org/downloads.html
->
https://cwiki.apache.org/confluence/display/SPARK/Useful+Developer+Tools#UsefulDeveloperTools-NightlyBuilds
On Sun, Jul 19, 2015 at 5:26 PM, Patrick Wendell wrote:
> Hey Sean,
Sean B.,
Thank you for giving a thorough reply. I will work with Sean O. and
see what we can change to make us more in line with the stated policy.
I did some research and it appears that some time between October [1]
and December [2] 2006, this page was modified to include stricter
policy surrou
Hey Sean,
One other thing I'd be okay doing is moving the main text about
nightly builds to the wiki and just have header called "Nightly
builds" at the end of the downloads page that says "For developers,
Spark maintains nightly builds. More information is available on the
[Spark developer Wiki](
I am going to make an edit to the download page on the web site to
start, as that much seems uncontroversial. Proposed change:
Reorder sections to put developer-oriented sections at the bottom,
including the info on nightly builds:
Download Spark
Link with Spark
All Releases
Spark Source C
To move this forward, I think one of two things needs to happen:
1. Move this guidance to the wiki. Seems that people gathered here
believe that resolves the issue. Done.
2. Put disclaimers on the current downloads page. This may resolve the
issue, but then we bring it up on the right mailing lis
Point well taken. Allow me to walk back a little and move us in a more
productive direction.
I can personally empathize with the desire to have nightly builds. I'm a
passionate advocate for tight feedback cycles between a project and its
downstream users. I am personally involved in several projec
>
> Please keep in mind that you are also "ASF people," as is the entire Spark
> community (users and all)[4]. Phrasing things in terms of "us and them" by
> drawing a distinction on "[they] get in a fight on our mailing list" is not
> helpful.
But they started it!
A bit more seriously, my perspe
Responses inline, with some liberties on ordering.
On Sun, Jul 12, 2015 at 10:32 PM, Patrick Wendell
wrote:
> Hey Sean B,
>
> Would you mind outlining for me how we go about changing this policy -
> I think it's outdated and doesn't make much sense. Ideally I'd like to
> propose a vote to modify
Hey Sean B,
Would you mind outlining for me how we go about changing this policy -
I think it's outdated and doesn't make much sense. Ideally I'd like to
propose a vote to modify the text slightly such that our current
behavior is seen as complaint. Specifically:
- What concrete steps can I take
Please note that when the policy refers to "developers" it means the
developers of the project at hand, that is participants on the dev@spark
mailing list.
As I stated in my original email, you're welcome to continue the discussion
on the policy including the definition of developers on general@in
Thanks Sean O. I was thinking something like "NOTE: Nightly builds are
meant for development and testing purposes. They do not go through
Apache's release auditing process and are not official releases."
- Patrick
On Sun, Jul 12, 2015 at 3:39 PM, Sean Owen wrote:
> (This sounds pretty good to me
(This sounds pretty good to me. Mark it developers-only, not formally
tested by the community, etc.)
On Sun, Jul 12, 2015 at 7:50 PM, Patrick Wendell wrote:
> Hey Sean B.,
>
> Thanks for bringing this to our attention. I think putting them on the
> developer wiki would substantially decrease visi
Hey Sean B.,
Thanks for bringing this to our attention. I think putting them on the
developer wiki would substantially decrease visibility in a way that
is not beneficial to the project - this feature was specifically
requested by developers from other projects that integrate with Spark.
If the c
>From a developer perspective, I also find it surprising to hear that
nightly builds should be hidden from non-developer end users. In an
age of Github, what on earth is the problem with distributing the
content of master? However I do understand why this exists.
To the extent the ASF provides any
I don't get this rule. It is arbitrary, and does not seem like something
that should be enforced at the foundation level. By this reasoning, are we
not allowed to list "source code management" on the project public page as
well?
The download page clearly states the nightly builds are "bleeding-edg
That would be great.
A note on that page that it's meant for the use of folks working on the
project with a link to your "get involved" howto would be nice additional
context.
--
Sean
On Jul 11, 2015 6:18 AM, "Sean Owen" wrote:
> I suggest we move this info to the developer wiki, to keep it ou
I suggest we move this info to the developer wiki, to keep it out from
the place all and users look for downloads. What do you think about
that Sean B?
On Sat, Jul 11, 2015 at 5:34 AM, Sean Busbey wrote:
> Hi Folks!
>
> I noticed that Spark website's download page lists nightly builds and
> instr
19 matches
Mail list logo
