Open Stack

Swapnil,

Dunno if it was malicious or someone just trying to understand how things work.

Worth reaching out to jinke [1]

[1] http://git.openstack.org/cgit/openstack/stackalytics/commit/?id=e2593c113d64868b44f27a9fba15a564855236c6

Thanks,
Dims

On Wed, Oct 11, 2017 at 12:35 PM, Swapnil Kulkarni <coolsvap at gmail.com> wrote:
> On Wed, Oct 11, 2017 at 9:52 PM, Michał Jastrzębski <inc007 at gmail.com> wrote:
>> I haven't seen "malicious" meeting starters yet, let's hope that won't
>> happen:) On the other hand, ad-hoc chair change can, and did, happen,
>> so I agree with fungi - I don't think we need to put restrictions on
>> that.
>>
>> On 11 October 2017 at 09:11, Jeremy Stanley <fungi at yuggoth.org> wrote:
>>> On 2017-10-11 21:35:26 +0530 (+0530), Swapnil Kulkarni wrote:
>>> [...]
>>>> The problem here is if we know who are most likely to chair the
>>>> meeting e.g. [1] we can allow them to start the meeting.
>>> [...]
>>>
>>> I'm pretty certain I wouldn't want to have to propose a patch to
>>> update that every time I needed someone to chair a meeting in my
>>> absence. This doesn't seem like a common enough issue to warrant the
>>> added complexity and red tape of access controls on our meeting
>>> automation.
>>> --
>>> Jeremy Stanley
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> Michal,
>
> I just gave one instance of malicious meeting attempt [1] happened
> today and it happened to be kolla meeting so I noticed its not correct
> timing for the same. I would put it as permission-ed access rather
> than restriction, because as much as we want to keep it open we need
> to maintain the genuineness of meeting. I would not want to stumble
> into a junk log file while I am reading it later looking for
> something.
>
>
> [1] http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-10-11-10.31.log.html
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims