OK, we're getting the early stages of the development going and the first thing to do is set up a development environment open-source style. I recently got this system to work on a Windows operating system and wanted to provide the info for anyone that wants to join in. I'll break the sequence into the following steps:
Since this process is as new to Don and I as it might be for you, don't sweat it when you read all of this and say "WTF?" I already said it about 30 times...but now I'm down to about 1 per hour. Once you get all of this running, things might start looking better. By the way, the cost for all of these downloads: $0.00 and your time.
Whenever you get lost, start back at the main page for all of this stuff: Drupal - Setting up a development environment
Here we go:
1) Set up a test WAMP/LAMP server
First, you'll need to install a server that will allow you to run Apache, MySQL, and PHP on whatever computer you are using. There are a number of good packages that will install a mini-server with AMP on a Linux, Windows, or Mac system. In this case, I tried two of these all-in-one packages called Uniserver and WAMP and both worked well.
*Note that you need to make sure that Windows IIS is turned off on your machine; otherwise, IIS and Apache will fight over the same port (80). You can check if IIS is running by opening your services window (typically at C:\WINDOWS\system32\services.msc) and "stopping" the IIS Admin service.
Links to start with:
2) Set up and configure an IDE
It seems that most of the Drupal community uses a tool called Eclipse as their Integrated Development Environment (IDE). For those of you in the Microsoft world, this is the same thing as Visual Studio or VBA or MS Access Code. Eclipse is free to download and allows for a number of plugins that gives you plenty of debugging and source control abilities while you hack away. As I am a rookie with eclipse, I can't talk too much about it...but what I've seen thus far looks sharp.
Links to start with:
3) Connect with the SCORE OS Google Code SVN
I know even less about SVN, but for those of you unfamiliar with "source control" -- this is the process that allows coders to work together while not stepping on each others' toes (no over-writing, creating conflicts, erasing, etc) and also gives us a good backup and version system as we progress. In order to hook up Eclipse to the SCORE OS Google Code base, you'll need to request a password from either Don or Randy.
Links to start with:
Non-members may check out a read-only working copy anonymously over HTTP.
svn checkout http://scoreos.googlecode.com/svn/trunk/scoreos-read-only
4) Reference Links