RobMensching.com /Blog
when setup isn't just xcopy

Posted by
Rob Mensching
Sunday, February 08, 2009 12:12 PM

Distributing culture is hard.

Last week I met with some PMs that work on the east coast. They fly over to the west coast to visit the Microsoft mothership every couple months. Our meeting was one of many face to face meetings they try to squish into a single week before flying home.

At the end of the meeting, one of the PMs mentioned that a couple developers on his team were interested in contributing to the WiX toolset. In fact, one had contacted me previously about participating but he never got involved. Rumor has it he went off and got married. <smile/>

I told the PM that one of the biggest challenges I face leading the WiX toolset is finding and developing contributors outside of the Redmond, WA area. Actually, my track record in maintaining remote contributors is down right dismal. Even now one of the contributors that recently moved back to the east coast is slowly drifting off.

I believe there are several facets to this issue. One of the biggest challenges is distributing the culture that keeps volunteers coming back to WiX toolset. And when I say "culture" here I do not mean "locale". I am talking about the organizational norms and collective history of the participants.

The WiX culture today revolves around the WiX Working Group meetings that happen every Thursday night (weather and holidays allowing). In those meetings status is shared, questions are answered and code gets written. But it goes beyond just making progress on the code that forms the WiX toolset.

For example, at Microsoft setup work is often pushed off to a junior developer or contractor from outside the company. I don't agree with that tendency but it is a reality. Thus there are regularly people using the WiX toolset that are new to Microsoft and often new to "professional" software development.

The result is that the more experienced developers end up sharing a lot of their stories about how to succeed inside Microsoft. Everyone shares stories about which groups are doing well and opportunities across the company. Around review time much advice is sought and offered about the way things work and how to help your manager help you.

To those of you "outside of the firewall" all of that Microsoft career advice might seem like a pointless piece of WiX culture. However, remember that development of the WiX toolset began in 1999 and wasn't released externally until 2004. That means the first 5 years of the WiX culture developed completely within the Microsoft culture.

Anyway, back to my point. There are a great many pieces of the WiX culture that I've done a poor job sharing with those people that don't show up for the WiX Working Group on Thursday night. So, I'm adding a new blog category culture. Under that category I will start sharing the things that I believe make up the WiX culture. Now the funny thing about "culture" is that when you are part of one, it is usually difficult to recognize the pieces that are unique or relevant or even interesting to others. Thus the posting to this category are likely to be very random and many be very uninteresting and other posts may just reflect my personal viewpoint.

To close, I'm also thinking about reshaping what I consider a very difficult problem of distributing culture into a new challenge. How to create a culture that can be distributed. I've seen ideas about that topic so I might dig into those later.

Did I ever mention that I have a minor in Communications? No? Well, keep coding... you know I am.

 


Posted by
Rob Mensching
Friday, February 06, 2009 4:30 AM

Release Candidate defined.

A week+ ago, I posted a blog entry noting that the WiX toolset was out of beta not in it. I also mentioned that we are now in the "release candidate" mode and provided a quick definition to differentiate it from "beta" mode. A few days later Steven Sinofsky posted a entire blog entry about Windows 7 entering the Release Candidate milestone. In typical Sinofsky-style, Steven posted a much longer definition of release candidate and placed it in context with the other typical milestones at Microsoft.

Now I'm still a little flexible with some of the bugs we'll take into the WiX toolset even though we are in release candidate mode. For example, as I mentioned in comments previously we took the MSI 5.0 changes late in WiX v3 for three reasons:

  1. Staying current with the Windows Installer is important for the WiX toolset.
  2. Implementing the Windows Installer beta functionality helps them find bugs.
  3. The next official release of the WiX toolset (after v3) will be available quite a while after Windows 7 ships, the MSI 5.0 functionality may be required by our customers before then.

We also still have some work to integrate Votive with the next version of Visual Studio. That work will be coming in late since we're waiting for their beta.

Anyway, I hope that provides some more detail about how we're approaching the end game for WiX v3. Getting the bug found and count down to zero is our primary focus. That and having a little fun along the way.

 


Posted by
Rob Mensching
Friday, February 06, 2009 4:09 AM

WiX v3.5 status or the lack thereof.

There was a comment on my WiX toolset bug count entry asking about the status of WiX v3.5 and more importantly the bootstrapper often referred to as Burn. The short answer is there is no status to report. Work on WiX v3.5 has not started in earnest because we are all focused on addressing the bugs in WiX v3.

Each week I hope we can finally turn our attention to creating the much needed WiX toolset bootstrapper. But each week our bug count has inched back up and it takes a concerted effort to get the count back down. Trust me, I'm excited to get into Burn. However, our first responsibility is to ship a high quality WiX v3 and then deliver a kick ass bootstrapper in WiX v3.5.

In the meantime, keep on coding. You know I am.

 


Posted by
Rob Mensching
Friday, February 06, 2009 3:44 AM

WiX toolset bug count after February 5th, 2009.

We had another bug bounce this week in the WiX toolset but the bugs were more distributed this time (i.e. the bugs weren't all fallout from the IIS7 CustomAction changes). Unfortunately, we did not make as much progress as last week and ended up with one more bug total. That's definitely not the trend we want to be following but finding the bugs now is better than finding the bugs later.

On the upside we still have zero extension bugs and we're back to zero bugs in candle. That makes me happy. We'll also be down to zero bugs in light soon (just need to figure out a good error message for a use case the Windows Installer does not support). Things are shaping up well for the core toolset, now we just need to see some movement on the Votive side of the house.

 

image

 


After