Update the seat title for "Fedora Community Action & Impact Coordinator" to "Fedora Community Architect"
I was recently working together with @mattdm and @bcotton on our role pages in the Council docs, as part of a review of our documentation. While reviewing the FCAIC role documentation, I took a new look at the role title and whether I felt it was still right. While it does describe the project well, it still doesn't feel quite right to me, in a similar way that Community Leader didn't feel right in 2016. I spent some time thinking about the FCAIC role, how it has changed over the years, and what I feel it describes. Since I am still early on in the role, it felt like a good time to consider a title change.
I settled on Fedora Community Architect as the new title for the FCAIC role. In addition to being shorter, I feel like it better describes the role. Community work does not have an industry-accepted job ladder, as is more common with software engineering. Red Hat eventually settled on the title of community architect for community work in its pioneering Open Source communities. I also like Community Architect as a title. There is more literature and examples for others to understand the work.
Ultimately, the goal of changing the name is to better describe the role and what the F.C.A. does in Fedora. The lengthy "F.C.A.I.C." title usually came with an explanation to others unfamiliar with Fedora and our community culture. F.C.A. is also a handy shortening of the longer F.C.A.I.C. acronym too!
There are two parts:
The second part is advantageous because it will also help me better determine the age and relevance of documentation over time. The important things will get updated first, but things that are secondary or outdated will lag behind. As I find outdated content, I can either update, redirect, or retire it.
The Community Action and Impact seat on the Fedora Council is renamed from "Fedora Community Action & Impact Coordinator" to "Fedora Community Architect"
I've created a topic on Fedora Discussion for this ticket.
Please keep this ticket focused. Discuss there, and record votes and decisions here. Thanks!
@jflory7 since this is a ticket, are you intending this to be put to a vote? Or is it fait accompli and you're just using this to track work?
I am using this ticket mostly to track the work, but also I am curious from others if there is more outreach that should go along with this. Like a CommBlog article perhaps?
I prepared a Community Blog article for review to summarize this change and why it was made. Most of the text comes from this issue. Once this article is scheduled for publishing, this issue can be closed as complete.
I am asking for the Fedora Council to take a preliminary review of the article as time allows, although I am not blocking for feedback by the Council since it was discussed during our February 2023 in-person hackfest in Frankfurt, Germany. I am proceeding with asking for a publish date for the article with @bcotton.
Metadata Update from @jflory7:
- Issue priority set to: Waiting on Assignee (was: Next Meeting)
The blog post is out. I'm calling this done. :wine_glass:
Metadata Update from @jflory7:
- Issue close_status updated to: resolved
- Issue status updated to: Closed (was: Open)
to comment on this ticket.