A Codeplex-like Site for "End User SharePoint"-like Solutions?

Yesterday, I saw a tweet from Joel Ward which immediately got my attention:

image  image

Joel and I went back and forth on Twitter for a while. The gist of the conversation was: What is the best game in town for tools and tricks for end users (Obvious answer: EndUserSharePoint.com) and would a repository of the useful code there and in other places have value?  Then we turned to email. 

From Joel:

…the thought related to the discussion that Ed, Bethany and I are doing for SPSDC. We get asked to implement lots of neat functionality for clients, and sometimes people want to do things themselves. But it’s hard to point non-technical or semi-technical people to a place where they can get solutions for non-programmers. EUSP is the best out there, but it’s not exactly what we were thinking.

Just a thought. What do you think?

Joel

and my reply:

Joel:

I do think it is a good idea.  You probably could see my ears perk up when you tweeted.

I think it would be an awesome thing to build, but it’s probably a non-trivial idea for a few reasons:

  • There are many different types of code (JavaScript, XSL, jQuery, workflows, etc.)
  • Some of the types of code can be encapsulated, some really can’t (workflows being a prime example)
  • Some of the things which are really helpful are full solutions (they work as is) and others necessarily need to be adapted to work
  • There would need to be a damn good taxonomy around the pieces to allow people to find the right one for the task at hand. Knowing which solution is the right one, having enough context to decide, is why some of us have jobs.  Even if we can hand people the exact right piece through some magical search mechanism, we have to show them how to use it, and maybe even help them.
  • No one wants to pay for this stuff and very few even want to contribute.  They are a fickle bunch of consumers.

I’m not trying to pooh-pooh at all. I would love to work on this.  I’ve already started a new Codeplex project at http://spxslt.codeplex.com/ where I’d like to house useful XSL templates.  My struggle with really getting it going: much of the same stuff as above, and it’s a subset (and probably a small subset) of the things that are available and useful to power users (or whatever we want to call them).  That and the fact that, even though I’ve had over 350 visits and over 1100 page views, I’ve really gotten *very* little input on how to make this darn thing useful for folks.  I can guess, but I’d rather try to get at least some things right up front.

Since you’re in consulting, you know that all of us consultants carry around a toolbox in our back pocket full of this stuff, whether from prior projects or just from our hunter/gathering.  It’s part of our own intrinsic knowledge management efforts, and it’s how we make it in the consulting jungle.

My belief is that it is better to give the tools away because then people see what value you have and want to enlist your help.  I know that not everyone feels that way, and the folks who don’t will continue to live in their walled gardens as long as someone is throwing food over once in a while.  I absolutely know that the SharePoint community is a game changer.  This is a community that acts like an open source one, yet we all have clearly stated that we are in this to make a living somehow.  We can’t lose when we try to offer our stuff for free, and in most cases, people are encouraging when we offer the same things at a reasonable fee.

All this said, yes, let’s figure out if we can come up with a way to build something like this and all come out winners in the end.

I think this is turning into a blog post!

Clearly, Mark Miller, Joel, and I ought to talk when we are all at SharePoint Saturday DC next weekend, if not sooner.

Similar Posts

4 Comments

  1. Hey Marc,

    I think ProduShare (http://www.produshare.com) can fill a portion of this requirement, at least in terms of being the place where these solutions could live and be accessible to end users. It needs some work obviously, but frankly, this is what we built it for.

    When you have those discussion please give it some thought, think it makes more sense than re-inventing the wheel again.

    1. Dan:

      I did think of ProduShare in all of this, honestly. I think we need to figure out what we’re trying to tackle and then decide what the best technical solution is. I’ll certainly keep ProduShare in mind. You aren’t coming to #SPSDC by any chance, are you?

      M.

  2. My thoughts on this:
    1/ A central repository is very Web 1.0 . My approach would rather be to have a list of pointers to different places.
    2/ The population of end users is much more heterogeneous than for developers. I fully agree that “the things which are really helpful are full solutions (they work as is)” and I wouldn’t point to any half baked solution (and more than half of the content found today on blogs is in this category).
    3/ With this in mind, who has the authority to decide what is a full solution and what is not?
    4/ Recognition and support from Microsoft is in my opinion essential for such an initiative. IT folks and .NET developers get a lot of exposure thanks to Microsoft (MVP program for example), but we are currently left out of this.

    I have started some initiatives on my side:
    – last year I built a list of blogs for end users, sorted by Technorati authority:
    http://www.pathtosharepoint.com/Pages/ForEndUsers.aspx
    I have learnt since then that ranking sites like Technorati and Postrank are crap. Bookmarking sites like Delicious look more promising, although there is definitely room for improvement.
    – I have created a central repository for my own fully baked solutions (leaving out sample scripts):
    http://www.pathtosharepoint.com/sharepoint-user-toolkit/default.aspx
    – I have a list of community resources (but again, not up-to-date):
    http://www.pathtosharepoint.com/Lists/Resources/AllItems.aspx

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.