asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Hillery <chill...@hillery.land>
Subject Re: Where to place meeting notes?
Date Sun, 17 May 2015 09:34:25 GMT
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" <dtabass@gmail.com> 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 <imaxon@uci.edu> 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
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message