I am not so sure that technology is the highest barrier to wider participation in documenting software. The one seemingly insurmountable hurdle, shared by all software projects, is that only the developers know what the software will do until they write their knowledge down. Someone who is not developing the software can only cross this hurdle in two ways:
o Learn the languages, tools, and processes used to develop the software until the source becomes readable. In other words, become another developer. o Interview developers at length to extract their knowledge (the way commercial software was documented, back when commercial software documentation was actually usable). Hello bottleneck. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents.
pgpvGRoD4kta6.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
