Thanks for the kind words, Bryan. It's been a pleasure and an honor to be part of this group.
What Bryan was gracious enough to elide is that my stepping back from the Open Organization Ambassadors is due to my also stepping away from Gratipay, the startup I've worked on for over five years and the context in which I've been exploring open organizational patterns and possibilities. I'm currently looking for my next opportunity (in software engineering or engineering management—resume attached! :), and who knows? Perhaps down the line I will pop up again in the issue tracker with new open organization stories to share from a new perspective. Until then, all the best to all of you. Keep changing the world, and I will catch up if I can down the line! chad ---- Chad Whitacre http://whit537.org/ +1-412-925-4220 (cell) On Fri, Oct 27, 2017 at 7:32 AM, Bryan Behrenshausen <[email protected]> wrote: > At the end of October, Chad Whitacre will finish his term as an Open > Organization Ambassador at Opensource.com. I'd like to thank Chad—and I > hope (as Chad would say) yinz'll join me in doing so too—for his > outstanding service to the group. > > Chad joined our community in August 2016 after sharing two insightful > stories about the way his startup, Gratipay, handled "hire-yourself > employment" [1] and "take-what-you-want compensation" [2]. As you might > imagine, those articles turned some heads. Clearly, Gratipay was paving > the way for organizations to think differently about some tried-and-true > processes, and Chad joined forces with us to help explain this new age > of open and distributed work to Opensource.com readers. > > To that end, Chad composed columns on issues like open source community > branding [3] and organizational ethics [4]. His tutorial on public issue > trackers [5] appeared in _The Open Organization Leaders Manual_. And his > piece on "open source's free rider problem" remains one of the most > popular open organization stories on Opensource.com [6]. > > As a community member, Chad was instrumental in ensuring we practiced > what we advocated every day. He was instrumental in establishing the > ambassador community's GitHub organization—now a fundamental component > in our ongoing activities—and helped open the community's publication > schedule there. He also spurred development of the Open Organization > Definition more than a year ago, after a robust discussion at All Things > Open in Raleigh, NC. > > Chad, I wish you all the very best as you embark on your next great > adventure. Thanks for all you've given to our community! > > Sincerely, > Bryan > > ----- > > [1] > <https://opensource.com/open-organization/16/5/employees- > let-them-hire-themselves> > > [2] > <https://opensource.com/open-organization/16/7/compensating-employees- > letting-them-take-what-they-want> > > [3] > <https://opensource.com/open-organization/17/4/how-branding-decisions-open > > > > [4] <https://opensource.com/open-organization/17/7/open-org-hacker-ethic> > > [5] <https://opensource.com/open-organization/17/2/tracking- > issues-publicly> > > [6] > <https://opensource.com/open-organization/16/11/open- > source-free-rider-problem> > > _______________________________________________ > Openorg-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/openorg-list >
_______________________________________________ Openorg-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/openorg-list
