hi devels,
without much thinking about tools and structure, I have started building a database of bugs and buglets in the core of Pd (aka Miller's sources). Before shaping it into a form suitable for a more general use, I would like first to collect as much data as I can, from pd-list, and from my experience. Which is the easy part.
The hard part, I think, is not just gathering reports, but managing them afterwards. Usually, there would be a person `responsible' for validating a particular category of a report, and guiding the report through its lifetime in the database. That person would either actually maintain the source, or closely cooperate with a maintainer. Such setup might prove too formal, though, in case of the ``Miller's & co(mmunity)'' development model. I do not know... perhaps, that model requires a `sync-person' tracking the releases, with Miller occasionally getting forwarded mailings or digests?
The tool is gnats, currently, chosen for the sake of being able to start easily and locally, without bloating my system with apache, mysql, and what not. Gnats is nicely designed, but for some odd reason hardly maintained anymore -- hence buggy, and largely abandoned outside of the freebsd world. The transition of my local database into a public service, will probably mean importing data into some other bug tracker (requiring, hopefully, only a simple script to be written, or adapted).
When more of the actual contents builds in, I will let you know. For the time being -- comments, please (and bug reports, of course).
Krzysztof
Hallo, Krzysztof Czaja hat gesagt: // Krzysztof Czaja wrote:
without much thinking about tools and structure, I have started building a database of bugs and buglets in the core of Pd (aka Miller's sources). Before shaping it into a form suitable for a more general use, I would like first to collect as much data as I can, from pd-list, and from my experience. Which is the easy part.
Thank you very much for this effort, and I think, that this is really needed sooner or later, so better start shaping it up now. I see lots of projects use Mantis (http://mantisbt.sourceforge.net/) e.g. Ardour or ALSA, and Mantis seems easy to set up, or Bugzilla, which looks harder to set up and probably is overikll for us. A quick google found import scripts to convert Gnats data to both, so starting with Gnats for now and later migrating to another one which maybe offers more feature should be no problem. We surly should use one of the popular bug tracking systems, because their developers know what they're doing and we don't.
I'll think up some bugs later. ;)
ciao
This is great, definitely needed. While the gnats upgrade path should work, we could also use the bug tracker on the SourceForge site, which is already set up and ready to go. I am not sure which software it is based on, but its nicely integrated on the same site as the CVS.
As for managing the bugs, I think we should start out with a limited group of people who can post bugs, those who can verify the bugs themselves. Then once it becomes established and we have willing maintainers, we could open it up to bug submissions to the general public.
.hc
On Wednesday, Feb 4, 2004, at 11:59 America/New_York, Krzysztof Czaja wrote:
hi devels,
without much thinking about tools and structure, I have started building a database of bugs and buglets in the core of Pd (aka Miller's sources). Before shaping it into a form suitable for a more general use, I would like first to collect as much data as I can, from pd-list, and from my experience. Which is the easy part.
The hard part, I think, is not just gathering reports, but managing them afterwards. Usually, there would be a person `responsible' for validating a particular category of a report, and guiding the report through its lifetime in the database. That person would either actually maintain the source, or closely cooperate with a maintainer. Such setup might prove too formal, though, in case of the ``Miller's & co(mmunity)'' development model. I do not know... perhaps, that model requires a `sync-person' tracking the releases, with Miller occasionally getting forwarded mailings or digests?
The tool is gnats, currently, chosen for the sake of being able to start easily and locally, without bloating my system with apache, mysql, and what not. Gnats is nicely designed, but for some odd reason hardly maintained anymore -- hence buggy, and largely abandoned outside of the freebsd world. The transition of my local database into a public service, will probably mean importing data into some other bug tracker (requiring, hopefully, only a simple script to be written, or adapted).
When more of the actual contents builds in, I will let you know. For the time being -- comments, please (and bug reports, of course).
Krzysztof
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
________________________________________________________________________ ____
"If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it."
- Thomas Jefferson
-
Frank Barknecht -
Hans-Christoph Steiner -
Krzysztof Czaja