Working preview build in 'quaid-toc-fixes-1' branch
by Karsten Wade
Hi all:
I've been working on producing a nice test build so I can begin
visualizing how the chapters are fitting together. After some tweaking,
I have committed a branch 'quaid-toc-fixes-1' with the changes.
Here is what it looks like:
https://www.theopensourceway.org/preview-1.99-book.html
(This build does NOT include any of the copyedits I have completed/am
working on this week. It is more for visualization purposes. I will
begin doing actual early builds as each PR lands, likely to that same URL.)
You can check my working branch out here:
https://github.com/theopensourceway/guidebook/tree/quaid-toc-fixes-1
I'm going to carry these changes in this branch for now, because there
are several pull requests with lots of changes in the main branch. I'll
rebase this branch against the main until all the PRs land, then I'll
land these nesting/build changes into main at that point.[1]
It's also possible that a different approach to building will get tested
and used for this preview, so this branch is only an ephemeral work in
progress at this point. I haven't looked at what the Open Organization
has been doing yet, for example.
Kind regards,
- Karsten
[1] The main thing happening in the branch are the two bash scripts that
add or remove a '=' character in place of each '=' that appears at the
start of a line. This has the effect of moving each section in the
chapter upward or downward in nesting, depending on which script runs.
So the work here is to rebase against the main branch, then rerun the
script and test the build. In the end it's just a few minutes work to
adjust the nesting for all chapters in a build.
--
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
4 years, 1 month
Push to preview release
by Karsten Wade
All:
Over the next week I'm going to focus on getting our preview release
ready and out for release.
Expect some new threads to pop-up on list here as I come across
decisions to make that can benefit from group input and consensus.
Please jump in with thoughts and answers, early and often. The sooner we
get to consensus, the more it helps the publishing pipeline.
Other items I'll do my best to document as I go, and for any smaller,
be-bold decisions I make, we can always reconsider them for the full 2.0
release etc.
Kind 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
4 years, 1 month
Being a community of practice
by Karsten Wade
I want to open a thread to discuss the kinds of things we are and can be doing from a community of practice (CoP) perspective, so above and beyond just working on the guide.
For one example, is there interest in having a monthly CoP meeting? It would be more than just business and social, but a chance to hear from each other around specific areas of practice.
For another, our OSPO at Red Has begun to bring content upstream that is more meta-practice material rather than specific items for the guide. We can discuss how this community can begin to act as stewards of a central repository of best practices content (what, how, and why).
And another, I've begun to talk publicly about this community of practice toward growing beyond the current 2.0 guide work. But we haven't really looked at how we want to run this CoP.
(This dovetails with a separate discussion we need to get started about governance of this community, so we can look at how to enter 2021 under community-defined leadership.)
Kind regards,
- Karsten
4 years, 1 month