Thank you Garrett, for the warm welcome, and also the opportunity to serve
the nanomsg community in this role.
The short story on why I've agreed to ramp up in activity and role is to
use this opportunity rebuilding momentum in nanomsg development. Martin's
vision and execution with nanomsg is worth following and building upon.
Garrett's continued execution and expansion of this vision is worth
supporting.
Many of us have waffled back and forth between tooling up with nanomsg or
not, and it took observing both Martin and Garrett's leadership for me to
finally understand this definitely remains a worthwhile investment.
Martin's leadership has been abundant with innovation. Garrett is able to
meet and wrestle at the innovator's level, yet also tackle the long-tail of
nitty-gritty required to polish up to production quality. The flak they've
taken aside, these fundamentals have continually provided a solid technical
base for the library.
If you're one who has spent some time waffling over to nanomsg or not to
nanomsg, keep an eye on this mailing list and on the main code repository
and issue tracker (https://github.com/nanomsg/nanomsg) over the weeks to
come. If you have ideas or outstanding issues, by all means, we'd like to
hear from you. Now, back to building ...
Kind regards,
*Jack Dunaway*
Principal Systems Architect
Wirebird Labs LLC | wirebirdlabs.com
On Thu, Apr 14, 2016 at 9:36 AM, Garrett D'Amore <garrett@xxxxxxxxxx> wrote:
It is with great pleasure that I’m happy to publicly welcome Jack Dunaway
(https://github.com/JackDunaway) to the nanomsg admin & git team. In
this role, Jack has agreed to become my chief deputy and advisor for all
things nanomsg. You may be familiar with Jack’s previous contributions to
nanomsg; most notably he is the author of the websocket transport.
While Jack and I will be collaborating for the benefit of nanomsg, this
does not represent a change in governance. I’m still the BDFL; but wise
rulers surround themselves with smart advisors (and listen to them!) and
delegate responsibility well. It’s my fervent desire to emulate wise
behavior here, so that we can emphasis the “B” in BDFL instead of the “D”.
Let me also state this publicly; in the event something were to prevent me
from being able to fulfill my responsibilities to libnanomsg, Jack
represents what I think is the best continuity insurance for libnanomsg.
Hopefully we will be able to cultivate further interest and expertise in
the code base, to help further distribute both the load and the risk.
Thanks so much Jack!
- Garrett
