Issues system moving to google code

[joevenzon]

The sourceforge issues system is a pain to use and so I hardly ever update it. I'm thinking of using the google code issues system instead, which is way faster and more flexible. I've used it for another project and it's great. Is anyone going to be upset if I clear out the sourceforge one and move to google code? The only downside is that you'd need a google account.

[cotharyus]

No issues from my part. I should be able to contribute somewhat more meaningfully in the near future. We'll see. Either way, I don't see a move towards making any stage of development more usable as a problem.

[joevenzon]

Alright, it's here now:

http://code.google.com/p/vdrift/issues/list

Contributors, give me your google account names (PM if desired) and I'll add them to the project.

[cotharyus]

Er, gmail account names? I'll give you one guess. Ok, time's up. It's cotharyus.

[zimluura]

i signed in and commented that i'd gotten a windows exe together by following the instructions ™

i see a few issues i'd be happy to help with. but should i comment on them here on the forums, or on googlecode??

[joevenzon]

I added you both to the project. I'm not actually sure what permissions you get as being a member as opposed to not, but whatever.

Zimluura, good question... I think that since more people read and comment on the forums, we should have any issue-related discussions that would be relevant to the wider audience in the forum. Think of the issues list like a fancy TODO list, and the issues comments are just comments that apply only to the todo list. So, a question like "how should this issue be resolved?" would be put in the forum, but something like "okay, fixed RXXXX" would be in the issues list.

[thelusiv]

I have added 10 or so more issues to the tracker, and changed a few others. I like the system, it is simple and works pretty well.