From dev-return-17308-archive-asf-public=cust-asf.ponee.io@beam.apache.org Thu Jun 6 17:33:04 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 24421180787 for ; Thu, 6 Jun 2019 19:33:04 +0200 (CEST) Received: (qmail 92455 invoked by uid 500); 6 Jun 2019 17:33:03 -0000 Mailing-List: contact dev-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list dev@beam.apache.org Received: (qmail 92415 invoked by uid 99); 6 Jun 2019 17:33:02 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jun 2019 17:33:02 +0000 Received: from mail-pg1-f175.google.com (mail-pg1-f175.google.com [209.85.215.175]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 97BA88AA7 for ; Thu, 6 Jun 2019 17:33:02 +0000 (UTC) Received: by mail-pg1-f175.google.com with SMTP id n2so1728368pgp.11 for ; Thu, 06 Jun 2019 10:33:02 -0700 (PDT) X-Gm-Message-State: APjAAAXRgnrGtURzl4EVG7KTrDA9dgd0A3VbRbKDRfy2NgvvZKqzfJrB gClh+3rnw6i2dDAkW1eR0CM8kophXW0psRwCHOXkzQ== X-Google-Smtp-Source: APXvYqwl14JMxKDqWy9GLAZTwHWBi3IByCSs/496Wt3jfg/E3EfRdtQS+fa3NJ+BAKA0N7US1QDIgblSDIe3VaHJwlc= X-Received: by 2002:a17:90a:ba81:: with SMTP id t1mr927971pjr.139.1559842381516; Thu, 06 Jun 2019 10:33:01 -0700 (PDT) MIME-Version: 1.0 References: <8c36c2e3-ee65-cab5-3042-5672a303796d@apache.org> In-Reply-To: From: Aizhamal Nurmamat kyzy Date: Thu, 6 Jun 2019 10:32:25 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [Discuss] Ideas for Apache Beam presence in social media To: dev@beam.apache.org Content-Type: multipart/alternative; boundary="0000000000000ec49a058aab1bb0" --0000000000000ec49a058aab1bb0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable With the spreadsheet in http://s.apache.org/beam-tweets, anyone can propose tweets. I will check it every few days, and ping/tag PMC members to review tweets and publish. Does that sound fine? If you have ideas on how to make the process better, please let me know. Thanks, Aizhamal On Wed, Jun 5, 2019 at 4:10 AM Thomas Weise wrote: > +1 > > What would be the mechanism to notify the PMC that there is something to > review? > > > On Tue, Jun 4, 2019 at 9:55 PM Kenneth Knowles wrote: > >> Bringing the PMC's conclusion back to this list, we are happy to start >> with the following arrangement: >> >> - Doc/spreadsheet/etc readable by dev@ (aka the public), writable by >> some group of contributors to set up a queue of news >> - Any member of PMC approves and executes the posts, with enough time >> elapsing to consider it lazy consensus >> >> Any mistake transcribing this conclusion is my own. And of course nothin= g >> is permanent, but we try and iterate. >> >> Kenn >> >> On Mon, Jun 3, 2019 at 2:18 PM Aizhamal Nurmamat kyzy < >> aizhamal@google.com> wrote: >> >>> Hello folks, >>> >>> I have created a spreadsheet where people can suggest tweets [1]. It >>> contains a couple of tweets that have been tweeted as examples. Also, t= here >>> are a couple others that I will ask PMC members to review in the next f= ew >>> days. >>> >>> I have also created a blog post[2] to invite community members to >>> participate by proposing tweets / retweets. >>> >>> Does this look OK to everyone? I=E2=80=99d love to try it out and see i= f it >>> drives engagement in the community. If not we can always change the >>> processes. >>> >>> Thanks, >>> aizhamal >>> >>> [1] s.apache.org/beam-tweets >>> [2] https://github.com/apache/beam/pull/8747 >>> >>> On Fri, May 24, 2019 at 4:26 PM Kenneth Knowles wrote= : >>> >>>> Thanks for taking on this work! >>>> >>>> Kenn >>>> >>>> On Fri, May 24, 2019 at 2:52 PM Aizhamal Nurmamat kyzy < >>>> aizhamal@google.com> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> I'd like to pilot this if that's okay by everyone. I'll set up a >>>>> spreadsheet, write a blog post publicizing it, and perhaps send out a >>>>> tweet. We can improve the process later with tools if necessary. >>>>> >>>>> Thanks all and have a great weekend! >>>>> Aizhamal >>>>> >>>>> On Tue, May 21, 2019 at 8:37 PM Kenneth Knowles >>>>> wrote: >>>>> >>>>>> Great idea. >>>>>> >>>>>> Austin - point well taken about whether the PMC really has to >>>>>> micro-manage here. The stakes are potentially very high, but so are = the >>>>>> stakes for code and website changes. >>>>>> >>>>>> I know that comdev votes authoring privileges to people who are not >>>>>> committers, but they are not speaking on behalf of comdev but under = their >>>>>> own name. >>>>>> >>>>>> Let's definitely find a way to be effective on social media. >>>>>> >>>>>> Kenn >>>>>> >>>>>> On Tue, May 21, 2019 at 4:14 AM Maximilian Michels >>>>>> wrote: >>>>>> >>>>>>> Hi Aizhamal, >>>>>>> >>>>>>> This is a great idea. I think it would help Beam to be more >>>>>>> prominent on >>>>>>> social media. >>>>>>> >>>>>>> We need to discuss this also on the private@ mailing list but I >>>>>>> don't >>>>>>> see anything standing in the way if the PMC always gets to approve >>>>>>> the >>>>>>> proposed social media postings. >>>>>>> >>>>>>> I could even imagine that the PMC gives rights to a Beam community >>>>>>> member to post in their name. >>>>>>> >>>>>>> Thanks, >>>>>>> Max >>>>>>> >>>>>>> On 21.05.19 03:09, Austin Bennett wrote: >>>>>>> > Is PMC definitely in charge of this (approving, communication >>>>>>> channel, >>>>>>> > etc)? >>>>>>> > >>>>>>> > There could even be a more concrete pull-request-like function >>>>>>> even for >>>>>>> > things like tweets (to minimize cut/paste operations)? >>>>>>> > >>>>>>> > I remember a bit of a mechanism having been proposed some time ag= o >>>>>>> (in >>>>>>> > another circumstance), though doesn't look like it made it >>>>>>> terribly far: >>>>>>> > >>>>>>> http://www.redhenlab.org/home/the-cognitive-core-research-topics-in= -red-hen/the-barnyard/-slick-tweeting >>>>>>> > (I haven't otherwise seen such functionality). >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > On Mon, May 20, 2019 at 4:54 PM Robert Burke >>>>>> > > wrote: >>>>>>> > >>>>>>> > +1 >>>>>>> > As a twitter user, I like this idea. >>>>>>> > >>>>>>> > On Mon, 20 May 2019 at 15:18, Aizhamal Nurmamat kyzy >>>>>>> > > wrote: >>>>>>> > >>>>>>> > Hello everyone, >>>>>>> > >>>>>>> > >>>>>>> > What does the community think of making Apache Beam=E2=80= =99s >>>>>>> social >>>>>>> > media presence more active and more community driven? >>>>>>> > >>>>>>> > >>>>>>> > The Slack and StackOverflow for Apache Beam offer pretty >>>>>>> nice >>>>>>> > support, but we still could utilize Twitter & LinkedIn >>>>>>> better to >>>>>>> > share more interesting Beam news. For example, we could >>>>>>> tweet to >>>>>>> > welcome new committers, announce new features consistentl= y, >>>>>>> > share and recognize contributions, promote events and >>>>>>> meetups, >>>>>>> > share other news that are relevant to Beam, big data, etc= . >>>>>>> > >>>>>>> > >>>>>>> > I understand that PMC members may not have time to do >>>>>>> curation, >>>>>>> > moderation and creation of content; so I was wondering if >>>>>>> we >>>>>>> > could create a spreadsheet where community members could >>>>>>> propose >>>>>>> > posts with publishing dates, and let somebody to filter, >>>>>>> > moderate, and manage it; then send to a PMC member for >>>>>>> publication. >>>>>>> > >>>>>>> > >>>>>>> > I would love to help where I can in this regard. I=E2=80= =99ve had >>>>>>> some >>>>>>> > experience doing social media elsewhere in the past. >>>>>>> > >>>>>>> > >>>>>>> > Best >>>>>>> > >>>>>>> > Aizhamal >>>>>>> > >>>>>>> > >>>>>>> >>>>>> --0000000000000ec49a058aab1bb0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
With the spreadsheet in http://s.apache.org/beam-tweets, anyone can propose tweets. I= will check it every few days, and ping/tag PMC members to review tweets an= d publish. Does that sound fine?
If you have ideas on how to make t= he process better, please let me know.

Thanks,=
Aizhamal

On Wed, Jun 5, 2019 at 4:10 AM Thomas Weise <thw@apache.org> wrote:
+1
<= /div>

What would be the mechanism to notify the PMC that ther= e is something to review?=C2=A0


On Tue, Jun 4, 2019 at 9:55 P= M Kenneth Knowles <= kenn@apache.org> wrote:
Bringing the PMC's conclusion back= to this list, we are happy to start with the following arrangement:
<= div>
=C2=A0- Doc/spreadsheet/etc readable by dev@ (aka the pu= blic), writable by some group of contributors to set up a queue of news
=C2=A0- Any member of PMC approves and executes the posts, with enou= gh time elapsing to consider it lazy consensus

Any= mistake transcribing this conclusion is my own. And of course nothing is p= ermanent, but we try and iterate.

Kenn
=
On Mon= , Jun 3, 2019 at 2:18 PM Aizhamal Nurmamat kyzy <aizhamal@google.com> wrote:
Hello= folks,

I have created a spreadsheet where people can su= ggest tweets [1]. It contains a couple of tweets that have been tweeted as = examples. Also, there are a couple others that I will ask PMC members to re= view in the next few days.

I have also created a blog post[2] to inv= ite community members to participate by proposing tweets / retweets.
Does this look OK to everyone? I=E2=80=99d love to try it out and see if i= t drives engagement in the community. If not we can always change the proce= sses.

Thanks,
aizhamal

[1] s.apache.org/beam-tweets
[2] https://git= hub.com/apache/beam/pull/8747

On Fri, May 24, 2019 at 4:26 PM = Kenneth Knowles <ke= nn@apache.org> wrote:
Thanks for taking on this work!

Kenn

On Fri, May 24, 2019 at 2:52 PM Aizhamal Nurmamat kyzy <= aizhamal@google.co= m> wrote:
Hi everyone,

I'd like to pilot this if t= hat's okay by everyone. I'll set up a spreadsheet, write a blog pos= t publicizing it, and perhaps send out a tweet. We can improve the process = later with tools if necessary.

Thanks al= l and have a=C2=A0great weekend!
Aizhamal

On Tue, May 21, 20= 19 at 8:37 PM Kenneth Knowles <kenn@apache.org> wrote:
Great idea.

= Austin - point well taken about whether the PMC really has to micro-manage = here. The stakes are potentially very high, but so are the stakes for code = and website changes.

I know that comdev votes auth= oring privileges to people who are not committers, but they are not speakin= g on behalf of comdev but under their own name.

Le= t's definitely find a way to be effective on social media.
Kenn

On Tue, May 21, 2019 at 4:14 A= M Maximilian Michels <mxm@apache.org> wrote:
Hi Aizhamal,

This is a great idea. I think it would help Beam to be more prominent on social media.

We need to discuss this also on the private@ mailing list but I don't <= br> see anything standing in the way if the PMC always gets to approve the
proposed social media postings.

I could even imagine that the PMC gives rights to a Beam community
member to post in their name.

Thanks,
Max

On 21.05.19 03:09, Austin Bennett wrote:
> Is PMC definitely in charge of this (approving, communication channel,=
> etc)?
>
> There could even be a more concrete pull-request-like function even fo= r
> things like tweets (to minimize cut/paste operations)?
>
> I remember a bit of a mechanism having been proposed some time ago (in=
> another circumstance), though doesn't look like it made it terribl= y far:
> http://www.redhenlab.org/home/the-cognitive-core-research-topics-i= n-red-hen/the-barnyard/-slick-tweeting
> (I haven't otherwise seen such functionality).
>
>
>
> On Mon, May 20, 2019 at 4:54 PM Robert Burke <robert@frantil.com
> <mailto:rob= ert@frantil.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0+1
>=C2=A0 =C2=A0 =C2=A0As a twitter user, I like this idea.
>
>=C2=A0 =C2=A0 =C2=A0On Mon, 20 May 2019 at 15:18, Aizhamal Nurmamat kyz= y
>=C2=A0 =C2=A0 =C2=A0<aizhamal@google.com <mailto:aizhamal@google.com>> wrote:
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Hello everyone,
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0What does the community think of maki= ng Apache Beam=E2=80=99s social
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0media presence more active and more c= ommunity driven?
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The Slack and StackOverflow for Apach= e Beam offer pretty nice
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0support, but we still could utilize T= witter & LinkedIn better to
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0share more interesting Beam news. For= example, we could tweet to
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0welcome new committers, announce new = features consistently,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0share and recognize contributions, pr= omote events and meetups,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0share other news that are relevant to= Beam, big data, etc.
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I understand that PMC members may not= have time to do curation,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0moderation and creation of content; s= o I was wondering if we
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0could create a spreadsheet where comm= unity members could propose
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0posts with publishing dates, and let = somebody to filter,
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0moderate, and manage it; then send to= a PMC member for publication.
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I would love to help where I can in t= his regard. I=E2=80=99ve had some
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0experience doing social media elsewhe= re in the past.
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Best
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Aizhamal
>
>
--0000000000000ec49a058aab1bb0--