This is to inform the few people outside the core EFS team that I have resigned from ML/BAC and taken a position with Bridgewater Associates. My last day at ML/BAC will be 2/25, and I start at BW on 2/28.
In my new role, it is entirely unclear if I will be able to remain heavily involved in the development of EFS. In fact, it is unclear if/when I will even use EFS in my new role. I was hired to join a team designing and building a distributed system infrastructure for Linux from the ground up, and I am not going in there with any preconceived notions about how to do things. These decisions will be made as a team, and if we decide to build something compatible with EFS, we may very well end up using it. At the very least, my involvement with EFS will be significantly attenuated for a few months. I will still monitor these mailing lists and the IRC channels, and will always be available to answer questions about EFS 3, and the tool kit I created around it (efsdeploy, etc). The future of EFS is, quite bluntly, completely unknown. The last 2 years I have spent rewriting and enhancing the codebase for the open source release, automating the creation of the test.efs and boot.efs environments, and making it possible to build an EFS based infrastructure from the ground up. Unfortunately, what we have today is still only part of the solution to the problem EFS addresses, and we have clearly failed to create a viable open source community around the product. The volume of emails on these mailing lists is evidence of this, as well as the fact that noone has really been able to get the product installed and running for a real domain yet. Time will tell, and hopefully bring clarity to the future of this product.
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
