From user-return-1416-archive-asf-public=cust-asf.ponee.io@kudu.apache.org Tue Jul 17 20:40:08 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id C61DF180600 for ; Tue, 17 Jul 2018 20:40:07 +0200 (CEST) Received: (qmail 27384 invoked by uid 500); 17 Jul 2018 18:40:06 -0000 Mailing-List: contact user-help@kudu.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@kudu.apache.org Delivered-To: mailing list user@kudu.apache.org Received: (qmail 27362 invoked by uid 99); 17 Jul 2018 18:40:06 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2018 18:40:06 +0000 Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 5E21E1EF8; Tue, 17 Jul 2018 18:40:05 +0000 (UTC) Received: by mail-lj1-f178.google.com with SMTP id p10-v6so1860105ljg.2; Tue, 17 Jul 2018 11:40:04 -0700 (PDT) X-Gm-Message-State: AOUpUlHIhjYgbJlS42NeBzC4mlle7fkfv3Gn5MMRhiqj8QLO2eSIOF9b XzkpBIhr+pFgZt5qUH2iWvLNfUyZzxO3erFSjKw= X-Google-Smtp-Source: AAOMgpdGiuBD7i150FRLBLq/oL/RKDQU2p+w0g47iLg5HUjPivlX+e7VhznvHfd/yiIgTih+i3Cb57vFDsK+8c0GVE4= X-Received: by 2002:a2e:80d3:: with SMTP id r19-v6mr2175284ljg.85.1531852803781; Tue, 17 Jul 2018 11:40:03 -0700 (PDT) MIME-Version: 1.0 From: Mike Percy Date: Tue, 17 Jul 2018 11:39:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Growing the Kudu community To: dev , user@kudu.apache.org Content-Type: multipart/alternative; boundary="00000000000037b95705713646f7" --00000000000037b95705713646f7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Apache Kudu community, Apologies for cross-posting, we just wanted to reach a broad audience for this topic. Grant and I have been brainstorming about what we can do to grow the community of Kudu developers and users. We think Kudu has a lot going for it, but not everybody knows what it is and what it=E2=80=99s capable of. Fo= cusing and combining our collective efforts to increase awareness (marketing) and to reduce barriers to contribution and adoption could be a good way to achieve organic growth. We=E2=80=99d like to hear your ideas about what barriers and pain points ex= ist and any ideas you may have to fix some of those things -- especially ideas requiring minimal effort and maximum impact. To kick this off, here are some ideas Grant and I have come up with so far, in sort of a rough priority order: Ideas for general improvements 1. Java MiniCluster support out of the box (KUDU-2411) 1. This will enable integration with other projects in a way that allows them to test against a running Kudu cluster and ensure quality withou= t having to build it themselves. 2. Create a dedicated Maven-consumable java module for a Kudu MiniCluster 3. Pre-built binary artifacts (for testing use only) downloadable with MiniCluster (Linux / MacOS) 4. Ship all dependencies (even security deps, which will not be fixed if CVEs found) 5. Make the binaries Linux distro-independent by building on an old distro (EL6) 2. Upgrade Gerrit to fix the =E2=80=9CNew UI=E2=80=9D GitHub Login Bug (= KUDU-2402) 1. Remove barrier to submitting a patch 2. Latest version of Gerrit has a fix for the bad GitHub login redirect 3. Upstream pre-built packages for production use (Start rhel7, maybe ubuntu) 1. This is potentially a pretty large effort, depending in the number of platforms we want to support 2. Tarballs -- per-OS / per-distro 3. Yum install, apt get: per-OS / per-distro 4. Homebrew? 4. CLI based tools with zero dependencies for quick experiments/demos 1. Create, describe, alter tables 2. Cat data out, pipe data in. 3. Or simple Python examples to do similar 5. Create developer oriented docs and faqs (wiki style?) 6. CONTRIBUTING.adoc in repo 1. Simplified 2. Quick =E2=80=9Cassume nothing tutorial=E2=80=9D 3. Video Guide? Ongoing marketing and engagement 1. Quarterly email to the dev / users list 1. Recognize new contributors 2. Call out beginner jiras 3. Summarize ongoing projects 2. Consistently use the beginner / newbie tag in JIRA 1. Doc how to find beginner jiras in the contributing docs 3. Regular blog posts 1. Developer and community contributors 2. Invite people from other projects that integrate w/ Kudu to post on our Blog 3. Document how to contribute a blog post 4. Topics: Compile and maintain a list of blog post ideas in case people want inspiration -- Grant has been gathering ideas for this 4. Archive Slack to a mailing list to be indexed by search engines (SlackArchive.io has shut down) Please offer your suggestions for where we can get a good bang for our collective buck, and if there is anything you would like to work on by all means please either speak up or feel free to reach out directly. Thanks, Grant and Mike --00000000000037b95705713646f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi = Apache Kudu community,

Ap= ologies for cross-posting, we just wanted to reach a broad audience for thi= s topic.

Grant and I have= been brainstorming about what we can do to grow the community of Kudu deve= lopers and users. We think Kudu has a lot going for it, but not everybody k= nows what it is=C2=A0and what it=E2=80=99s capable of. Focusing and combini= ng our collective efforts to increase awareness (marketing) and to reduce b= arriers to contribution and adoption could=C2=A0be a good way to achieve or= ganic growth.
<= br>
We=E2=80=99= d like to hear your ideas about what barriers and pain points exist and any= ideas you may have to fix some of those things -- especially ideas requiri= ng minimal effort and maximum impact.

To kick this off, here are some ideas Grant and I have come up= with so far, in sort of a rough priority order:

Ideas for general improvements
  1. = Java MiniCluster support out of the box (KUDU-2411)
    1. This will enable integration with other projects in a= way that allows them to test against a running Kudu cluster and ensure qua= lity without having to build it themselves.
    2. Create a dedicated Maven-consumable java module for a Kudu MiniCluster<= /li>
    3. Pre-built binary artifacts (for testing = use only) downloadable with MiniCluster (Linux / MacOS)
    4. Ship all dependencies (even security deps, which will not b= e fixed if CVEs found)
    5. Make the binaries= Linux distro-independent by building on an old distro (EL6)
  2. Upgrade Gerrit to fix the =E2=80=9CNew UI=E2=80= =9D GitHub Login Bug (KUDU-2402)
    1. Rem= ove barrier to submitting a patch
    2. Latest= version of Gerrit has a fix for the bad GitHub login redirect
    Upstream pre-built packages for production use = (Start rhel7, maybe ubuntu)
    1. This= is potentially a pretty large effort, depending in the number of platforms= we want to support
    2. Tarballs -- per-OS /= per-distro
    3. Yum install, apt get: per-OS= / per-distro
    4. Homebrew?
  3. CLI based tools with zero dependencies for quick ex= periments/demos
    1. Create, describe= , alter tables
    2. Cat data out, pipe data i= n.
    3. Or simple Python examples to do simil= ar
  4. Create developer oriented docs a= nd faqs (wiki style?)
  5. CONTRIBUTING.a= doc in repo
    1. Simplified
    2. Quick =E2=80=9Cassume nothing tutorial=E2=80=9D
    3. Video Guide?
Ongoing marketing and engage= ment
  1. Quarterly email to the dev / users list
  2. Recognize new contributors
  3. Call out beginner jiras
  4. Summarize ongoing projects
  • Co= nsistently use the beginner / newbie tag in JIRA
    1. Doc how to find beginner jiras in the contributing docs
  • Regular blog posts
    1. Developer and community contributors
    2. Invite people from other projects that integrate w/ K= udu to post on our Blog
    3. Document how to = contribute a blog post
    4. Topics: Compile a= nd maintain a list of blog post ideas in case people want inspiration -- Gr= ant has been gathering ideas for this
  • Archive Slack to a mailing list to be indexed by search engines (SlackAr= chive.io has shut down)
    • Please offer your suggestions for where we can get a= good bang for our collective buck, and if there is anything you would like= to work on by all means please either speak up or feel free to reach out d= irectly.
    Thanks,

    Grant and Mike

    --00000000000037b95705713646f7--