[PD-dev] Tracker to Mailing List interface

[Hans-Christoph Steiner]

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  
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

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.

.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!