tag:blogger.com,1999:blog-4367289903826616184.post1137093269513056542..comments2024-03-28T19:07:12.729+11:00Comments on How 2 Map: Introduce yourself at FOSS4G (was Doc Experiments and Alternatives)Jody Garnetthttp://www.blogger.com/profile/10376195727731958785noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4367289903826616184.post-856109743857278152011-09-05T03:00:03.783+10:002011-09-05T03:00:03.783+10:00I'll see you at FOSS4G!
I think it's int...I'll see you at FOSS4G! <br /><br />I think it's interesting that you've pinned documentation as success factor in open source development... I hadn't thought about that. I've been trying to figure out ways to keep hackathon projects going past the initial event and that would be one solution. However, I think equally important is getting a continued commitment from everyone involved or encouraging some sort of interest in the project. You could have really comprehensive documentation and they still might not be interested. I think it would be interesting to have some sort of social model for continued development (whether it be coding or documenting) perhaps based on the concepts being developed for workforpie.com that turn commitments into social scores.<br /><br />In that way, you decrease the problems wiki-vandalism, encourage questions/problems in a stack overflow type setting, and maintain and encourage a core socially.<br /><br />For me, books and user-lists cover too broad of a spectrum, they often lose my interest almost immediately. Plus they really need some sort of recognized player to be the curator/moderator.<br /><br />The problem with hackathon projects tends to be 1-off concepts that get developed quickly and then abandoned. Perhaps more recognition and community-building would encourage further development.Jacob Greerhttps://www.blogger.com/profile/07826677180620596538noreply@blogger.com