Ryan Masuga is conspicuously absent.
Obviously not every EE rockstar can be included, and he may have declined, but I’m surprised to not see his name.
This is exciting to me. Even if nothing more comes of this than the developers working in conjunction with EE. This will mean a deeper understanding of the product for them and that translates into more blog posts and discussions of EE.
And I found out there was a newsletter!
We have numerous devs interested in participating. But in order to do this right, we needed to start small. Originally we were going to keep it to four, but a couple extras snuck in. Once we have at least one release out with contributions, we’ll assess how we can expand. We’re guessing the “lieutenant model” is going to work best, so we’re already setup up for that internally. What this means is that once we’re satisfied with work flow (and other issues related to contribution), theoretically any dev could contribute to EE, whether they are on Reactor or not. I think we’re a ways from this, but if it works, that would be the end goal.
The article doesn’t say it, but I should publicly note that our own Wes Baker and Derek Jones are the ones responsible for making this work internally. DJ takes care of all the non-technically logistics and managing our tool set and Wes is spearheading it from our dev team side, making sure we’re talking with the Reactor group regularly, reviewing code, etc… It would not be happening without them.
Once things are settled more internally we’ll have Wes share how things are setup.