Announcing the Better Shared Source Initiative

I would like to announce the Better Shared Source Initiative, where we have taken some of the most popular shared source modules and have them pass a series of checks to make sure that they meet the Sitecore best practices.

A Sitecore solution architect have been assigned one of the selected modules and the solution architect should then become a champion of that module, meaning that when a question about that module is posted on the shared source forum that person should be able to answer the question within a reasonable amount of time. For the modules that get a high number of posts a specialized forum for just that module will be created. As of now there are specialized forums for the EviBlog, Image Gallery, Dynamic flash for marketers etc.

The list of modules selected is available here at the index list of the shared source modules. The project rooms for each of the selected modules should also contain this

TestedbySitecore_M_OnBlack

with a link to the list of the checks that the module has gone through in order get such a label.

If the module has been validated by Customer Service the project room will also feature a supported by Sitecore label.

SupportedbySitecore_M_OnBlack

It was our intention that people would be more comfortable using the shared source modules on their site if they knew that a solution architect from Sitecore had made sure that the quality of the modules meets the checks on the list before implementing them.

So how does a shared source module become a part of the Better shared source initiative? Well first of the module should meet the checks that I mentioned before and then every once in a while we will ask our Sitecore offices what shared source modules are popular and most used by the Sitecore partners and developers and what the solution architect’s and Pre-sales use themselves. Then we take the top of the list and test them to make sure that they do meet the checks on the list and when ready we will add it to the list of modules that gets labeled with a “Tested by Sitecore” label on the project room so that visitors would know which modules have been tested by Sitecore.

Sitecore’s Customer Service have also had a look at the list of modules that have been labeled “Tested by Sitecore” and have decided that they would also offer support for these modules for a fixed price per module.

This means that developers who might have looked at implementing a shared source module but decided not to because of the lack of support can now reconsider using shared source modules for their solutions.

Advertisements

~ by Jimmie Overby on January 14, 2011.

8 Responses to “Announcing the Better Shared Source Initiative”

  1. This is excellent news 🙂 Am especially looking forward to seeing how the “Supported By Sitecore” initiative will be used.

  2. Good initiative, I’m sure you will benefit greatly from having even more supported modules. I suggest that your next improvement in the shared source initiative be to provide the contributor with more power and insight. E.g. Being able to track number of downloads and administer commit rights to their modules. I’m sure that giving even more value to the contributors will turn out to give more value to Sitecore as well.

  3. […] To do this Sitecore have introduced two different levels of support for Sitecore modules: Test by Sitecore and Supported By Sitecore, these badges allows us to better assess the quality of the modules on offer and confidence in the modules. More can be found on the Shared Source blog. […]

  4. […] To do this Sitecore have introduced two different levels of support for Sitecore modules: Test by Sitecore and Supported By Sitecore, these badges allows us to better assess the quality of the modules on offer and confidence in the modules. More can be found on the Shared Source blog. […]

  5. How does Sitecore decided what open source projects they will test? Is there a way of submitting projects?

    • Hi Mike,
      For the first round picks we asked our offices to gather a list of the modules they heard where popular and then assigned them to our SA’s. For the next round we could have a poll and have people nominate modules, what do you think?

      • I think a poll is a useful way.
        I also think that having a way for developers to submit themselves with supporting evidence would be great, for example:
        * The project web site
        * Project source repo
        * Evidence of sufficient testing
        * Why they think it is awesome and of benefit to the community

        Hopefully requiring the above information will act as a partial filter to those projects that aren’t of a high enough quality.

        Another option is to have a page where open source projects can be listed with their supporting information, then other users can come along and endorse the project. When the project gets to a certain number of endorsements it will then be considered for the Tested By Sitecore status. You could then have a second threshold for the Supported by Sitecore. For example 20 endorsements and Sitecore will test, 50 endorsements and Sitecore will Support it.

      • That sounds like a great idea, I will definitely keep this in mind for the next round of better shared source and even incorporate it into the Shared Source Library.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: