Agreed! We don't want to dismantle our university project meetings -
but - we also do want to share what happens in that context with the
whole community. No decisions will be made in those meetings - the dev
list will always be used to discuss stuff and to get consensus/decisions
made - but they do serve a useful purpose to keep progress being made
and accountability for those whose "day job" it is to be contributing on
a weekly basis. This would be like if Hortonworks or Cloudera published
notes from their internal meetings and shared them with the rest of the
Hadoop community - so it's actually intended as added openness rather
than closed-ness or inner circle-ness. (We could decide to just not
share the notes, which is what probably goes on elsewhere - but we
thought it might be nice to be all the more open.) Make sense?
On 5/17/15 3:21 AM, Jochen Wiedmann wrote:
The question is not, whether there is something "useful" (for whom)?
It is generally recommended to avoid inner circles, and the like, and
have as much transparency as possible. That avoids that others are
getting the feeling to be outsiders.
Jochen
On Sun, May 17, 2015 at 11:34 AM, Chris Hillery <[email protected]> wrote:
I don't think you're going to get a lot of useful real-time discussion
about things via IRC. At that point, we may as well just send status in
email - which I'm not necessarily opposed to, but that does seem like a
fairly significant shift in group culture.
Ceej
aka Chris Hillery
On May 16, 2015 11:06 PM, "Mike Carey" <[email protected]> wrote:
That sounds like an interesting possibility....!
On 5/15/15 11:01 PM, Henry Saputra wrote:
We could what Apache Aurora did. Using IRC to do the meeting and allow
ASF IRC bot [1] to record and send to dev@ list.
[1] http://www.apache.org/dev/asfbot.html
On Fri, May 15, 2015 at 7:01 PM, Ian Maxon <[email protected]> wrote:
Hi all,
Most of us attend a weekly "AsterixDB" meeting, either via Skype or
in-person. However the focus of this meeting is two fold. One part of it
is
regarding the development of AsterixDB, and the other part is about the
research efforts that many of us are undertaking, that may not
necessarily
be directly relevant to AsterixDB itself.
Because of that, the minutes from these weekly meetings often contain
things that would be of interest to all committers and folks otherwise
interested in AsterixDB, but they also contain things that are unrelated.
So on one hand it seems natural to post the minutes to this development
list, I think there is still uncertainty about whether or not simply
doing
that is the right thing.
Have other Apache projects dealt with this situation? i.e. what to do
when
meetings contain information and decisions relevant to the project, but
also address other non-Apache concerns? Any/all guidance and input would
be
appreciated.
Thanks,
- Ian
