Yes, this has been mulled dozens of times over the years, and this "if it
didn't happen on mailing list it didn't happened at all" is the bottom
line. Note; the maturity model doesn't mention mailing lists, other than
footnote 11 talking about what happens outside public space.
However, one person
2015/8/11 上午5:17於 "林晉樟" 寫道：
>
>
> 2015/8/11 上午5:16於 "Eduardo Enocia" 寫道：
> >
> > Sent from my ALCATEL one touch Android.
> > On Aug 7, 2015 6:13 PM, "Ulrich Stärk" wrote:
> >
> > > We use it to communicate with people in all parts of the world. US,
South
> > > America, Several European
> > > count
2015/8/11 上午5:16於 "Eduardo Enocia" 寫道：
>
> Sent from my ALCATEL one touch Android.
> On Aug 7, 2015 6:13 PM, "Ulrich Stärk" wrote:
>
> > We use it to communicate with people in all parts of the world. US,
South
> > America, Several European
> > countries, Asia. So I'd say it's pretty global.
> >
>
Sent from my ALCATEL one touch Android.
On Aug 7, 2015 6:13 PM, "Ulrich Stärk" wrote:
> We use it to communicate with people in all parts of the world. US, South
> America, Several European
> countries, Asia. So I'd say it's pretty global.
>
> Uli
>
> On 06.08.15 19:24, Louis Suárez-Potts wrote:
HI,
> On 10 Aug 15, at 14:10, Ajoy Bhatia wrote:
>
> Just wanted to make a comment on the mail from Louis Suárez-Potts <
> lui...@gmail.com>, in which he related his conversation with James H., a
> Slack engineer. Comments are inline below. Highlighting is mine:
>
> So, I pinged the nice folks
Ajoy Bhatia 於 2015年8月11日週二 2:11 寫道：
> Just wanted to make a comment on the mail from Louis Suárez-Potts <
> lui...@gmail.com>, in which he related his conversation with James H., a
> Slack engineer. Comments are inline below. Highlighting is mine:
>
> So, I pinged the nice folks at Slack (and the
Just wanted to make a comment on the mail from Louis Suárez-Potts <
lui...@gmail.com>, in which he related his conversation with James H., a
Slack engineer. Comments are inline below. Highlighting is mine:
So, I pinged the nice folks at Slack (and they really are nice!, or at
> least the guy I com
2015/8/11 上午1:38於 "林晉樟" 寫道：
>
>
> 2015/8/11 上午1:36於 "林晉樟" 寫道：
> >
> >
> > 2015/8/11 上午1:36於 "林晉樟" 寫道：
> > >
> > >
> > > 2015/8/11 上午1:35於 "Benson Margulies" 寫道：
> > > >
> > > > I think it's important to recognize how the board and the foundation
> > > > have handled this issue over time.
> > > >
>
2015/8/11 上午1:36於 "林晉樟" 寫道：
>
>
> 2015/8/11 上午1:35於 "Benson Margulies" 寫道：
> >
> > I think it's important to recognize how the board and the foundation
> > have handled this issue over time.
> >
> > The absolute requirement is open decision-making. Avoiding real-time
> > communications avoids many
2015/8/11 上午1:36於 "林晉樟" 寫道：
>
>
> 2015/8/11 上午1:36於 "林晉樟" 寫道：
> >
> >
> > 2015/8/11 上午1:35於 "Benson Margulies" 寫道：
> > >
> > > I think it's important to recognize how the board and the foundation
> > > have handled this issue over time.
> > >
> > > The absolute requirement is open decision-making.
2015/8/11 上午1:35於 "Benson Margulies" 寫道：
>
> I think it's important to recognize how the board and the foundation
> have handled this issue over time.
>
> The absolute requirement is open decision-making. Avoiding real-time
> communications avoids many possible failures of open decision-making.
> (
I think it's important to recognize how the board and the foundation
have handled this issue over time.
The absolute requirement is open decision-making. Avoiding real-time
communications avoids many possible failures of open decision-making.
(Not, of course, all.) After all, the simplest primrose
Steve Rowe 於 2015/8/11週二 0:21 寫道：
>
> > On Aug 9, 2015, at 8:52 PM, Roman Shaposhnik
> wrote:
> >
> > On Sun, Aug 9, 2015 at 8:45 AM, Bertrand Delacretaz
> > wrote:
> >> On Sun, Aug 9, 2015 at 3:48 AM, jay vyas
> wrote:
> >>> ...1) We have to trust PMCs to foster a healthy and transparent
> ro
Jay Vyas 於 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".
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, Ma
On Mon, Aug 10, 2015 at 09:43:39AM -0700, Marvin Humphrey wrote:
> On Mon, Aug 10, 2015 at 9:21 AM, Steve Rowe 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 a
Marvin Humphrey 於 2015/8/11週二 0:43 寫道：
> On Mon, Aug 10, 2015 at 9:21 AM, Steve Rowe 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
On Mon, Aug 10, 2015 at 9:21 AM, Steve Rowe 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 hobbyis
On Monday, August 10, 2015, Steve Rowe wrote:
>
> > On Aug 9, 2015, at 8:52 PM, Roman Shaposhnik > wrote:
> >
> > On Sun, Aug 9, 2015 at 8:45 AM, Bertrand Delacretaz
> > > wrote:
> >> On Sun, Aug 9, 2015 at 3:48 AM, jay vyas > wrote:
> >>> ...1) We have to trust PMCs to foster a healthy and tra
> On Aug 9, 2015, at 8:52 PM, Roman Shaposhnik wrote:
>
> On Sun, Aug 9, 2015 at 8:45 AM, Bertrand Delacretaz
> wrote:
>> On Sun, Aug 9, 2015 at 3:48 AM, jay vyas wrote:
>>> ...1) We have to trust PMCs to foster a healthy and transparent roadmap.
>>> Exclusive cliques and backchannels should n
On Sun, Aug 9, 2015 at 8:45 AM, Bertrand Delacretaz
wrote:
> On Sun, Aug 9, 2015 at 3:48 AM, jay vyas wrote:
>> ...1) We have to trust PMCs to foster a healthy and transparent roadmap.
>> Exclusive cliques and backchannels should not ever exist in a healthy ASF
>> project, period
>
> That's w
On Sun, Aug 9, 2015 at 3:48 AM, jay vyas wrote:
> ...1) We have to trust PMCs to foster a healthy and transparent roadmap.
> Exclusive cliques and backchannels should not ever exist in a healthy ASF
> project, period
That's where our "if it didn't happen on the project's dev list, it
didn't h
Good point benson, and I definetely agree with the values *but* I
don't think i agree w/ the conclusion.
1) We have to trust PMCs to foster a healthy and transparent roadmap.
Exclusive cliques and backchannels should not ever exist in a healthy ASF
project, period.
2) Restricting a projects
On Sat, Aug 8, 2015 at 5:09 PM, Louis Suárez-Potts wrote:
> (top post)
>
> So, I pinged the nice folks at Slack (and they really are nice!, or at least
> the guy I communicated with), and asked them about:
>
> * open source: No.
> * the issue of uncaptured conversations, as Ted D. mentioned ("the
> On 08 Aug 15, at 17:17, Jay Vyas wrote:
>
> the asf uses slack and hip hat and atlassian already so the open source
> debate is moot, right?
Yes. The virtue of open source, here, would also lie in being able to do open
source-things, like contribute modules freely that we could then use f
the asf uses slack and hip hat and atlassian already so the open source debate
is moot, right? People will use the best tools for the job and so that should
be the focus. I'm neutral on slack vs irc, but I think if growing the ASF is
important slack will be of major benefit.
> On Aug 8, 2015
(top post)
So, I pinged the nice folks at Slack (and they really are nice!, or at least
the guy I communicated with), and asked them about:
* open source: No.
* the issue of uncaptured conversations, as Ted D. mentioned ("there is a huge
danger of off-list discussions…").
To the latter, whic
We use it to communicate with people in all parts of the world. US, South
America, Several European
countries, Asia. So I'd say it's pretty global.
Uli
On 06.08.15 19:24, Louis Suárez-Potts wrote:
> Hi,
> I’m curious who here also uses Slack. Besides me, that is.
>
> One thing I’m interested i
I'm also using slack for work in my new company. It makes sense for us as a
lot of the activities imply real-time synchronization between members of
teams spread around the world.
But as part of my job is to enhance the community supporting tools, I'm
finding that slack is useful, but, as previous
I use slack for work. The Apache Mahout project has been using it as well.
There is a huge danger of off-list discussions that go unreported (as with
IRC, but seemingly more so because of a better interface and easier access
to one-on-one conversations). The problem is not the tool itself or the
Same here using slack at work and irc for apache chats
Regards, Achim
sent from mobile device
Am 06.08.2015 9:33 nachm. schrieb :
> I use Slack at work, but favor the openness of IRC for everything else.
>
> Mo
>
> Sent from my iPhone
>
> > On Aug 6, 2015, at 1:57 PM, Peter Hunsberger
> wrote:
I use Slack at work, but favor the openness of IRC for everything else.
Mo
Sent from my iPhone
> On Aug 6, 2015, at 1:57 PM, Peter Hunsberger
> wrote:
>
> Outside of Apache, the NEO4J project uses Slack. It seems pretty active
> with a pretty global user base.
>
> Peter Hunsberger
>
> On T
Outside of Apache, the NEO4J project uses Slack. It seems pretty active
with a pretty global user base.
Peter Hunsberger
On Thu, Aug 6, 2015 at 12:24 PM, Louis Suárez-Potts
wrote:
> Hi,
> I’m curious who here also uses Slack. Besides me, that is.
>
> One thing I’m interested in is, How global
On Thu, Aug 6, 2015 at 10:24 AM, Louis Suárez-Potts wrote:
> Hi,
> I’m curious who here also uses Slack. Besides me, that is.
>
> One thing I’m interested in is, How global is its reach?
I'm very much curious about this as well. Geode users have been
asking whether we can start a slack channel fo
34 matches
Mail list logo
