| *** jamesmcarthur has joined #openstack-tc | 00:58 | |
| *** marst has joined #openstack-tc | 01:31 | |
| *** lbragstad has joined #openstack-tc | 01:40 | |
| *** jamesmcarthur has quit IRC | 01:45 | |
| *** jamesmcarthur has joined #openstack-tc | 01:55 | |
| *** jamesmcarthur has quit IRC | 02:06 | |
| *** jamesmcarthur_ has joined #openstack-tc | 02:06 | |
| *** lbragstad has quit IRC | 02:17 | |
| *** irclogbot_3 has quit IRC | 02:23 | |
| *** edmondsw has quit IRC | 02:26 | |
| *** ricolin has joined #openstack-tc | 02:35 | |
| *** marst has quit IRC | 02:40 | |
| mnaser | tc-members: we have not made much progress following up on https://review.openstack.org/#/c/639376/ and https://review.openstack.org/#/c/639010/ -- i would like to propose an adhoc meeting for this. any objections? | 02:53 |
|---|---|---|
| gmann | mnaser: +1 for adhoc meeting. you want to have adhoc meeting to discuss/online review the specs one by one or about plan on review etc | 02:55 |
| *** jamesmcarthur_ has quit IRC | 02:59 | |
| mnaser | gmann: i think it would be good for tc members to go over them and we can discuss them throughly to iterate and get a mergable copy so teams can plan for the ptg for this (within the timelines lance proposed) | 03:01 |
| gmann | ok. make sense. +1 | 03:03 |
| *** whoami-rajat has joined #openstack-tc | 03:46 | |
| *** jaosorior has joined #openstack-tc | 05:45 | |
| *** e0ne has joined #openstack-tc | 06:40 | |
| *** Luzi has joined #openstack-tc | 06:53 | |
| *** jaosorior has quit IRC | 06:58 | |
| *** e0ne has quit IRC | 07:02 | |
| *** jaosorior has joined #openstack-tc | 07:11 | |
| *** jaosorior has quit IRC | 07:35 | |
| *** jaosorior has joined #openstack-tc | 07:44 | |
| *** jaosorior has quit IRC | 07:44 | |
| *** tosky has joined #openstack-tc | 08:05 | |
| *** tosky has quit IRC | 08:07 | |
| *** tosky has joined #openstack-tc | 08:25 | |
| *** dtantsur|afk is now known as dtantsur | 09:11 | |
| ttx | +1 | 09:32 |
| ttx | We'll likely want an ad-hoc meeting to discuss leaderless projects too | 10:02 |
| *** e0ne has joined #openstack-tc | 10:28 | |
| *** edmondsw has joined #openstack-tc | 11:50 | |
| *** jaosorior has joined #openstack-tc | 11:51 | |
| *** whoami-rajat has quit IRC | 12:35 | |
| *** ijolliffe has joined #openstack-tc | 12:43 | |
| fungi | yes, if memory serves how we handled it last time was to have the election officials propose the updated ptl list to governance based on election results and with the leaderless teams having a placeholder string, then volunteers can propose patches replacing that placeholder with their information and adding or updating an appointed list with the upcoming cycle name, then we discuss those volunteers and | 12:47 |
| fungi | also any other options we might want to exercise | 12:47 |
| *** e0ne has quit IRC | 12:51 | |
| *** e0ne has joined #openstack-tc | 12:52 | |
| dhellmann | that matches my memory | 12:56 |
| *** mriedem has joined #openstack-tc | 12:58 | |
| *** whoami-rajat has joined #openstack-tc | 13:08 | |
| *** lbragstad has joined #openstack-tc | 13:18 | |
| *** needssleep is now known as TheJulia | 13:18 | |
| *** marst has joined #openstack-tc | 13:26 | |
| mnaser | ttx: what was that open source based service that was like doodle? | 13:34 |
| mnaser | for scheduling time | 13:35 |
| *** marst has quit IRC | 13:41 | |
| zaneb | mnaser: framadate | 13:44 |
| ttx | framadate.org | 13:44 |
| * cmurphy takes note | 13:45 | |
| mnaser | something i struggle with is coming up with _when_ to potentially schedule these meetings :\ | 13:47 |
| mnaser | if we had some pre-existing slot we all agreed on in advance it's easy to point back at it | 13:48 |
| mnaser | as i think if we setup this 'meeting', it would be good to have the community know in advance about it as well | 13:48 |
| mnaser | having some of our potential goal champions being here makes a lot of sense too | 13:48 |
| mnaser | how do we feel about coming up with a slot of time once a week that we can exercise/meet if need/want to, that way we can reuse it every week? | 13:49 |
| zaneb | mnaser: potential goal champions are in completely opposite time zones though, so I'm not sure that having a standing slot is going to be able to solve that problem | 13:51 |
| mnaser | zaneb: maybe two different slots that we can choose through to accommodate them or pick which one works best | 13:51 |
| zaneb | yeah, that could work | 13:51 |
| mnaser | that way i can (somewhat) assume the tc members will be (somewhat) available in those slots rather than really guess what works over the next few days | 13:52 |
| dhellmann | mnaser : what about just using our office hour slots, with a pre-announced topic? | 13:57 |
| dhellmann | I assume at least some of us have already carved out those times in our schedules | 13:57 |
| *** e0ne has quit IRC | 13:58 | |
| *** e0ne has joined #openstack-tc | 14:05 | |
| *** marst has joined #openstack-tc | 14:07 | |
| bauzas | ttx: pro-tip: framadate can be self-hosted if we go using it :p | 14:16 |
| ttx | bauzas: yes, but I like teh opportunity to point to Framasoft's un-Googlisation effort | 14:18 |
| bauzas | ttx: oh I know :) https://twitter.com/charlesbouttaz/status/956797379222654976?lang=fr | 14:20 |
| jroll | I would be fine with using an existing office hours slot for these | 14:34 |
| fungi | or the slot we've already agreed to use for our monthly-ish meetings | 14:36 |
| fungi | nothing says we can't do meetings during that time on the off-weeks, and also keeps the meeting volume a little better spread out | 14:36 |
| fungi | (that is to say, we're less inclined to schedule an ad hoc meeting in the same week as our monthly meeting) | 14:37 |
| zaneb | +1 on using that for one of the slots | 14:37 |
| *** e0ne has quit IRC | 14:41 | |
| *** e0ne has joined #openstack-tc | 14:42 | |
| *** e0ne has quit IRC | 14:53 | |
| *** e0ne has joined #openstack-tc | 14:55 | |
| TheJulia | ++ | 14:58 |
| *** jamesmcarthur has joined #openstack-tc | 15:02 | |
| *** e0ne has quit IRC | 15:05 | |
| *** Luzi has quit IRC | 15:13 | |
| *** e0ne has joined #openstack-tc | 15:20 | |
| *** weshay|rover is now known as weshay | 16:02 | |
| *** e0ne has quit IRC | 16:14 | |
| *** e0ne has joined #openstack-tc | 16:19 | |
| *** diablo_rojo has joined #openstack-tc | 16:33 | |
| mnaser | the suggestion to use office hours seems very reasonable | 16:46 |
| mnaser | tc-members: https://framadate.org/1Q5i7gqQsZDH9dBQ -- i'll post to the ML | 16:50 |
| ricolin | ++ | 16:50 |
| mnaser | tc-members: in case you're not subscribed to foundation@lists.openstack.org -- claire has sent an invite for the upcoming board meeting. https://wiki.openstack.org/wiki/Governance/Foundation/8April2019BoardMeeting | 16:54 |
| fungi | this is the one where kata and zuul are likely to be presenting their confirmation requests | 16:54 |
| mnaser | fungi: do you know if they will be making a request to be voted on or making a request where a follow up meeting will have a confirmation afterwards (jbryce might have input) | 16:56 |
| mnaser | i'm just trying to gauge this within the scope of perhaps having the tc involved in the process, if we need to be involved _before_ the 8th or after | 16:57 |
| fungi | i think it's the meeting at which the board will either vote on the movement to confirm, or choose to defer | 17:00 |
| fungi | i think we need to be involved before the 9th | 17:00 |
| fungi | er, before the 8th | 17:00 |
| dhellmann | yes, that's why jbryce has been asking us how we want to do that | 17:05 |
| fungi | basically, tc members with knowledge of these projects should raise any concerns with the board before they meet (and honestly if nobody on the tc is familiar with them then that's a concern too) | 17:05 |
| fungi | we could do so my collaboratively drafting a resolution, though that seems heavy-handed | 17:06 |
| fungi | and i doubt they're seeking that level of formality anyway | 17:07 |
| fungi | i think the goal is that if we have verifiable/substantiated concerns, then we let the board know so they can decide if they share those concerns | 17:08 |
| fungi | what the tc wants is to make sure that they don't approve a project and then later discover that we disapproved of the choice, or that there were issues we knew about before hand which hadn't been brought to their attention | 17:11 |
| fungi | er, what the *board* wants i mean | 17:11 |
| fungi | keepnig tat in mind i think helps frame the scope of our expected feedback | 17:13 |
| fungi | keeping that... sheesh i can't type today | 17:13 |
| *** e0ne has quit IRC | 17:14 | |
| fungi | so a lightweight process could be to solicit input from tc members and even the openstack community at large in an etherpad, then clean it up a little and have someone (perhaps the chair) post it to the foundation ml | 17:14 |
| mnaser | fungi: right, but the thing is we don't have the material to base our info on. | 17:27 |
| mnaser | having the slides that will be presented would be nice, as a quick overview. i don't want to assume our entire community and tc members know exactly what kata and/or starlingx do | 17:28 |
| fungi | mnaser: in my opinion, we're not being asked to render our opinion on the pilot project's slide deck or even their application for confirmation, we're being asked to weigh in on the project itself based on information we already have over the course of its pilot phase | 17:30 |
| fungi | if most of the tc don't know what kata and zuul do, then that's great feedback to provide as it means those pilot projects haven't been integrating with other osf projects successfully (that's one of the points in the confirmation guidelines) | 17:31 |
| mnaser | that's fair | 17:31 |
| fungi | if most of the tc don't know what airship and starlingx do, that's probably good to rectify soon but not as important since it doesn't sound like they're applying to be confirmed yet | 17:32 |
| fungi | i think if we just limit our feedback to interactions and concerns we already have day-to-day with these projects (or lack of interaction for that matter) then that's probably sufficient | 17:33 |
| mnaser | i think perhaps as a first step, perhaps we should open up an etherpad for every project and start leaving small points, which we can then switch to something more digestable afterwards. how does this sound? | 17:33 |
| fungi | sure, that sounds like exactly what i suggested | 17:35 |
| mnaser | fungi: indeed that was your suggestion which now all makes sense | 17:35 |
| fungi | cool, want me to start pads for openstack tc feedback on kata and zuul and mention them in posts to openstack-discuss? | 17:36 |
| mnaser | fungi: that'd be great. perhaps even recommended some sort of 'deadline' so we can be on schedule | 17:36 |
| *** jamesmcarthur has quit IRC | 17:38 | |
| fungi | yeah, i'll propose that we finalize the content to send to the board via the foundation ml on monday april 1 (wow maybe i should make that april 2?) so as to be a week before the board meeting | 17:38 |
| gmann | mnaser: fungi : in etherpad, are we going to have list of questioner or evaluation points where we can add our feedback ? integration to other OSF projects is one good point fungi mentioned. | 17:39 |
| *** jamesmcarthur has joined #openstack-tc | 17:39 | |
| mnaser | gmann, fungi: https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines having that in there would be good thing to follow | 17:39 |
| gmann | +1, that will be nice | 17:40 |
| mnaser | fungi: a week seems plenty for us to clean things up for a consumable format to the board, and gives 2 weeks for community at large | 17:40 |
| fungi | i'll link that and the feedback thread from the foundation ml at the top of each etherpad | 17:40 |
| *** ricolin has quit IRC | 17:41 | |
| mnaser | thank you once again fungi :) | 17:42 |
| mnaser | tc-members: we have a full day at the ptg so we can need to get planning -- http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003916.html -- who can pick this up please? this is a great way of getting your feet wet if you're new to the tc :) | 17:43 |
| jbryce | One point I'd add to the comments about pilot project confirmation feedback is that it doesn't just need to be concerns. If there are positive opinions about a project or its usefulness (e.g. my zuul example from the mailing list) that could also be valuable | 17:57 |
| fungi | yep, i see those as valuable though less critical. but in the spirit of positivity i'm mentioning positive feedback before negative ;) | 17:58 |
| fungi | "...useful examples for how the project does or does not meet this or other guidelines..." | 17:59 |
| fungi | just about done drafting the preamble to the two etherpads, which will also comprise most of my messages to the ml | 17:59 |
| *** ijolliffe has quit IRC | 18:00 | |
| *** ijolliffe has joined #openstack-tc | 18:00 | |
| *** ijolliffe has quit IRC | 18:01 | |
| mnaser | imho just going over the guidelines and leaving comments about each point to me sounds like its the best thing to do | 18:10 |
| fungi | yep, that's basically how i'm laying out the pads | 18:17 |
| gmann | yeah, how much we can fill for each point will be good way to feed. | 18:17 |
| fungi | https://etherpad.openstack.org/p/openstack-tc-kata-confirmation-feedback and https://etherpad.openstack.org/p/openstack-tc-zuul-confirmation-feedback for the record | 18:17 |
| fungi | working on e-mail to the community about those now | 18:18 |
| fungi | i guess if we're directing feedback to the etherpad, i can get away with doing one message to the ml for the pair of pads | 18:20 |
| *** dtantsur is now known as dtantsur|afk | 18:23 | |
| *** gmann is now known as gmann_afk | 18:34 | |
| *** jamesmcarthur has quit IRC | 18:41 | |
| fungi | pads mentioned in http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003938.html | 18:43 |
| *** mriedem has quit IRC | 18:45 | |
| *** mriedem has joined #openstack-tc | 18:48 | |
| *** jamesmcarthur has joined #openstack-tc | 18:56 | |
| *** gmann_afk is now known as gmann | 18:56 | |
| *** jamesmcarthur has quit IRC | 19:00 | |
| *** jamesmcarthur has joined #openstack-tc | 19:18 | |
| *** jamesmcarthur has quit IRC | 19:19 | |
| *** jamesmcarthur has joined #openstack-tc | 19:23 | |
| *** whoami-rajat has quit IRC | 19:55 | |
| *** jamesmcarthur has quit IRC | 20:00 | |
| *** jamesmcarthur has joined #openstack-tc | 20:09 | |
| *** jamesmcarthur has quit IRC | 20:10 | |
| *** jamesmcarthur has joined #openstack-tc | 20:10 | |
| *** irclogbot_3 has joined #openstack-tc | 20:11 | |
| *** dklyle has quit IRC | 20:14 | |
| *** dklyle has joined #openstack-tc | 20:18 | |
| *** irclogbot_3 has quit IRC | 20:25 | |
| *** irclogbot_3 has joined #openstack-tc | 20:26 | |
| *** e0ne has joined #openstack-tc | 20:28 | |
| *** e0ne has quit IRC | 20:41 | |
| mnaser | asettle, fungi, jroll, TheJulia, ricolin: https://review.openstack.org/#/c/642272/ this change doesn't have your vote yet but it's ready to merge. just wanted to check-in if there's a reason behind the non-vote or if there's any strong objections :) | 20:56 |
| jroll | mnaser: mostly just still catching up from being in irl meetings all last week :) | 20:57 |
| mnaser | what's irl | 20:57 |
| jroll | in real life | 20:57 |
| mnaser | i just know irc | 20:57 |
| mnaser | :p | 20:57 |
| jroll | heh | 20:57 |
| jroll | and RC+1 | 21:00 |
| diablo_rojo | As you all go about your weeks and chat with other PTLs can you help me advocate for getting release highlights done? And if anyone has questions to send them to me? | 21:16 |
| diablo_rojo | I think there are only like a half a dozen projects that have them done at this point. | 21:16 |
| smcginnis | diablo_rojo: It might be good to have a note published to the ML from you reminding folks of that. | 21:19 |
| smcginnis | Maybe tag it [ptl] | 21:19 |
| mnaser | i think these release highlights are pretty important | 21:19 |
| mnaser | it's important because it helps the foundation marketing staff know that things are still going on here | 21:20 |
| diablo_rojo | smcginnis, will do | 21:22 |
| diablo_rojo | mnaser, helps me out as I am the one that got roped into collecting that stuff for the marketing machine to process. | 21:22 |
| mnaser | should we make having cycle highlights some sort of requirement.. just like releasing? :x | 21:23 |
| *** irclogbot_3 has quit IRC | 21:26 | |
| *** irclogbot_3 has joined #openstack-tc | 21:27 | |
| cmurphy | diablo_rojo: deadline for that is in two weeks right? https://releases.openstack.org/stein/schedule.html | 21:28 |
| diablo_rojo | cmurphy, deadline is RC1 I think, not final RCs | 21:31 |
| diablo_rojo | Yeah RC1 | 21:31 |
| diablo_rojo | Otherwise the marketing team wouldnt have enough time to do their processing/make prettying | 21:32 |
| diablo_rojo | So.. they are due this week. | 21:32 |
| cmurphy | oh crap | 21:32 |
| diablo_rojo | cmurphy, lol if there is anything I can do to help let me know? | 21:32 |
| smcginnis | cmurphy, diablo_rojo: We'd like to get them now, but we've always stated final RC was the deadline. | 21:33 |
| smcginnis | Hopefully most teams know what their highlights will be by this point though. | 21:33 |
| cmurphy | i already pushed a wip i just need feedback from the team | 21:34 |
| diablo_rojo | smcginnis, lol then the process doc is wrong | 21:34 |
| smcginnis | diablo_rojo: Yeah, I'm noticing that. | 21:34 |
| smcginnis | diablo_rojo: We have the countdown email and the doc saying RC1, but the published schedule since we started tracking them has been final RC. | 21:35 |
| diablo_rojo | For my sanity I would love for them to get populated starting at m2 but I know thats not the most feasible. | 21:35 |
| diablo_rojo | I think RC1 being the deadline should be doable? Or we need to make the distinction that we will still accept them, but that they might not be a part of the final press release that gets created if they come in later. | 21:36 |
| diablo_rojo | I have the marketing team wanting to meet this Thursday.. | 21:36 |
| smcginnis | I think that's what we've said before. They can be added after the deadline for maybe some historical value, but that's too late for marketing to really do anything with them. | 21:38 |
| diablo_rojo | smcginnis, testing the schedule change now and then will push the patch and get the email out after | 21:42 |
| fungi | it's not just the marketing team that these matter for either, aside from the likelihood that they're referred to by a lot of our extended community, it's also where industry press and analysts are sent for official documentation of the big things we got done in a given release cycle | 21:43 |
| smcginnis | fungi: I don't think that was intended. For example, we don't link to it anywhere. Anne wanted these to be the raw input that they process to know what to share with those folks. | 21:46 |
| smcginnis | Not that that isn't what ends up happening, but that wasn't the goal. | 21:46 |
| fungi | ahh, i thought we did have links into the cycle highlights. maybe that was for a later iteration after we'd done it for a few cycles and saw whether it was working out | 21:48 |
| fungi | but regardless, the information gets circulated to a variety of folks outside just the foundation marketing team, even if they massage it a bit first and come up with distilled subsets for press releases and whatnot | 21:49 |
| fungi | on the subject of supported runtimes, what go-based projects do we actually have in openstack? there was the piece of swift which i think eventually just died on a feature branch, and then some project which was going to apply to be part of openstack but i can't recall which one it was | 21:52 |
| smcginnis | None that I'm aware of. That's why I punted on adding that for stein. :) | 21:52 |
| TheJulia | mnaser: somewhat the same reason as jroll. Sadly not irl, but lots and lots of virtual meetings :( | 21:54 |
| * fungi virtually has a real life | 21:56 | |
| * fungi really has a virtual life though | 21:56 | |
| * TheJulia wonders if virtual life results in becoming like Minbari | 22:00 | |
| * TheJulia has virtual life, irc, the occasional donation and non-profit merriment, quests to obtain cat foot, and runs to the home improvement/food stores. | 22:00 | |
| notmyname | smcginnis: fungi: I see references to swift and golang, but I'm not sure of the context of if it's something I need to pay attention to | 22:07 |
| fungi | notmyname: i was just trying to recall the extent to which there is any golang represented in official openstack projects | 22:13 |
| fungi | the hummingbird feature branch never merged to swift did it? | 22:13 |
| fungi | the context is the proposal for tested runtimes in the train cycle https://review.openstack.org/642272 | 22:14 |
| notmyname | that patch seems fine to me, wrt golang in swift | 22:15 |
| notmyname | ie "no official, defined golang version" | 22:15 |
| fungi | cool, thanks for looking! | 22:15 |
| *** marst has quit IRC | 22:17 | |
| fungi | TheJulia: i rather wonder if virtual life results in becoming like the vorlon | 22:52 |
| TheJulia | fungi: Great question, but I would like to pass on the encounter suit | 23:08 |
| fungi | dunno, those seemed sorta important | 23:08 |
| fungi | and now i want to pull out the box set and watch b5 all the way through again | 23:09 |
| *** mriedem has quit IRC | 23:20 | |
| *** tosky has quit IRC | 23:48 | |
| *** jamesmcarthur has quit IRC | 23:51 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!