Most of the Community Platform Engineering (CPE) team met in person last month in Brno during a week. CPE team is the team at Red Hat that works on Fedora and CentOS infrastructure. As a distributed team, we usually use DevConf.cz as an opportunity to meet face to face.
This is an update on what we have been up to during this week.
Continue readingI was selected to work with Fedora on the Fedora Happiness Packets for GSoC 2018! A shout-out to Jona and Bee for helping me with the proposal and initial PRs!
Hi there! My name is Anna. I go by the username Algogator on IRC and elsewhere.
The Happiness Packets is an open source platform to spread gratitude and appreciation among contributors in the community. For Fedora Appreciation Week 2018, having a Fedora themed Happiness Packets site will encourage and make it easier for people to send positive feedback to their peers (anonymously if they like). I’ll be mainly working on integrating fedmsg (to award a Fedora Badge for sending a message) and adding authentication (for FAS) to the Django project. Read more about my work on Fedora Happiness Packets over the summer on my personal blog.
This week, the Fedora Infrastructure team is convening for a Hackathon from April 9-13 at Fredericksburg, VA. You can also attend/partake remotely in #fedora-admin from 09:30 UTC-5 daily. The hackathon is intended to help the team leap ahead for several critical Fedora and CentOS initiatives. We interviewed members of the Fedora Infrastructure team to ask what the goals for the hackathon are and why it is needed.
The Fedora package tagger application is looking for new maintainers by April 5, 2018; otherwise, Fedora Infrastructure will retire the app.
Before DevConfCZ 2018, the Fedora Infrastructure team met to review the “state of the apps” in Fedora’s infrastructure. The fedora-tagger application is currently broken since the decision to retire PkgDB. The core Infrastructure team does not have bandwidth and time to focus on this application, since there are other areas to focus on at the upcoming Infrastructure Hackathon.
I was asked whether I can share sort of a report about interesting events or issues I was involved in or I noticed in the Fedora project and community which happened during the last week. So here is my first post:
This is actually two weeks old decision made by Fedora Council, however it has an overlap to the last week as well. For those who do not know, Fedora Council has decided to support Modularity initiative driven by Modularity WG and Server SIG to deliver the Fedora 27 Server edition as the Modular one. To give this initiative some spare time to be able to deliver the content in high quality the Fedora 27 Server edition is going to be delivered a bit later then the rest of the Fedora 27 release. During the last week there was done work on scheduling of this edition and the currently planned target date for Fedora 27 Server GA is 2017-11-28 having the rain date planned on 2017-12-12. See the details on Langdon’s personal page.
Beside of the scheduling there is of course hard work in progress, delivering for example lorax templates to be able to build images, and lot more.
On the Go/No-Go meeting held on Thursday 2017-09-28 the representatives of FESCo, RelEng, QA and PgM has concluded the Fedora 27 Beta build 1.5 is GOLD and can be delivered as the official F27 Beta release.
For some time already there are discussions how to deal with “string freezes” during the Fedora Release Cycle. The last week Randy Barlow, as a FESCo representative, has requested a feedback on the current policies. Please check it out and respond, if you have anything to add.
Bex has opened bid process for the next Flock 2018. I am personally glad to see the bid process started so early.
Justin has took the initiative and together with Ryan Lerch, working on the UI, have requested a deploy of an Election Application update. Hopefully, we will see more fluent flow of upcoming Elections thanks to this update.
On Fedora Council we were working on scheduling and overall organization of Elections. Finally, we have a new schedule which, as we believe, helps to solve some of the issues and complaints we were facing during the past election cycles.
During the last week we have also realized, we have an issue collecting Talking Points for Fedora 27 release. I would like to ask anyone who can contribute here, to do so. And thanks Gabriele to lead this initiative.
And of course, the list above is not exhaustive and there is much more going on in Fedora community. The list above just summarizing some tasks which has drawn my attention.
Earlier in Kevin’s announcement, it was announced that Fedora Infrastructure will retire fedorahosted.org. They urge all its active projects to move to pagure.io (or any other place they feel best meets their needs). The tentatively scheduled retirement date is February 28th, 2017.
After this announcement, there are many discussions and movement in different sub-projects. Some teams have already completed the migration successfully.
Fedora Infrastructure currently maintains two different sites for general open source code hosting: fedorahosted.org and pagure.io.
Fedorahosted.org was established in late 2007 using Trac for issues and wiki pages, Fedora Account System groups for access control and source uploads, and offering a variety of Source Control Management tools (git, svn, hg, bzr). With the rise of new workflows and source repositories, fedorahosted.org has ceased to grow, adding just one new project this year and a handful the year before.
Co-authored by Courtney Pacheco and Ralph Bean
Note: This article is a follow-up to Introduction to Modularity.
The purpose of our Modularity initiative is to support the building, maintaining, and shipping of modular things. So, in order to ensure these three requirements are met, we need to design a framework for building and composing the distribution.
In terms of the framework, in general, we are concerned about the possibility of creating an exponential number of component combinations with independent lifecycles. That is, when the number of component combinations becomes too large, we will not be able to manage them. So that we don’t accidentally make our lives worse, we must limit the number of supported modules with a policy and provide infrastructure automation to reduce the amount of manual work required.
Continue reading
Gmail is a popular email service and web client for browsing, receiving, and sending email. Gmail is used by billions of people across the world. It’s one of the simplest, most accessible email services even with being full of features. Did you know that it is possible to read and reply to other email services directly from Gmail? I’ve been doing this for years. Here is how to do it with your Fedora (fedoraproject.org) email alias.
This post was originally shared on Ralph Bean’s personal blog.
After talking with mleonova at devconf the other week, we got the idea in our heads to hold a weekly “web dev clinic” over video chat for the #fedora-apps crew. It will be a video chat lasting ~1 hour, once a week where, if you’re working on Fedora web apps or websites, you can come and either get help on a problem you’re facing, or show off your work, or both.
We’re going to try for a first meeting this coming Friday at 15:00 UTC in this video channel. We’ll run it a few weeks in a row and see how it goes.. maybe continue indefinitely?
Copyright © 2019 Fedora Community Blog
Theme by Anders Noren — Up ↑
Recent Comments