Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish Fedora DevConf CZ retrospective #3

Open
6 tasks
jwflory opened this issue Oct 17, 2024 · 0 comments
Open
6 tasks

Publish Fedora DevConf CZ retrospective #3

jwflory opened this issue Oct 17, 2024 · 0 comments
Assignees
Labels
CATEGORY::events In-person and virtual events PROJECT::Fedora Fedora Project Community Architecture SCOPE::new change Adds new capabilities or functionality

Comments

@jwflory
Copy link
Member

jwflory commented Oct 17, 2024

Summary

Publish a public retrospective that summarizes the Fedora Project participation at DevConf CZ and why this is an important event for the Fedora community.

Background

Fedora contributors are everywhere and many of our community members represent the community at events large and small, formally and informally. However, some events have special significance and DevConf CZ is one of those events. It is an important event because Fedora has participated for a long time, but also because it attracts our contributor community. It is also tied closely to Red Hat due to its proximity to the RH Brno office, making it a convenient location for Fedora contributors employed by Red Hat in Europe. So, because DevConf CZ is an important event for our community, we need to document and message on the value of the event for Fedora.

The scope of this issue is to put together a retrospective on DevConf CZ and Fedora, using a data-driven approach and offering recommendations for how Fedora can continue to use DevConf CZ as an important event for our contributor community. It also sets the stage for why we are making certain changes to the Flock 2025 planning.

Details

There are some data sources to consider, as well as a potential roadmap for achieving this issue.

Data sources

Fedora Badges data

Fedora swag survey

A tip of the hat to @smeragoel who put together this survey and helped us get attendees to fill this out during the event:

A bar chart showing the preferences of 49 people for their favorite swag items. The responses are used to help determine popular swag items that the Fedora Project community wishes to see. This survey was shared with attendees at DevConf CZ, a yearly open source conference in Czechia. The chart includes categories such as T-shirts, Pens, Stickers, Socks, Bags, Tech Items, Drinkware, Stress Balls, Notebooks, Pajamas, Hoodies, Fedora Geekos, Mugs, Screen Cleaners, and more. The most popular swag item is t-shirts, followed by socks, stickers, and drinkware.

Roadmap

  • Write a thesis statement for the value of DevConf CZ to the Fedora community
  • Create an outline for an article spotlighting the Fedora engagement at DevConf CZ
  • Draft an article that fits the outline, use the data sources above to support the thesis statement
  • Request review by Dorka Volavkova, Jason Brooks, Matthew Miller, Aoife Moloney
  • Request editor review in the CommBlog
  • Schedule and publish article!

Outcome

A stronger connection is made between the Fedora community and DevConf CZ, and its role as an important event for the community is better understood by contributors and users alike.

@jwflory jwflory added PROJECT::Fedora Fedora Project Community Architecture CATEGORY::events In-person and virtual events SCOPE::new change Adds new capabilities or functionality labels Oct 17, 2024
@jwflory jwflory self-assigned this Oct 17, 2024
@jwflory jwflory added this to the Fedora Council 2025 Hackfest milestone Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CATEGORY::events In-person and virtual events PROJECT::Fedora Fedora Project Community Architecture SCOPE::new change Adds new capabilities or functionality
Projects
Status: Backlog
Development

No branches or pull requests

1 participant