(Create initial draft of retrospective) |
(Add some positives to our list of accomplishments) |
||
| Line 12: | Line 12: | ||
=== What did we do right? === | === What did we do right? === | ||
* We really did a goob job with… …because… | * We really did a goob job with… …because… | ||
* The Elections cycle for December 2015 was handled very well and become the fourth most participated election of all-time in Fedora. Using the Community Blog as a publishing platform for candidate interviews helped share candidate platforms and also help build readership of the Community Blog. The overall communication about the elections went smoothly and helped set the bar for what's needed for future elections. --[[User:Jflory7|Jflory7]] ([[User talk:Jflory7|talk]]) 15:01, 5 July 2016 (UTC) | |||
* Introducing the [[Community Blog]] as a publishing platform and separating it from the [[Magazine]] helps us specialize between "marketing" and "internal communication". The CommBlog is great for publishing contributor-specific news about development, events, and updates across the project. It allows the Magazine to have a more strategic approach in reaching out to non-contributors and users as well. --[[User:Jflory7|Jflory7]] ([[User talk:Jflory7|talk]]) 15:01, 5 July 2016 (UTC) | |||
* | |||
=== What can we do better? === | === What can we do better? === | ||
Revision as of 15:01, 5 July 2016
This is a CommOps retrospective generated using the Marketing retrospective SOP (sort of).
History
This is the first-ever CommOps retrospective for a Fedora release. Taking a page from the Marketing retrospective, the CommOps retrospective is a chance for us to reflect on our progress and accomplishments as a team, evaluate what worked well, what didn't work well, and how we can improve. This retrospective is open for participation to any and all contributors. Whether you contributed once to a topic in a meeting or if you closed 100 tickets, your opinion and thoughts are equally valued in this retrospective to help better gauge how we are doing and what we can do better.
In the past year, a lot of things have happened. Firstly, CommOps became a thing! We officially began around October or so, judging by our first meeting date. We've created over 70 tickets in our Trac, closed roughly half of them, and are helping bring unity and cohesion to the project. One of the deliverables from our work is the Community Blog, which recently hit over 100 posts. With coming release cycles, we hope to accomplish more as a team and a project together. Some of the largest objectives for coming release cycles is improving the on-boarding process for new members of sub-projects and teams, as well as helping improve communication of information across teams, such as with Ambassadors and Design.
Good Stuff
What did we do right?
- We really did a goob job with… …because…
- The Elections cycle for December 2015 was handled very well and become the fourth most participated election of all-time in Fedora. Using the Community Blog as a publishing platform for candidate interviews helped share candidate platforms and also help build readership of the Community Blog. The overall communication about the elections went smoothly and helped set the bar for what's needed for future elections. --Jflory7 (talk) 15:01, 5 July 2016 (UTC)
- Introducing the Community Blog as a publishing platform and separating it from the Magazine helps us specialize between "marketing" and "internal communication". The CommBlog is great for publishing contributor-specific news about development, events, and updates across the project. It allows the Magazine to have a more strategic approach in reaching out to non-contributors and users as well. --Jflory7 (talk) 15:01, 5 July 2016 (UTC)
What can we do better?
- We could have done… …better by trying to…
Improvements
Where did we have gaps?
- There were gaps with how we… …because…
How do we bridge them?
- We can solve… …by…
Ideas and Wishlist for F25
- I wish for…
Improve this retrospective!
If you see a way to improve this retrospective, please go ahead and edit the page - you don't need to ask for anyone's permission. Read more about our contribution philosophy.