settingsLogin | Registersettings

[openstack-dev] [tc] [kolla] [PTL] who can start the official meeting?

0 votes

I was attending the weekly requirements meeting when I noticed someone
started the kolla meeting [1] on openstack-meeting-4 channel. I thought we
had the restrictions on the chairs, but apparently there's not. Can we
think about having one such restriction?

[1]
http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-10-11-10.31.html

Best Regards,
Swapnil


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Oct 11, 2017 in openstack-dev by me_at_coolsvap.net (1,860 points)   2

8 Responses

0 votes

On 2017-10-11 17:51:59 +0530 (+0530), Swapnil Kulkarni (coolsvap) wrote:
I was attending the weekly requirements meeting when I noticed
someone started the kolla meeting [1] on openstack-meeting-4
channel. I thought we had the restrictions on the chairs, but
apparently there's not. Can we think about having one such
restriction?

We don't implement technical solutions to social problems of this
nature. If you have an issue with the person who started the kolla
meeting in your absence, please take it up with them.
--
Jeremy Stanley


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Oct 11, 2017 by Jeremy_Stanley (56,700 points)   3 5 7
0 votes

I agree with Jeremy that we shouldn't attempt to implement technical
solutions for non-technical problems. But to that end, I'd be curious
to know what the problem was with this. In my experience it has been
an asset to have the meeting start on time even if the regular chair
is for some reason delayed.

I've benefited from that in Trove, and on at least one occasion I've
started the oslo meeting and the regular chair came in and took over a
while later.

The short log that coolsvap provided doesn't exhibit a problem, as
best as I can tell; people without bouncers sometimes do lose their
internet connection :(

-amrith

On Wed, Oct 11, 2017 at 9:55 AM, Jeremy Stanley fungi@yuggoth.org wrote:
On 2017-10-11 17:51:59 +0530 (+0530), Swapnil Kulkarni (coolsvap) wrote:

I was attending the weekly requirements meeting when I noticed
someone started the kolla meeting [1] on openstack-meeting-4
channel. I thought we had the restrictions on the chairs, but
apparently there's not. Can we think about having one such
restriction?

We don't implement technical solutions to social problems of this
nature. If you have an issue with the person who started the kolla
meeting in your absence, please take it up with them.
--
Jeremy Stanley


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by amrith.kumar_at_gmai (3,580 points)   2 3
0 votes

Hi Jeremy, Amrith,

On Wed, Oct 11, 2017 at 7:50 PM, Amrith Kumar amrith.kumar@gmail.com wrote:
I agree with Jeremy that we shouldn't attempt to implement technical
solutions for non-technical problems. But to that end, I'd be curious
to know what the problem was with this. In my experience it has been
an asset to have the meeting start on time even if the regular chair
is for some reason delayed.

I agree this is a non-technical problem and if someone else who can
start the meeting in the absence of the chair is always helpful. 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.

[1] https://github.com/openstack-infra/irc-meetings/blob/master/meetings/requirements-team.yaml#L10

I've benefited from that in Trove, and on at least one occasion I've
started the oslo meeting and the regular chair came in and took over a
while later.

The short log that coolsvap provided doesn't exhibit a problem, as
best as I can tell; people without bouncers sometimes do lose their
internet connection :(

This is all the log there is. I don't even know if the person who
started the meeting is contributor to kolla or openstack for that
matter. My only query is people who know about official meetings will
not do it, but can we restrict those who dont? Otherwise there is no
meaning to the official meetings if anyone can start them anytime.

-amrith

On Wed, Oct 11, 2017 at 9:55 AM, Jeremy Stanley fungi@yuggoth.org wrote:

On 2017-10-11 17:51:59 +0530 (+0530), Swapnil Kulkarni (coolsvap) wrote:

I was attending the weekly requirements meeting when I noticed
someone started the kolla meeting [1] on openstack-meeting-4
channel. I thought we had the restrictions on the chairs, but
apparently there's not. Can we think about having one such
restriction?

We don't implement technical solutions to social problems of this
nature. If you have an issue with the person who started the kolla
meeting in your absence, please take it up with them.
--
Jeremy Stanley


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@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@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Swapnil_Kulkarni (2,500 points)   2 3
0 votes

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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Oct 11, 2017 by Jeremy_Stanley (56,700 points)   3 5 7
0 votes

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@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@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Michał_Jastrzębski (9,220 points)   1 5 5
0 votes

On Wed, Oct 11, 2017 at 9:52 PM, Michał Jastrzębski inc007@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@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@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@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Swapnil_Kulkarni (2,500 points)   2 3
0 votes

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@gmail.com wrote:
On Wed, Oct 11, 2017 at 9:52 PM, Michał Jastrzębski inc007@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@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@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@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Davanum_Srinivas (35,920 points)   2 4 8
0 votes

Dims,

This was just a fella in the kolla community experimenting without attempting to cause harm. IOW he didn’t know exactly what he was doing which is helpful when messing with the meeting bots (.

No harm done anyway, so no need to take any corrective action in implementation.

Cheers
-steve

On 10/11/17, 11:15 AM, "Davanum Srinivas" davanum@gmail.com wrote:

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@gmail.com> wrote:

On Wed, Oct 11, 2017 at 9:52 PM, Michał Jastrzębski inc007@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@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@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@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-- 
Davanum Srinivas :: https://twitter.com/dims

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@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@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 27, 2017 by Steven_Dake_(stdake) (24,540 points)   2 10 23
...