@Spencer and Hans re. Google Code: If the repository was ported too, a move like that may avoid an increase in the complexity of the ChucKs web presence, while gaining a issue tracker and an open wiki again. That sounds good to me.<br>
<br>I guess that the main costs of Google code then are:<br>1. Dependency on Google (people may be reluctant to trust or support Google)<br>2. The move to a different SCM system (although my impression is that SVN is very widespread too, and perhaps more likely than CVS to be adopted by new developers).<br>
<br>While the option of a move to a different SCM system is being considered, it's worth taking a look at github and launchpad too (which both avoid the scary google issue).<br><br>Github http:<a href="http://www.github.com">www.github.com</a><br>
Michael's Lick project on github is a relevant example: <a href="http://github.com/heuermh/lick">http://github.com/heuermh/lick</a><br>Github project hosting is free for open source stuff. It includes a wiki, and issue tracker and a neat facility to view branch hierarchy. The main disadvantage i think is that this would involve transitioning to git, which I'm guessing most ChucK devs are not already using (?).<br>
<br>Launchpad <a href="https://launchpad.net/">https://launchpad.net/</a><br>
Launchpad is a very similar deal to github, except it uses the Bazaar SCM instead of git. Also free for open source projects. Has an issue tracker, but no wiki as far as I can see. Bazaar seems to be designed with ease of use in mind, less powerful than git--but by no means feature poor, and more friendly. Bazaar is the most obscure of the three SCMs mentioned here I think, which also has a cost.<br>
<br><div class="gmail_quote">On Wed, Dec 30, 2009 at 8:58 AM, Spencer Salazar <span dir="ltr"><<a href="mailto:ssalazar@cs.princeton.edu">ssalazar@cs.princeton.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Firstly, I didn't realize the CS wiki had become so closed-up. I think all things considered this has diminished most of the value of that wiki to the ChucK community.<br>
<br>
Secondly, I'd like to give a shout out to Google Code. I successfully moved miniAudicle from Princeton CS CVS to Google Code, which has SVN (mountains better than CVS!), a simple wiki, and a simple issue tracker, on a single website. I've been tossing around the idea of moving ChucK to Google Code as well, but haven't quite had the time/willpower to reach agreement with the ChucK team that thats the right move. The main disadvantage of Google Code that I see is that some people don't trust Google.<br>
<font color="#888888"><br>
spencer<br>
</font><div><div></div><div class="h5"><br>
<br>
On Dec 28, 2009, at 5:12 AM, Kassen wrote:<br>
<br>
> Tomasz;<br>
> @kassen. I completely agree with your take on both the pros and cons of an extra issue tracker.<br>
><br>
><br>
><br>
> Great, I really hope the DEV's will chime in on this but so far they have been silent on the issue... there may be good reasons for that, I don't know. When I wrote that last mail, BTW, I wasn't aware of the exact extend of the change to the WiKi that you outline below. This changes matters.<br>
><br>
><br>
> Ah. The change is probably spam related then. Here's a screen grab of the not-so-friendly registration screen at the moment:<br>
> <a href="http://img.skitch.com/20091228-c6rsmfqnnerdhritkjip3u9kh1.jpg" target="_blank">http://img.skitch.com/20091228-c6rsmfqnnerdhritkjip3u9kh1.jpg</a><br>
><br>
><br>
> Yeah, I'm sure it's spam. I'd vouch for you, I must count as a member of that WiKi's community by now but clearly I'm not Princeton-CS so that probably doesn't count. Ok, I understand that move but for our purposes that's probably the end of the WiKi as a tool. I'm sure that if you'd ask somebody like Dan or Tom nicely you could get in but I also suspect that neither feels like confirming a few accounts a week through whatever set of red-tape that procedure may have. Another issue is that it's now xmass break so the web department there probably doesn't feel like doing a lot (and rightly so!).<br>
><br>
> Ge will have to make a call here, I feel, but Ge seems offline and might be with his family and hence out of reach. Let's push for a solution here in a week or so after new year (on our calender), because this needs a solution. Submitting bugs should be easy.<br>
><br>
> Good that you brought this up. To me right now this seems like a more urgent issue than any individual bug may be.<br>
><br>
> Yours,<br>
> Kas.<br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> chuck-users mailing list<br>
> <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>
> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br>
_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
</div></div></blockquote></div><br>