Jay Vyas <jayunit100.apa...@gmail.com> 於 2015/8/11週二 1:00 寫道:

> 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 transparent
> tell "we can easily have this discussion in the community"....
>
> > On Aug 10, 2015, at 12:43 PM, Marvin Humphrey <mar...@rectangular.com>
> wrote:
> >
> >> On Mon, Aug 10, 2015 at 9:21 AM, Steve Rowe <sar...@gmail.com> wrote:
> >>
> >> If Slack could be configured to send a periodic transcript to the
> project’s 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
>

Reply via email to