Search
693 results for “fedoracpt”
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Today we are starting the nomination & campaign period during which we accept nominations to the “steering bodies” of the following teams:
- FESCo (Engineering) (5 seats)
- Fedora Council (1 seat)
- Mindshare (1 seat)
This period is open until 2023-11-27 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name.
The steering bodies are currently selecting interview questions for the candidates.
Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period.
Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2023-05-17) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections schedule. For more information about the elections, process see the Elections docs.
https://communityblog.fedoraproject.org/f39-elections-now-open/
#electionCampaigns #elections #FedoraCouncil #FedoraEngineeringSteeringCommitteeFESCo_ #FedoraMindshareCommittee
-
This is a part of the Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Friday, 8 December and closes promptly at 23:59:59 UTC on Thursday, 21 December.
Interview with Kevin Fenzi
- Fedora Account: Kevin
- IRC/Nick: nirik
- Matrix Channels typically found in: #fedora-admin/admin, #fedora-noc/noc, #fedora-releng/releng, #fedora-devel/devel
- Fedora User Wiki Page
Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?
I wish to continue to serve the fedora community on FESCo to provide history and help make today’s decisions based on yesterdays learning.
How do you currently contribute to Fedora? How does that contribution benefit the community?
I currently am lucky to be employed by Red Hat working full time on Fedora Infrastructure. But outside of that ‘day job’ I try and do as many things as I can to help the fedora community: Maintaining packages, providing feedback on plans or ideas, doing release engineering tasks (often in non ‘work’ times).
How do you handle disagreements when working as part of a team?
I try and reach consensus until it becomes clear thats not possible. However, it almost always is possible, you just need to look at things from other perspectives and consider what solution would work for everyone. This is not foolproof, but helps to handle disagreements when they happen.
What else should community members know about you or your positions?
I’m happy to talk to anyone from the community anytime about fedora items. Feel free to contact me on matrix or irc or email. I’m human and make mistakes, but I like to think I learn from them and do better over time. 🙂
elections, Fedora, Fedora Engineering Steering Committee (FESCo)https://communityblog.fedoraproject.org/fesco-election-interview-with-kevin-fenzi-2/
#elections #Fedora #FedoraEngineeringSteeringCommitteeFESCo_
-
This is a part of the Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Friday, 8 December and closes promptly at 23:59:59 UTC on Thursday, 21 December.
Interview with Tomas Hckra
- Fedora Account: Tomas Hckra
- IRC/Nick: jednorozec/humaton
- Matrix Channels typically found in: fedora-releng, #fedora-devel, #fedora-devel, #fedora-noc
- Fedora User Wiki Page
Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?
I believe that my perspective as a fedora release engineer can bring some new opinions into the steering process. My focus is mostly on user/contributor self-service where possible so we can remove obstacles for new people coming into the Fedora project.
How do you currently contribute to Fedora? How does that contribution benefit the community?
Over the last decade, I went through package maintenance and app development. Currently, I am part of the release engineering team, helping out with releases and related infrastructure work. Right now I am working on dropping the Product Definition Center from our workflows so we can reduce the complexity in our package-related processes and tooling.
How do you handle disagreements when working as part of a team?
Most of the team disagreements I was part of were caused by communication issues and misunderstanding of one or the other side. So I strongly believe that most problems are resolvable by listening, considering the other side, and communicating about the disagreement clearly. The next step is building consensus keeping in mind all the viewpoints that caused the conflict in the first place.
What else should community members know about you or your positions?
I am a full-on open-source nerd, everything in my house is running open-source SW. I am not shy of public speaking you can find some of my talks on YouTube like this one about opensource home automation: https://www.youtube.com/watch?v=HUhHaHnzhYA
Two main ideas that define my approach to technology:
“I want all things open and all sources shown”
“Where is a serial console there is a way”https://communityblog.fedoraproject.org/fesco-election-interview-with-tomas-hckra/
#elections #Fedora #FedoraEngineeringSteeringCommitteeFESCo_
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Voting in the Fedora Linux 39 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 21 December, and don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
Fedora Council
There is one seat open on the Fedora Council.
Mindshare Committee
There is one seat open on the Mindshare Committee.
Fedora Engineering Steering Committee (FESCo)
There are five seats open for the Fedora Engineering Steering Committee (FESCo).
https://communityblog.fedoraproject.org/f39-elections-voting-is-now-open/
-
Today we are starting the nomination & campaign period during which we accept nominations to the “steering bodies” of the following teams:
- FESCo (Engineering) (5 seats)
- Fedora Council (1 seat)
- Mindshare (1 seat)
This period is open until 2023-11-27 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name.
The steering bodies are currently selecting interview questions for the candidates.
Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period.
Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2023-11-29) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections schedule. For more information about the elections, process see the Elections docs.
https://communityblog.fedoraproject.org/f39-elections-now-open/
#electionCampaigns #elections #FedoraCouncil #FedoraEngineeringSteeringCommitteeFESCo_ #FedoraMindshareCommittee
-
Today we are starting the nomination & campaign period during which we accept nominations to the “steering bodies” of the following teams:
- FESCo (Engineering) (5 seats)
- Fedora Council (1 seat)
- Mindshare (1 seat)
This period is open until 2023-11-27 at 23:59:59 UTC.
Candidates may self-nominate. If you nominate someone else, please check with them to ensure that they are willing to be nominated before submitting their name.
The steering bodies are currently selecting interview questions for the candidates.
Nominees submit their questionnaire answers via a private Pagure issue. The Election Wrangler or their backup will publish the interviews to the Community Blog before the start of the voting period.
Please note that the interview is mandatory for all nominees. Nominees not having their interview ready by end of the Interview period (2023-11-29) will be disqualified and removed from the election.
As part of the campaign people may also ask questions to specific candidates on the appropriate mailing list.
The full schedule of the elections is available on the Elections schedule. For more information about the elections, process see the Elections docs.
https://communityblog.fedoraproject.org/f39-elections-now-open/
#electionCampaigns #elections #FedoraCouncil #FedoraEngineeringSteeringCommitteeFESCo_ #FedoraMindshareCommittee
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 12 February – 16 February 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issuesFedora Infra
- Adding ansible role zabbix/zabbix_templates to handle creation of templates, hostgroups. Work toward releng compose cronjob monitoring.
- Fixed: fas2discourse group sync adding and removing people very frequently
- Planned Outage – server updates – 2024-02-07 22:00 UTC
- Rack and setup new FY23Q4 machines
- Fixed: power9 builders slow
- Fixed: https://dl.fedoraproject.org/pub/ is empty
- Fixed: Error in pdc_import_compose with new compose format
- Add communishift user documentation
CentOS Infra including CentOS CI
- CS10 composes seem to have NFS disk issues
- HDD issue on sponsored node
- Helping Cloud SIG
- WIP: Migrate aarch64 workload on new Ampere/snow machines
- Migrate s390x workload on new Z16
Release Engineering
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-7-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 15 Jan – 19 Jan 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issuesFedora Infra
- OIDC client credentials for image builder
- Fixed issue with password reset in IPA
- Migrate DBs and deploy new DNF countme package: python3.11-mirrors-countme-0.1.2-1.el8
- Fixed F39 testing repo not in sync
CentOS Infra including CentOS CI
Release Engineering
- Developing Zabbix SOP detailing steps to add releng compose cronjob monitoring here / here
- Update/reboot/reinstall builders before mass rebuild
- Add ostree container native images (bootc)
- Mass rebuild for Fedora Linux 40 was postponed for one day to 2024-01-18 because of toolchain rebase.
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Sponsored James Richardson into the packager group
- Organizing new time slot for EPEL Steering Committee meeting
List of new releases of apps maintained by CPE
- Patch update of Bodhi from 8.0.1 to 8.0.2 on 2024-01-12: https://github.com/fedora-infra/bodhi/releases/tag/8.0.2
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-3-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 08 January – 12 January 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).Fedora Infra
- Zabbix ticket with RH IT closed here
- Zabbix agent now rolled out to entire Fedora Infra Production hosts. Debugging one or two things on releng hosts and ipsilon.
- Fixed: Intermittent Skipping of Messages in Fedora Messaging Bus Setup
- countme log gathering script improvment/cleanup
- Clean out old SOPs
- Add step for creating dist-git groups to groups how-to
- Create cname for Discourse staging instance
- Add Flatpak Cache as a OpenShift app
CentOS Infra including CentOS CI
- Decommission old sponsored nodes
- rpmautospec on CentOS Stream Koji
- Reconfigure koji runroot plugin for additional cs10 koji volume
Release Engineering
- fedora-common-ostree: Prepare for ppc64le support in bootupd & bootupd: Minor clean up
- F40: KDE: Split initial setup packages into their own group
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Monthly Office Hours call last Wednesday
- EPEL Steering Committee call
- James Richardson onboarding
- Requested vorbis-tools for EPEL9 to fix icedax package
Community Design
CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.
Updates
- Working on Creative Freedom Summit 🤩
- Podman / Podman Desktop Hackathon running this week
- Getting assets ready for FOSDEM
List of new releases of apps maintained by CPE
Minor update of Noggin from 1.8.0 to 1.9.0 on 2024-01-10
Minor update of FMN from 3.2.0 to 3.3.0 on 2024-01-10If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-2-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 08 January – 12 January 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).Fedora Infra
- Zabbix ticket with RH IT closed here
- Zabbix agent now rolled out to entire Fedora Infra Production hosts. Debugging one or two things on releng hosts and ipsilon.
- Fixed: Intermittent Skipping of Messages in Fedora Messaging Bus Setup
- countme log gathering script improvment/cleanup
- Clean out old SOPs
- Add step for creating dist-git groups to groups how-to
- Create cname for Discourse staging instance
- Add Flatpak Cache as a OpenShift app
CentOS Infra including CentOS CI
- Decommission old sponsored nodes
- rpmautospec on CentOS Stream Koji
- Reconfigure koji runroot plugin for additional cs10 koji volume
Release Engineering
- fedora-common-ostree: Prepare for ppc64le support in bootupd & bootupd: Minor clean up
- F40: KDE: Split initial setup packages into their own group
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Monthly Office Hours call last Wednesday
- EPEL Steering Committee call
- James Richardson onboarding
- Requested vorbis-tools for EPEL9 to fix icedax package
Community Design
CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.
Updates
- Working on Creative Freedom Summit 🤩
- Podman / Podman Desktop Hackathon running this week
- Getting assets ready for FOSDEM
List of new releases of apps maintained by CPE
Minor update of Noggin from 1.8.0 to 1.9.0 on 2024-01-10
Minor update of FMN from 3.2.0 to 3.3.0 on 2024-01-10If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-2-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 08 January – 12 January 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).Fedora Infra
- Zabbix ticket with RH IT closed here
- Zabbix agent now rolled out to entire Fedora Infra Production hosts. Debugging one or two things on releng hosts and ipsilon.
- Fixed: Intermittent Skipping of Messages in Fedora Messaging Bus Setup
- countme log gathering script improvment/cleanup
- Clean out old SOPs
- Add step for creating dist-git groups to groups how-to
- Create cname for Discourse staging instance
- Add Flatpak Cache as a OpenShift app
CentOS Infra including CentOS CI
- Decommission old sponsored nodes
- rpmautospec on CentOS Stream Koji
- Reconfigure koji runroot plugin for additional cs10 koji volume
Release Engineering
- fedora-common-ostree: Prepare for ppc64le support in bootupd & bootupd: Minor clean up
- F40: KDE: Split initial setup packages into their own group
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Monthly Office Hours call last Wednesday
- EPEL Steering Committee call
- James Richardson onboarding
- Requested vorbis-tools for EPEL9 to fix icedax package
Community Design
CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.
Updates
- Working on Creative Freedom Summit 🤩
- Podman / Podman Desktop Hackathon running this week
- Getting assets ready for FOSDEM
List of new releases of apps maintained by CPE
Minor update of Noggin from 1.8.0 to 1.9.0 on 2024-01-10
Minor update of FMN from 3.2.0 to 3.3.0 on 2024-01-10If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-2-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 08 January – 12 January 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).Fedora Infra
- Zabbix ticket with RH IT closed here
- Zabbix agent now rolled out to entire Fedora Infra Production hosts. Debugging one or two things on releng hosts and ipsilon.
- Fixed: Intermittent Skipping of Messages in Fedora Messaging Bus Setup
- countme log gathering script improvment/cleanup
- Clean out old SOPs
- Add step for creating dist-git groups to groups how-to
- Create cname for Discourse staging instance
- Add Flatpak Cache as a OpenShift app
CentOS Infra including CentOS CI
- Decommission old sponsored nodes
- rpmautospec on CentOS Stream Koji
- Reconfigure koji runroot plugin for additional cs10 koji volume
Release Engineering
- fedora-common-ostree: Prepare for ppc64le support in bootupd & bootupd: Minor clean up
- F40: KDE: Split initial setup packages into their own group
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Monthly Office Hours call last Wednesday
- EPEL Steering Committee call
- James Richardson onboarding
- Requested vorbis-tools for EPEL9 to fix icedax package
Community Design
CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.
Updates
- Working on Creative Freedom Summit 🤩
- Podman / Podman Desktop Hackathon running this week
- Getting assets ready for FOSDEM
List of new releases of apps maintained by CPE
Minor update of Noggin from 1.8.0 to 1.9.0 on 2024-01-10
Minor update of FMN from 3.2.0 to 3.3.0 on 2024-01-10If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-2-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work. Happy New Year to everyone!
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 01 January – 05 January 2024
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).Fedora Infra
- RH IT tickets to open firewall ports for production zabbix completed (mostly). Starting to auto enroll the hosts with the server.
- Update infrastructure documentation
- [PagureExporter] v0.1.2 tag temporarily yoink’d in order for RH IT to expunge any (potentially) sensitive info from cached views
CentOS Infra including CentOS CI
Release Engineering
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- EPEL Survey Results blog post published
- hyperkitty added to EPEL 9
- Added lasso-epel to EPEL 8 and 9 to ship missing perl-lasso subpackage
ARC Investigations
The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.
Updates
- Dist-Git decoupling & ecosystem mapping
- Investigation finished and document available
- Announced to community and looking for feedback
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-1-2024/
-
This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contain updates for CPE (Community Platform Engineering) Team as the CPE initiatives are in most cases tied to I&R work.
We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.
Week: 27th November – 1st December 2023
Infrastructure & Release Engineering
Purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
Planning boardFedora Infra
- Inactive packager removal for the F39 cycle
- Make scripts to sync log files more robust
- [openshift/project] Fix the parameter order for oc apply
- Fix 500 on release-monitoring.org
- Update infra documentation
- New email alias for grome-sig
- [Pagure Exporter] Added .gitleaks.toml to avoid false positives
- [Pagure Exporter] Enhanced testing support using VCR.py
CentOS Infra including CentOS CI
- Please add epel-rpm-macros to all Hyperscale SIG buildroots
- Consolidate/reduce aarch64 workload
- Reinstall refreshed sponsored server
- Fix: Duffy seems to be inaccessible from CentOS CI OCP
- TMT compose testing prorotype
- New Koji prune policy – dry run and deployment
Release Engineering
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Retired EPEL 7 packages that fail to install due to puppet retirement
ARC Investigations
The ARC (which is a subset of the CPE team) investigates possible initiatives that CPE might take on.
Updates
- Dist-Git decoupling & ecosystem mapping
- Design of new dist-git added
- Summary of current dist-git deployment added
- You can follow your work here:
- Hackmd.io document used for notes
- Tickets for investigation
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on matrix.
https://communityblog.fedoraproject.org/infra-releng-update-week-48-2023/
-
Join the Fedora community today, 10 November and tomorrow, 11 November, for the Fedora Linux 39 Release Party & 20th Anniversary celebration. As we ring out the recent release from this past Tuesday, we continue the tradition of gathering the community for two days of sessions and social activities. Join us for the event on the RingCentral Hopin platform. Registration is required, but free.
==> Register here <==
We have an exciting line-up of content to share with you. The full schedule is also available on the Fedora Wiki. We hope you can tune in and catch it live. If not, the sessions will be recorded and shared on the Fedora Project YouTube at a later date.
You can also earn a limited-edition variant of our usual release party Fedora Badges series, created by Chris Idoko and Marie Nordin:
Artwork for the “Let’s have a party” Fedora Badge for this release’s event.We hope to see you there!
Schedule: Fedora Linux 39 Release Party & 20th Anniversary Celebration
Screenshot of the F39 Release Party & 20th Anniversary Celebration schedule. See wiki page.https://communityblog.fedoraproject.org/fedora-linux-39-release-party-20th-anniversary-celebration/
#20thAnniversary #community #event #events #Fedora39 #FedoraCommunityArchitectFCA_ #FreedomFriendsFeaturesFirst #releaseParties
-
Co-authored by benny Vasquez and Justin W. Flory.
In just over two months, the Fedora Project returns to FOSDEM in Brussels, Belgium from 3-4 February 2024 again with a stand, a bunch of friends, and our usual role as organizers of the (Linux) Distributions Developer Room (dev room).
CFP is open until 5 December 2023!
The Distributions dev room opened its CFP a couple of weeks ago. We have seen great ideas come in! If you would like to join us, submit your talk for inclusion no later than December 5th. If you’re looking for ideas, we’ve got a list of potential topics on our official CFP announcement, and you can always look at previous years for more ideas.
Important dates for FOSDEM 2024
- CFP closes: Tuesday, 5 December 2023
- Deadline for accepted speakers to confirm: Tuesday, 12 December 2023
- Final schedule announcement: Friday, 15 December 2023
What is a FOSDEM Developer Room?
Developer rooms are assigned to self-organizing groups to work together on open source projects, to discuss topics relevant to a broader subset of the community, etc.
From the FOSDEM website
The general idea is that a group of people get together to organize a mini-event inside the FOSDEM umbrella. The groups of folks submit a proposal to the FOSDEM organizers, and then recruit content and build a schedule for the room. Everyone involved is likely to be a volunteer, but the content is always extremely beneficial, and presented by leaders and experts on their topics.
How to attend
FOSDEM is a free conference that requires no registration of any kind. You just show up on the days of the event, and then attend the talks that you want to attend. It is an extremely popular event, so the talks are also recorded and posted later on the FOSDEM website.
When the schedule is live, you’ll be able to find it on the FOSDEM website, so keep an eye out for updates!
Help out as a volunteer
Will you be at FOSDEM next year from 3-4 February 2024? The Distributions dev room welcomes volunteers to help with various day-of logistics for running the dev room. If you are interested in helping out with the Distributions dev room, send an introduction email to the FOSDEM distributions-devroom mailing list.
https://communityblog.fedoraproject.org/cfp-fosdem-2024-distributions-dev-room/
#CallForPapersCfP_ #community #conference #conferences #events #FedoraAmbassadors #FOSDEM #FOSDEM2024
-
Happy new year everyone! The Fedora Ops Architect weekly has resumed after a little downtime post the holiday period. I hope you all have had a pleasant January and the year is off to a good start. Below are a few items that you might find interesting happening around the project space right now, and I look forward to being able to bring a more diverse spread of information on various activities in Fedora in weeks to come!
Upcoming Travel & Events
Some of you maybe travelling to CentOS Connect (Feb 1st & 2nd) & FOSDEM (Feb 3rd & 4th) this year – lucky you! I will be too and I am looking forward to seeing folks there so come say hi 🙂 However, this comes with the possibility that replies to messages and service requests might be a little slower with people being away from their computer, so please do be patient and as always, for anything in crisis, (ie a service is causing an outage that is infrastructure related), please check the status page, open a ticket in the infra repo and check in on the #fedora matrix channel.
The deadline for devconf.cz call for proposals is also fast approaching, March 3rd 2024, so make sure you get your talks in by this date for consideration!
Fedora Linux 40 Release
Mass Rebuild Finish Delayed
The mass rebuild finish date has been extended by one week to allow for side-tags to be merged and bugs that have emerged during the mass rebuild to be resolved, amongst other tasks, to ensure the build is done well. Right now, the targeted finish date is February 20th. All tasks from the mass rebuild start date up until and including the Beta Freeze have been extended by one week. Please check the release schedule for up to date milestone dates, and report any issues in the schedule repository.
Spins/Labs Keepalive Request
As per a requirement made by FESCo, if you are a maintainer or work in a spin or lab, you must confirm that this is to continue to be built for Fedora Linux 40. A number of tickets have been created in the schedule repo and labeled as spins/keepalive request, please confirm your keepalive request for your respective spin or lab. If you maintain a spin or lab, and did not receive a ticket to confirm, please feel free to create an issue in the repo and tag me for awareness.
Fedora Linux 40 Changes
All deadlines have now passed for changes to be proposed for Fedora Linux 40. If you are an owner of an approved chnage, please be aware that your change must be in a ‘Testable‘ state by 6th Feb 2024. All approved changes to date can be found on the Change Set page. Below are a list of changes that are currently awaiting a decision from FESCo:
- PyTorchRelese
- Replace iotop with iotop-c
- ROCm6Release
- Optimized Binaries for the AMD64 Architecture
- Java21
- ibus-anthy 1.5.16
- IBus 1.5.30
- Fedora IoT Unified Core
- DefaultBpfman
- ArmMinimalImageOSBuild
- Anaconda dir and image installations in automated text mode
- Deprecate ntlm in cyrus sasl
- Fedora IoT Bootable Container
Hot Topics
Join the conversation about planning for src.fedoraproject.org on discourse. I would love to see this topic getting his topic needs more opinions and ideas on how we can move forward with our git forge evaluation efforts this year.
There’s a thread on discourse where Fedorans visiting FOSDEM this year are sharing their plans in order to meet and connect with others attending the event too!
Another thread has been started to talk about creating and introducing a Flock location policy for DEI too, which is such an important conversation to have.
You can also weigh in on the Can We Have a Fedora OEM Installer discussion, and there’s a good conversation happening in the Criteria for making Fedora Atomic the default desktop experience thread too if you want to get involved in that conversation as well.
Help Wanted
That’s all from me this week folks, its good to be back! I look forward to experiencing my first FOSDEM this year next week, and more importantly, meeting more of the fedora community members in person too. Have a great week everyone, and as always – don’t hesitate to reach out 🙂
https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-3/
-
Starting soon: #FedoraHatch at #osc22: Packaging in @fedora and @opensuse. Originally prepared by @Defolos, but yours truly is presenting instead!
-
We are excited to invite you to the first edition of the Fedora Mentor Summit. It’s an yearly event for our community members interested in mentorship as a practice. The event is on April 1st and 2nd – 1300 UTC to 1700 UTC. Registration is open now!
This community members lead event is full of agenda of intriguing discussions, interesting talks and fun activities that everyone can be a part of. While the final schedule is still being planned, you can see the draft at the event fedocal.
What’s in it for you?
- As a Mentor: You will be able to hear and learn from mentors across various Open Source Projects. You will also get to share your experiences as a mentor to help others. You can help us by sharing how we can improve mentorship in the Fedora Project in future. You will enjoy your time networking with others, and may find yourself at the crossroads to take up new mentorship opportunities!
- As a student/mentee: Yyou will get to know our Mentored Project alumni and a lot more leaders in the space. You can interact with them about their experiences and learn how they empower mentees. You will learn how the community looks out for students and projects, and utilize a good networking opportunity.
- As a curious community member: Mentorship is all about skills that you want to learn and pass on. Everyone with the interest to learn, teach, and create a project that leads towards the success of the Fedora Project as an organization can potentially be a future mentor. This event can open doors for anyone willing to learn new skills on mentorship and community building.
Join us!
We are hosting this over Hopin on Friday, 2022-04-01 and Saturday, 2022-04-02 1300 UTC to 1700 UTC. You can also help us with suggestion and feedback as we continue shaping the event in the Mindshare matrix channel, or using our task tracker.
https://communityblog.fedoraproject.org/fedora-mentor-summit-is-here/
-
All this week, we will be testing internationalization (i18n) features in Fedora 34. Those are as follows:
- kasumi-unicode: — kasumi-unicode will be generated newly with kasumi.spec in kasumi project.
- ibus-anthy for default Japanese IME:— The current default Japanese IME(input method engine) is ibus-kkc and the default is going to change to ibus-anthy to develop Japanese IME more effectively.
- ibus-m17n as default Sinhala IME :— The current default input method for Sinhala is ibus-sayura. This should change to the ibus-m17n input method “m17n:si:sayura – sayura (m17n)”
- ibus-unikey as default Vietnamese IME :— This recommended default input method for Vietnamese will be changed from ibus-bogo to ibus-unikey
- EnableHarfBuzzInFreeType :— Goal of this feature is to enable usage of HarfBuzz in FreeType to improve hinting of glyphs of languages which needs more complicated text shaping.
- IBus 1.5.24 :— IBus will provide GTK4 IM module and enhance
ibus-setupto search input method names more easily.
How to participate
Most of the information is available on the Test Day wiki page. In case of doubts, feel free to send an email to the testing team mailing list.
Though it is a test day, we normally keep it on for the whole week. If you don’t have time tomorrow, feel free to complete it in the coming few days and upload your test results.
Let’s test and make sure this works well for our users!
https://communityblog.fedoraproject.org/test-week-internationalization-i18n-features-for-fedora-34/
#FedoraTestDays #internationalizationI18n_ #qualityAssuranceQA_
-
All this week, we will be testing internationalization (i18n) features in Fedora 34. Those are as follows:
- kasumi-unicode: — kasumi-unicode will be generated newly with kasumi.spec in kasumi project.
- ibus-anthy for default Japanese IME:— The current default Japanese IME(input method engine) is ibus-kkc and the default is going to change to ibus-anthy to develop Japanese IME more effectively.
- ibus-m17n as default Sinhala IME :— The current default input method for Sinhala is ibus-sayura. This should change to the ibus-m17n input method “m17n:si:sayura – sayura (m17n)”
- ibus-unikey as default Vietnamese IME :— This recommended default input method for Vietnamese will be changed from ibus-bogo to ibus-unikey
- EnableHarfBuzzInFreeType :— Goal of this feature is to enable usage of HarfBuzz in FreeType to improve hinting of glyphs of languages which needs more complicated text shaping.
- IBus 1.5.24 :— IBus will provide GTK4 IM module and enhance
ibus-setupto search input method names more easily.
How to participate
Most of the information is available on the Test Day wiki page. In case of doubts, feel free to send an email to the testing team mailing list.
Though it is a test day, we normally keep it on for the whole week. If you don’t have time tomorrow, feel free to complete it in the coming few days and upload your test results.
Let’s test and make sure this works well for our users!
https://communityblog.fedoraproject.org/test-week-internationalization-i18n-features-for-fedora-34/
#FedoraTestDays #internationalizationI18n_ #qualityAssuranceQA_
-
Tuesday, 2019-03-26 is the Fedora 30 Modularity Test Day!
We need your help to test if everything runs smoothlyWhy Modularity Test Day?
Featuring one of major change[1] of Fedora 29 we would test to make sure that all the functionalities are performing as they should.
Modularity is testable today on any Workstation, Labs, Spins and we will focus on testing the functionality.
It’s also pretty easy to join in: all you’ll need is Fedora 30 (which you can grab from the wiki page).We need your help!
All the instructions are on the wiki page, so please read through and come help us test! As always, the event will be in
#fedora-test-dayon Freenode IRC.Share this!
Help promote the Test Day and share the article in your own circles! Use any of the buttons below to help spread the word.
https://communityblog.fedoraproject.org/fedora-30-modularity-test-day-2019-03-26/
-
Tuesday, 2019-03-26 is the Fedora 30 Modularity Test Day!
We need your help to test if everything runs smoothlyWhy Modularity Test Day?
Featuring one of major change[1] of Fedora 29 we would test to make sure that all the functionalities are performing as they should.
Modularity is testable today on any Workstation, Labs, Spins and we will focus on testing the functionality.
It’s also pretty easy to join in: all you’ll need is Fedora 30 (which you can grab from the wiki page).We need your help!
All the instructions are on the wiki page, so please read through and come help us test! As always, the event will be in
#fedora-test-dayon Freenode IRC.Share this!
Help promote the Test Day and share the article in your own circles! Use any of the buttons below to help spread the word.
https://communityblog.fedoraproject.org/fedora-30-modularity-test-day-2019-03-26/
-
ibus-speech-to-text will provide voice dictation capabilities to any application supporting IBus input methods in #Fedora Linux 42, using VOSK for local voice recognition.
🔗 https://fedoraproject.org/wiki/Changes/ibus-speech-to-text
