| *** Guest3022 is now known as diablo_rojo | 12:52 | |
| *** dasm|off is now known as dasm | 13:50 | |
| whoami-rajat | gmann, hi, I had a question about the SLURP release cadence, is there any change that needs to be highlighted from the original plan or is it the same as before? https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html | 17:11 |
|---|---|---|
| gmann | whoami-rajat: it is same. except some releasenotes things which rosmaita is working i think but that can be highlights/communicated once completed? | 17:12 |
| whoami-rajat | gmann, sure, thanks | 17:14 |
| clarkb | gmann: a key part of why I don't want to set the expectation that openstack (or any other project) will get special notifications is that doing so requires extra effort that is better spent directly helping the projects where we can't get away from it. In this case we have a simple solution that anyone can participate in and it reduces my workload. That frees me up to hvae more | 17:15 |
| clarkb | time to do things like speed up CI jobs (something I've been poking at recently becuse openstack noticed job timeouts). | 17:15 |
| clarkb | The OpenDev team does try to take openstack's release cycle into account when planning changes. We also spend the majority of our time working on things that benefit openstack | 17:16 |
| clarkb | avoiding unnecessary busy work on top of that allows us to more effectively continue to support openstack | 17:16 |
| gmann | clarkb: sure, I am saying to send the highlight things not all. | 17:17 |
| gmann | but i agree on your bandwidth things and focus on key things | 17:17 |
| clarkb | well everything sent to service-announce is a highlight. Since we're intentionally trying to avoid overwhelming people with messages | 17:17 |
| gmann | but in reality especially in open source- best communication way is to try in all possible places where we have the audience | 17:18 |
| JayF | Eh; there's absolutely two sides to that coin | 17:19 |
| JayF | and signal:noise on the openstack list is pretty noisy due to the mix of projects we have in (most folks don't care about all the projects) | 17:19 |
| fungi | highlighting those things by bringing them up on the openstack-discuss ml is something i try to do as tact sig chair/opendev liaison/community manager for openstack, but i don't want people to assume it's comprehensive. following service-announce (which is very low traffic) is still preferable | 17:19 |
| gmann | +1 | 17:19 |
| JayF | We have a responsibility to be in the places where those messages are sent; I was not living up to that responsibility until now (but now I'm subbed and will see them) | 17:19 |
| clarkb | and to be clear if something changes and it doesn't get announced there that is good feedback to us as well | 17:20 |
| clarkb | we try to strike a balance and I'm sure sometimes we underestimate what ends up being end user visible | 17:20 |
| fungi | also, for the openstack-discuss volume concern, i try to tag the things i post in reference to opendev announcements as [dev][infra][tact-sig] in case anyone's got mail filters for those | 17:21 |
| clarkb | fungi: oh I stopped tagging them [infra] because I was told a while back that no one looked at those :) | 17:21 |
| clarkb | basically everyone treated them as emails for the infra team not emails from the infra team | 17:22 |
| clarkb | but maybe setting expectations about what those tags mean is a good idea | 17:22 |
| fungi | the two are interrelated. obviously anyone can read them, so it seems logical to mean "anyone interested in the infra activities" (whether or not they're participating directly in them) | 17:31 |
| *** timburke__ is now known as timburke | 20:56 | |
| *** dasm is now known as dasm|off | 22:41 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!