| gmann | rosmaita: replied to your comment in this, please check if that make sense https://review.opendev.org/c/openstack/governance/+/837891/2/reference/projects.yaml#2148 | 00:36 |
|---|---|---|
| gmann | ade_lee: added few comments in FIPS goal, please check https://review.opendev.org/c/openstack/governance/+/838601 | 00:54 |
| gmann | we will review this on priority as Zed cycle which is miletsone 1 is already staretd | 00:54 |
| gmann | ade_lee: also please add this checklist in your goal doc, you do not need to change the whole template as I changed it after your goal was proposed but just having this checklist will work for us https://github.com/openstack/governance/blob/master/goals/template.rst#goal-checklist | 00:57 |
| opendevreview | Slawek Kaplonski proposed openstack/governance master: Define Technical preview framework https://review.opendev.org/c/openstack/governance/+/839880 | 08:56 |
| opendevreview | Slawek Kaplonski proposed openstack/governance master: Remove release names starting from 2023.1 release https://review.opendev.org/c/openstack/governance/+/839897 | 10:16 |
| *** iurygregory__ is now known as iurygregory | 11:14 | |
| fungi | slaweq: are you also preparing the mailing list thread for that ^ ? | 11:42 |
| slaweq | fungi: I didn't yet | 12:03 |
| slaweq | but I will | 12:03 |
| fungi | thanks! | 12:03 |
| *** pojadhav is now known as pojadhav|afk | 13:50 | |
| gmann | slaweq: thanks, | 14:04 |
| gmann | yes we definatly put these key changes in ML always. | 14:04 |
| spotz | dpawlik and I are meeting with the TripleO folks about e-r on Monday | 14:06 |
| gmann | spotz: nice, on IRC or call? and what time ? | 14:06 |
| spotz | call, 9 my time | 14:07 |
| gmann | spotz: and you are in CST i think? | 14:09 |
| gmann | slaweq: added 1 comment on release name patch https://review.opendev.org/c/openstack/governance/+/839897 | 14:50 |
| gmann | slaweq: please check if that make sense? | 14:50 |
| slaweq | gmann: thx I will | 14:53 |
| fungi | in case anyone needs convincing that the decision to get rid of "admin" was the right choice, this is the sort of confused vulnerability report we get periodically from users/operators about it: https://launchpad.net/bugs/1970932 | 14:54 |
| slaweq | gmann: I will address Your and fungi's comments later today or during the weekend as now I have to leave | 14:55 |
| fungi | thanks! | 14:56 |
| gmann | slaweq: no issue, on Monday is ok. do not take it for weekend as anyways we need to wait for 7 days to merge this so no hurry at all | 14:57 |
| slaweq | gmann: thx, sure :) | 14:57 |
| gmann | tc-memebrs: for next TC video call on 28th, I am going to make it mostly with two topic 1. CFN overview by Jie (as we discussed in ML) 30 min 2. tick-tock release notes (30 min or less) 3. anything else if time permit. | 15:09 |
| gmann | sorry 5th May video call | 15:11 |
| gmann | please let me know if something else you have to discuss? and in weekly meeting from 12th onwards we will continue on our usual agenda | 15:11 |
| fungi | please also remember that google meet isn't likely to be a good option for participants from mainland china (i.e. the chinamobile folks representing cfn) due to its inaccessability there | 15:17 |
| gmann | yes, I am in discussion with them if that does not work. | 15:18 |
| gmann | tc-members: need one more vote on this https://review.opendev.org/c/openstack/governance/+/839100 | 17:06 |
| jungleboyj | Thumbs up from me. | 17:07 |
| gmann | thanks | 17:08 |
| opendevreview | Merged openstack/governance master: Remove TC Liaisons framework https://review.opendev.org/c/openstack/governance/+/837891 | 17:13 |
| opendevreview | Merged openstack/governance master: Fix keystone PTL model documentation https://review.opendev.org/c/openstack/governance/+/838940 | 17:18 |
| fungi | gmann: back to our earlier discussion about list moderation filters, if you really want to help avoid adding work for list moderators then please avoid cross-posting messages to multiple lists at the same time, as it results in people who aren't subscribers to one or more of those lists to reply to them anyway, causing their posts to all be held for approval: | 17:21 |
| fungi | https://wiki.openstack.org/wiki/MailingListEtiquette#Avoid_cross-posting | 17:21 |
| * fungi is moderator for both the openstack-discuss and foundation lists, where that is now happening for the release naming thread | 17:22 | |
| opendevreview | Merged openstack/governance master: Retire openstack-helm-docs https://review.opendev.org/c/openstack/governance/+/839100 | 17:22 |
| opendevreview | Merged openstack/governance master: Resolution to drop the lower constraints maintenance https://review.opendev.org/c/openstack/governance/+/838004 | 17:22 |
| fungi | also people who subscribe to both lists are now getting two copies of replies | 17:23 |
| gmann | so we should duplicate the discussion in both ML or do not inform other ML as this message is relavant. | 17:37 |
| gmann | asking other ML to join discussion there is same things now they have to subscribe there | 17:38 |
| fungi | see the wiki article, you can also send something to one list letting people know about the discussion happening on the other list and encouraging them to subscribe and participate there | 17:38 |
| fungi | i understand the desire to send a message to multiple mailing lists (and that section of the wiki article sympathozes wit those desires), but that's not how mailing lists are menant to work | 17:39 |
| gmann | I will better remove the other ML as they are informed now. too many things to take care in emails. will keep things in openstack-discuss and anyone wanted should have subscribed that. | 17:39 |
| fungi | yes, it's an openstack project discussion, so while it's nice to let the subscribers of the foundation mailing list know the discussion is taking place, sending a single message with both lists as recipients of that message creates a lot of duplicate deliveries and held messages on both lists | 17:41 |
| gmann | and is it better that they all have to subsribe the openstck-discuss ML just for one thread ? | 17:42 |
| gmann | with all these restriction on ML, I am not sure how to make such (receipents and two ML topic) communication better but definitly current one are not good at all. | 17:42 |
| fungi | if they all want to discuss an openstack project matter, then the openstack-discuss mailing list is the right one to do that on | 17:43 |
| gmann | well this topic is not just for us, we want to do better communication to all stack holder and foundation is one important one here | 17:44 |
| gmann | we have two solution here 1. do not mind seeing two copies as you subscribed on both ML 2. Ask 100(or more ) members to subscribe openstack-discuss ML jsut for one thread | 17:44 |
| fungi | yep, communication to people who want to know the discussion is taking place makes sense. it also makes sense to encourage them to come to the place where the discussion is happening if they want to get involved in the discussion | 17:45 |
| gmann | I feel first one is fine but if you think thats not and 2nd one is, I will remove the foundation ML thread | 17:45 |
| gmann | but that is not good and something we should fix how I am not sure. | 17:45 |
| fungi | it's not about opinions, i'm explaining how mailing lists work. i get that it's probably a little strange to people who haven't been deeply involved in open source communities for decades, but mailing lists aren't like instant messaging channels or web forums and you have to be aware of the differences when using them | 17:47 |
| clarkb | gmann: I think that it is a bit of a simplification to say they would join openstack-discuss for one thread. OpenStack discussion is meant to ahppen on that mailing list. Foundation board members etc that are interested in openstack should join that mailing list for all the other discussions relevant to them as well | 17:48 |
| gmann | that is ok I am saying, current rule/MailingListEtiquette for cross ML topic are something we should improve. | 17:48 |
| fungi | also you can't effectively "remove" the other addresses from messages which have been delivered, that's done, it happened and they'll be replying to both mailing lists now if they reply to any of those messages. the most you can hope to do is clean them up in new replies you send and (more importantly) avoid doing the same thing in the future | 17:48 |
| fungi | gmann: it's not a "rule" we can "improve" it's how mailing lists work | 17:49 |
| gmann | I will ask them to remove too as it is creating lot of *issues* | 17:49 |
| fungi | please don't. that creates even more replies, and just exacerbates the problem. it will eventually end with the discussion dies down | 17:50 |
| fungi | and i know you were trying to do the right thing, i'm just saying in the future please be mindful of the problems that cross-posting creates | 17:54 |
| gmann | sure, I am removing that and gradually hoping all will keep one in list. | 18:05 |
| fungi | thanks! | 18:06 |
| fungi | also as an aside, the correct e-mail address for the foundation mailing list these days is foundation@lists.openinfra.dev (lists.openstack.org finally only has openstack project mailing lists as of the beginning of this year) | 18:07 |
| gmann | ack, thanks | 18:09 |
| fungi | that reminds me, i need to clean up the defunct openstack mailing lists i reached out about months ago | 18:10 |
| gmann | slaweq: thanks for starting it, added few comments there https://review.opendev.org/c/openstack/governance/+/839880 | 19:11 |
| spotz_ | gmann yep cst | 19:23 |
| spotz_ | Glad to see more folks speaking up about the naming, I felt like the only one for a while and then ttx | 19:40 |
| gmann | everyone like name, but we are not understanding the problem with that :) | 19:41 |
| *** spotz_ is now known as spotz | 19:53 | |
| spotz | That's better | 19:53 |
| spotz | For promotion, community building, etc the name brings folks together. Like for the RDO contributor item we're doing a sports theme(yoga mat didn't win) and putting our mascot(hopefully) on a yoga mat. People will remember that sort of thing more then the item they got with 2022.1 on it | 19:55 |
| spotz | When speaking to press announcing the Yoga release as the 25th release is more memorable then the 25th release which was 2022.1 | 19:55 |
| spotz | Code doesn't matter it won't care | 19:56 |
| spotz | Operators I always have to think back to my first version, it's easier to remember Grizzly then what tag it might have been | 19:56 |
| gmann | we can achieve all these with tag line per release, with more than one word tag line per release | 22:46 |
| gmann | there is no doubt it has some benfits but what are saying is it causes more tourble than benefits | 22:47 |
| opendevreview | Ghanshyam proposed openstack/governance master: Remove release names starting from 2023.1 release https://review.opendev.org/c/openstack/governance/+/839897 | 23:37 |
| gmann | mnaser: spotz gouthamr ^^ updated it with all the problem and the ways we tried. but I did not mean to remove your -1. please re-vote or re-review | 23:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!