*** d34dh0r5- is now known as d34dh0r53 | 12:12 | |
spotz_ | Asked on the elections channel yesterday but does anyone know where events.rst lives? It doesn't appear to be in the elections or governance repos but it is called on the election index.rst page | 12:31 |
---|---|---|
fungi | i'll follow up in the election channel | 13:01 |
*** gthiemon1e is now known as gthiemonge | 16:00 | |
opendevreview | Amy Marrich proposed openstack/election master: Adding dates for upcoming election to be displayed on the election page https://review.opendev.org/c/openstack/election/+/886653 | 17:22 |
gmann | thanks spotz_ for ^^. one thing to update in case you missed. In this cycle start, I have made release number work for the election process. candidate dir/template etc works on release number but if you find any issue let me know(in case i missed to test anything) | 17:24 |
gmann | spotz_: and also good to add you in election official list https://github.com/openstack/election/blob/master/doc/source/index.rst#election-officials | 17:26 |
spotz_ | gmann Yeah I did it with the number, it apparently went from number back to name last election we're not sure why so if it causes an error again maybe we can debug | 17:29 |
gmann | spotz_: yeah, it should be working fine now but yes we can debug and fix if any issue | 17:30 |
opendevreview | Amy Marrich proposed openstack/election master: Adding dates for upcoming election to be displayed on the election page https://review.opendev.org/c/openstack/election/+/886653 | 17:42 |
fungi | it's not so much that we don't know why, as that i'm too lazy to go digging through discussions from february until we've given the people who hit the issues last time a chance to provide background | 17:48 |
fungi | but worst case i can check review comments and irc channel logs | 17:48 |
gmann | I have fixed most of them and tested all scripts/template in Mar and it should be working | 17:49 |
fungi | sounds great, thanks! | 17:57 |
knikolla | sounds like RHEL source code won't be available moving forward https://lwn.net/Articles/935592/ | 18:13 |
fungi | well, it will be "available" for certain definitions of the word | 18:14 |
knikolla | Depends on the differences between CentOS stream and a RHEL release, I guess. | 18:15 |
fungi | well, the dodgy bit, which i'm sure their ip lawyers took plenty of time on, is where they will cancel your subscription/access if you exercise your right to redistribute software you received under the gpl | 18:19 |
fungi | you're agreeing to a contract which, i think, is basically curtailing the rights granted by the license | 18:20 |
fungi | anyway, people who make many times as much money as i do are certainly going to be debating that seeming contradiction for months and years to come | 18:21 |
knikolla | great use of time and resources | 18:22 |
fungi | it makes me dubious of the ongoing discussion we've got with folks there about the possibility of being able to make rhel-based images available for zuul jobs running in opendev | 18:23 |
fungi | they're already trying to figure out changes that would be needed to the license agreements, and this news seems like a step in the opposite direction for that entire business unit | 18:24 |
knikolla | I think the lack of any other binary-compatible alternatives makes getting access to RHEL images more likely, rather than less. | 18:25 |
knikolla | Third parties developing for RHEL systems still need their CI, where they might have relied on Centos/Alma/Rocky. | 18:26 |
JayF | This makes me extremely loathe to support any RHEL enterprise OS, to be honest. | 18:29 |
fungi | well, the challenges for opendev's case are that we do everything transparently/openly in public, inc | 18:30 |
JayF | It's an openly hostile move to open communities and I have no desire for my time/effort to go to enhance something that's as closed as they can get it legally. | 18:30 |
fungi | luding mirroring packages and publishing images for download | 18:30 |
fungi | and also we can't really thoroughly secure any license key they might give us to download packages unless we restricted access to what could trigger jobs running on those images or what access the jobs would have when running in them | 18:31 |
JayF | I'm an upstream dev struggling to troubleshoot CI issues on an OS that I *can* locally replicate | 18:31 |
JayF | how would I trobuleshoot in the case of a closed OS? | 18:32 |
fungi | exactly | 18:32 |
fungi | those are the topics they're apparently discussing, but my hopes are not high they'll come back with a solution | 18:32 |
JayF | "They" being RHEL? | 18:32 |
fungi | though it might be "sign up for a free developer account" | 18:33 |
fungi | they being ibm/rh | 18:33 |
JayF | There's a certain about of bi-directional trust required to work on someones' platform. That's been pretty well broken. Even if we can solve the technical problems, it seems to me that we are going directly against one of our opens if we endorse the use of a distribution that is closing up collaboration instead of opening it up | 18:33 |
knikolla | ++ on trust. | 18:35 |
fungi | yes, i've also tried not to set any expectations that we have enough demand for testing on actual rhel to overcome the maintenance burden and resource costs, so probably the bits of feedback i'm seeing are aftereffects of internal wars being waged within their organization | 18:35 |
JayF | Are we going to secure assurances, legal and otherwise, to ensure they'll continue allowing us to test for the 18-supported-months? What about for time after in "EM" or whatever it's called at that point | 18:35 |
fungi | i mean, opendev doesn't provide any guarantees we'll be able to supply anything in particular, though we try hard to make sure our projects have what they need as long as we can do so | 18:39 |
fungi | if we did have rhel images available, we'd document the caveats and let projects decide what risks they're comfortable with | 18:40 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!