Today my friend Sara Chipps and I are announcing the creation of the MVC Melee! The contest will be a 48 hour competition where teams of ASP.NET MVC developers will have 2 days to come up with a rad web application idea and put it in action. The public will judge. Prizes will be given. Bragging rights will be secured.

What the what?

MVC Melee is based on the Rails Rumble which has been going on for a couple years now. It’s a wonderful competition which has produced some amazing web sites. I tried last year to get a team together but couldn’t make it happen. After the rumble was over I wondered why we didn’t have a similar competition in the MVC space? Sara concurred and the MVC Melee was born! The Rails Rumble folks have been very supportive so far which has been great!

How’s it work?

The rules are pretty straight forward. We’ve launched an informational site with the details of the competition, FAQ, etc. Naturally there is a twitter account too. Teams should be 1 to 4 people and any resources you use for your site should be free. The constraints are very heavily based on the Rails Rumble rules but modified where applicable. This is our first time out so we have to be a little conservative about what’s allowed to be used. Future melees may be easier to open up to additional libraries such as home brew MVC frameworks.

Lets get it on!

We anticipate registration will open around May 1st so start thinking about web site ideas and team candidates! Aesthetics and usability are part of the judging criteria so think about having a designer on the team who can sling Photoshop and CSS like a ninja.

I’m REALLY looking forward to see what folks can come up with in 48 hours! Help us spread the word and join the melee!

An interesting choice the Horn project team made was to keep the repository (not the design pattern, the actual place where the project meta data is stored) building from source and eschew binary packages altogether. Paul actually makes a very compelling case for this choice in his presentation at DSL DevCon.

While I agree that having the build from source option available is a good idea, I don’t think it should be the default option. Or at least, I think that a binary install option of equal weight should be available.

The Horn dependency and package system is based, at least in part, on the Gentoo Linux Portage manager. When Gentoo first showed up on the linux scene I started using it as my linux desktop and server of choice. The Portage system has awesome dependency resolution and listed the latest and greatest versions of packages like KDE, Gnome, and all the STABLE versions my favorite applications. I highlight stable because that’s what I like to use – the stable version – especially for important or production situations.

The thing I hated about Gentoo was waiting for packages and their dependencies to compile. Most small applications built fast. Most large ones, like x-org, Gnome, and KDE didn’t. The process usually went something like this: Start build, go to bed, wake up the next day and hope there were no build errors.

Now to be fair, there are no packages in Horn that will take all night to build. However…

log4net Build Failure

This is what happened when I tried to install log4net from source. The build failed. This happens more often than people may think. And it’s why I think a “install from binary” option is needed.

Pauls argument for building from source via his presentation goes something like this:

1. All developers like to use the bleedingest edgiest version of a software package so we all download from trunk and compile.
2. Because of this, we have dependency issues during builds because the source from a dependent package may be out of date. Thus, that package also needs to have the freshest source pulled and built. (ie, dependency checking and resolution)

I agree that these are issues. But only when building from source. The question then becomes, do most developers use the latest trunk builds of open source projects like Nhibernate, Castle Windsor, and MVCContrib?

Having spent a lot of time on both the MSDN and ALT.NET side of the developer camps, I’m comfortable saying that a lot of people don’t want to build from source. They don’t want to use the latest bleeding edge version. They just need the package to work stably and reliably. Horn pulls the source from the repository itself where the project is hosted. (so far only svn is supported but git is on the way) There is no gateway to be sure packages are stable and feature complete. Just because something builds doesn’t mean it’s ready to be tagged as the next version.

This raises some more questions which I haven’t been able to answer myself yet: Who decides what packages are inside of Horn right now? Presumably Paul and his team are playing things a little close to the vest right now, adding prominent open source projects to their repository, and making sure they build correctly.  And that’s the right thing to do. But who decides when the next version of a package is ready to be included in the repository? Does the original developer team have a say? If they commit each night and the Horn build “checker” doesn’t fail does this mean that a new build of a project is available each day? In the future, will I be able to add my own open source project to the Horn repository? Will I have any control over how often it’s versioned?

I’ve actually been thinking a lot about this problem over the last couple of months and I think I have a solution which I’ll detail in a future post.

For now, however, I really do wish the Horn project team well. I’ve already joined the Google Horn Developer Group to follow the goings on and will hopefully be able to inject some opinion about adding binary support.

Give the Horn project a look. It very well could be the future of .NET package management for community and open source projects!

Quickie Introduction

First, I’m going to briefly (very briefly) touch on the basic machinations behind twitter. The upshot is that you get 140 characters to type something. Anything. Usually a “tweet” describes what your doing but can be anything from a random thought to a question for your followers.

Who are followers? The other major mechanic to understand about twitter is that in order for people to see what you’re writing, they have to subscribe to your feed or “follow” you. There are several ways to do this but the most basic is simply to open a browser to your profile at http://twitter.com/profile_name and click the “follow” button under your avatar. Presto. now anything you type will show in your subscribers’ feeds. Likewise, when you click another user’s follow button, anything they tweet will show in your feed. This interaction is the fulcrum upon which twitter’s power really lies.

So? Now what?

From this point there are many directions you can take. You may choose to follow only your friends and have them follow you. You may choose to follow celebrities, news anchors, or organizations. You may even only follow companies, if they’re on twitter, that have a product your are interested it knowing about.

The direction I took was a little bit different than any of those but I do use twitter for each of the previously mentioned purposes. The main reason I like twitter so much is community. Community is the key idea I want to try and get across. To me twitter isn’t very useful for following people I’ve never met, will never meet, and who are half a world away. I am interested in following local people who are involved with or are interested in the same things I am. For me, that’s local technology and culture. For you it could be real estate. Or marketing. Or public relations. Or art.

I signed up for twitter in April 2008. I didn’t really “get it” but I knew I wanted to get better plugged into the Philadelphia technology and culture scene. I wanted to meet the people involved and get involved myself. One of the BEST tools I used to get started was Twitter Local. Twitter profiles allow you to set your location. Mine says “Philadelphia, PA” for example. Twitter Local allows you to search for tweets by location as they happen. From there it’s just footwork… so to speak. I spent a long time sifting through local tweets to begin to stitch together the community I was looking for. From there I started following people and paying attention to what they had to say. Then I followed people they were following and paid attention to what THEY had to say. Along the way I replied to some tweets and got into plenty of interactive conversations but my main goal was to FIND people. If you are trying to find people by topic, regardless of location, there is http://search.twitter.com This is the reverse process of the one I just described but it’s certainly worth mentioning. You’ll know when you have found the people you’re looking for. They will start tweeting about local community events or pointing out people who are contributing to projects. My first Philadelphia technology community event was Ignite Philly where I met Roz Duffy who I would later team up with to put on our own event! But that story is for another post.

It’s the Community, Stupid.

Today I’d say about 85% of the people I follow on twitter are local community leaders, planners, contributors, and Philadelphia enthusiasts. I sprinkle in a few Internet celebrities, too, so I can keep an eye on things but like I’ve been saying, the power of twitter is local community!

What’s your next step? If you’re a Realtor, search for other Realtors on twitter! If you’re in marketing, search for other marketers! When you find the rest of your local community, whatever it is, things will start to happen. Conversations will unfold. And you will be part of them.

• Dinner with the City Paper food critic, David Snyder, PhilaFoodie,
• Dinner for Two at Fork in Philadelphia,
• A Gift Certificate and T-shirt from Tattooed Mom’s,
• Treats courtesy of Open Source Cupcakes,
• A $75 gift certificate to the Wine School of Philadelphia.

As well, Scott McNulty and Marisa Mclellan of Fork You Live will be giving a cooking demo! Events like these are a constant reminder to me of the power of Philadelphia’s people and culture. Community leaders are constantly stepping up to put on events, raise awareness, and contribute to wonderful causes. Moreover, Philabundance is reporting low stocks this year so contributions are needed more than ever! See you on the 9th at National Mechanics!

In April of this year I attended my first Barcamp, Barcamp Orlando. BCO was organized by Gregg Pollack of the Rails Envy podcast (one of my favorites). I really didn’t quite know what to expect other than what I saw from the previous years’ recap video. To date, my experience with technology conferences had been

Courtesy: aschek

mostly the seminar type; dripping with marketing pitches and tutorials describing the features of new products. I didn’t find anything wrong with these conferences but I didn’t feel particularly connected with the people I met in attendance either. I could tell that I wanted more.

I found what I was looking for.

In the two days that comprised Barcamp Orlando, I met the most passionate, creative, intelligent, and flat out NICE developers, creatives, and new media pioneers I had ever seen. Each talk I went to turned into a discussion. The pros of the speaker’s ideas were weighed vigorously against the cons of an audience member’s challenges. Groups of like-minded campers spun off into ad-hoc discussion forums to hash out the latest changes to WordPress or to talk about their latest open source project. Developers from every corner of the landscape brought their unique insight to the congregation. It was brilliant. And for the first time I felt like I was part of a discussion and not part of an audience.

A series of fortunate events.

At the same time and in an extremely fortuitous coincidence I had recently begun using twitter. This led to using TwitterLocal. TwitterLocal led me to gradually stitch together the tech community that had been right in my back yard the whole time. Soon I was going to workshops at IndyHall and attending community-oriented events like Ignite Philly. Around this time I met Roz Duffy who seemed to have as passionate a desire to bring Barcamp to Philadelphia as I had.

Over the next few months we announced Barcamp Philly and started actively looking for locations and volunteers. Geoff DiMasi from P’unk Ave introduced us to staff at The University of the Arts in downtown Philadelphia and it was obvious from the first tour that we had found our venue. Over time we obtained sponsors and raised a small army of volunteers who shared our interest in putting on a community-driven event. Roz turned the Barcamp Philly website into a brilliantly effective hub of information, promotions, and a list of interesting profiles of Barcamp Philly registrants.

Courtesy: Roz Duffy

On Saturday, November 8th, Philadelphia got its first Barcamp and it surpassed my wildest expectations. We reserved ten rooms and allotted seven one-hour time slots. All but a few slots were used before the end of the day. The talks ranged from community organizing, to making your own business cards, to rethinking the entire structure of a university institution. Carl Leiby made an amazing mobile schedule for us that has since turned into it’s own open source project! The attendees were bursting with enthusiasm. At the end of the day we made our way down to Old City to National Mechanics for our after party. Euphoric is a strong word but playing Rock Band with 150 of your newest friends at the end of a exceptional day comes damn close.

The following Monday I opened my email and found that the community was still buzzing. Talks of other local “camps” had started. Barcamp attendees were already organizing their new events. Leaders were emerging. Communities were solidifying. The momentum was strong and the excitement was palpable.

Helping to organize Barcamp Philadelphia has been one of my proudest moments. The community of volunteers, contributors, and sponsors involved with making it happen are ROCK STARS and are a credit to the city.

I can’t wait for Barcamp Philly 2009!

Photos of Barcamp Philly 2008

Barcamp Philly Wiki

Also, do check out Roz’s excellent post.