Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8ADEB200BA6 for ; Tue, 18 Oct 2016 18:59:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 896D4160AE5; Tue, 18 Oct 2016 16:59:50 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A9223160ACE for ; Tue, 18 Oct 2016 18:59:49 +0200 (CEST) Received: (qmail 4543 invoked by uid 500); 18 Oct 2016 16:59:48 -0000 Mailing-List: contact dev-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@spark.apache.org Received: (qmail 4532 invoked by uid 99); 18 Oct 2016 16:59:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2016 16:59:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 9D8CAC2427 for ; Tue, 18 Oct 2016 16:59:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.898 X-Spam-Level: * X-Spam-Status: No, score=1.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LQdmpw-6icR1 for ; Tue, 18 Oct 2016 16:59:45 +0000 (UTC) Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com [209.85.192.182]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 1CC655F39A for ; Tue, 18 Oct 2016 16:59:45 +0000 (UTC) Received: by mail-pf0-f182.google.com with SMTP id 128so97813452pfz.0 for ; Tue, 18 Oct 2016 09:59:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=DdnuvqoPGQx+twXbBMpVn3CWvExNlk83RR7dg3u/5Fs=; b=KZb3bIO0CztJE4mvEqQgj1VhFAhir5uwidHFgqnJp6H5oryCWBGAf/9YaZGd2CNzsE qZQEQyd1zGjm3qI9faI9+0NuAHxMX9vZqBjADMGG8j+43jP/Ya+P9ZtrJCs49OW8y4ib jQCXtrcMQxEqQHWJmNXcmvJc6L0WrnWWIAQjHPrm+K+MAl4sIIo78fMbZGTswUYT523p xWB5OeY9w6QjuEXb25uNgHn63hNE1sQUowUresP91Rh3ZjVTjEQBDJ+c/n4Ih+nb6yTh SMlRmapimcfNUzY5v+tAQbCzZ55RAgc7rXDj9WmgXNHziICpt+n8rTRChHON6dVKU69h 7/ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=DdnuvqoPGQx+twXbBMpVn3CWvExNlk83RR7dg3u/5Fs=; b=iBBjh3yxWqikM5Uc97OI0qPfF9sSWd3lhsTbHSDNxoFkLLzyOdodDBKAHavhVooKZt ah+olvsDG7GE5IrChPe2SmLHYbsHMLt8k1TuEiGj4vBvd7e7p++K0xz9dkjV+dnRivPw vTGIO78FrBO4xOCmJX0yhn/cnaKjZTnbwGPOAIg0w3Tt82brz1ncFExaA14lFoHliyty oFyYcfV71abSCxPCoaHAxiUeOCY8RgrC07gq2b5PMvnuBIx0YD7vCBK0zEmCCt42wwz4 /2igYQuMDJXljE5a4AsR9k4pk4R2QBSiIAJXTpQItq0yI6eVb0vs6n/om+RAbHi9mog8 H1jQ== X-Gm-Message-State: AA6/9RmQbaZlaCiZC0TSpzhsqNcrBbg095POyrnrnjIjp+fL0uEDKBmay1EOHu0ekypX0Q== X-Received: by 10.99.157.75 with SMTP id i72mr1797772pgd.147.1476809981113; Tue, 18 Oct 2016 09:59:41 -0700 (PDT) Received: from [192.168.1.105] (DN12439jv.stanford.edu. [68.65.166.127]) by smtp.gmail.com with ESMTPSA id xs10sm57478502pac.24.2016.10.18.09.59.40 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 18 Oct 2016 09:59:40 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_7AA79EED-9BB6-4EB2-A6C1-A4425EFDF279" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Mini-Proposal: Make it easier to contribute to the contributing to Spark Guide From: Matei Zaharia In-Reply-To: Date: Tue, 18 Oct 2016 09:59:40 -0700 Cc: Sean Owen , dev@spark.apache.org, Holden Karau Message-Id: References: To: Cody Koeninger X-Mailer: Apple Mail (2.3124) archived-at: Tue, 18 Oct 2016 16:59:50 -0000 --Apple-Mail=_7AA79EED-9BB6-4EB2-A6C1-A4425EFDF279 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Is there any way to tie wiki accounts with JIRA accounts? I found it = weird that they're not tied at the ASF. Otherwise, moving this into the docs might make sense. Matei > On Oct 18, 2016, at 6:19 AM, Cody Koeninger = wrote: >=20 > +1 to putting docs in one clear place. >=20 > On Oct 18, 2016 6:40 AM, "Sean Owen" > wrote: > I'm OK with that. The upside to the wiki is that it can be edited = directly outside of a release cycle. However, in practice I find that = the wiki is rarely changed. To me it also serves as a place for = information that isn't exactly project documentation like "powered by" = listings. >=20 > In a way I'd like to get rid of the wiki to have one less place for = docs, that doesn't have the same accessibility (I don't know who can = give edit access), and doesn't have a review process. >=20 > For now I'd settle for bringing over a few key docs like the one you = mention. I spent a little time a while ago removing some duplication = across the wiki and project docs and think there's a bit more than could = be done. >=20 >=20 > On Tue, Oct 18, 2016 at 12:25 PM Holden Karau > wrote: > Right now the wiki isn't particularly accessible to updates by = external contributors. We've already got a contributing to spark page = which just links to the wiki - how about if we just move the wiki = contents over? This way contributors can contribute to our documentation = about how to contribute probably helping clear up points of confusion = for new contributors which the rest of us may be blind to. >=20 > If we do this we would probably want to update the wiki page to point = to the documentation generated from markdown. It would also mean that = the results of any update to the contributing guide take a full release = cycle to be visible. Another alternative would be opening up the wiki to = a broader set of people. >=20 > I know a lot of people are probably getting ready for Spark Summit EU = (and I hope to catch up with some of y'all there) but I figured this a = relatively minor proposal. > --=20 > Cell : 425-233-8271 > Twitter: https://twitter.com/holdenkarau = --Apple-Mail=_7AA79EED-9BB6-4EB2-A6C1-A4425EFDF279 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Is there any way to tie wiki accounts with = JIRA accounts? I found it weird that they're not tied at the = ASF.

Otherwise, = moving this into the docs might make sense.

Matei

On = Oct 18, 2016, at 6:19 AM, Cody Koeninger <cody@koeninger.org> = wrote:

+1 to putting docs in one clear place.


On = Oct 18, 2016 6:40 AM, "Sean Owen" <sowen@cloudera.com> = wrote:
I'm OK with that. = The upside to the wiki is that it can be edited directly outside of a = release cycle. However, in practice I find that the wiki is rarely = changed. To me it also serves as a place for information that isn't = exactly project documentation like "powered by" listings.

In a way I'd like to get = rid of the wiki to have one less place for docs, that doesn't have the = same accessibility (I don't know who can give edit access), and doesn't = have a review process.

For now I'd settle for bringing over a few key docs like the = one you mention. I spent a little time a while ago removing some = duplication across the wiki and project docs and think there's a bit = more than could be done.


On Tue, Oct 18, 2016 at 12:25 PM Holden Karau = <holden@pigscanfly.ca> wrote:
Right now the wiki isn't = particularly accessible to updates by external contributors. We've = already got a contributing to spark page which just links to the wiki - = how about if we just move the wiki contents over? This way contributors = can contribute to our documentation about how to contribute probably = helping clear up points of confusion for new contributors which the rest = of us may be blind to.

If we do this we would = probably want to update the wiki page to point to the documentation = generated from markdown. It would also mean that the results of any = update to the contributing guide take a full release cycle to be = visible. Another alternative would be opening up the wiki to a broader = set of people.

I know a lot of people are = probably getting ready for Spark Summit EU (and I hope to catch up with = some of y'all there) but I figured this a relatively minor = proposal.
--
Cell : 425-233-8271
Twitter: https://twitter.com/holdenkarau

= --Apple-Mail=_7AA79EED-9BB6-4EB2-A6C1-A4425EFDF279--