OK, how's this for a compromise: provide BOTH. Provide a source code repository for those who want a peek into the latest and greatest, and provide a Web page with downloadable .zip, .tgz, or whatever for those who just want a canned solution without all the overhead. At a minimum, provide the downloadables, but don't provide only the source code. Not everyone likes to take on new projects and hobbies -- sometimes they just want a tool to get a job done.
Sean Dague wrote: > Honestly, if you are going to release the software anyway, the effort to > do a public source tree (when things like github, source forge, and > google code exist) is pretty minimal. The net effect being that people > get to poke at bits between releases. > > Most people won't bother, but the ones that will are typically the ones > you'll actually get useful bug reports or even patches from. > _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 4 - Sqeak! and eToys Jul 2 - KVM (Tenative) Aug 6 - Zenos Sep 3 - TBD
