Lessons from OSCON: The Power Toys Team Learns How To Go "Open" - Port 25: The Open Source Community at Microsoft
< Back to Blogs
Lessons from OSCON: The Power Toys Team Learns How To Go "Open" by MichaelF on September 11, 2006 03:16PM

Be careful what you write on your blog about having such a great time at OSCON, because the Port 25 team will find it!  I mentioned that I had wanted to do a second video regarding everything I had learned at OSCON.  I was (almost) embarrassed how my first video interview fell into the category of “common misconceptions about running OSS projects.”  Knowing me, I had to correct this at once.

 

James Howison, a doctoral student on Kevin Crowston's NSF-funded research team at the Syracuse University Information School and a regular presenter at O’Reilly events, gave this incredible tutorial about OSS communities.  I couldn’t wait to get back to campus to show my team what I had learned and how we were going to apply it to our power toys.  So, we all decided to film the presentation in order to capture the discussions of a team at Microsoft going open and have something to share with other teams that are interested.  I think this is extremely cool stuff, and I hope you agree and want to see more like it.

 

As a follow-up we hope to get James in for a pod cast interview in the near future to provide some feedback and insight on this topic.  Stay tuned.


Video: The PowerToys Team Learns How To Go "Open"

 

Alternate Video Format

-Download MP4 Video

 

Links:

Presentation Outline:  http://port25.technet.com/videos/transcripts/sfosconoutline.pdf

Presentation Slides:  http://port25.technet.com/videos/transcripts/sfosconslides.pdf

Comments RSS
  1. Just watched the video (Sara tipped me off!).  It's just great and very exciting to see our, and that of other's (like the Hars and Ou and Lakhani and Wolf surveys), work really being used and the team getting excited about this whole open source adventure.

    I found the discussion early in the piece about 'Reverse platform play' as an intriguing notion, I think that it wouldn't be a sensible way to _launch_ a platform, but since your platform is already really widely spread, I think it's a different situation.

    I'd tweak the discussion about the leadership to make clear that transition is actually uncommon, but is more common amongst highly successful projects.  I read that as saying that a successful leadership transition is a really good sign (if I'm trying to assess a community that I'm looking at).  I don't know that I would interpret that as 'one ought to transition a currently successful project' if I was trying to build a community (unless, as you pointed out, the current leader is getting tired).

    The reaction to the 'for pay' reflected the idea that it is fine to employ someone full-time as a 'core dev', but the 'community feeling' and the discussion on bounties was spot-on. I liked your analysis of the summer of Code and would add that it doesn't create competition because not everyone is eligible.

    The calls for action were spot-on, I was really impressed with the way you were able to take some of the airy-fairy academic discussion and turn in into action for your project.

    I could sense a certain trepidation about the 'going open' part from the team.  One transitional possibility that might ease the transition is to set-up the infrastructure, mailing-lists etc (these are a feature of codeplex, right?), well before you go open and ensure that people are using them almost exclusively (rather than person to person email).  ie build the habit of internal openness before going totally open.  

    Then you could consider making the internal-open archives truly open when you open the forums up to others (clearly a judicious inspection of the archives for sensitive or prejudicial info or discussion would be sensible).  Also you can deal with issues with exchange email and public mailing lists (like making sure the team doesn't use RTF email (causing the infamous winmail.dat files), even HTML is sometimes difficult and so you'd need a pretty strong reason to not make the lists text only).  I realize that your target audience is all on Windows, but that doesn't mean that they will be using Outlook and similar so it's worth thinking about.

    Cheers,

    James

    ps.  The resources for the tutorial are up at:

    http://floss.syr.edu/Presentations/oscon2006/

    posted at 08:01PM 09/11/2006
  2. The Port 25 team filmed me giving my Developer Solutions (power toys) team a presentation on all that...

    posted at 12:40AM 09/12/2006
  3. Sara recently attended OSCON and wanted to give our team a recap of what she learned there. We figured...

    posted at 01:24PM 09/12/2006
  4. Port 25 said:

    When we started port25 and the OSSL it was met with great skepticism. But there have been a lot of changes going on around us here at Microsoft. And one of those I wanted to bring to your attention...

    posted at 07:28PM 09/12/2006
  5. This week you can watch the first in a series of videos featuring members of the Microsoft C# team. A video of Raj Pai, the Group Program Manager for the C# team, leads off the series.

    posted at 01:24AM 09/15/2006
  6. Port 25 said:

    About a month ago, I did a presentation on What I Learned from OSCON, based primarily on James Howison's talk on OSS Communities. Since James had such great and interesting feedback on my presentation, we decided to do a follow-up podcast...

    posted at 06:52PM 10/03/2006
  7. On our one-year anniversary of our power toys release, I gave a Microsoft Engineering Excellence Talk

    posted at 08:38PM 07/21/2007
  8. On our one-year anniversary of our power toys release, I gave a Microsoft Engineering Excellence Talk

    posted at 09:23PM 07/21/2007
Post a Comment
*
*