From user-return-1419-archive-asf-public=cust-asf.ponee.io@kudu.apache.org Tue Jul 17 21:18:57 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 56EC6180600 for ; Tue, 17 Jul 2018 21:18:56 +0200 (CEST) Received: (qmail 28035 invoked by uid 500); 17 Jul 2018 19:18:55 -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 28025 invoked by uid 99); 17 Jul 2018 19:18:54 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2018 19:18:54 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4FB7318043D for ; Tue, 17 Jul 2018 19:18:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.998 X-Spam-Level: * X-Spam-Status: No, score=1.998 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, T_REMOTE_IMAGE=0.01] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=impact-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id usmGGlYxA0E2 for ; Tue, 17 Jul 2018 19:18:52 +0000 (UTC) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 90F425F175 for ; Tue, 17 Jul 2018 19:18:51 +0000 (UTC) Received: by mail-wr1-f49.google.com with SMTP id j5-v6so2287513wrr.8 for ; Tue, 17 Jul 2018 12:18:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=impact-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qr8WKiGR+VurZQ5lqaoh9UaDahOL7ReoLXsyjWu2nXM=; b=MgogjoMGnCmmZsK2Mc86lzaf4V2eLVIpkCkOawXSxG4rhV9W3hYKGPBuBf4gvPsWP8 +9ziokPgBMfIfo5okKpvAx+QcCAhN1CQ05SP45ghRcInhF24MFPoXx2d0KNqcjT/QRUV 2YRySacKfhmrioLXaZALCRf2kC556VXamkzhNh+kS1ohC6VaF2fO7hWCmhzjWcSMBTyr 6HRsMOjmSXQ239lhuxYKlllA8JO+4CJqieYIkRHwJREj2ThjvtCYXSxEQ5iJDCReQFU1 VAWVX5iJGbS6yFIHMbIAdsevx5rrWcyTwvjmjiDkw3KAe5zU6ORdwLdgmVG0LXTPB1gA inNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Qr8WKiGR+VurZQ5lqaoh9UaDahOL7ReoLXsyjWu2nXM=; b=ZtRTtcAGxXLLyHRWLWOPUy9qStDgcCHYbmYKOWJSyh6oKuyvvE48PDdHi1xDWRo1ZF 3xPRg1L7kUfobs8RSH/cwjD1BRp2f3fLBKe8TZQgoDhS7cOKhO1ziPKQPQloVhKyeo5/ 8xhq0TmFXOp0E3bLkP7imoPuVbbyA7TU6BsVf4q14RuDJiwZuE+Rc/uMpEsDTHeYO45v 6q86TE9AZBGCuxh0Pu4rohOFBkRzACc5B54Yr4Fw8v7/eZLCYhyenCyWL5ULQLSJQxH9 rjnn3BFQl55izsope1LjpSMoeY84UHGDtg41VzqD80ysne/AO5GAXGXtYlSOSqzq+ktF T3VQ== X-Gm-Message-State: AOUpUlGKY9+AB29veI54SuYW1wni0fb75XqgjdIirpIVnjqGg1nRGOb+ o4+1ekAvYXp1ERNFZfYSOUg6YR+AVrrD2g0n+KU4ZeWv X-Google-Smtp-Source: AAOMgpdbcwTQPneL0RMJBj/0RRLSL/XUlapkCaNRytOpe9Kcjp3JDYddNdp2omGRbrJIZIL5y8nOl4zM/bTuvYpYXFE= X-Received: by 2002:adf:f28c:: with SMTP id k12-v6mr2114770wro.263.1531855130179; Tue, 17 Jul 2018 12:18:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mauricio Aristizabal Date: Tue, 17 Jul 2018 12:18:39 -0700 Message-ID: Subject: Re: Growing the Kudu community To: user@kudu.apache.org Cc: dev@kudu.apache.org Content-Type: multipart/alternative; boundary="000000000000e1c8c7057136d0ec" --000000000000e1c8c7057136d0ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks very much Grant! I will start participating in #kudu-backup On Tue, Jul 17, 2018 at 12:15 PM Grant Henke wrote: > Thank you for the quick feedback Tim and Maurice. > > Tim, I have some rough work on the Java/Maven/Gradle related parts to the > MiniCluster that I have been experimenting with locally. It would be grea= t > to coordinate and collaborate with you on those contributions. > > Mauricio, we have been doing a lot of work on Kudu's backup features as a > top priority. The formal design communication exists on the dev mailing > list here, but also a lot of conversation is happening in the Slack > #kudu-backup channel. Your feedback on the design docs would be great! Du= ly > noted on the conference feedback. > > On Tue, Jul 17, 2018 at 2:04 PM Mauricio Aristizabal > wrote: > >> My new-user thoughts: MiniCluster is nice but right now we get by >> launching a docker instance in tests, it's pretty fast. What's really >> hurting adoption at our org is lack of a proper backup/snapshot/replicat= ion >> feature. As for marketing, i think conferences are crucial, so I was >> disappointed that Strata SJ 2018 didn't have a single session on Kudu, >> there were no committers in attendance that I could tell, and it wasn't >> being highlighted at all in the Cloudera booth. Between Strata and >> ScalaDays I must have enthusiastically mentioned the product to 15 peopl= e >> and none had heard of it. -m >> >> On Tue, Jul 17, 2018 at 11:40 AM Mike Percy wrote: >> >>> 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 f= or >>> it, but not everybody knows what it is and what it=E2=80=99s capable of= . Focusing >>> 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 point= s exist >>> and any ideas you may have to fix some of those things -- especially id= eas >>> 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 qua= lity >>> without 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 B= ug (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/demo= s >>> 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 thi= s >>> 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 >>> >>> >> >> -- >> Mauricio Aristizabal >> Architect - Data Pipeline >> mauricio@impact.com | 323 309 4260 >> https://impact.com >> >> >> >> > > > -- > Grant Henke > Software Engineer | Cloudera > grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke > --=20 Mauricio Aristizabal Architect - Data Pipeline mauricio@impact.com | 323 309 4260 https://impact.com --000000000000e1c8c7057136d0ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks very much Grant! I will start participating in #kud= u-backup

On Tue, Jul 1= 7, 2018 at 12:15 PM Grant Henke <= ghenke@cloudera.com> wrote:
=
Thank you for the quick feedback Tim and Maurice.=C2=A0
Tim, I have some rough work on the Java/Maven/Gradle relat= ed parts to the MiniCluster that I have been experimenting with locally. It= would be great to coordinate and collaborate with you on those contributio= ns.=C2=A0

Mauricio, we have been doing a lot = of work on Kudu's backup features as a top priority. The formal design = communication exists on the dev mailing list here, but also a lot of conver= sation is happening in the Slack #kudu-backup channel. Your feedback on the= design docs would be great! Duly noted on the conference feedback.

On Tue, Jul 17, 2= 018 at 2:04 PM Mauricio Aristizabal <mauricio@impact.com> wrote:
My new-user thoughts: MiniCluster is= nice but right now we get by launching a docker instance in tests, it'= s pretty fast.=C2=A0 What's really hurting adoption at our org is lack = of a proper backup/snapshot/replication feature.=C2=A0 As for marketing, i = think conferences are crucial, so I was disappointed that Strata SJ 2018 di= dn't have a single session on Kudu, there were no committers in attenda= nce that I could tell, and it wasn't being highlighted at all in the Cl= oudera booth.=C2=A0 Between Strata and ScalaDays I must have enthusiastical= ly mentioned the product to 15 people and none had heard of it. -m
On Tue, Jul 17, 2018 at 11:40 = AM Mike Percy <mp= ercy@apache.org> wrote:
Hi Apac= he Kudu community,

Apolog= ies for cross-posting, we just wanted to reach a broad audience for this to= pic.

=
Grant and I have bee= n brainstorming about what we can do to grow the community of Kudu develope= rs and users. We think Kudu has a lot going for it, but not everybody knows= what it is=C2=A0and what it=E2=80=99s capable of. Focusing and combining o= ur collective efforts to increase awareness (marketing) and to reduce barri= ers to contribution and adoption could=C2=A0be a good way to achieve organi= c growth.

<= /div>
We=E2=80=99d li= ke to hear your ideas about what barriers and pain points exist and any ide= as you may have to fix some of those things -- especially ideas requiring m= inimal effort and maximum impact.

To kick this off, here are some ideas Grant and I have come up wit= h 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 t= hat allows them to test against a running Kudu cluster and ensure quality w= ithout having to build it themselves.
    2. Cr= eate a dedicated Maven-consumable java module for a Kudu MiniCluster
      3. Pre-built binary artifacts (for testing use on= ly) downloadable with MiniCluster (Linux / MacOS)
    3. Ship all dependencies (even security deps, which will not be fixe= d if CVEs found)
    4. 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 Gi= tHub Login Bug (KUDU-2402)
    1. Remove ba= rrier to submitting a patch
    2. Latest versi= on 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 po= tentially a pretty large effort, depending in the number of platforms we wa= nt to support
    2. Tarballs -- per-OS / per-d= istro
    3. Yum install, apt get: per-OS / per= -distro
    4. Homebrew?
  4. CLI based tools with zero dependencies for quick experime= nts/demos
    1. Create, describe, alte= r tables
    2. Cat data out, pipe data in.
    3. Or simple Python examples to do similar
  5. Create developer oriented docs and faq= s (wiki style?)
  6. CONTRIBUTING.adoc in= repo
    1. Simplified
    2. Quick =E2=80=9Cassume nothing tutorial=E2=80=9D
      3. <= li style=3D"margin-left:15px">Video Guide?
Ongoing marketing and engageme= nt
  1. Quarterly email to the dev / users list
      2. =
    1. Recognize new contributors
    2. Call out beginner jiras
    3. Summarize ongoing projects
  2. Consis= tently use the beginner / newbie tag in JIRA
    1. Doc how to find beginner jiras in the contributing docs
    2. 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 con= tribute 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
    3. = Archive Slack to a mailing list to be indexed by search engines (SlackArchi= ve.io has shut down)
Please offer your suggestions for where we can get a go= od 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 dire= ctly.

<= /div>
Thanks,

Grant and Mike



--
=
=
Mauricio Ar= istizabal
Architect - Data Pipeline
=C2=A0=C2=A0=C2=A0=C2=A0

=C2=A0


--
=
Grant Henke=C2=A0
Software Engineer | Cloudera
<= a href=3D"mailto:grant@cloudera.com" target=3D"_blank">grant@cloudera.com |=C2=A0twitter.com/gchenke | linkedin.com/in/granthenke


--
=
Mauricio Ar= istizabal
Architect - Data Pipeline
=C2=A0=C2=A0=C2=A0=C2=A0

=C2=A0
--000000000000e1c8c7057136d0ec--