Congratulations everyone! Sincerely,
Dr. Philip A. Foster Maximum Change Leadership & Business Consulting *"Developing 21st Century Leaders and Organizations"* http://www.maximumchange.com Best selling author of The Open Organization (TM) - A New Era of Leadership and Organizational Development. Publish Date: June 2016: http://tiny.cc/gwpzby The Open Organization is a registered Trademark of Maximum Change. Organization 3.0 - The Evolution of Leadership and Organizational Theories Toward an Open System for the 21st Century. http://www.amazon.com/dp/B00D5UIY3M <http://www.facebook.com/l.php?u=http%3A%2F%2Fwww.amazon.com%2Fdp%2FB00D5UIY3M&h=tAQFpwLA4&s=1> telephone: (513) 399-7247 skype: philip.a.foster facebook: http://www.facebook.com/maximumchangeinc twitter: http://www.twitter.com/maximumchange and http://www.twitter.com/openorgs linkedin: http://www.linkedin.com/in/maximumchange blog: http://maximumchange.wordpress.com/ *This message is intended only for the use of the party addressed and may contain information that is confidential. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately.* On Fri, Jun 30, 2017 at 12:00 PM, <[email protected]> wrote: > Send Openorg-list mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/openorg-list > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Openorg-list digest..." > > > Today's Topics: > > 1. Now Available for Public Comment: OpenOrg Maturity Model > (Bryan Behrenshausen) > 2. Re: Now Available for Public Comment: OpenOrg Maturity Model > (Allison Matlack) > 3. Re: Now Available for Public Comment: OpenOrg Maturity Model > (Bryan Behrenshausen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Jun 2017 14:54:46 -0400 > From: Bryan Behrenshausen <[email protected]> > To: [email protected] > Subject: [Openorg-list] Now Available for Public Comment: OpenOrg > Maturity Model > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > Hello friends, > > The Open Organization Ambassadors are please to announce a final draft > of their most recent collaborative effort, The Open Organization > Maturity Model. As the Model's introduction explains: > > > "The Open Organization Maturity Model is a framework for helping your > organization become more transparent, inclusive, adaptable, > collaborative, and communal. It outlines steps that individuals, teams, > and organizations can take to critically examine their organizational > practices and chart their progress toward becoming a more open > organization (as outlined in the Open Organization Definition)." > > This document is the product of months of hard work and persistence, and > it's now publicly available on GitHub for public comment and review. The > group welcomes feedback as it prepares to determine whether it will > incorporate the document into the official Open Organization Definition. > You can comment here: > > https://github.com/open-organization-ambassadors/open- > org-definition/pull/13 > > Congratulations to everyone who helped the project come this far. > > Sincerely, > Bryan > > > > ------------------------------ > > Message: 2 > Date: Fri, 30 Jun 2017 08:53:46 -0400 > From: Allison Matlack <[email protected]> > To: Bryan Behrenshausen <[email protected]> > Cc: agilecoaches <[email protected]>, [email protected] > Subject: Re: [Openorg-list] Now Available for Public Comment: OpenOrg > Maturity Model > Message-ID: > <CABCW1OFpS9_JsqrV0fC4iwT-7zknj5Zi9fXROpjajrmPoBtT5g@ > mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hey Bryan, > > I forwarded this email to the Agile Coaches group -- I thought we might > want to contribute to (or at least be aware of) these initiatives as we > start to think about transformation work at Red Hat. > > There was a question about our usage of github that I'd like to bring back > to this list: > > "the comment in the overall readme for that github repo says that comments > need to be submitted by a date in order to incorporated into the general > repo. Is it not the open source way to always take additional comments and > Pull Requests to improve the overall process and practices?... I wanted to > ask why we aren't keeping comments and improvements items as a consistent > and iterative manner to achieve the goal of the best product possible." > > My initial guess was that you needed comments by a certain date due to > publication/announcement reasons. But is there a specific reason why we're > not calling for continual comments/improvements? > > Thanks, > -Allison > > > On Thu, Jun 29, 2017 at 2:54 PM, Bryan Behrenshausen <[email protected]> > wrote: > > > Hello friends, > > > > The Open Organization Ambassadors are please to announce a final draft > > of their most recent collaborative effort, The Open Organization > > Maturity Model. As the Model's introduction explains: > > > > > "The Open Organization Maturity Model is a framework for helping your > > organization become more transparent, inclusive, adaptable, > > collaborative, and communal. It outlines steps that individuals, teams, > > and organizations can take to critically examine their organizational > > practices and chart their progress toward becoming a more open > > organization (as outlined in the Open Organization Definition)." > > > > This document is the product of months of hard work and persistence, and > > it's now publicly available on GitHub for public comment and review. The > > group welcomes feedback as it prepares to determine whether it will > > incorporate the document into the official Open Organization Definition. > > You can comment here: > > > > https://github.com/open-organization-ambassadors/open-org- > > definition/pull/13 > > > > Congratulations to everyone who helped the project come this far. > > > > Sincerely, > > Bryan > > > > _______________________________________________ > > Openorg-list mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/openorg-list > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <https://www.redhat.com/mailman/private/openorg-list/ > attachments/20170630/10cdf0f6/attachment.html> > > ------------------------------ > > Message: 3 > Date: Fri, 30 Jun 2017 09:12:22 -0400 > From: Bryan Behrenshausen <[email protected]> > To: Allison Matlack <[email protected]> > Cc: agilecoaches <[email protected]>, [email protected] > Subject: Re: [Openorg-list] Now Available for Public Comment: OpenOrg > Maturity Model > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > On 06/30/2017 08:53 AM, Allison Matlack wrote: > > "the comment in the overall readme for that github repo says that > > comments need to be submitted by a date in order to incorporated into > > the general repo. Is it not the open source way to always take > > additional comments and Pull Requests to improve the overall process and > > practices?... I wanted to ask why we aren't keeping comments and > > improvements items as a consistent and iterative manner to achieve the > > goal of the best product possible." > > > > My initial guess was that you needed comments by a certain date due to > > publication/announcement reasons. But is there a specific reason why > > we're not calling for continual comments/improvements? > > Hi Allison, > > Thanks so much for forwarding this along. I'm excited to see what the > Agile Coaches group makes of our community's work?not to mention what > they will add to the effort! > > The answer to the coaches' excellent question is a rather simple and > boring one, I'm afraid: > > As an open source project, the Maturity Model would indeed _always_ be > open to continual enhancement and modification, and I'm sure the group > joins me in welcoming feedback and pull requests at all times. > > The dates on _this specific_ announcement are in place simply to bracket > a period of "public comment" on the _final draft_ of the document as the > ambassadors determine whether to officially incorporate the model into > the Open Organization Definition repository. We are setting a date by > which we want to make that decision. So put another way: The "deadline" > is not something like a final deadline for comments, modifications, > feedback, and enhancements _in general_; it's more like a conclusion to > a _particular_ period of discussion that we're all having as we > determine whether the community ultimately endorses the collaborative > work that came out of the first few drafting periods (and wishes to > finally include it in the public repository). That's why the document is > presently, technically, a pull request. > > I hope that makes sense! More questions and comments surely welcome! > > Bryan > > > > ------------------------------ > > _______________________________________________ > Openorg-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/openorg-list > > > End of Openorg-list Digest, Vol 18, Issue 16 > ******************************************** >
_______________________________________________ Openorg-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/openorg-list
