[PD-dev] Tracker to Mailing List interface

[guenter geiger]

On Thu, 21 Oct 2004, Hans-Christoph Steiner wrote:
> There are a couple of things that do need to be set up:
>
> In these three sections (Bugs, Support, and Patches), we need to come
> up with a list of Categories and Groups.  There are already some
> Categories, we can try those out and see how they work.  I took a look
> at some other SourceForge project to see what kind of Categories they
> used.  It seems that most people use the categories to label what kind
> of problem it is rather than which part of the code it is in, things
> like "Authentication Issues" or "Internationalization" (phpMyAdmin); or
> "Crash/Runtime error" (Fink).  Groups seem to be version numbers
> (0.37-2, 0.37-devel, etc.).  Here are some quick ideas for some

I have added some Categories (I took the categories because
this was the tab that is on the submit page).

They are currently:
zexy
puredata-dev
puredata
externals
abstractions

I am not sure if we need two qualifiers. It is important to have
distinct reports for puredata, the externals, etc.

We could add flext, cyclone, maxlib, iemlib etc,

One big advantage in categorizing with sub projects is that
it is orthogonal. This is hard to do with other more abstract
categories (should I file a bug report against hardware support,
audio problems or the MaxOS X package if pd only runs with
-noadc on my machine ?)
Lets make bug reporting not too difficult at the beginning.
If we need more structure we can add it later.

> Categories for Pd:
>
> Bugs
> 	Crashers
> 	Hardware Support (sound cards, OpenGL, etc.)
> 	Audio Problems
> 	Video Problems
> 	MacOS X packaging
> 	Windows Installer
> 	Debian Packages


> Patches
> 	MSP Core
> 	devel_0_37
> 	externals
> 	doc

The patches are mainly thought to be against Pd. This should be a
collection of suggestions, easily browsable, mainly to facilitate the
incorporation of features from the development branch.

We actually shouldn't need patches against the development branch.
Categorization is basically the same as with bugs.

>
> As for the Support section, I think we shouldn't use it, unless we have
> volunteers who are willing to check up on Support tickets, I think we
> should try to focus all such requests to the list and start maintaining
> the FAQ.  Having a forum interface to the lists would be awesome for
> those who don't want to join the lists.

I agree that the support section is what the list should be about.
Personally I am not missing a forum, others might find it useful though.
A good FAQ is something that should be worked out at the puredata.org
site.

Guenter


>
> .hc
>
>
> On Oct 21, 2004, at 3:24 AM, guenter geiger wrote:
>
> >
> > On Wed, 20 Oct 2004, Hans-Christoph Steiner wrote:
> >
> >> Its great that you set these up.
> >
> > Well, they were set up from the beginning, I am just trying to promote
> > them actually. SF documentation says that one could monitor each of
> > these
> > trackers, but I couldn't find the button to turn that on, thats why I
> > thought mailing list would be nice too.
> > Anyhow, if Johannes doesn't want to manage the mailing lists I am going
> > to set them up on sourceforge. Probably that would be the easiest thing
> > in terms of maintenance, and this way Johannes doesn't have the
> > additional
> > work.
> >
> > Three distinct lists is probably the best solution.
> >
> > Guenter
> >
> >> A managable bug tracking system will
> >> be most helpful.  As for the mailing lists, is it not possible for
> >> people to sign up for these mailings themselves via SourceForge?  The
> >> extra mailing lists might still be a good idea tho, to provide a
> >> central place to register for this kind of info.  I vote for three
> >> distinct mailing lists so you can choose which messages you want.
> >>
> >> .hc
> >>
> >> On Oct 20, 2004, at 6:32 AM, guenter geiger wrote:
> >>
> >>>
> >>> Hi,
> >>>
> >>> I was thinking about sending the tracker information to a
> >>> mailinglist,
> >>> so that we all can monitor them, look at the bug reports, etc. etc.
> >>>
> >>> IMO there are two options. One is to send all the tracker info to
> >>> the pd-dev list, the other is to have separate lists like
> >>> pd-bugs, pd-feature, pd-patches or one pd-tracker .... (well, its
> >>> three options already).
> >>>
> >>> Anyhow, in either case I think it would be best if the lists would be
> >>> hosted by IEM (speaking set up by Johannes) just like the others.
> >>> In case of using pd-dev directly, this list would have to be opened
> >>> to noreply at sourceforge.net (thats where the tracker notification will
> >>> be sent from).
> >>>
> >>> Please let me know what you think about it.
> >>>
> >>> Guenter
> >>>
> >>>
> >>> _______________________________________________
> >>> PD-dev mailing list
> >>> PD-dev at iem.at
> >>> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
> >>>
> >>
> >>                                      http://at.or.at/hans/
> >>
> >>
> >>
> >> _______________________________________________
> >> PD-dev mailing list
> >> PD-dev at iem.at
> >> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
> >>
> >>
>
> ________________________________________________________________________
> ____
>
>                    ¡El pueblo unido jamás será vencido!
>
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
>