<html><body bgcolor="#FFFFFF"><div>Git and GitHub has the largest mindshare among open source developers that I am aware of (I come from the open source dev community, not academia). If you want to be discovered or collaborate, I recommend that route.<br>
<br>Duane</div><div><br>On May 6, 2011, at 1:19 PM, Brian Olson <<a href="mailto:bql@bolson.org">bql@bolson.org</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>I counter-recommend git. I don't like it. If you like the new 'distributed version control' system style, I recommend Mercurial. <a href="http://code.google.com"><a href="http://code.google.com">code.google.com</a></a> also supports mercurial.<div>
<br></div><div>My own election simulator is also up on google code, also with subversion.</div><div><br></div><div>It's kinda hidden inside my project for multi-language (C/Java/perl) election method implementation library.</div>
<div><br></div><div><a href="http://code.google.com/p/voteutil/"><a href="http://code.google.com/p/voteutil/">http://code.google.com/p/voteutil/</a></a></div><div><br></div><div><a href="http://code.google.com/p/voteutil/source/browse/#svn/sim_one_seat"><a href="http://code.google.com/p/voteutil/source/browse/#svn%2Fsim_one_seat">http://code.google.com/p/voteutil/source/browse/#svn%2Fsim_one_seat</a></a></div>
<div><br><div><div>On May 6, 2011, at 8:29 AM, Jameson Quinn wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I recommend you put it up on GitHub. Git handles versioning and source control for you, and github is a good place for people who want to suggest code changes to do it directly, so it's easy for you to just accept or reject those suggestions. If you don't want to have to learn Git's command-line interface, there are a few gui tools: you can use git-cola for making checkins, and giggle or gitg for looking at the history of checkins.<br>
<br><div class="gmail_quote">2011/5/6 Kristofer Munsterhjelm <span dir="ltr"><<a href="mailto:km_elmet@lavabit.com"><a href="mailto:km_elmet@lavabit.com">km_elmet@lavabit.com</a></a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Quite some time ago, I rewrote and expanded the singlewinner part of my<br>
election method analysis program, mainly to add a cache to make X,,Y and X//Y methods very fast if results for base methods and sets X and Y had been calculated earlier -- and to only calculate the pairwise matrix one instead of 200 times if I were to find the results of 200 Condorcet methods.<br>
<br>
The last week or so, I've been cleaning up that code, and a version is<br>
up on Google Code at <a href="http://preview.tinyurl.com/5rd5krp" target="_blank"><a href="http://preview.tinyurl.com/5rd5krp">http://preview.tinyurl.com/5rd5krp</a></a> . It's only<br>
tested on Linux, has some known bugs, and the actual structure isn't<br>
documented apart from comments, but there it is.<br>
<br>
I'll probably continue working on it now that I know how versioning<br>
works :-) If anyone has any questions or want to add to it, go ahead and reply!<br>
<br>
----<br>
Election-Methods mailing list - see <a href="http://electorama.com/em" target="_blank"><a href="http://electorama.com/em">http://electorama.com/em</a></a> for list info<br>
</blockquote></div><br>
----<br>Election-Methods mailing list - see <a href="http://electorama.com/em"><a href="http://electorama.com/em">http://electorama.com/em</a></a> for list info<br></blockquote></div><br></div></div></blockquote><blockquote type="cite">
<div><span>----</span><br><span>Election-Methods mailing list - see <a href="http://electorama.com/em">http://electorama.com/em</a> for list info</span><br></div></blockquote></body></html>