Hi Chris, Good question. As a registered CodePlex member you are allowed to do most everything in the project. Users can register by clicking on register in the upper-right-hand corner of the CodePlex page.

Any non-registered visitor can view the project pages and download the releases, and registered users can also post to the discussion forums and file issues.

At the moment only SLK team members can be developers and update the code. As the project grows and approaches the V1 release, we are investigating how we will bring on new developers from the community.

We have our own in house .NET VLE at present and have also been working with Class Server v4 from within SharePoint Portal Server 2003. We've managed to get Class Server working very nicely from within Portal Server (NOT SharePoint Services) to create a really
functional and slick Learning Gateway.

This year we we're going to work on integrating our .NET VLE with Class Server, however, since the announcement of the SLK a few months ago, we have altered our development plan accordingly to include the pre-release of the SLK.

Will we be able to contribute to the development of this product in a similar way that other open source VLE's have been developed through community contributions? I.e. submit code revisions for review and possible inclusion.

We have some great ideas and some very talented people, including developers, and we would like to see this project become a major success.

Hi Daniel. Thanks for your interest in contributing to the project. It is absolutely our intent that you be able to contribute to this project just like any other community-source project. At this point, however, we are not prepared to take code submissions;
the SLK project is still rather bound to an internal set of development tools and processes that doesn't lend itself to outside submissions.

We will be transitioning this process to full support for developer submissions as we get closer to our v1 release in January. As we get closer to that date, we will let everyone know how they can get involved directly as developers on the project.

In the mean time, please feel free to post your thoughts on the SLK, what you like about it, priorities for improvement, etc. You can get a good sense of where we're going between now and January by reading our specifications in the 'specifications' folder
of the source code package. Once we are feature complete, we will also be taking bug submissions through this site.