| opendevreview | Rico Lin proposed openstack/governance master: Add project health check tool https://review.opendev.org/c/openstack/governance/+/810037 | 01:25 |
|---|---|---|
| *** rpittau|afk is now known as rpittau | 07:30 | |
| opendevreview | Elod Illes proposed openstack/project-team-guide master: Add section about stable-only patches https://review.opendev.org/c/openstack/project-team-guide/+/810661 | 12:58 |
| *** diablo_rojo is now known as Guest768 | 13:21 | |
| *** Guest768 is now known as diablo_rojo | 14:04 | |
| opendevreview | Merged openstack/governance-sigs master: Modified Cloud Research SIG to active state https://review.opendev.org/c/openstack/governance-sigs/+/809887 | 14:58 |
| gmann | tc-members: meeting time | 15:00 |
| gmann | #startmeeting tc | 15:00 |
| opendevmeet | Meeting started Thu Sep 23 15:00:07 2021 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'tc' | 15:00 |
| gmann | #topic Roll call | 15:00 |
| jungleboyj | o/ | 15:00 |
| gmann | o/ | 15:00 |
| dansmith | o/ | 15:00 |
| ricolin | o/ | 15:01 |
| spotz_ | o/ | 15:01 |
| gmann | let's wait for 1 more min for other tc-members | 15:02 |
| * mnaser is booked in something else but reading | 15:02 | |
| gmann | #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions | 15:03 |
| yoctozepto | o/ | 15:03 |
| gmann | today agenda ^^ | 15:03 |
| diablo_rojo | o/ | 15:03 |
| gmann | #topic Follow up on past action items | 15:03 |
| gmann | no action item from previous meeting | 15:03 |
| gmann | #topic Gate health check (dansmith/yoctozepto) | 15:03 |
| dansmith | I have not noticed any burning issues lately | 15:03 |
| yoctozepto | same here | 15:03 |
| dansmith | which is like, amazing | 15:04 |
| jungleboyj | Seems that things have been running smoothly. | 15:04 |
| jungleboyj | Yeah. Let's not jinx it. | 15:04 |
| gmann | +1, yeah going good in this release. let's hope for same for next 1-2 week too :) | 15:05 |
| gmann | #topic TC tags analysis | 15:05 |
| gmann | #link https://docs.google.com/spreadsheets/d/18GXibtdQnSkIwA7DsBvX9dPwbw9JH76AhhRUknzBb3Q/edit | 15:05 |
| gmann | I have added it a items for next newsletter also #link https://etherpad.opendev.org/p/newsletter-openstack-news | 15:05 |
| gmann | feel free to update wording or so | 15:06 |
| jungleboyj | ++ | 15:06 |
| belmoreira | o/ (late) | 15:06 |
| gmann | yoctozepto: anything else we need to do on this before PTG discussion ? | 15:06 |
| spotz_ | +1 | 15:06 |
| gmann | belmoreira: hi | 15:06 |
| jungleboyj | Just updated the wording a bit. Otherwise looks good. | 15:07 |
| gmann | jungleboyj: thanks | 15:07 |
| yoctozepto | gmann: nothing I can think of | 15:07 |
| jungleboyj | I don't think there is more before the PTG. | 15:07 |
| gmann | yoctozepto: ok, I will remove it from next meeting agenda? | 15:08 |
| yoctozepto | gmann: ++ | 15:08 |
| jungleboyj | ++ | 15:08 |
| gmann | #action gmann to remove 'TC tags analysis' from agenda | 15:08 |
| gmann | #topic Project Health checks framework | 15:08 |
| gmann | #link https://etherpad.opendev.org/p/health_check | 15:08 |
| gmann | #link https://review.opendev.org/c/openstack/governance/+/810037 | 15:08 |
| opendevreview | Rico Lin proposed openstack/governance master: Add project health check tool https://review.opendev.org/c/openstack/governance/+/810037 | 15:08 |
| gmann | thanks ricolin for starting it. | 15:09 |
| ricolin | new patch set^^^ | 15:09 |
| ricolin | It's currently only a tool to pull some status | 15:09 |
| belmoreira | thanks ricolin | 15:09 |
| diablo_rojo | Still that is a good start ricolin :) | 15:09 |
| gmann | we discussed it yesterday and dansmith brought a good point of 'why we're collecting them and what we action to do' | 15:09 |
| jungleboyj | Agreed. | 15:09 |
| gmann | I added the Purpose and Action item section in etherpad at top | 15:10 |
| jungleboyj | That is helpful. | 15:10 |
| ricolin | gmann, thx | 15:10 |
| diablo_rojo | Agreed- we can pull stats all day long, but it doesnt matter if no one looks/ we aren't actually doing anything with them lol | 15:10 |
| gmann | we can go with plan of 1. merge the current tool proposed by ricolin 2. discuss on purpose and action items/labeling the project etc | 15:10 |
| gmann | is it fine? or we want to do both together ? | 15:11 |
| ricolin | +1 on both | 15:11 |
| ricolin | maybe not labeling IMO, but some monthly check will be nice | 15:12 |
| spotz_ | It makes sense to stage the first or wait | 15:12 |
| fungi | yeah, focusing on stats which you expect to actually be useful to inform a decision/action the tc will take is a good way to scope it | 15:13 |
| diablo_rojo | Who's job will that be? to do the monthly check? | 15:13 |
| gmann | TC members | 15:13 |
| diablo_rojo | I feel like if no one is 'assigned' everyone will assume a different TC member will do it? | 15:13 |
| jungleboyj | diablo_rojo: ++ | 15:13 |
| gmann | I feel if we will not label or so then it is hard to proceed to next step/actionable thing | 15:13 |
| dansmith | and is monthly really necessary? | 15:13 |
| belmoreira | however, keeping metrics is also important (It can give us a different overview over time) | 15:14 |
| gmann | not monthly, I will say twice in a cycle | 15:14 |
| diablo_rojo | Yes. I figured TC members would be the ones responsible lol | 15:14 |
| diablo_rojo | dansmith, +1 | 15:14 |
| ricolin | dansmith, or twice a cycle? | 15:14 |
| jungleboyj | dansmith: That does seem excessive. | 15:14 |
| ricolin | like gmann said | 15:14 |
| gmann | diablo_rojo: yeah we can discuss on assignment like we do for goal, gate checks etc | 15:14 |
| jungleboyj | Twice a cycle makes sense. Middle and end ... ? | 15:14 |
| dansmith | twice a cycle seems much better than monthly | 15:14 |
| yoctozepto | ++ | 15:14 |
| ricolin | If you use that tool to run against Sahara or some projects that we have concerns with, it's totally clue there for some of them | 15:14 |
| gmann | middle will be more beneficial like we check and take decision so that release/CI&CD things can be saved during release time | 15:15 |
| ricolin | agree | 15:16 |
| gmann | but to judge the stats we need some threshold to decide so that we can consider that project to be a candidate for next step (removal or help) | 15:16 |
| gmann | and threshold depends on type of projects like for lib etc there are always less activities compare to service projects or so | 15:17 |
| diablo_rojo | I feel like those thresholds are going to be different depending on the kind of project though. | 15:18 |
| diablo_rojo | Cause there are more stable ones that are much more quiet. | 15:18 |
| gmann | at for handling the incoming request not how much code they produce. like if very less patch there but they take care of bugs/reviews then it is all good | 15:18 |
| spotz_ | Different projects might have different thresholds | 15:18 |
| jungleboyj | True. Core projects vs others. | 15:18 |
| fungi | libs vs services is a sort of arbitrary split, and there are many factors which can result in higher or lower numbers for those various kinds of activities | 15:18 |
| gmann | yeah that is just example | 15:18 |
| fungi | where to set a threshold, if you have one at all, should probably be based on long-term analysis of all projects looking for correlations | 15:20 |
| jungleboyj | Agreed. I don't think we have enough information right now that we could create thresholds. | 15:20 |
| ricolin | fungi, you mean like compare the data with the one we generated earlier for same project? | 15:20 |
| jungleboyj | ++ | 15:21 |
| fungi | ricolin: look at numbers for projects you consider to be in a healthy state, and projects you consider to be in a risky state, across different historical timeframes | 15:21 |
| gmann | we need some category where we can divide the projects stats to be consider as good or not good. | 15:22 |
| fungi | but really, analyze all projects, because you're going to need the largest sample size you can muster given there's not really that many projects and your analyses are likely to be rife with statistically insignificant observations | 15:22 |
| ricolin | fungi, +1 | 15:23 |
| gmann | let's start the '' | 15:23 |
| gmann | let's start the 'usage and actionable things on what data/threshold or so' | 15:23 |
| gmann | in etherpad or so and then we can start replacing it with TC liaison framework | 15:24 |
| fungi | i.e. if you set thresholds at all, base them on observations as to how teams are actually working not on assumptions about how you think teams should be working | 15:24 |
| spotz_ | ++ | 15:24 |
| gmann | yes, we can map those with the project removal criteria | 15:25 |
| gmann | #link https://governance.openstack.org/tc/reference/dropping-projects.html | 15:25 |
| gmann | we need to make sure we have a agreed & documented interpretation of stats generated by this tool instead of everyone interpret it differently | 15:26 |
| gmann | and meanwhile we can review/merge the current tool which can be extended later also #link https://review.opendev.org/c/openstack/governance/+/810037/ | 15:27 |
| ricolin | +1, will be nice if we actually got something to documented down | 15:27 |
| ricolin | officially | 15:27 |
| jungleboyj | ++ | 15:27 |
| gmann | I will keep it in agenda and everyone add your opinion on etherpad about stats usage/label project etc | 15:28 |
| gmann | anything else on topic? | 15:29 |
| ricolin | not from me | 15:29 |
| gmann | ok, thanks again ricolin | 15:29 |
| gmann | #topic Xena Tracker | 15:29 |
| gmann | #link https://etherpad.opendev.org/p/tc-xena-tracker | 15:29 |
| gmann | we have 5 items to finish (excluding gate health checks we we do every week) and out of them two (tag, goal) are needed to be discussed in PTG | 15:30 |
| gmann | and this project health tool which is also in-progress | 15:31 |
| gmann | other two items are: | 15:31 |
| gmann | 1. Getting projects to broadast out/mentor - https://etherpad.opendev.org/p/tc-spread-the-word | 15:31 |
| gmann | we have etherpad now with some data | 15:31 |
| spotz_ | Need to add words to make that an email then grab addresses and send it | 15:32 |
| gmann | spotz_: ok and to add it in project-team-guide? | 15:32 |
| spotz_ | We could yeah | 15:33 |
| gmann | ok, I think we have enough/all places listed there where we can broadcast the things | 15:34 |
| spotz_ | Yeah and most are established so don’t think they’ll go away | 15:34 |
| gmann | spotz_: may be you can start the ML/patch? | 15:34 |
| spotz_ | Yeah I got drug away working on a conference deck. I’ll slip this in real quick | 15:35 |
| gmann | thanks | 15:36 |
| gmann | 2. Stable core team process change | 15:36 |
| gmann | mnaser: jungleboyj any news on this? | 15:36 |
| jungleboyj | Last I heard mnaser was working on something but haven't seen an update. | 15:36 |
| gmann | ok | 15:37 |
| mnaser | ill just push up what i have now so far, i think i was waiting for it to be a little too perfect | 15:37 |
| fungi | that's what the review process is for ;) | 15:37 |
| gmann | mnaser: +1, that will be great | 15:37 |
| jungleboyj | mnaser: Awesome. I will review. :-) | 15:38 |
| gmann | anything else/update on Xena tracking items ? | 15:38 |
| gmann | I think we will be able to finish all of them in Xena itself (except few which need final discussion in PTG) | 15:38 |
| gmann | good progress everyone and thanks for working on those. | 15:39 |
| jungleboyj | That is good. | 15:39 |
| gmann | #topic Open Reviews | 15:39 |
| gmann | #link https://review.opendev.org/q/projects:openstack/governance+is:open | 15:39 |
| gmann | I think we are good here, few project updates are there but waiting for project-config to merge before | 15:40 |
| gmann | mnaser: fungi if you can quickly review this project-config #link https://review.opendev.org/c/openstack/project-config/+/808072/1 | 15:41 |
| gmann | I have one more thing to discuss | 15:41 |
| mnaser | done gmann | 15:41 |
| gmann | thanks | 15:42 |
| gmann | as we have same TC members continuing this term, i have not reset the TC liaison list. which I think we do not need to rest as we are also working on alternate framework to replace it | 15:42 |
| gmann | is it fine for all? | 15:42 |
| gmann | s/rest/reset | 15:42 |
| dansmith | sounds good | 15:42 |
| jungleboyj | Makes sense. | 15:43 |
| yoctozepto | ++ | 15:43 |
| gmann | cool, anything else for today ? | 15:43 |
| diablo_rojo | We want to do have k8s folks meet at the PTG with us? | 15:43 |
| diablo_rojo | I can start coordinating that. | 15:43 |
| diablo_rojo | Do we want to let them pick their timeslot from our available times? | 15:44 |
| gmann | yeah, we sent email to them and have it in our PTG etherpad too to have a slot for them | 15:44 |
| gmann | waiting for their reply | 15:44 |
| spotz_ | I’ll be at oss next week and at kubecon if we need to reach out to anyone | 15:44 |
| diablo_rojo | gmann, hadn't seen the email. I can ask them at their next meeting. | 15:44 |
| gmann | yeah, I asked to pick any time they want. | 15:45 |
| gmann | diablo_rojo: I kept you in CC | 15:45 |
| diablo_rojo | spotz_, I think that any of the k8s steering that are travelling will be at kubecon. | 15:45 |
| gmann | diablo_rojo: +1 that will be great, please check | 15:45 |
| diablo_rojo | gmann, sounds good. Will do. | 15:45 |
| gmann | diablo_rojo: thanks | 15:45 |
| gmann | spotz_: diablo_rojo you are traveling to kubecon or virutal ? | 15:45 |
| ricolin | thanks diablo_rojo | 15:45 |
| opendevreview | Mohammed Naser proposed openstack/governance master: wip: stable core team https://review.opendev.org/c/openstack/governance/+/810721 | 15:46 |
| gmann | anything else for meeting today? | 15:46 |
| mnaser | i updated the stable core team stuff i had so far, appreciate early reviews and maybe if jungleboyj can help out with the proposed solutions part | 15:47 |
| spotz_ | I’ll be there | 15:47 |
| gmann | mnaser: +1, thanks for that | 15:47 |
| gmann | spotz_: i see | 15:47 |
| gmann | let's close meeting. thanks everyone for joining. | 15:47 |
| gmann | #endmeeting | 15:47 |
| opendevmeet | Meeting ended Thu Sep 23 15:47:43 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:47 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2021/tc.2021-09-23-15.00.html | 15:47 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2021/tc.2021-09-23-15.00.txt | 15:47 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2021/tc.2021-09-23-15.00.log.html | 15:47 |
| diablo_rojo | gmann, no I don't think I will be going. | 15:47 |
| gmann | diablo_rojo: k | 15:48 |
| jungleboyj | Thank you! | 15:48 |
| diablo_rojo | Thanks! | 15:48 |
| spotz_ | Thanks! | 15:48 |
| ricolin | Thanks | 15:48 |
| yoctozepto | thanks gmann | 15:51 |
| mnaser | i think a fair people will not be going to in-person kubecon | 15:51 |
| gmann | yeah, it will good to see how many prefer in-person. | 15:52 |
| gmann | I am not even getting much confidence of going to restaurant for dine-in :) which I want badly :P | 15:54 |
| mnaser | we've got vaccine passports here in quebec | 15:54 |
| mnaser | so restaurants are all double vaccinated people | 15:54 |
| mnaser | doesn't mean it's perfect but hey | 15:55 |
| gmann | yeah, I also got the vaccine passport but somehow I am not prepared mentally :) | 15:55 |
| gmann | one time i tried and saw 150 people and came back :) | 15:56 |
| mnaser | yeah im not so much better, we've had the vaccine passport since sept 1 and i havent used it once lol | 15:56 |
| spotz | I think it helps I've been doing animal stuff where they force social sitancing to soome degree and were outside. I did order KN95 masks for the conferences | 16:01 |
| *** rpittau is now known as rpittau|afk | 16:02 | |
| jungleboyj | A lot of companies aren't letting people travel yet. We do go out in public here but Rochester, being a medical town, has a lot of vaccinated people and low Covid rates. | 16:02 |
| jungleboyj | Still not doing large events or going up to the Twin Cities. | 16:03 |
| gmann | humm | 16:06 |
| fungi | yeah, living in a tourist trap has probably made this harder, we did dine inside a few restaurants briefly in the spring when rates dropped, before the summer surge, but we're back to basically not entering buildings other than our own home, and wearing masks any time we'll be in the vicinity of other humans regardless of whether they're vaccinated | 16:14 |
| gmann | yeah | 16:15 |
| gmann | mnaser: fungi can you review this project-config patch also https://review.opendev.org/c/openstack/project-config/+/808675 | 16:16 |
| fungi | done | 16:16 |
| gmann | thanks | 16:16 |
| fungi | you bet | 16:16 |
| spotz | gmann fungi diablo_rojo jungleboyj - if y'all orr anyoone else is about can you look at https://etherpad.opendev.org/p/tc-spread-the-word and let me know what you think? | 17:11 |
| jungleboyj | spotz: I made a couple nit-picky changes. Otherwise looks good. | 17:14 |
| fungi | yeah, nothing else springs to mind but if i think of something i'll suggest it | 17:15 |
| fungi | there's a blurry line between blogs and e-zines, too (do people still say e-zine?) | 17:16 |
| fungi | for example, superuser.openstack.org is more of an e-zine, like opensource.com | 17:16 |
| fungi | i think both are great ways to go about getting the word out though | 17:17 |
| fungi | and the opensource.com editors are generally also excited to get new content | 17:17 |
| fungi | lwn is another | 17:18 |
| diablo_rojo | spotz, looking now | 17:24 |
| diablo_rojo | Looks fine to me. | 17:26 |
| spotz | fungi: If it's written I just considered them blogs to be honest:) | 17:29 |
| fungi | cool, then opensource.com and lwn.net may be good additions | 17:30 |
| fungi | fwiw, i have to restrain my desire to still call them weblogs | 17:30 |
| spotz | Now to find where I put the etherpad! | 17:30 |
| fungi | https://etherpad.opendev.org/p/tc-spread-the-word | 17:31 |
| fungi | you linked it just above | 17:31 |
| spotz | I know, I just couldn't find the tab. I don't have my extra monitors up right now:( | 17:32 |
| fungi | hah. if your browser is like mine, you can put the url into the url bar and it will autocomplete an option to switch to that tab | 17:33 |
| spotz | added opensouorce.com annd lwn.net as 6 and 7 | 17:33 |
| fungi | and this concludes another meeting of tab hoarders anonymous | 17:33 |
| dansmith | tree style tabs ftw | 17:34 |
| fungi | whichever firefox devs thought there was a reason to help users not re-open the same page in multiple tabs was a genius | 17:34 |
| jungleboyj | :-) | 17:36 |
| gmann | spotz: lgtm. | 17:48 |
| spotz | Tabs and multiple windows and multiple browsers. It's a mess | 17:49 |
| spotz | Ok email addresses put together so I'll get it out in a second:) | 17:50 |
| spotz | changed the first paragraph - As a TC initiative during the Xena cycle, we took on the task of putting together a list of possible places you as PTLs could help spread the word about what you and your team mates do. Getting the word out about your project is a great way to get additional contributors and users, for both your project and OpenStack as a whole. Not everyone enjoys talking to groups or writing, so we've put tog | 17:54 |
| spotz | ether a list of potential opportunities so you can choose what makes you comfortable. | 17:54 |
| spotz | I thought it lacked context | 17:54 |
| fungi | sounds great | 17:55 |
| jungleboyj | spotz: Looks good! | 17:56 |
| gmann | spotz: thanks Looks good. | 17:57 |
| spotz | etherpad formats better then gmail:) | 18:04 |
| spotz | sent | 18:08 |
| fungi | heh | 18:11 |
| spotz | gmann: I'm thinking a spread-the-word.rst file, or did you have something else in mind? | 18:18 |
| gmann | spotz: sounds good. | 18:20 |
| spotz | Ok sweet | 18:20 |
| gmann | tc-members: on ELK help thread: there is a plan to have meeting with OpenSearch dev team (an open source fork of Elasticsearch) next week to explore what would be involved in migrating OpenStack's tools to a donated hosted OpenSearch. If you'd like to join, add your availability to the poll- https://doodle.com/poll/k2i4mgsnftspaqeh | 18:26 |
| fungi | not migrating. but someone could perhaps build a replacement making use of it | 18:43 |
| fungi | remember opendev is not planning to continue providing the indexing services which would feed into that either, someone still needs to be interested in doing that part for the backend to be of any use | 18:45 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 18:45 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 19:01 |
| fungi | spotz: what do you think about adding things like the open infrastructure foundation newsletter? i suppose that would be an additional category? | 19:01 |
| spotz | fungi: Do they take full articles? I honestly don't know | 19:02 |
| fungi | not full articles, but they do spotlights and community updates, both of which could certainly be used to "spread the word" about a project or effort | 19:02 |
| fungi | perhaps with less effort than writing a full article too | 19:02 |
| fungi | wonder if there are other similar options in that vein too | 19:03 |
| spotz | True | 19:07 |
| gmann | as newsletter team expect the overall updates from TC, in 'spread the word' we can add something 'communicate to TC if you would like to highlights specific updates to newsletter' so that we can maintain central review of overall updates from openstack | 19:11 |
| fungi | well, the tc is one place the newsletter editors get info from for the openstack section, but diablo_rojo, ttx and i also add things beyond that if they seem appropriate | 19:12 |
| gmann | I am talking about openstack | 19:12 |
| fungi | yep, me too | 19:12 |
| fungi | still, letting the tc know or adding something to the crowdsourced etherpad for the newsletter are certainly good ways to go about it | 19:13 |
| fungi | just saying that openstack-related content for the newsletter doesn't always come through the tc | 19:13 |
| fungi | but we do try to include anything the tc asks to be included | 19:13 |
| gmann | I think that is what TC review every month via https://etherpad.opendev.org/p/newsletter-openstack-news | 19:14 |
| gmann | but as TC does not own the newsletter things I am ok if newsletter news can be done directly from all openstack projects as individual or from TC as central place | 19:16 |
| gmann | but to make it aesy to maintain at least for openstack projects, it is good to mention to communicate it via TC in spread-the-word | 19:17 |
| fungi | yeah, i mean a majority of the content for the openstack section comes from that etherpad, we just also sometimes add stuff directly to the newsletter we think of at the last minute if it's important/relavant but missing from the etherpad, and also the newsletter editorial team does spotlight pieces which are often about openstack topics and generally don't come from that etherpad | 19:17 |
| fungi | though might sometimes be inspired by entries from there | 19:18 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 19:22 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 19:37 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 19:46 |
| spotz | I will spam you all!!!!:) | 19:46 |
| spotz | And curse out the rst docs... | 20:00 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 20:01 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 20:17 |
| gmann | spotz: commented, few formatting issues otherwise lgtm | 22:31 |
| spotz | gmann formatting was why all the patches:) Thanks I'll get that tonight or in the morning:) | 22:36 |
| opendevreview | Amy Marrich proposed openstack/project-team-guide master: Added spread-the-word.rst https://review.opendev.org/c/openstack/project-team-guide/+/810766 | 22:41 |
| spotz | ccross your fingers | 22:41 |
| fungi | spotz: one trick is to `tox -e docs` and then point your browser at file:///.../doc/build/html/ | 22:41 |
| fungi | if you don't want to have to wait for the docs job in zuul to run | 22:42 |
| fungi | i often do that to check formatting before i push | 22:42 |
| spotz | fungi yeah that didn't want to run locally for me:( | 22:43 |
| spotz | It's a local problem I just haven't gotten around to arguing eith | 22:43 |
| fungi | ahh | 22:43 |
| opendevreview | Merged openstack/project-team-guide master: Tag deliverables as retired https://review.opendev.org/c/openstack/project-team-guide/+/796687 | 22:43 |
| spotz | So it was honestly faster to wait for Zuul though apologies for spammage:) | 22:45 |
| fungi | heh, no worries | 22:46 |
| spotz | And the rrst docs arer so inconsistent between - and * and do you need a blank line or should you indent. I was honestly happy to see a green pass | 22:47 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!