#115 ISA SIG
Closed a year ago by jwboyer. Opened a year ago by jwboyer.

Florian Weimer has proposed creating a CentOS ISA SIG:

https://lists.centos.org/pipermail/centos-devel/2023-February/142782.html

Through discussion we have changed the name from "x86 SIG" to "ISA SIG" to express that the SIG is open to other ISA change experimentation beyond x86 in the future. The initial work will be focused on x86-64 architecture baselines and optimizations.

We have discussed this on the list and in the previous two CentOS Board meetings and addressed all of the outstanding questions with no objections to the SIG being created from any of the Board members or community members present. I am creating this ticket to follow process and would like to propose we approve it rapidly.


For the record, I am the Board Sponsor/Champion for this SIG.

I believe all issues have been now resolved. Let's give this until May 3rd for anyone to raise any concerns and if none then we can close and move forward.

I chose May 3 so that we've got a few work days for folks to comment.

Metadata Update from @jwboyer:
- Issue assigned to jwboyer

a year ago

It's well passed May 3. Closing this as approved.

Metadata Update from @jwboyer:
- Issue status updated to: Closed (was: Open)

a year ago

@jwboyer What happens next? Do I need to file a ticket elsewhere to have the SIG actually created? Who is going to be the chair? I expect some admin needs to create a group for the SIG in the account system at the very least. Sorry, I'm confused.

@jwboyer What happens next? Do I need to file a ticket elsewhere to have the SIG actually created? Who is going to be the chair? I expect some admin needs to create a group for the SIG in the account system at the very least. Sorry, I'm confused.

I don't blame you. Our SIG documentation is confusing and says what needs to be done, but not how to actually do it. I'll work with @bstinson and others next week to sort this out.

For now, I will assume you are the chair. If that's not correct, let me know.

Login to comment on this ticket.

Metadata