Author: Ben Cotton (page 1 of 21)

Community Blog monthly update: April 2021

This is the latest in our monthly series summarizing the past month on the Community Blog. Please leave a comment below to let me know what you think.

Continue reading

Friday’s Fedora Facts: 2021-17

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)!

Fedora Linux 34 was released on Tuesday. Fedora Linux 32 will reach end of life on Tuesday 25 May.

Join us tomorrow for day two of the Fedora Linux 34 Release Party

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

Continue reading
Sticky post

F34 elections nominations now open

Today we are starting the Nomination & Campaign period during which we accept nominations to the “steering bodies” of the following teams:

This period is open until 2020-05-12 at 23:59:59 UTC.

Continue reading

Friday’s Fedora Facts: 2021-16

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)! Fedora Linux 34 is GO and will release on Tuesday 27 April. Fedora Linux 32 will reach end of life on Tuesday 25 May.

Join us at the Fedora Linux 34 Release Party next Friday and Saturday.

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

Continue reading

Friday’s Fedora Facts: 2021-15

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)! The Final freeze is underway. The F34 Final Go/No-Go meeting is Thursday.

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

Continue reading

Community Blog monthly update: March 2021

This is the latest in our monthly series summarizing the past month on the Community Blog. Please leave a comment below to let me know what you think.

Continue reading

Friday’s Fedora Facts: 2021-14

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)! The Final freeze is underway. The F34 Final Go/No-Go meeting is Thursday.

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

Continue reading

Help wanted: program management team

I’d love to spend time in different Fedora teams helping them with program management work, but there’s only so much of me to go around. Instead, I’m putting together a program management team. At a high level, the role of the program management team will be two-fold. The main job is to embed in other teams and provide support to them. A secondary role will be to back up some of my duties (like wrangling Changes) when I am out of the office. If you’re interested, fill out the When Is Good survey by 15 April, or read on for more information.

About the team

You can read more about the team on Fedora Docs, but some of the duties I see team members providing include:

  • Coordination with other Fedora teams (e.g. Websites, design)
  • Consulting on team process development and improvement
  • Tracking development plans against the Fedora schedule
  • Issue triage and management
  • Shepherding Change proposals and similar requests

Since this is a new team, we still have a lot to figure out. As we go, we’ll figure out what works and adjust to match.

About you

You don’t need to be an expert to join the team. I’d like everyone to have some experience with either contributing to Fedora or project/program management. If you’re lacking in one, we can help fill in the gaps. You should be well-organized (or at least able to fake it) and have 3-5 hours a week available to work with one or more teams in Fedora.

How to join

Fill out the When Is Good survey by 15 April to indicate your availability for a kickoff meeting. This will be a video meeting so that we can have a high-bandwidth conversation. I’m looking for four or five people to start, but if I get more interest, we’ll figure out how to scale. If you’re not sure if this is something you want to do, come to the meeting anyway. You can always decide to not participate.

How to get help from this team

If you’re on another Fedora team and would like to get support from the program management team, great! We don’t have a mechanism for requesting help yet, but that will be coming soon.

Friday’s Fedora Facts: 2021-13

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)! The Final freeze begins Tuesday.

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

Remember that many locations are changing to/from summer time in the next few weeks.

Continue reading

Policy proposal: Update default content license to CC BY-SA 4.0

Earlier this month, Matthew Miller suggested the Fedora Council update the default content license from the Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license to the Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0) license. This license applies to content (not code) submitted to Fedora that does not have an explicit license attached. It does not override the explicit license choices of contributors or upstream projects.

Continue reading
Olderposts

Copyright © 2021 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑