Videos for Red Hat Summit 2021
by Karsten Wade
Folks:
Would you be interested in making a short (1 to 3 minutes) video that
highlights a key takeaway about this community and our content for
attendees at Red Hat Summit 2021?
This year (and once again) the Red Hat Summit is going to be a virtual
experience. Our community has a booth in the wildly popular[1]
"Community Central" part of the virtual expo hall.
For our virtual booth, there are some materials I've been working on
with Bryan Berenshausen. The Open Source Way is sharing a booth in a
"Knowledge Sharing" area with the Open Org community
(https://theopenorganization.org/) that Bryan is a community manager for.
Part of this is having two videos for the Open Source Way. It's
recommended (and kind to everyone) to have shorter videos to help with
online conference fatigue.
The deadline for a finished MP4 file is 12 March 2021. If you'd like to
brainstorm ideas, see who might want to collaborate, and so forth,
please speak up.
What are some stories we've been itching to tell?
What are some fiery opinions we want to hold forth on?
What care can we show the world via this medium?
I'm quite curious what we'll come up with!
Regards,
- Karsten
[1] In-person, the Community Central space is quite literally the center
of activity on the expo hall floor, as attendees come to meet directly
with contributors and leaders of many key open source upstream projects.
Booth staff often includes non-Red Hatters who are able to attend the
event with an Exhibitor pass. Online last year we didn't find as much
value for contributors to be present during the virtual experience, but
everyone benefited from helping create presentations and videos for
upstream communities.
--
Karsten Wade [he/him/his]| Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
https://theopensourceway.org | https://github.com/theopensourceway/guide
3 years, 9 months
Our brand
by Karsten Wade
Discussions have started back up around creating a brand with associated
logo, color palette, design elements, and the like. You are invited to
participate, as a community member reviewing design ideas, or directly
involved in generating designs and related tasks.
Ideally, we'll be able to apply some beta decisions in the debut
announcement, such as color palette and a logo idea.
Main branding task and tracking ticket:
https://github.com/theopensourceway/theproject/issues/62
Logo discussion:
https://github.com/theopensourceway/theproject/issues/13
These elements are the building blocks and patterns for the website,
guidebook styling, print book styling (for PDF), and so forth.
If you are interested in this topic, we should be seeing some items
coming from Tuomas Kuosmanen and Shaun McCance (from Red Hat's OSPO) for
your input.
The list of items in issue #13 are the needs we're tracking for this.
Take a look, any questions or anything missing?
We could use some illustration skills, especially around a book cover
design that can be applied to the PDF and prepare for a possible printed
run future.
Tuomas—what other skill gaps do we need to fill?
There are also some web designer skills needed around styling the
Asciidoc output, including building a multi-page website for the HTML
version (perhaps generated by Antora?).
Shaun—what skill gaps do we have around the various book rendering tools?
There are some large and some small tasks in here, and we should all be
able to review some iterations of the work created by those who step up
to work on the task. Ultimately, we should let designers and the doers
of the task decide on the choices we consider and brand we land on.
Best regards,
- Karsten
--
Karsten Wade [he/him/his]| Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
https://theopensourceway.org | https://github.com/theopensourceway/guide
3 years, 9 months
Read the whole book? An invite
by Karsten Wade
Hiya folks,
As we get closer to drawing a lot more eyes on our guidebook, now is a
great opportunity to go back and read some or all of the content with
refreshed eyes.
https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html
https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.pdf
Following are ideas on what you can do with your comments or fixes:
In addition to reading the entirety for the sense of cohesion and
narrative, some things you might look out for:
* Grammatical anything.
* Glitches, messed up markup, etc.
* Whatever else catches your eye.
What to do if you find something to fix or comment on?
1. You can check the common bugs lists, this is where most easy typos
go: https://github.com/theopensourceway/guidebook/issues/194
2. You can choose to find the .adoc file and do fixes to result in a
pull request.
3. If you want to write up a list of comments and reference points (page
& para on PDF/link & para for HTML), you can put those in a single
GitHub issue, or an email, or a stand-alone document.
4. If Google Doc is your tool at this point or for this task, you can
pull in the doc to a Google Doc then share that with us for commenting
back on and make it public read-only, that would be great, too.
For the last two methods (3 & 4), once we are finished discussing any
proposed changes in an issue/doc/thread, we could use help from anyone
with experience or wanting to learn about editing Asciidoc directly and
using GitHub to make the pull request. You would go through the edits
and comments, make them in the associated files, then do a pull request
for the edits. I will train and hand-hold anyone interested in this.
Caveats
=======
* The PDF has some known issues; we'll try to get them all on the common
bug reports (below).
* We're shuffling in and around some content that has been coming in
since the 2.0 release; the idea is to roll in these additions and
changes for the debut (thus it'll really be 2.0.1 or so). I'll work to
keep that clean, and offer chances for reviews of the new content.
Best regards,
- Karsten
--
Karsten Wade [he/him/his]| Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
https://theopensourceway.org | https://github.com/theopensourceway/guide
3 years, 9 months