I'll weigh in on this as well: - Firstly, I don't think giving up control to google code outweighs the advantages of hosting everything ourself. I really don't have an idea how much work the upgrades are, but the recent spam attack seems like a one time issue, not something we're going to be constantly fighting against. - I agree that we should stop expecting all our users to open tickets, but I'm afraid if we start a new database, it will be a lot of work to get all the relevant tickets migrated. If we don't do that right, the time to find a tickets doubles (you'd have to search the new AND the old one each time). Besides, each user who would otherwise would have opened the hundredth "Facebook doesn't work" ticket, will now just post on the forums/tweet/IRC/mail it to us. Which would be about the same amount of effort to respond to as it would be to close a duplicate. So we would also need to update the support part of the website,
On 29 nov 2010, at 21:00, Colin Barrett wrote: > > My main concern with all of this though is who is going to do all this work? > This sort of blue sky restructuring is great to think about, but I think it's > also important to think about the low hanging fruit that can be done quickly > and easily that will make a big difference. > > For example, I think reorganizing our site to de-emphasize Trac for support > would be a big help, and doesn't seem like a ton of work. Similarly, let's > bring out our in-app help documentation online (it's already HTML, no?) -- > don't underestimate the power of Google! Link to it in the footer of adium.im > and bam, Googling for Adium problems just got way easier. > > -Colin > > I totally agree with the last point. I've started with something, but I'll start a new thread on that, as this one doesn't seem to have reached a consensus yet. Thijs
