--- Stacey <[EMAIL PROTECTED]> wrote: > If the goal is to start an *open* source project then it > shouldn't be *closed* for non-members to use as well. Or is > the Church going to host a large database for the other 75% > of the boy scouts (the non-LDS ones)? If this is a LDS-only > project then it most likely would be used outside of Utah. > We meet with and work with more scout leaders outside of the > Church. Right now, our council is pretty well standardized on > TroopMaster it seems. For example, when the topic of scout > tracking software comes up in our round tables this what we are > trained on.
TroopMaster is the only software that the Utah National Parks Council offers training on, too, and the only one they sell in their store. They're happy to accept advancement reports from any software that implements the ScoutNet standard, though. > So does a nice import/export feature. In fact, it would be > nice to be able to import records from other scouting software > as well like TroopMaster. If some new troop tracking software > is going to be successful, IMO, then it would need to be able > to import data from other tracking software. Otherwise people > will continue using what they are using rather than take the > time to re-enter all the data into a new system. A good import/export feature (both for TroopMaster and its few competitors, and for the online re-chartering system) would be a huge need. The other make-or-break feature I haven't heard about yet in this discussion is the ScoutNet standard for reporting advancement and such like things to the council office. _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
