I'm somewhat stalled/stuck with the bits around the debut
announcement this month. I'm also recognizing I'm falling into my
habit under stress of feeling responsible for everything and not putting
energy into communicating and asking for help. ;-D
So to follow our own best practices, I'd like to outline where we are
with the debut and what needs to be completed so other folks can take on
some of the responsibilities and pleasure of the work. That is, would
you like to help?
The status and to-do item tracking is here:
Even the 'Assigned' items need help in creating and reviewing the works.
Cards have varying levels of details, I hope there is enough to start
with, ask any questions please. (This plan/list came from an original
punchlist and may be incomplete!)
I'm working on the two blog posts right now, and I'll leave other cards
unassigned for others to pick up and work on. Those include:
* Creating the good old release announcement itself.
* Working with Shaun, Tuomas, and myself on branding and logo.
- We are featuring our "brand in beta form" for the release; it may
be alpha form?
* Applying alpha/beta branding to HTML/CSS, PDF, and EPub.
* Review GitHub page and theopensourceway.org
for changes ahead of
* Preparing social media content for the debut.
Chime in with interest, don't hesitate, even small contributions are
welcome and helpful!
To set the context for the debut: the end goal is to have a project
release announcement to attract readers to our work. Our subtext is,
growing our readership (users) while making this overall project easy to
participate in attracts and enables members and contributors for the
community of practice.
Once the debut/promotion of our efforts is out there, we can begin other
community efforts that depend on the world knowing about the guidebook:
* Those of us interested in gathering 'why' stories from non-author
community managers can start. The planning for that happens here:
* Editorial is cleared to begin working on the 2.1 content—
- Expansion of self-care/mental health
- Expansion of mentoring content
- What else?
* Discuss and choose a governance for ourselves.
* Start the community of practice elements, such as monthly
demo/practice meetings open to the wider community.
* All the other stuff at:
Karsten Wade [he/him/his]| Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen