Hi all My comments
*Mailing list* It works well for me now as I have most e-mails in my GMail already. But initial research was not easy, as had to download some archives and search through them. Any solution offering search box would be welcome. Like Google Groups or whatsoever. But whatever you pick, just check, how accessible the search is. I already met few phpBB installations, where it was hard or impossible to search.
*Bug tracking* What I like on Open Source is, that I have strong chance, that if there are some known problems, I can find them in advance by simple research of bug list and discussions. I remember the time, when I was developing AutoCAD applications, deciding technology to use, researched available resources, found no problems, entered the technology and hit the problem. Answer "What you describe has ID 123456 in our bug tracking system" was something what upset me quite well. That time we were already spending some hours on it we could avoid this, if the bug list would be open.
*Systems and processes* I know about one great team, using Redmine for managing tasks (large ISP provider maintaining dedicated servers who has to solve a lot of configuration and sw development tasks) No system is perfect, at least until real processes are established. It is like MS Outlook - great tool, but how shall one be using it? Ability to create complex grids and filters did not help me much in my work management, until I found GTD methodolyhttp://en.wikipedia.org/wiki/Getting_Things_Done, defining higher level processes and principles (usable in any list management solution incl. paper planner)
So whatever you pick, be sure you take care about definition of processes first. This approach also saves a lot of time in learning any tool, as you then easily know, what features you may skip.
Many years I was using JBoss application serverhttps://issues.jboss.org/browse/JBASand learned a lot about JBoss internal processes.
1. Using JIRA for bug tracking, defining milestones, presenting those plans to the public, showing list of implemented features. 2. Keep discussion out of JIRA - in discussion forum. They first started discussion in discussion forum and as soon as it went stable, it was entered into JIRA as an issue or feature request. This way all got freedom to discuss and JIRA stayed clean for working. 3. They have even some formalized rules for this, I found it couple of years ago somewhere on the web.
Good luck with your great effort.
Jan
2011/1/27 Michael Seiferle michael.seiferle@uni-konstanz.de
Hi,
thanks for your hint. JIRA/Atlassian looks quite interesting, we are currently developing some ideas to externalize our to-date internal only ticket system. We are using Redmine at the moment for both project management and tickets. We are considering several solutions, I'll keep you posted with updates!
More opinions & thoughts from the list would be welcome as well.
Kind regards
Michael
Am 27.01.2011 um 00:13 schrieb NewIntellectual:
For the first, I have used the popular JIRA system (
http://www.atlassian.com/). While I think it could use improvements, it's pretty powerful and I think it would be better than what exists now. They say that it's free to use for open source projects.
I have found the GNU mailing list system to be cumbersome to use, since
it is all email based, and the archives are not automatically searchable, nor grouped in any way by subject. There are a number of free discussion board systems, including at least one based on Java, and I think that would be a big improvement.
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk