Close followers of Parrot have probably noticed that Allison Randal, our esteemed architect, hasn't been very active over the last few months. After her recent announcement that she'd been hired as Technical Architect for an obscure Linux distribution called "Ubuntu", folks might be wondering what Parrot's future looks like. This is doubly true because the architect position has had a bus number of one. If Allison were hit by bus or otherwise incapacitated, there was no structure in place to ensure that someone could step up and keep Parrot moving in a consistent direction.
Burnout has also been a problem for Parrot's past architects, partly because the architect ended up being responsible for managing most of Parrot. We've done a great job of making Release Manager a straightforward process that can be performed by any Parrot developer with a commit bit. The Release Manager position, however, has been the exception. Most of the interesting roles, e.g. managing Parrot as a product or working with the wider OSS community, haven't been formalized and have fallen to the architect in the absence of someone willing to take the lead. Allison is a capable leader and an A-list hacker, but Parrot has passed the point where it can be formally managed by a single volunteer, even one of her caliber.
It was in this environment that Jim Keenan put together a meeting of Parrot developers in Portland, Oregon. Many topics were discussed, among which was a restructuring of Parrot to split responsibilities into separate roles. Andrew Whitworth has already covered the idea in its current state, which will undoubtedly change as we progress. The end result is that we'll be splitting responsibilities into 5 teams, only one of which will cover architecture. We'll be solidifying the structure and formally voting on leads in the coming weeks, but interim leads have already volunteered for most available positions to get the process bootstrapped. Andrew is provisionally in charge of the Product Management and in addition to posting some thoughts on the team structure, has already started fleshing out his vision for the Product Management team.
Then at last Tuesday's #parrotsketch meeting, Allison announced that she would be stepping down immediately, and that she had chosen me to succeed her as head of the architecture team.
What this means for Parrot's immediate future is that while I'll be the closest analog to Allison, Parrot won't rest primarily on my shoulders in the same way that it did on previous architects'. It will be the architecture team's job to look to the future and determine where Parrot needs to go, but other jobs will be delegated to different teams, allowing all of us to specialize without letting anything important falling by the wayside.
Allison mentioned that after the meeting, she felt like a huge weight had been lifted from her shoulders. She plans on staying with Parrot as a developer, but will be focusing most of her energy on Pynie. For those of us wondering what Parrot's future looks like, we now have part of the answer and a reason for optimism. It will take some time until we figure out just how the different teams will interact and what it means to be on a team, but the new team structure promises to help us become a more focused community and to produce a high-quality production-ready platform for interoperable dynamic language implementations.