by Garrett Serack on June 24, 2010 04:21pm
It has been nearly three months since launching the CoApp project, and in that time I've been absolutely amazed at the response that we've gotten, and the community folks that have jumped on board. As a matter of fact, it's been far busier than I had hoped, and was prepared for.
Initially, I thought that we'd see a few people interested, and maybe two or three volunteer to become committers, and we'd start slowly and build up to actually producing something. Well, within a week or two of the kickoff of the project,130 people joined the developer mailing list, and we've got 13 committers.
Unexpected rapid growth causes its own problems, first being the lack of something for 13 people to actually start working on, and a definite gap between the vision that I had started with and what everyone understood to be the ‘plan'. On top of that, the sheer number of people both internally and externally to Microsoft who wanted to know more and how they could start using it made it a challenge to answer their questions, make the appearances to talk about CoApp, put enough design in place to unblock committers, and oh, wait, actually produce code!
Early on, one of the problems I had is that folks didn't quite know exactly what we would be producing, so I wrote out seven points that describe the scope that the CoApp project is focused on:
- Provide a specification for package types and how applications are packaged, so that they can behave themselves in a common ecosystem.
- Provide tools to make packaging easier.
- Shallow-fork a lot of OSS projects to provide clean, well-maintained Windows binaries.
- Provide tools to make shallow-forking & maintaining packages easier.
- A user experience and a service that will allow end-users to manage their installed packages trivially (including updating...etc).
- A specification for metadata so that any publisher who conforms to the package specification can build and distribute packages using via the client tools (5).
- Binary and source packages of applications and libraries forked in (3).
With that in mind, we could move forward.
In mid-May, Microsoft hosted the CoApp Design and Development summit, where 13 folks from around the world came to Redmond. We spent two days going over my initial vision, adding in everyone's ideas, and finally fleshing out some of the design and the plan moving forward. As is typical with this type of project, folks are more interested in coding than documenting, but we're slowly filling in the blanks. (Our rough notes on Day 1 and Day 2. Oooh--And some pictures!)
To match Point #1 on our list of what CoApp is, we have to crystallize what exactly a CoApp-style package looks like. Initially, I had thought that there would be several package types (apps, shared libraries, source code, static libraries, drivers, etc...) but during the summit we came up with a change to that.
A package can contain multiple roles; each role installs a particular type of thing. So, there are several role types (App, shared library, source code, developer library, and drivers) This subtle yet important difference allows collections of things to be versioned as a group and cuts down on the number of packages for a particular purpose. We also studied in depth how complicated things like Perl and Python will need to be assembled in order to provide the flexibility and power they require.
Some of the details (notably device drivers, the concepts of feature advertisement and product composition necessary for things like Python) we're putting off until later to have a bit of experience and understanding how well our design works for the less complex packages. So, other than that I'm fairly sure that we've got a pretty good idea of how those packages are going to look. Certainly it's enough information for me to hand-roll some MSIs that we can use for testing.
I've also spent a bunch of time setting up project infrastructure and the skeleton code and build system for the sub-projects on Launchpad. It's now possible to actually build CoApp, even though nothing actually does anything. This allows some unblocking of the developers who wanted to get cracking.
Currently, we're working on Point #2, which is split into a couple of separate tracks. The CoApp client engine (which is the client component that handles all the magic at install time) is being led by Elizabeth Smith. Elizabeth is a well-known open source (PHP, gtk and others) developer who has wide expertise in C and Windows. The other track is the developer tools where I'm working with a handful of developers to begin fleshing out their design and start cranking out code over the summer.
I would also like to thank all of the committers who came out to the Design & Development Summit in May: Elizabeth Smith, Rafael Rivera, Adam Kennedy, Trent Nelson, Philip Allison, Adam Baxter, Jonathan Ben-Joseph, Ted Bullock, Nasser Dassi, Trevor Dennis, Olaf Vanderspek, Kevin Moore, Mark Stone and Rob Mensching.
Your efforts are greatly appreciated, and I'm looking forward to continuing to work together.