Thank you, Evan, for your outstanding contribution to the Erlang world. It's one thing to write innovative software and another thing entirely to to attract and cultivate a vibrant, self sustaining community around it. You've done both through rare good-humored leadership. I have no doubt that you are destined toward boundless success in your new venture.
Lloyd R. Prentice Sent from my iPad > On Feb 26, 2014, at 9:05 PM, Peter Yuen <[email protected]> wrote: > > Sad to hear the bad news, but good luck Evans! > >> On Thursday, December 19, 2013 5:22:45 AM UTC+8, Evan Miller wrote: >> Hi everyone, >> >> I have some good news and some bad news that I'd like to share with the >> community. >> >> First, the good news: Chicago Boss now has a full-time employee! Zach Kessin >> (author of "Building Web Applications with Erlang" and host of the Mostly >> Erlang podcast) will be working over the next 6 months to bring CB to 1.0. >> He's new to CB but has already done some great work improving CB's error >> reporting, adding specs and tests, and refactoring the code base. I'm >> looking forward to seeing all his contributions in the next few months. >> >> Zach's work is being sponsored by Dmitry Polyanovsky, a long-time CB >> community member and contributor of many patches. Dmitry will be working on >> improving the documentation and website, and will be setting milestones and >> guiding Zach's efforts for the next few framework releases. I've been a fan >> of Dmitry's contributions, and having talked to him over the last few >> months, I think he knows exactly what CB needs to reach maturity. >> >> And now, the bad news: it's been a fun ride, but I am planning to retire >> from Erlang and Chicago Boss. But don't cry for me: I've been having success >> with my desktop software business (wizardmac.com) and realized that going >> forward I will no longer have the time to dedicate to both CB and Wizard. >> (Incidentally I also left grad school a couple months ago to focus on >> Wizard.) Finished software products require a ton of focus and work, and I >> just don't have the mental capacity to manage two projects at once. I wish >> there were more hours in the day! >> >> I've given this a lot of thought, and I think it's probably the right time >> in CB's trajectory for me to start transitioning out anyway. My specialty is >> trying crazy ideas and getting them to work. (It's amazing the number of >> times people laughed at me when I told them I was working on a Rails-like >> web framework in Erlang!) CB has been a wonderful playground for me to try >> out my ideas, whether it was with the template system, BossDB, the compiler >> hacks, BossMQ… well, you get the idea :D. And I've loved being part of a >> community that has appreciated my work and made countless improvements and >> contributions to it. >> >> But at this point, CB doesn't need any more crazy ideas -- it needs >> stability! Tests, specs, documentation, QA, error messages, deployment >> tools, that sort of thing. I guess it's selfish of me, but these things tend >> to make my eyes glaze over. That's part of the reason CB has been stalled >> out at version 0.8 the last year or two. >> >> So, taking all this together, I've been busy taking steps to hand off my >> Erlang projects to folks who I trust can guide them to maturity. Dmitry & >> Zach will be shepherding CB to 1.0, and Andreas Stenius will be taking the >> reins over ErlyDTL. (Andreas, by the way, has been doing FANTASTIC work to >> merge the Zotonic fork of ErlyDTL back into mainline.) My "retirement" has >> been in the works for a couple months, and I waited until I knew CB would be >> in good hands to make today's announcement. >> >> Finally: transitions are tough, and I will be relying on YOU the community >> to keep CB's core values alive: a no-nonsense web framework with an open and >> welcoming community. Zach has been very productive already, but he is still >> figuring out "how we do things around here", so I'd really appreciate it if >> you all will take time to answer his questions and weigh in on any proposed >> changes. >> >> Over the next few months I'll still be making myself available to answer >> questions, offer guidance, and resolve any impasses. But to be honest, I >> think between the community and the 1.0 leadership, you guys won't really >> need me anyway :D >> >> Well, that's it for news. Gosh, it's been almost 6 years since I wrote the >> first line of code that later became Chicago Boss. Working with Erlang has >> been an education in itself, and bouncing ideas off of so many smart people >> has been a unique privilege. I still believe Erlang and CB are the right way >> to build fast websites, and with ARM servers and devices on the horizon, >> there's a ton of potential ahead. But as for me -- it's time to climb other >> mountains! >> >> Thanks again for your patience, support, and continuing contributions. I'm >> proud of the framework and community we've built together, and look forward >> to watching it grow and flourish without me. Feel free to ping me with any >> questions, and of course give me a shout if you're ever in Chicago. >> >> Cheers!!! >> >> Evan >> >> >> -- >> Evan Miller >> http://www.evanmiller.org/ > > -- > You received this message because you are subscribed to the Google Groups > "ChicagoBoss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at http://groups.google.com/group/chicagoboss. > To view this discussion on the web visit > https://groups.google.com/d/msgid/chicagoboss/66b25e9a-1e73-447d-913b-a91b0d575cf0%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/F9492874-D4A5-424D-8E98-7A7A44BCEB6A%40writersglen.com. For more options, visit https://groups.google.com/groups/opt_out.
