Thursday, 2018-10-11

*** devananda has quit IRC00:12
*** devananda has joined #openstack-tc00:13
openstackgerritMohammed Naser proposed openstack/governance master: Update the charter section with meetings every 2 weeks  https://review.openstack.org/60956200:16
*** annabelleB has quit IRC00:26
*** annabelleB has joined #openstack-tc00:50
*** annabelleB has quit IRC00:53
*** gagehugo_ has quit IRC01:24
*** gagehugo has joined #openstack-tc01:25
lbragstadthanks dhellmann01:27
*** clarkb has quit IRC01:38
*** jamesmcarthur has joined #openstack-tc02:09
*** lbragstad has quit IRC02:40
*** jamesmcarthur has quit IRC03:06
*** e0ne has joined #openstack-tc06:02
*** dims has quit IRC06:29
*** e0ne has quit IRC06:29
*** dims has joined #openstack-tc06:33
*** dims has quit IRC06:38
*** dims has joined #openstack-tc06:39
*** jpich has joined #openstack-tc07:59
*** dtantsur|afk is now known as dtantsur|08:44
*** dtantsur| is now known as dtantsur08:44
*** e0ne has joined #openstack-tc09:05
*** tosky has joined #openstack-tc09:06
*** e0ne has quit IRC09:27
*** e0ne has joined #openstack-tc09:43
evrardjpdhellmann: is the timezone correct on the wiki page?09:44
*** jamesmcarthur has joined #openstack-tc10:04
*** jamesmcarthur has quit IRC10:09
*** gouthamr has quit IRC10:14
*** e0ne has quit IRC10:35
*** e0ne has joined #openstack-tc10:38
*** e0ne has quit IRC11:04
*** dtantsur is now known as dtantsur|brb11:21
gmanndhellmann: thanks for info11:26
* gmann add 'tc-members' keyword as notification alert in IRC client 11:27
dimso/11:27
*** dangtrinhnt_x has joined #openstack-tc11:45
*** e0ne has joined #openstack-tc11:51
*** gouthamr has joined #openstack-tc12:05
mnasermorning all12:12
*** mriedem has joined #openstack-tc12:21
ttxmnaser: good morning12:24
mnaserttx: hopefully you're doing okay :)12:24
mnaserhttp://lists.openstack.org/pipermail/openstack-dev/2018-October/135674.html12:25
mnasertc-members: ^ play chime in by votes/discussion/etc12:26
ttxmnaser: yes. Short night though :)12:29
*** dangtrinhnt_x has quit IRC12:34
openstackgerritMerged openstack/project-team-guide master: Update stable-branches doc to mention $series-em tag  https://review.openstack.org/60829912:36
*** jamesmcarthur has joined #openstack-tc12:41
*** mriedem is now known as mriedem_afk12:54
*** jamesmcarthur has quit IRC13:02
*** e0ne has quit IRC13:11
*** dims has quit IRC13:12
*** dims has joined #openstack-tc13:14
*** dtantsur|brb is now known as dtantsur13:15
*** dims has quit IRC13:19
*** e0ne has joined #openstack-tc13:21
dhellmannevrardjp : I suspect not. It's an in person meeting, so I'm guessing it would be local time13:27
*** lbragstad has joined #openstack-tc13:31
openstackgerritMerged openstack/governance master: Assert stable:follows-policy on octavia-lib  https://review.openstack.org/60527313:47
*** mriedem_afk is now known as mriedem13:56
*** annabelleB has joined #openstack-tc14:05
*** dims has joined #openstack-tc14:22
*** knikolla has joined #openstack-tc14:23
*** e0ne has quit IRC14:33
*** annabelleB has quit IRC14:41
*** e0ne has joined #openstack-tc14:42
*** dims has quit IRC14:43
*** dims has joined #openstack-tc14:48
*** annabelleB has joined #openstack-tc14:53
*** openstackgerrit has quit IRC14:58
*** openstackgerrit has joined #openstack-tc14:59
dhellmanntc-members: time for office hours15:00
evrardjpo/15:01
fungiso it is!15:01
TheJuliao/15:01
smcginniso/15:01
dhellmanndoes anyone have any topics to raise today?15:02
*** mriedem has quit IRC15:03
dhellmannreally? no one wants to talk about meeting frequency? :-)15:04
*** lbragstad has quit IRC15:04
*** annabelleB has quit IRC15:04
TheJuliadhellmann: well, async + getting coffee15:04
dhellmannTheJulia : what are you even doing here? aren't you getting married or on a honeymoon or something?15:04
smcginnisBut office hours isn't the time to raise topics, it's when we're available for folks to come with questions, right? :)15:05
* fungi is asyncing some coffee too15:05
* smcginnis was wondering the same about TheJulia 15:05
evrardjpsmcginnis: :D15:05
TheJuliaI would prefer for fairly regular meetings. I thought we were gaining consensus on every two weeks, then it seems (at least to me) that it become once a month, and now once a week. I do feel once a month is too in-often to have a meeting of record15:05
TheJuliadhellmann: basically vacation after summit15:05
*** lbragstad has joined #openstack-tc15:05
dhellmannTheJulia : +115:06
smcginnisTheJulia: DId the wedding already happen?15:06
TheJuliasmcginnis: Tuesday15:06
smcginnisTheJulia: Congrats!!15:06
evrardjpTheJulia: congrats!15:06
* dhellmann looks for the champagne emojii15:06
TheJuliaI really like every two weeks, a happy point between the two proposals15:06
dhellmannthere are 2 proposals up for vote right now as patches, one for monthly and one for every 2 weeks15:06
TheJuliait _is_ also okay to say "well, no topics, lets start and end the meeting15:07
fungiit seems we have a couple of basic positions. one is that the meetings are to tick the "at least quarterly" checkbox for foundation bylaws (at least until we can get the bylaws changed), and the other is to bring back the old meetings we used to have15:07
TheJuliaI thought it was weekly15:07
dhellmannhttps://review.openstack.org/#/c/609562/1 says 2 weeks15:07
smcginnisMy take was we started with the bylaws saying we needed quarterly, so we said how about monthly. Which then became weekly/bi-weekly.15:07
TheJuliaOh, well, somehow I didn't grok that15:07
* TheJulia can blame post wedding brain haze right?15:07
dhellmannTheJulia : yes, you get a pass for another few days15:08
smcginnisDefinitely! :)15:08
lbragstadbiweekly: https://review.openstack.org/#/c/609562/15:08
fungii fall more in the tick-the-checkbox camp and would rather we have "official meetings" as infrequently as we can get away with, and limit the topics on the agenda as much as possible15:08
lbragstadmonthly: https://review.openstack.org/#/c/608751/15:08
zanebTheJulia: congrats!15:08
lbragstadcongrats TheJulia :)15:08
smcginnis🍾15:08
dhellmannif we think there are differences about the intent of meetings, maybe we should talk a bit more in depth about the sorts of topics we do want to cover in them15:08
smcginnisdhellmann:  I agree.15:09
*** e0ne has quit IRC15:09
smcginnisThat seems to be the root of the issue from what I can tell. We have differing opinions of what it is for, so differing opinions of how often we should have them.15:09
dhellmannI have a couple of sample topics in https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee right now15:09
evrardjpI have the impression we should get the logs of previous conversations, because that's exactly what was said previously.15:09
smcginnisdhellmann: Those look fine.15:10
zanebagree with fungi. we need to decide if we're trying to rescind https://governance.openstack.org/tc/resolutions/20170425-drop-tc-weekly-meetings.html or if we're just checking the bylaws box15:10
smcginnisBut I think all the reasons we decided to drop a regular meeting still stand.15:10
smcginnis^^15:10
fungii still feel like "official meetings" were not well-suited to community input/involvement and so would rather we not cover anything where we want community involvement in the discussion. i also think there's very little we do where we shouldn't welcome community involvement in our discussions15:10
lbragstadoutside of those sample topics, have there been any topics recently that would have been better suited for an official meeting than office hours?15:10
smcginnisI also find it a little ironic that we are trying to do this after an extended discussion about helping global members participate.15:11
dhellmannlbragstad : the alternatives also include the mailing list, and we've been trying to push more discussion there15:11
*** annabelleB has joined #openstack-tc15:11
fungiwe had official meetings once upon a time because that was how the tc officially registered its votes on resolutions. we moved to asynchronous voting in gerrit, but the meetings continued15:11
dhellmannesp. now that we have a member in an APAC TZ again15:11
* dims catching up15:12
TheJuliaWhy don't we do quarterly and as a standing agenda item of "review current health deltas"?15:13
TheJuliaSo we're both fulfilling the requirement, and we're actually having a meaningful setpoint15:13
TheJuliaor checkin point15:13
dhellmannwell, that is one of the topics on the proposed agenda for november15:13
smcginnisI would be fine if that is all they are. Or as dhellmann's other topic of preparing for any face to face agendas.15:13
dhellmannfrom a practical standpoint we need to have more than quarterly meetings scheduled, because we're going to end up cancelling some and I don't want us to have to scramble to reschedule at the last minute15:14
smcginnisWhy would we need to cancel some?15:14
dhellmannholidays; everyone being gone to an event; life15:14
dhellmannlet's say I anticipate it happening and would like to design resilience into the system15:15
smcginnisI'd rather we just handle those likely rare occasions on a case by case need to schedule alternate times when we identify conflicts.15:15
dhellmannI really dislike the idea of having to coordinate 13 schedules on short notice. :-/15:15
evrardjpdhellmann: convention over configuration!15:15
smcginnisNot everyone needs to be present, just a quorum.15:16
dhellmannwell, that's true15:16
dhellmannok, so if someone wants to propose quarterly, please write the patch15:16
evrardjpthat was what I meant smcginnis , thanks for clarifying in english terms :)15:16
smcginnisIf we don't do Monday's or Friday's, and we keep it away from when we know Summits and things land (although that could be considered a meeting) we can avoid the need for most last minute scheduling.15:16
smcginnisevrardjp: ;)15:16
smcginnisWe would then have three options. Do we need to set up a cordocet vote on this? :)15:17
TheJuliadhellmann: I think the meetings should take place regardless of availability of one or even five members. As long as we have some sort of quorum we should be good15:17
evrardjpdhellmann: I think the point was to ensure it is done quarterly so doubling the frequency (or more) would do -- that's why a month was proposed. But still the agenda is my concern15:17
dhellmannquarterly would have us at november, february, may, and august15:18
*** lbragstad has quit IRC15:18
*** lbragstad has joined #openstack-tc15:19
evrardjp#troll_mode PTG + Summits would have met the quarterly requirements15:20
*** e0ne has joined #openstack-tc15:20
fungievrardjp: they did, roughly speaking15:20
dhellmannso what topics should we *not* plan to discuss in meetings/15:20
dhellmann?15:20
*** e0ne has quit IRC15:20
fungievrardjp: that's part of why we're discussing the requirement again now that we are combining the next ptg with a summit15:20
smcginnisIf we make them only about health check updates and in-person meeting planning, that works for me.15:21
TheJuliadhellmann: Anything that has arisen in the prior week or two is a good starting point in my mind15:21
evrardjplet's do midcycles! #troll_mode off15:21
*** mugsie has joined #openstack-tc15:21
smcginnisIt's narrow enough to discourage discussions that should happen here and on the ML.15:21
dhellmannTheJulia : I was hoping for something more specific15:21
evrardjpdhellmann: the point I was concerned with is the community health's tracking status updates15:21
fungii'd rather discuss things as they arise rather than saving discussion of them for up to two weeks15:22
TheJuliadhellmann: Sadly I don't have a time machine, if I did I would :)15:22
dhellmannevrardjp : you can expect to have those mentioned in every single meeting while I am chair15:22
*** openstackgerrit has quit IRC15:22
evrardjpdhellmann: these are important topics indeed, I would like those to be very open15:22
evrardjpI am afraid of a negative impact.15:22
evrardjpI'd rather not have this become a  "restricted to tc meetings"15:23
dhellmannevrardjp : I will ask tc-members every meeting whether they have talked to their teams and updated the wiki with new data. If there are significant issues to bring up, we may go into those, but I expect those to be raised when we learn about them and not kept for the meeting.15:23
dhellmannyes, that's the point of saying it will be a status update15:24
zanebI'd like to hear from the fornightly crowd what they think _should_ be on the agenda. I'm sympathetic in principle to having some sort of cadence to drive things forward. but I'd like to know which things y'all think are worth saving up for 2 weeks15:24
dhellmannmnaser and ttx aren't here today, so we may have to wait to hear from them15:26
evrardjpI have the impression this meeting becomes a two weeks "update" to the "outside"15:26
TheJuliaSo what if keep a very focused specific agenda, including healthchecks, and try to keep the things that come up to as they arise?15:26
mnaserI just checked into my hotel room15:27
TheJuliaI think we can't do full updates every two weeks15:27
mnaserReading scrollbaxk to follow up15:27
evrardjpwhile the rest of the conversations are happening live15:27
dhellmannmnaser : hi!15:27
dhellmannTheJulia : yeah, that's why I suggested monthly :-)15:27
TheJuliaI'm on board with monthly if that is a main purpose of the meeting15:27
dhellmannevrardjp: that's not how I see it. I see the meetings as a chance for us to have an internal conversation about our work as a team.15:28
lbragstadcorrect me if i'm wrong, but is the end goal to attempt to change the bylaws?15:28
evrardjpI am fine with x as long as the purpose is clear in the motion15:28
evrardjpdhellmann: I see15:28
fungii don't object to using the meeting as a means of communicating information to a larger audience. the suggestion was that there's some subset of the community who consumed tc meeting minutes (back when we had meetings) as their primary means of keeping up to date on what we're doing15:28
zanebevrardjp: I got the same impression from mnaser. but Doug already has a weekly email to update the community weekly. I don't see how a meeting will do that better15:28
dhellmannlbragstad : I'm not sure we would be able to remove the meeting requirement from the bylaws, so I want us to be meeting the requirement just in case.15:28
mnaserOkay I caught up a little15:28
mnaserLet me open my laptop to type things out!15:29
lbragstaddhellmann ok15:29
evrardjpI guess multiple purposes are raised here, and maybe that should be stated in the document15:29
*** clarkb has joined #openstack-tc15:29
evrardjpit was not so clear to me at least but let me re-read this once again15:29
fungilbragstad: ttx and i have asked jbryce to pass along to the foundation's legal counsel that we're interested in being able to move some of those parts of the bylaws into our charter, at which point we'll have more freedom to alter or remove them as requirements without having to muster 10% of the foundation membership to vote on it15:30
lbragstadok, that makes sense15:30
fungibut how far we get with that will depend on lots of factors15:30
lbragstadtl;dr we have to live with it for the time being15:30
mnaseralright so15:31
dhellmannfwiw, I think there's some utility to us having regular formal meetings, regardless of whether we're required to do so.15:31
fungiwe have an alternative option of trying to explain how our current practices satisfy the requirements as stated in the bylaws, too15:31
mnaserfirst of all, do we have agreement that we'll have meetings (so that i don't spend time talking about why i think they were important?)15:31
mnaserbecause that's probably the point to discuss prior to the frequency15:32
dhellmannas chair, I will be calling meetings to meet our obligations in the bylaws, whether the rest of you want them or not :-)15:32
dhellmannso the only questions are how often and what will they cover15:32
mnaserright: so here is my pov15:32
*** mriedem has joined #openstack-tc15:32
evrardjpdhellmann: I think we agree with you there :)15:32
mnaseroffice hours are great to encourage external members to come in and bring up subjects, however, i think we can all agree that they have been a bit of a failure unfortunately15:33
mnaserthe EU friendly hours is attended by the 2-3 members in EU15:33
mnaserAPAC friendly hours are pretty much dead15:33
fungiyes, i believe that calling meetings with some regular frequency is our best option to be able to prove that we satisfy the requirements in the bylaws, and i also agree that doing it with somewhat greater frequency than the bylaws require gives us the flexibility to skip meetings without having to worry too much about failing to comply15:33
evrardjpmnaser: I do not agree on the failure15:33
mnaserand the US friendly hours is just the TC talking about TC things15:33
mnaserthere is no "office hours" where community can come and talk to us about things.  it's very hard.15:33
mnaserwe're all very vocal and the hour almost always becomes more than one15:34
*** jamesmcarthur has joined #openstack-tc15:34
mnaserand it probably is very intimidating for a community member to come here and be like "can i have some time"15:34
mnasernow, with the proposed new meetings that happen, someone can email the tc mailing list, or a tc member, or the chair and say: hey.. i'd like for us to talk about this15:34
evrardjpmnaser: without office hours I wouldn't have been asking my questions, and learning a lot in here. I was very intimidated at first. I still am tbh. I am sure with meetings it would have been worse.15:34
mnaserand we can actually slot them in and give them the time15:34
zanebmnaser: meetings were even more intimidating15:34
smcginnisevrardjp: Meetings were much much worse.15:35
mnaserrather than trying to get in here and *race* to bring your topics up15:35
fungii'm at least able to follow the discussions in our office hours, whereas my comments during the official meetings we used to hold were infrequent and asynchronous because by the time i could read and type a reply the discussion had already moved on15:35
mnasereven I have subjects that i want to discuss with the tc15:35
mnaserthat i cant even find the time to bring uo15:35
mnaserbecause office hours just fly by with several topics and they're all equally important15:35
smcginnisThere should be no designated time to bring up discussions15:35
TheJuliafungi: I find that often an issue with many voices in a limited timespan irc meeting15:35
smcginnisOffice hours is a completely wrong time to save a topic for.15:35
mnaserbut i'm in EU right now15:35
zanebmnaser: meetings were like that too15:36
mnaserif i post something at 8am when i wake up15:36
fungistart discussing something when you have something to discuss and people will reply when they're around to reply15:36
mnaserzaneb: i disagree, meetings have an agenda15:36
evrardjpmnaser: someone can just ask on this channel at anytime, and we say "this would be a great topic for next office hour" -> everybody could talk this way15:36
smcginnisAnd use the ML too.15:36
mnaseras chair/vice chair, if we're talking about $foo and the conversation moves to $bar15:36
mnaserwe say: hey all, remember why we're here, let's take a step back15:36
mnaserand conclude this subject15:36
smcginnismnaser: Did you attend any of the meetings we used to have. It was defintely not a time conducive to introducing something new.15:36
mnasersmcginnis: did we have a preset agenda in advance? i may have not attended them but i've certainly heard many community members complain about the fact that they cant keep up15:37
TheJuliaIt seemed to often just be a rehash to get people on to the same page15:37
zanebmnaser: you are talking about meetings in the abstract, but I am talking specifically about the meetings the TC used to hold in IRC. which were exactly like office hours except worse15:37
mnaserwell maybe let's have structured meetings15:37
smcginnisMuch worse.15:37
mnaserstart by roll call, follow up on actions, 2-3 timeboxed discussions15:37
* dims shudders15:37
mnaserwhere we have to come to a conclusion at the end of15:37
evrardjpI'd rather keep office hours and have structured meetings both aren't exclusive imo.15:37
dhellmannwe did have agendas, which forced us to time-box discussions, which caused them to happen *very* rapidly15:37
mnaserwell15:37
fungialso the topic needed to get added to the agenda far enough in advance that it could be announced we were going to be discussing whatever it was, and usually at least half of the agenda ended up on a backlog to discuss at a future meeting15:38
mnaserby havign 1 meeting every month15:38
mnaserwe have even *LESS* time to discuss things15:38
mnaserwhere as if we have a loaded subject15:38
mnaserwe can actually slot it out and distribute it more15:38
mnaserif we have more space and time15:38
fungii'm still unconvinced meetings should be for discussing things. that's where i think our old meetings failed us15:38
* lbragstad was under the assumption the meetings would only contain administrative stuff15:39
smcginnisWe still have all the reasons for https://governance.openstack.org/tc/resolutions/20170425-drop-tc-weekly-meetings.html , we're discouraging APAC participation *right after* we just had a big move to better encourage it, and discussions should be at any point here or on the ML.15:39
smcginnisfungi: ++15:39
zanebmnaser: the point is, by not having frequent meetings we're able to discuss stuff *outside* of meetings so we have *more* time15:39
smcginnislbragstad: That is my hope.15:39
TheJuliafungi: ++15:39
mnaseri dont think that our meetings were going to be some "board meeting" style15:39
lbragstadmnaser it sounds like you think meetings should contain more content than just administrative things?15:39
smcginnisThe less frequently we have meetings, the more likely we will have discussions outside of them.15:39
mnaseradministrative but also slots for community members to ask for subjects to bring up that are important for them15:40
mnaserjust look at this office hour so far15:40
mnaserit's nothing but tc15:40
mnaserand if you tell me anyone right now will come up and propose a subject while we all discuss this..15:40
mnaseri doubt they would15:40
smcginnisWhich is a failing of ours that we waited for office hour to talk about this.15:40
mnaserso we stop discussing in office hours then, we listen.15:41
lbragstadthis could have been a meeting thing (meta-meeting discussions ftw)15:41
TheJulialbragstad: but we're not logging it15:41
fungiwe're logging it15:41
mnaserso for example this very discussion15:41
TheJuliawell, kind of yeah15:41
mnaserthat we have15:41
lbragstadwhich would open up office hours for the discussions your hoping to have15:41
fungikind of completely logging it15:41
mnasercommunity members cant actually really see a lot of it15:41
TheJuliafungi: I know, but it is not an explicit meeting log15:41
mnaserlets be honest, who would be like "hey today i'm gonna open eavesdrop.openstack.org and read all through #openstack-tc"15:41
mnaserthat's just unrealistic15:42
TheJuliaWe need to reach consensus on purposes, we're quite literally all over the  map15:42
mnaserevery office hour is essentially a meeting15:42
mnaserthat's whats happening.15:42
mnaserwe just dont want to call it a meeting15:42
TheJuliamnaser: and I think that was fungi's point regarding the requirement15:42
mnaserthe heavy discussion happens in office hours15:42
evrardjpsmcginnis: agreed with you there15:42
fungio15:43
fungier15:43
fungii'm good with discussing these things outside office hours15:43
mnaserand IMHO talking more outside office hours15:43
fungithroughout the week15:43
mnasermakes it even more stressful for external members to keep up with this15:43
dhellmannI did start this conversation on the mailing list. I thought we more or less had consensus there before I started writing patches. Could we have concluded this conversation in either of those places?15:43
fungiand we *did* discuss this earlier in the week outside office hours too15:43
mnasersomeone who wants to know what's going on with the tc but doesn't read logs everyday will have no idea whats going on15:43
TheJuliabut their level of caring about what is going on is likely at a completely different level15:44
fungibut really unless we get more diligent about moving these discussions to the mailing list (at which point it will be at least as much text) we're not fitting this sort of volume of discussion into an official timeboxed meeting so people who want to see what we're discussing are not going to be able to get that from meeting minutes15:44
TheJuliaand office hours level topics might not make much sense for many contributors to find out what is going on15:45
mnaserTheJulia: you'd be surprised at how many people want to know whats going on but just cant keeu p15:45
mnaserthe *board* we report to cant even keep up with us, and they care.15:45
TheJuliaThe positive outcome of holding a fixed meeting with an agenda is you have an easily digestible output. The thing that we're hitting here is we have different desired end results.15:45
mnaserTheJulia: i think you really summarize what is the outcome i want there15:46
evrardjpwell we have many efforts, I'd like to understand how we're gonna work15:46
fungialso that an easily-digestible uotput is a fiction since we're going to discuss a lot more than we can fit into even a weekly hour-long meeting15:46
mnaserit's letting people digest what we do easier, and also making it easy to be slotted in15:46
evrardjpI think we should let dhellmann give his vision, and we should follow him then15:46
TheJuliaYou know, it is okay to change, pivot, adjust15:47
mnaserTheJulia: ++15:47
TheJuliawe just have to have a measurable output15:47
lbragstad+1 if we need to adjust we should be able to do so15:47
mnaseri don't plan to have this hard set in stone, it might suck for the first few times, and then we'll nail it down15:47
TheJuliaso if we go monthly and find we need more often, then so be it. Perhaps we change the standing topics up between meetings15:47
mnaserTheJulia: i worry that no one will ever say "we need to meet more often"15:48
fungithis is why i think if the goal is to provide some periodic report of what we're doing for the sake of people who best consume that via meeting minutes, the meetings should just be summarizing and reporting prior discussions, not actually discussing things15:48
mnaserits easier to skip meetings than ask to plan for more, imho.15:48
TheJuliabut also, we quite literally can't address every contingency, case issue, or desire in a singular solution.15:48
mnasermaybe we should just15:48
mnaserdelete #openstack-tc15:48
mnaserthat'll force us all on the ML :D15:48
fungithere are plenty of people in the community who would like to just delete the tc entirely ;)15:49
*** jamesmcarthur has quit IRC15:49
mnaseror come up with a no-irc-discussion policy15:49
smcginnisI feel dhellmann's weekly TC email is the proper medium for communicating "what is the TC doing". Meeting logs, channel logs, and ML posts are all the sausage making.15:49
fungismcginnis: i agree with you, but i'm hearing people say that there is some audience who won't read those but will read meeting minutes for some reason15:49
*** annabelleB has quit IRC15:49
smcginnisThen those people can read the logs if they wish.15:50
mnaserwe can't just have open discussion all the time, it just doesn't work honestly15:50
TheJuliamnaser: ++15:50
mnaserit's hard for all of us to keep up15:50
mnaserthe VERY example of this failing is literally this conversation15:50
mnaserare we meeting? are we not? are discussing every week or every 2 weeks or every month?15:51
smcginnisIf we can't have open discussions without a set time block, then I agree with those that the tc should be disbanded. We've failed.15:51
mnaserno management entity exists to discuss 24/715:51
*** jamesmcarthur has joined #openstack-tc15:52
TheJuliasmcginnis: There are different types of discussions15:52
fungiwe don't discuss 24x7, we discuss asynchronously with varying degrees of synchronicity15:52
smcginnisfungi: ++15:52
mnaserfungi: but that has made it hard for us to consume information and for those who want to know what we're doing as well15:52
smcginnisTheJulia: If the desired output is somewhere someone can catch up on what we are doing, then we need to work together on making Doug's weekly email meet those needs.15:52
TheJuliaIf we set a time, and hold to it.... then we can increase the synchronous discussion for important topics, but we also need to stay on topic15:52
fungiright this moment the discussion is much more synchronous, but other times this week i've responded to comments from the previous day15:52
dhellmannsmcginnis : yeah, I could use some help with those15:52
mnaserfungi: which is confusing and difficult.15:53
*** dklyle has quit IRC15:53
mnaserwho really here reads every single message in #openstack-tc, honestly.15:53
smcginniso/15:53
fungii find it less confusing and difficult than discussing in a formal meeting, but that may simply be me15:53
zanebI read at least 95%15:53
mnaserbecause i remember we all had a lot to do and i find times where i get so unreasonably behind15:54
TheJuliaI'm more towards 90-95%, and sometimes I don't immediately grok because context is not clearly set as to the topic of discussion15:54
fungiif we go back to formal meetings, i'll likely go back to not synchronously participating in the meetings because it's too hard to get a word in edgewise. i can follow up after the meeting once i've had a time to read15:54
TheJuliaIf we try to recall the topic that we started with, can we?15:54
mnasermonthly vs biweekly meetings, and content of meetings15:55
fungiand whether meetings were simply to meet a bylaws requirement or something we found useful in the past15:55
TheJuliawell, content was our first discussion pivot15:55
TheJuliafungi: that was the second pivot15:55
mnaseralso: i'd like to say that the tc members have changed over time, so if a group of people couldnt make meetings useful, doesnt mean the rest cant15:56
dhellmannwould it work if we said topics need to be raised on the mailing list in advance of the meeting, and that the meetings would not go into deep discussions?15:56
fungii agree, and i'm not against trying again, i just don't expect i'll be chiming in much if at all15:56
mnaserdhellmann: i think that's how it should work. an agenda prepared well in advance.15:56
TheJuliadhellmann: I like that idea15:57
dhellmannmnaser : that's not the same thing as what I said15:57
dhellmannI said we wouldn't go deep on any topics, either.15:57
dhellmannso we would talk about the fact that an issue was still under discussion, or agree that it had been resolved, but not get into the details15:58
TheJulia"Do we have consensus, yes/no?" "Do we need to have further discussion on this, yes/no?"15:58
dhellmannright15:58
TheJuliaWe can table that discussion15:58
dhellmannand if so, go back to the ML15:58
TheJuliaexactly15:58
*** dklyle has joined #openstack-tc15:58
dhellmannI'm not sure that really meets what mnaser is trying to accomplish15:59
TheJuliaI would concur with that assessment15:59
mnaserdhellmann: i think i would be ok with this15:59
TheJuliamnaser: do you feel that we could use it as an information source for broadcasting outward?16:00
dhellmannok, so I think that covers the agenda question16:00
dhellmannit leaves open the question of how often we need to do that, though16:00
mnaserTheJulia: yes, that's what i took time to think a bit about16:00
mnaserbecause the answer to those questions will say "the tc has figured out x but is still thinking about y and working on z"16:00
*** dtantsur is now known as dtantsur|afk16:00
mnaserdhellmann: if we have that discussion every month, we should have a no-tc-discussion-during-office-hours rule16:01
lbragstadso long as it is concise in meeting minutes, i think it would be easier for others to consuem16:01
TheJuliamnaser: I think there is value in discussion, but ensuring we have consensus should not be restricted or limited to office hours. This time should be "how can we help each other?" "how can we help others in the community?"16:02
mnaseron second thought, we probably should always work a no-tc-discussion-during-office-hours type of rule anyways16:02
fungii'm good with keeping office hours for community interaction and having discussions about random topics between tc members outside office hours (and also on the mailing list as much as possible)16:02
mnaserTheJulia: but it ends up with deep discussions that members probably have a hard time interjecting16:02
*** annabelleB has joined #openstack-tc16:03
mnaseri still feel like having those lightweight meetings that doug proposes every 2 weeks is reasonable16:03
TheJuliamnaser: We are not going to be able to prevent that. It will occur regardless of restrictions, we will just end up shifting visibility16:03
mnaserbecause every month might be a very long time16:03
mnaserTheJulia: i'm sure people see us talk plenty outside those hours :)16:03
mnaserheck, we can even try inviting members to office hours and say16:03
* lbragstad has to run - will read scrollback16:03
mnaserhey $select_projects, we'd love for you to come hangout for this office hour16:04
mnaserwe wanna chat, learn a bit more about you, how are things going, do you need help16:04
TheJuliaWe're not going to get them all, but we could have a standing "Anything from project leaders?" topic16:04
mnasermake it a social event to avoid a dead office hour i guess16:04
TheJuliatime box it to 10 minutes or something16:04
dhellmannTheJulia : during the meeting?16:04
TheJuliadhellmann: possibly, I'm just tossing that idea out there16:05
* TheJulia suspects it will not stick and we can move on16:05
dhellmannTheJulia : sure, I'm just making sure I'm clear on what you're saying16:05
TheJuliadhellmann: ack16:05
*** annabelleB has quit IRC16:05
mnaserdhellmann: TheJulia: i think it's probably better if a project wants to bring up soemthing they can email the tc16:06
TheJuliamnaser: social events are good for community building. There is some value in building relationships... but that also seems like noise to other discussion, but it is important. Like me getting married this week. Only a couple people in this channel would have even had a clue otherwise16:06
TheJuliamnaser: mailing list imho :)16:06
mnaserTheJulia: late congrats :D16:06
mnaser(boots totally work btw)16:06
TheJuliamnaser: thanks16:06
TheJulia<316:07
dimscongrats @TheJulia ! :)16:07
* TheJulia steps away for a couple minutes to take away whatever toy the kitten has found16:07
mnaserbut yeah, lets make office hours somewhere that we attract community members and keep the meetings as following up on the state of things16:07
*** jamesmcarthur has quit IRC16:08
TheJulia1M * '+'16:08
dhellmannspeaking of hours, we're a bit over right now and I have an appointment I have to go to16:09
dhellmannI think this was useful for at least clarifying what folks want out of the meetings16:09
TheJuliaSo back to the topic at hand, lets go back and vote with what we feel is acceptable to ourselves, keeping in mind it is okay and likely expected for us to pivot16:09
dhellmannplease go vote on the 2 timing patches, and take any further discussion to the mailing list thread16:09
dims++ dhellmann16:10
dhellmanntc-members: a reminder, I'm going to be out 13-28 Oct, and mnaser will act as chair while I'm away16:10
TheJuliadhellmann: thanks! Have a wonderful time away!16:11
mnaser(we have the house all for ourselves, let's have a big party)16:11
zaneblol :D16:12
TheJuliamnaser: and invite everyone?16:12
mnaserheck ya16:13
mnaserpush up those governance changes to include that all tc members get fancy food and unlimited alcohol at every events16:13
TheJuliaMy doctor will likely express displeasure at that16:15
*** jamesmcarthur has joined #openstack-tc16:29
*** gouthamr has quit IRC16:34
*** jpich has quit IRC16:38
*** mriedem is now known as mriedem_afk16:43
*** dklyle has quit IRC17:04
jrollmnaser | who really here reads every single message in #openstack-tc, honestly. <- me17:07
mnaserjroll: that very message is proof :P17:07
jrollikr17:07
jrollI read a not-quite-a-meeting about meetings!17:07
fungisoon perhaps we can have a meeting about not-quite meetings to balance it out17:21
*** jamesmcarthur has quit IRC17:34
*** dklyle has joined #openstack-tc17:35
smcginnisWe should schedule a meeting to discuss it.17:38
*** jamesmcarthur has joined #openstack-tc17:39
*** ianychoi has quit IRC17:41
*** jamesmcarthur has quit IRC17:56
*** jamesmcarthur has joined #openstack-tc17:57
*** jamesmcarthur has quit IRC18:02
*** mriedem_afk is now known as mriedem18:09
*** gouthamr_ has joined #openstack-tc18:25
*** openstackstatus has quit IRC18:28
*** jamesmcarthur has joined #openstack-tc18:29
*** openstackstatus has joined #openstack-tc18:30
*** ChanServ sets mode: +v openstackstatus18:30
TheJuliaShould there be specific constraints for that meeting?18:36
*** jamesmcarthur has quit IRC19:03
*** tosky__ has joined #openstack-tc20:16
*** tosky has quit IRC20:17
*** clarkb has quit IRC20:18
*** clarkb has joined #openstack-tc20:19
*** tosky__ is now known as tosky20:23
*** gouthamr_ is now known as gouthamr21:53
dhellmanntc-members: here's another interesting article from Nadia Eghbal, this time about supporting open source projects: https://nadiaeghbal.com/user-support22:06
dhellmannthe change over time in motivation for maintainers vs. users was an interesting observation that may apply to us22:06
dhellmannthe bit about bug reporting templates seems like something for the storyboard team, too22:07
clarkbdhellmann: one thing I took from it is that research may also explain some of the interactions we've got with various parts of the community. Like with user committee/AUC looking for a home.22:07
clarkbin other communities they seem to be far more integrated as part of the support scaffolding22:07
dhellmannyeah, interesting22:07
dhellmannmrhillsman, maybe you have thoughts on that? ^22:08
clarkbansible in particular was called out as having people doing a lot of support that don't necessarily have a ton of commits in the codebase22:08
dhellmannI wonder if it has implications for our plan to merge all of the mailing lists22:08
dhellmannI still think being able to observe support-related traffic would be useful, fwiw22:09
clarkbdhellmann: beyond the issue tracker(s), mailing lists, and IRC?22:12
clarkb(we should be able to observe all of that traffic today)22:12
clarkbask.openstack.org too22:12
dhellmannthe article/research implies that combining the lists isn't going to automatically make it more likely that developers are going to start answering more questions from users22:12
dhellmannby "observe" I mean "I want to read"22:12
dhellmannrather than meausre22:13
dhellmannI'm not doing that with the bug trackers or ask.o.o but I'm on all of the mailing lists today22:13
clarkboh got it, yup I think even if it doesn't cause people to support more users, it should make it easier for that to happen or to loop in specific individuals once traige is done22:14
dhellmannyeah, that's a good point22:15
dhellmannand I don't think that was a significant factor in our decision anyway. avoiding fracturing the community was the main thing in my mind, at least22:15
*** openstackgerrit has joined #openstack-tc22:20
*** mriedem is now known as mriedem_gone22:23
*** mriedem_gone has quit IRC22:24
*** openstackstatus has quit IRC22:28
*** openstackstatus has joined #openstack-tc22:29
*** ChanServ sets mode: +v openstackstatus22:29
dimsthanks dhellmann queued it up for reading22:32
fungiyeah, it had some good design consideration takeaways for the storyboard team too22:33
fungii removed three retired teams and added one new team to https://wiki.openstack.org/wiki/OpenStack_health_tracker#Project_Teams22:39
fungiit should now match https://governance.openstack.org/tc/reference/projects/22:39
fungii also split the board committees/working groups from the uc teams/working groups and synced them up with their respective governance pages22:59
fungiand i added a couple of missing sigs23:02
*** tosky has quit IRC23:15
*** spotz has quit IRC23:17
*** spotz has joined #openstack-tc23:55
*** lbragstad has quit IRC23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!