The new OpenEverything organization

OpenRasta has been there for many years, and is the most widely used alternative framework for ReST applications.

OpenWrap has been there for a year and a half, and has some usage for advanced users wanting a nicely-architected package manager that doesn’t take dependencies on lots and lots of other technologies and doesn’t require VS.

And we have sub-projects, such as OpenFileSystem, an IO abstraction library that ought to  make using the file system easier, shipping with an in-memory version that should work the same way as your target operating system.

Now all those projects are at varying stages in their life, and the amount of work I used to give to only OpenRasta has been vastly disolved, which in turns means that some users are starting to get quite annoyed with our dreadful homepage and our lack of binary downloads.

Add to this the competitive pressure on OpenRasta introduced by Nancy and the future openrasta copycat WebAPI from the photocopier machine Microsoft, and you’ll understand that the current trend is not sustainable.

This year I’ve decided to simplify my life and delegate much more of my work to a community that has been so far very supportive but very unwilling to contribute anything back. I also want to go back to enjoying working on OSS software to build great solutions and not focus my energy on simply competing with any tool and framework microsoft invents to duplicate existing OSS solutions. I have a vision and I want to deliver on that, OpenRasta and OpenWrap are two sides of that, and I want to start making them work together the way I want without having to be dragged in competitive races with Microsoft’s marketing dollars.

So we had a planning meeting with some of the companies that use OpenRasta in anger in London and want to step up their contributions (7digital and huddle, we love you guys!), and decided that we were going to change how things are done in the OpenEverything projects.

Project organization

First and foremost, I’m going to contribute much less to the 2.1 branch of OpenRasta, and patches / merges / new builds are going to be handled by the contributors that are given write access to the git repository. This gives away a lot of my power.

I’m going to be focusing on the outstanding modules for OpenRasta that add a whole bunch of functionality that will be rolled-back in 3.0: the caching module (soon to arrive in 0.2 version), the new config API (with compact fluent API and convention-based config) and the dynamic / json out-of-the-box support. There’s also a new openrasta-diagnostics module that I’ve started building and want to get out there. I’ll also contribute some work towards the async support that has been requested by some.

OpenFileSystem 2.0 is going to be under Henrik Feldt supervision, and will be a merge of the amazing work he did on long-path and transactional file system support.

All of our versioning is going to be a strict application of 2.0 (which is now the only standard in OpenWrap), so that will solve any breaking changes being introduced without knowing.

Of course, OSS is not a democracy, so I keep a veto right on certain changes that would impact future versions, or architectural changes that do not fit with the vision I have for all those projects. This is give and take, I give some of the control of more than 4 years worth of my development time, but I will keep the main architect role for the time being.

As for releases, anytime someone with commit access wants to create a new release, the process is very simple: they email on the mailing list, and if there’s no majority opposition, we have a new build. Simples.

Orphaned projects

Sadly, we do have some orphaned projects in all this. Mostly, the container support for each of the IoC containers is not up-to-date for StructureMap (tests are broken) and Unity (I have no understanding of the code, so while I *think* I fixed the latest build, I can’t try it out). At this stage, anyone with a vested interest in those projects should start contributing and come help out, or risk that code not being maintained anymore.

OSS is not just take, it’s give too

That leaves a real question for those companies that have used OpenRasta to make money and provide a killer-architecture and have contributed absolutely nothing back since the beginning.

I’ll let you in on a little secret. I give the code away on everything, so it is a company’s legal right to take and not give back. As a side-effect, it is my complete right to completely ignore those that make money on our hard work and want to keep it all to themselves, and my responsibility to not prioritize the needs of those that contributes over those that are selfish..

OSS is also about giving back, and this year it’s what is being enforced on the OpenEverything projects. Fostering contributions is what we want to get to. No more free-lunch though, that’s for sure.


This new organization should let OpenRasta absorb patches and get on the 2.1 release cycle faster, and then on to 2.2, etc. This will allow me to focus on what I want to build for 3.0, and this will also allow more contributors to own projects more directly than before.

If you have comments or feedback on all those new plans, please let us know on the now unified openeverything-dev mailing list.

Please don’t use it for user questions, we’ve moved all support of all those frameworks to stackoverflow where google can do its job and users can find their answers more quickly.

This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Anonymous

    Seb, I listened to the interview you did about a week ago and it didn’t sound like WebAPI is much of a “copycat” to me… in fact, the reason I found that interview is because your comments above made me wonder if a Microsoft-supported hijacking of everything good in OpenRasta would make my life easier. Why? Mostly for the reasons listed on Daniel’s blog. I went a lot further with OpenRasta, but I’ve been hesitant to use it again because it seems like such a moving target.

    I’m one of those people, I guess, who mostly “doesn’t give back.” When I was using OR for that other different project almost two years ago, I spent about a week tracking down a nasty handful of bugs in Ninject which, as far as I could tell, only broke OR. However, I have other concerns and projects, and consequently I couldn’t devote any serious amount of time to new work on OR. While I was actively using OR, I spent a lot of time trying to clean up the documentation when I’d run into a problem, because that was easier to do in small slices.

    But I’m writing to tell you a quick story. I learned something from a friend and investor on a big-budget project I had started a few years ago. I asked him why he wasn’t more involved with my project. I knew he was generally interested in what we were doing over all, and since he was waiting for a return on a seven figure investment, I expected he’d want to be deeply involved. He said, simply, that he lacked my “passion” for the project. I think that’s what you’re seeing with OR. A lot of people (like me) truly believe in it. We think you’re on the right track, and like me, we’ll contribute something from time to time. But it isn’t our baby, and we can’t be expected to hitch our wagons to it.

    I do like what you’ve said here. I look forward to being able to just pull down a binary and use the thing. I have pushed OR hard whenever possible — both within my primary employer, as well as individual projects I was doing, and also to other developers who are advanced enough to be giving serious thought to doing REST correctly. I evangelize. I’ve contributed. I appreciate it. But I don’t think any important OSS project would have ever succeeded had the founders been so wrapped up in keeping score between give and take. If I had 40 hours in a day, I’d give some to OR, but for now, using it and promoting it are all I can do.

    So… looking forward to seeing those ready-to-eat builds come available!

    • Sebastien Lambla

      I understand what you’re saying, there is no question that not everyone has the time or the passion to contribute to a project.

      On the other hand, companies and individuals that save time and money by using a project do have both the time they saved and the commitment to share back.

      We’re very lucky in the Open stack to have some of those companies standing up to the challenge, and the role of the new organization is to empower them and remove me as a bottleneck, while keeping me on as the friendly dictator that I am.

      That said, there are some that have not contributed and could have, and those I have no time for.

      I’m only highlighting how disheartening this is because the projects have become much less enjoyable to manage. The more successful a project is, the more you spend on support and marketing, the least you have the time to build new stuff. And when the balance tips too much in one direction, I don’t enjoy it, users don’t get anything and some people are still happily laughing their way to the bank.

      I put 20 to 30 hours a week on various projects, the more projects the least amount of time I can give to each of them. It’s not sustainable and hence why some of that work needs to be handled by the community or the projects left to die. This is what the new organization is there to promote, ownership from the community, and I really hope that it is what we’ll achieve.

  • Pingback: The Morning Brew - Chris Alcock » The Morning Brew #1033