Hello Thomas On Fri, 2008-01-04 at 14:16 +0100, Thomas Perl wrote: > Hello, Paul! > > Thanks for your feedback regarding my questions. I hope that we also get > some other people to respond to get an overview of the options we have. > > Paul Rudkin wrote: > > I have started on some documentation (locally) however with the dynamics > > of some of the features right now I may stick with a version just to get > > a baseline up on the Wiki. > > It would be great if you could slowly start to migrate that > documentation to the Wiki. It doesn't matter if it is "done" or not > (documentation will never fully be "done"), so just push it on the wiki, > link it from the start page (maybe even create a "User guide" page that > links the single documentation pages together from one place. It's a > wiki and its history is fully saved, so you can't really do anything > wrong - and if, it's quickly reverted, anyway :) I will get into it over the next week or so. I have to go on a business trip tomorrow for a few days so my weekend is very short this week!
> > I don't mind helping with the TODO list etc. Should we even consider a > > Bug/Feature reporting system such as Bugzilla? This may help us assign > > bugs/features to various developers? Just a thought? > > Yes, I was considering a bug tracker, but quickly realized that all bug > trackers that were usable (Bugzilla, Mantis, ..) required users to > register. If possible, I want to make reporting bugs as easy as > possible. Having to register an account before filing a bug is not "as > easy as feasible". If we decide to introduce a bug tracker, I'm thinking > about Launchpad.net or Bugzilla. Any suggestions/experience with either > of them, or even suggestions for other bug trackers? I have recently implemented Bugzilla at work so I am rapidly becoming an expert with it. We have various products that have PC based software as well as embedded software so it is proving really useful to prioritise the software effort with respect to critical bugs etc. Prior to Bugzilla bugs/features were tracked in a spreadsheet that ended up difficult to manage. It is only used internally (i.e it's not available for the public to view) and it works extremely well end customers report problems via our Customer Service department who then end up filing bugs if they are real bugs. I would think that registration would be essential for a public facing Bugzilla site, if somebody really wants to report a bug they will register and will be advised of it's progress automatically. If you don't have to register then I can't help to think that it could get abused....on that subject I am surprised registration is not required to edit the gPodder wiki for the same reason! Whichever system we go for, I am more than happy to host it if my webhost company supports it! (I am sure it does). Perhaps we should register gPodder.org? Paul _______________________________________________ gpodder-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-devel
