I am not necessarily advocating adoption of any particular software development process, but this article:
http://www.methodsandtools.com/archive/archive.php?id=69 enumerates some issues I would like to suggest have relevance to this discussion (listed under "Some common problems [that] can be observed in troubled projects"). I think if we do our job at the front of the project before attempting to generate code and paint ourselves into corners with early design choices, we can avoid some of those and end up with a seriously excellent new APRS system that shares pretty much only the name of Xastir. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "It's so simple to be wise: just think of something stupid to say and then don't say it." --- Sam Levinson _______________________________________________ Xastir-dev mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
