[chuck-users] Issue/bug tracker system?

[Tomasz Kaye's brain]

@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.

I guess that the main costs of Google code then are:
1. Dependency on Google (people may be reluctant to trust or support Google)
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).

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).

Github http:www.github.com
Michael's Lick project on github is a relevant example:
http://github.com/heuermh/lick
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 (?).

Launchpad https://launchpad.net/
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.

On Wed, Dec 30, 2009 at 8:58 AM, Spencer Salazar
<ssalazar at cs.princeton.edu>wrote:

> 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.
>
> 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.
>
> spencer
>
>
> On Dec 28, 2009, at 5:12 AM, Kassen wrote:
>
> > Tomasz;
> > @kassen. I completely agree with your take on both the pros and cons of
>  an extra issue tracker.
> >
> >
> >
> > 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.
> >
> >
> > Ah. The change is probably spam related then. Here's a screen grab of the
> not-so-friendly registration screen at the moment:
> > http://img.skitch.com/20091228-c6rsmfqnnerdhritkjip3u9kh1.jpg
> >
> >
> > 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!).
> >
> > 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.
> >
> > Good that you brought this up. To me right now this seems like a more
> urgent issue than any individual bug may be.
> >
> > Yours,
> > Kas.
> > _______________________________________________
> > chuck-users mailing list
> > chuck-users at lists.cs.princeton.edu
> > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20091230/39cc2a43/attachment.html>