Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
References: <0A45B62D-00FA-4F66-B357-E0240F9E65A1@gmail.com>
 <55C484B5.8000504@spielviel.de>
 <86B34B78-B3F6-4DE7-AD71-325272BA3C17@gmail.com>
 <CALhtWkc=C89sOcA9pn4vPxaLd68v6Nc8zjCXYFAjTJsHauuKtA@mail.gmail.com>
 <CACVCA=cjn_LO8YaRR3ta3phsBUihGBXM0eV_hChG40VnHm4HZQ@mail.gmail.com>
 <CAEWfVJm9QC6tUuKKVv56NmkVL0MDRZyjt3K6KF5NVMVU1DJ-Kg@mail.gmail.com>
 <CA+ULb+v4v+UZrP3ZBZnxQkGBAcosPksn+CCi_=pyfcJpax5y9Q@mail.gmail.com>
 <00A12D1F-16AE-4798-B274-5D22B3E5D891@gmail.com>
 <CAAS6=7joeZZzP2GfO5UGmcZZG_b2kXqE=_asrwO4D7Aewq167w@mail.gmail.com>
 <B828AA7D-5519-4F80-8CC9-59E6DF33E837@gmail.com>
In-Reply-To: <B828AA7D-5519-4F80-8CC9-59E6DF33E837@gmail.com>
From: =?UTF-8?B?5p6X5pmJ5qif?= <line0928769960@gmail.com>
Date: Mon, 10 Aug 2015 17:02:55 +0000
Message-ID: 
 <CAFjJE51o+BSTpbgLUNNkG9Sm5U6G7nCoHsDqycG=XmWxrwEGmw@mail.gmail.com>
Subject: Re: slack
To: dev@community.apache.org
Content-Type: multipart/alternative; boundary=047d7ba9743686bb5e051cf7f577

--047d7ba9743686bb5e051cf7f577
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Jay Vyas <jayunit100.apache@gmail.com> =E6=96=BC 2015/8/11=E9=80=B1=E4=BA=
=8C 1:00 =E5=AF=AB=E9=81=93=EF=BC=9A

> A great offset to the **true danger** which is "Real time closed door
> communication" is "Real time open communication.".
>
> This gives the open source engineer a defensible  reason to be transparen=
t
> tell "we can easily have this discussion in the community"....
>
> > On Aug 10, 2015, at 12:43 PM, Marvin Humphrey <marvin@rectangular.com>
> wrote:
> >
> >> On Mon, Aug 10, 2015 at 9:21 AM, Steve Rowe <sarowe@gmail.com> wrote:
> >>
> >> If Slack could be configured to send a periodic transcript to the
> project=E2=80=99s dev mailing list, problem solved, no?
> >
> > No.  People in out-of-the-way time zones are excluded when issues are
> > worked out during rapid-fire discussions. So are hobbyists and
> > part-time people who can't hover over the keyboard at every moment.
> > Real-time communications consolidate power in the hands of people who
> > are paid to work on the project.
>
> >
> > Of course, excluding people is quite convenient if you're a company
> > that's here for the brandwashing paying lip-service to Apache ideals
> > while actually ramming through your agenda. But in theory at least,
> > Apache isn't here to serve them.
> >
> > Marvin Humphrey
>

--047d7ba9743686bb5e051cf7f577--