On Mon, Aug 10, 2015 at 09:43:39AM -0700, Marvin Humphrey 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?
It only works to the extent that summaries are then available for wider consumption, before any decision are made (if any) on list. We should not shy-away from using these alternate communication channels, but we should remind people how they could be used in conjunction with thwir project mailing lists. > > 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
pgpmKgWjhoFI1.pgp
Description: PGP signature
