Its interesting how people are never really satisfied with bug tracking, despite there being quite a market and competition.
I guess cause they are really trying to solve 2 overlapping problems: bugs and issue tracking for project teams with some project management, and on the other side is it a place for end users to log issues/requests/bugs etc... (the latter are the ones that might be "scared away"). I sort of wonder if a solution is something like JIRA for the project side, and then for a more user driven front end something like uservoice - where things get voted on, it aggressively de-dupes things... On Jul 14, 10:35 pm, Straun <[email protected]> wrote: > As an open source project surely you must rate exposure to your > community as highly desirable? > > My only observation is that strangely Google code does not get much > exposure via Google itself, instead projects on SF get the best > exposure. This might be because the page ranking systems rate SF long > standing might above googlecode's fresh faced approach. > > I have yet to see if Kenai does any better. > Good Luck. > > On Jul 14, 12:13 pm, Reinier Zwitserloot <[email protected]> wrote: > > > > > I'm looking around for online project hosting, and frankly, I'm not > > really finding the perfect solution. > > > NB: JIRA gets a double negative because it's utterly useless for Joe > > Schmoe who would like to file a bug. You get a massive screen filled > > with bells and whistles, which is just going to scare people away. > > Google Code's home-grown issue tracker, but then without requiring you > > to have a google login, that'd be perfection. > > > kenai: Supports git (++), wiki (+), JIRA or bugzilla as issue tracking > > (--). Bonus: Netbeans integration. > > > github: Supports git (++), wiki (+), useless home-rolled issue tracker > > (--). Bonus: Lots of repository visuals. > > > google code: Only supports hg (-), wiki (+), nice homegrown issue > > tracker (+). Bonus: It's google, so stable under load. > > > sourceforge: Vague sense of being from the 90s (-), Supports git (++), > > no wiki (-), not so nice homegrown issue tracker (-). > > > None of them really convince me. Right now I'm hosting the repository > > and wiki on github, but hosting the downloads and the issue tracker on > > google code. I wonder if that's even allowed on those services. I must > > say I looked at sourceforget only for writing this post and they've > > done quite a job on improving the look. It used to be that your > > average user would get utterly overwhelmed by the vast amount of > > options, almost all of which led to empty pages because project admins > > didn't use any of those niche features. > > > Which ones am I missing (It is an open source project, but if it costs > > a little, that might be okay)? > > > The perfect project hosting: > > > - git support (required) > > - wiki (nice to have) > > - bug tracking that isn't going to scare away a user, and preferably > > doesn't require a user to create an account first (required) > > - hosting some sort of static homepage (nice to have) > > - download section that supports direct linking (required - no user is > > going to navigate a forest to download something) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
