If we decide to publish a third edition of the Leaders Manual, I'd like to update the book's preface.

Author @shabnoorshah shared an early draft of a chapter she's writing to this effect.

This is a proposed chapter from @HeidiHVL.

In v2.2., p. 164, the caption for Figure 1 doesn't accompany its associated image. Instead, it's on the next page (p. 165). The caption should always remain with the image.

Figure captions seem to be an issue in v2.2 (see #37).

This is a proposed chapter from Catherine Louis.

This is a proposed chapter from @samuelknuth.

Editor @semioticrobotic will write a short preface to the new edition of the book.

I'm finding grammatical errors in the chapters. Am I able to make changes and create a pull request?

Or, because these chapters are originally blog posts, we can't fix any errors we find?

Any chance on releasing this as ePub also? PDF is good for printing, but not very friendly for readers. Thanks.

This is a proposed chapter from Jim Hall.

This is a proposed chapter from MaryJo Burchard.

This is a proposed chapter from @arob98.

The fourth inline subhead on PDF page 30 is not typeset correctly. I should be typeset in small caps, as the preceding three inline subheads are.

Hi there, Not sure if this had already been discussed and I missed it... I was wondering if there was a possibility of walking the walk and move from CC-BY-SA to at least CC-BY? Mostly b/c the license stacking issues that come with an SA restriction can cause so many problems for folks who want to remix our materials. CC-BY is the most restrictive license (other than CC0, which isn't really a license) recommended by the Open Access Scholarly Publishers Assn: https://oaspa.org/why-cc-by/

In v2.2, p. 129, the caption for Figure 1 contains an improper line break. Testing indicates a missing carriage return before the caption.

The new Leaders Manual chapter from Jos Groen references a figure (DISCO model), but that figure is not included in our images folder. We'll need to collect it and confirm licensing.

The book's preface directs readers to a now-deprecated GitHub repository for this book and its materials. We need to update that link to https://github.com/open-organization/open-org-leaders-manual.

As the Leaders Manual begins the long, slow march toward a second edition, we might want to consider re-visiting the book's subtitle to be sure it's as compelling as it could be.

It's currently:

Instructions for building the workplace of the future.

Would another subtitle—one more reflective of proposed changes to the book's table of contents—be better suited to the new edition?

Source files for book chapters contain hyperlinks that should actually be footnotes. Before we release any future editions, we should convert all those hyperlinks to footnotes. Doing this would save an incredible amount of time in production.

Instructions

Markdown syntax for footnotes is (surprise!) very simple. A footnote has two parts: the in-text part and the at-the-end part.

At the end of a sentence with a footnote, you add the following text:

[^unique-identifier]

Where unique-identifier is a brief (one or two words) that identify that footnote and distinguish it from all others in the whole book (that part is important).

Then, at the end of the document, you add:

[^unique-identifier]: The text of the footnote.

And that's it! When the chapter renders, it'll contain sequential footnotes all linked to their appropriate references.

Notes

• If you'd like to see an example of how this works, see my preface, which I've already updated.
• I am happy to participate in this effort but wanted to be sure to open up the work to others, too, as this sort of task is something a newcomer might also complete to become more familiar with our materials (and make a huge impact on a core project right away!).

This book's unique introduction comes from @jenkelchner.

As this volume uses Red Hat Text for headings, headers, and section separators, the footer should also use this typeface.

Please can the following grammatical be fixed, thank you.

Page 51, Paragraph 1, Sentence 2

From
"Or your could get more creative: "

(remove 'r' from 'your')

To
"Or you could get more creative: "

Page 55, Paragraph 3, Sentence 5

From
"But ultimately whether you do this through a something like a spreadsheet, an intranet site, or a special tool doesn't matter."

(remove duplicate 'a' before 'something', and move 'doesn't matter' to the beginning of the sentence)

To
"But, ultimately, it doesn't matter whether you do this through something like a spreadsheet, an intranet site, or a special tool."

Page 55, Paragraph 4, Sentence 1

From
"A3 reports are the result of a work method or a problem solving approach, one that emerged from Toyota and the Toyota Production System,"

(remove 'a' "," and "one" from sentence)

To
"A3 reports are the result of a work method or problem solving approach that emerged from Toyota and the Toyota Production System,"

Page 57, Paragraph 1, Sentence 1

From
"In his book Toolbox for the Agile Coach: Visualization Examples Jimmy Janlén describes"

(italicize the book title, add "," before author)

To
"In his book Toolbox for the Agile Coach: Visualization Examples, Jimmy Janlén describes"

Page 57, Paragraph 2, Sentence 2

From
"The transparency make sure everyone know the status of different improvements,"

(add 's' to 'make' and 'know')

To
"The transparency makes sure everyone knows the status of different improvements,"

After years of talk about tech's lack of diversity, open source leaders want to learn how they can solve this problem. If OS maintainers design communities with diversity and inclusion embedded in their projects' strategies, many past problems will be easier to address. This proposed new chapter to the Leaders Manual will discuss:

• The difference between diversity and inclusion

• Why diverse, inclusive open source communities are more successful

• How to embed diversity and inclusion into your OS project's strategy

• Case studies of successfully diverse, inclusive OS communities, including Mozilla and Kubernetes

This chapter will be based on a presentation I gave at OS Summit North America in San Diego in August 2019.

We've published the Open Leadership Definition! But currently it's not part of our manual for leaders. I think it should be.

Abstract:
Conventional organizations have a difficult time understanding how they can transform their culture using the Open values. Often, the change feels overwhelming and the advice feels too theoretical and "pie in the sky". However, there are practical ways that leaders can use to start being more open and using the Open Org values.

This chapter begins by asking "what is culture?" and describes how time-bound project definitions and open values can be used to transform organizational culture.

Hi there. I spotted a few minor fixes to be made to the content. If this could be updated, that would be great, thanks.

Pg 66, last paragraph, sentence 2
From
using "agile" is an explanation
to
using "agile" as an explanation

Pg 73, 1st paragraph, last sentence
from
chose
to
choose

Pg 92, 7th paragraph, 1st sentence
remove repeated word "culture"

Pg 95, 2nd paragraph, 2nd last sentence
from
voice of the community inside company
to
voice of the community inside the company

Pg 96, 3rd paragraph, 4th sentence
from
rules that they undertakes
to
rules that they undertake

Pg 101, 1st paragraph, last sentence
This one is tricky. I'm not entirely sure what the intention of the sentence. However, here is my interpretation of it.

From
In this day and age,thanks to the advent of open source communities research department is opening up to the entire world.
to
In this day and age,thanks to the advent of open source communities, research departments are opened up to the entire world.

Pg 116, 3rd paragraph, last sentence
remove repeated word "to"

Pg 125, 1st paragraph, 1st sentence
From
In a scene in from
to
In a scene from

Pg 126, 5th paragraph, 3rd sentence
from
(o how don't they)
to
(or how they don't)

Pg 137, last paragraph, 2nd sentence
remove repeated word "use"

Pg 152, 5th paragraph, 1st sentence
from
way to solve multiples issues
to
way to solve multiple issues

Pg 152, 5th paragraph, last sentence
from
clarity of purpose the talents
to
clarity of purpose and the talents

The link to the Dejavu Sans website on page 8 of the book seems to be wrong. May be the link to https://dejavu-fonts.github.io/ would be appropriate instead.

Margins for some of the book's front matter (the copyright page, the table of contents, etc.) are too narrow. The PDF and printed versions of the book look cramped as a result.

In preparation for a revised Third Edition of the Leaders Manual, we need to review the table of contents and create a working ToC for the revised edition.

Before we ship a new version of the manual, we'll want to be sure our About the contributors section is updated.

The footnote on (PDF) page 52 is somehow formatted, as the footnote appears above the separator rather than below.

This is a proposed chapter from Irupé Niveyro.

I've reviewed this article and started making adjustments. It's still highly relevant and I don't think it needs loads. Have been working in the original google doc:

https://docs.google.com/document/d/1LAInEJ67uFP-UL8aiw9XCViJlg_5xLBYAODyw2aed1g/edit

This is a proposed chapter from @jenkelchner and MaryJo Burchard.

This is a proposed chapter from @LauraHilliger and @amatlack.

Alternate heading: Visualize your plans

Strategic (and other) plans are often shared only with a certain group and perhaps communicated in an all staff meeting and on the intranet and then forgotten by the masses. By making plans visual and open you will get more collaboration as well as better understanding of the plans and the way forward. I would share examples on how to use visualization methods, techniques, and tools to better collaborate and communicate plans and progress.

This is a proposed chapter from Alessio Fattorini.

This is a proposed chapter from @samuelknuth.

The repository README does not explain inclusion of ePub format.

Can @trncb please fix and submit a pull request?

This is a proposed chapter from Michael Doyle.

This is a proposed chapter from DeLisa Alexander.

We need to review/revise/update articles in preparation for the revised Third Edition of the Open Org Leaders Manual.

• Update the article
• Update personal bio (for #45 )

This is a proposed chapter from @jenkelchner.

This is a proposed chapter from Curt Carver.

Author @RonMcFarland would like to reprint a recently published essay series on the subject of collaboration, bias, and cognitive noise.

That series ran recently on Coaching Buttons as:

• Fighting life's distractions
• Reduce noise to make better decisions

We can (re)combine these installments into a single chapter.

New writing from @JosGroenNL on his specific approach to transformational leadership.

The word "pasties" appears here (p. 93 of the PDF) when the word should be "pastries."

This is a proposed chapter from Catherine Louis.

Either update and add new ideas and experiences or write a separate chapter. What do you think @semioticrobotic ? I have a more recent example using the Open Decision Framework and a bit more experience using A3 reports. Then Spotify Rhythm and the Servant Door is now a bit old (and probably not relevant in Spotify either).

This is a proposed chapter from Chad Sansing, Sarah Allen, and Stephanie Wright.