[Onboardc-project] The source is up

[David B. <da...@xp...>]

(Copied from post on OnBoardC Yahoo group--delete this if you already read
it)

OK, I finally fixed a couple of problems that were keeping me from
committing the source to the CVS repository: (1) WinCVS requires Tcl/Tk --
not documented in the SF installation instructions, and (2) a simple error
of having the the case wrong in the directory path. Perhaps I should add the
problem that took the most time to fix: (3) a two week backlog of tasks for
work that needed to be completed for a product release.

So, feeling a bit foolish, but I'm relieved to finally announce that the
source code is finally out there on the SourceForge site where I'll have
less of a chance to slow things up (especially since it looks like Wade is
back).

For some reason the Summary page does not acknowledge that any files have
been committed, but if you browse the CVS tree you can see the files and
should be able to check out working copies if you have CVS installed
properly on your system (and have developer access, which I can give you as
soon as you tell me you want it and give me a SourceForge login ID). Let me
know if you have trouble and I'll try to solve any problems as quickly as
possible.

The instructions SourceForge offers for uploading web pages to their web
server leave much to be desired, but when I get finished tonight I'll try to
move the home page from it's current location at
www.xpinneret.com/OBC/index.html to SourceForge and get a proposed task list
up for discussion.

Much appreciated is the work to get OnBoardC compiling in GCC and updated
versions of CW.  I'd like to open discussion again about how we should
handle getting a version that compiles in *both*.  Do we start with two
forks and then when each is compiling in it's respective compiler begin
taking stabs at merging them? I think since the source was originally
written for CodeWarrior there might be some logic to getting it to compile
in CW first (using the 4.0 SDK) then turning to GCC as the second task.

Once we have a decision on this we'll post a task list, vote on it, assign
points-of-contact to the tasks, and give the "Jolly Roger" to the first
developer on the list. But let's take this discussion over to the
onboardc-project list. As for the voting, it looks like the Survey feature
on SourceForge is worth a try to handle this.

Last I spoke to Matthew, he was going to see if he could create some web
pages for helping us manage and display the status of the Roger. He designed
a very nice site for another open source Palm project on SF (still under
construction at http://filecaddy.sourceforge.net). Take a look and offer
comments if you think you'd like something similar.

David