Hi Folks,
After Sam's talk at last month's Monospace conference in Austin TX,
I've given his questions some braincycles and I'd like to share those
with you.
1. What should the foundation focus on?
Well, I'm as biased as you can get, but personally, I believe the
foundation should focus on the .Net ecosystem.
You never really hear about foundations getting involved in the
Microsoft stack all that often, and it's a massively under served o/s
space.
Obviously there are a lot of interesting open source ecosystems out
there, and the foundation has to be judicious on where to focus it's
limited resources. Still, having a foundation that focuses 80% of it's
efforts on the .Net opensource space would, in my opinion, go a long
way.
Farther than any other ecosystem in play.
2. What can the foundation do for open source .Net projects?
I realize we are all heavily tempted to say "Compensate full time open
source developers".
We all have our pet projects and we'd all like to see them turn a
profit, increase our sex appeal and provide us with nirvana-like
enlightenment. But truth be told - none of these are realistic
expectations.
I have serious reservations regarding paying open source developers
for 2 reasons:
1) It's not cost effective. on the xM$ funding the foundation has it
isn't realistic to keep a host of o/s project functioning.
I'd rather see 100 open source projects supported and elevated by the
foundation, rather than just 10.
As long as the contribution is meaningful and relevant, quantity is
still a factor here.
2) Incentive based volunteering has been proven time and again to fail
miserably.
Open source involvement is an act of passion, of devotion, and of
personal fulfillment.
Once you change those motives to Monterey compensation, it's been
empirically proven, that you'll get less bang for buck.
More on those studies can be found at these talks:
http://www.ted.com/talks/dan_pink_on_motivation.html - Showing that
monetary incentives are proven to detract quality from long running
creative tasks.
http://www.ted.com/talks/lang/eng/barry_schwartz_on_our_loss_of_wisdom.html
- Has a related study on how personal virtue trumps monetary
compensation at 10:53.
After giving this core question a month of spare braincycles I think
there's a better investment out there.
**** Hire a DPE (Developer Platform Evangelist) for open source
projects ****
I'd like to speak out on behalf of the massive Microsoft Developer
Marketing organization - it rocks.
Microsoft through it's DPE org has made the Microsoft Stack a
resounding success.
When people ask "Why isn't foo open source framework adopted and bar
Microsoft framework is?" the answer is always the same.
The Microsoft DPE org markets microsoft products.
And the DPEs are so competent, so articulate, so communicative, that
they effectively convey the benefits of frameworks and platforms.
Open source projects are mostly doomed to death by obscurity.
In my opinion, getting more adoption for open source projects, is all
about positive engagement with potential customers.
And let me make this clear: most open source projects evangelism done
nowadays ends up driving people away!
How many times have you seen open source advocates bash folks using a
comparable microsoft framework? Lots of times.
How many times have you read an angry blog post on a competing open
source framework from an advocate of another o/s framework? All too
often.
How many times have you watched a well organized webcast video series
on open source projects? Never.
When is the last time you went to a major conference (TechED, Mix,
PDC) and saw small-medium open source projects being promoted? Never.
(With the only exception I knew about being the Moonlight project)
Personally, I believe a good objective for the foundation would be to
hire a technical DPE that can engage with the community on it's on
terms.
Some possible duties for afore mentioned DPE could be:
1. Attend top-tier and local conferences. Decisions are made by people
who are in the room. People go to conferences to be educated.
That's single the best evniorment to expose developers to new ideas,
projects and frameworks.
That DPE should probably have a strong community reputation prior to
hiring so it makes it easier for him/her to speak at TechEd, Mix,
PDCs, TechDays, DevTeach, DevConnections and wherever not.
2. Produce technical content for the foundation promoted open source
projects.
In the Online world: Blogs, newsgroups, forums, webcasts, online
articles, tutorials etc.
And Offline: Publish books, write articles for magazines (CoDe
magazine, MSDN magazine, Visual Studio Magazine), help set up offline
lecture materials for local speakers, etc.
In my opinion, the single best thing the foundation can do for open
source projects, is put a professional, well-mannered and articulate
face to them.
I'd love to hear feedback on this idea.
Thanks for taking the time to read my 0.02$,
-- Justin