I'd like to think a little more about the first draft requirements of the Advancement Tracker Tom Welch asked about.

Suppose one of us or some of us were starting on a shoestring, maybe at the SourceForge site offered.  I am wondering, irrespective of the language, and obviously platform agnosticism is essential, what the inital stab at an open source Advancement tracker might want to look like to the end user.

Should we start with a Troopmaster clone?  Is that what Tom Welch has in mind?

Then should we plan for possible connection/synchronization to a central repository a la MLS?  And multiple languages and advancement programs?

Tom Haws
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss

Reply via email to