A little more details about the hangout issue:

Owner of hangout meeting is responsible to accept incoming requests. Since
Karthik is sick today so we had to create a new temporary meeting, which is
not ideal.



On Tue, Mar 27, 2018 at 4:09 PM, Ning Wang <wangnin...@gmail.com> wrote:

> Thanks for the suggestions.
>
> On Tue, Mar 27, 2018 at 4:02 PM, Dave Fisher <dave2w...@comcast.net>
> wrote:
>
>>   - Looking for another host for our Mailing list
>>
>>
>> The Mailing List must be dev@heron.incubator.apache.org using any other
>> mailing list is not the Apache Way.
>>
>>
>>   - Hangout is killing us today! We need a better solution.
>>
>>
>> Discuss items in plain sight of the whole community on this list. This
>> allows other developers to participate asynchronously.
>>
>> Regards,
>> Dave
>>
>>
>> On Mar 27, 2018, at 3:47 PM, Ning Wang <wangnin...@gmail.com> wrote:
>>
>> Hi,
>>
>> Here is a super brief notes for today's sync meeting:
>>
>>
>>   - Hangout is killing us today! We need a better solution.
>>   - Per component cpu/disk config is added but not used yet.
>>   - Looking into failing integration tests. This has been affecting us
>>   quite a big
>>   - New works on nomad scheduler (docker support)
>>   - New padding configs (to improve padding calculation and avoid hard
>>   coded configs) are documented and shared:
>>   https://docs.google.com/document/d/10JNZNYtcUIlsEyXcWWQUyh
>> cSoQoJZMvYrTYT8UFo4dQ/edit
>>   - Clean up and k8s scheduler related works ongoing
>>   - New scala examples have been added. Next step is to document them and
>>   integration tests
>>   - Looking for another host for our Mailing list
>>   - Code change ongoing to make the website apache ready. ETA next
>>   weekend. Apache Infra setup is needed for starting the website.
>>   - Apache transfer is on going by Twitter’s OSS team.
>>   - We need to finalize the meetup date @maosong.
>>
>>
>>
>>
>> Meeting notes are tracked here:
>> https://docs.google.com/document/d/1cTIBq3jOVRTSR0Zd5OKK20OqwT2l9
>> 0xXiY_HssVo8mE/edit?ts=5aa84932#
>>
>>
>>
>

Reply via email to