[Typo3-bugs] Team page on TYPO3.org

[Michael Scharkow]

Michael Stucki wrote:
> Hi Michael,
> 
> 
>>1. What's our team name, we have "bug filter team" (but we do more than
>>just filtering), bug tracker team and bug fixing team (which I'd
>>prefer). Shall we have a poll on this?
> 
> 
> I prefer "bug hunters" :-)

AAAAAARRRRRRGGGGGGHHHHHHHHHHHH!


>>2. Is this list read-only for non-members? Do we want to keep this? Who
>>gets the foreign mail for moderation, stucki? Can we use this for
>>lengthier discussions about bugs, or just for general stuff?
> 
> 
> The list is closed for non-members. If anybody wants to subscribe he needs my 
> approval.
> 
> Last week I did some clean-up and compared the list of subscribers with the 
> user accounts on bugs.typo3.org.
> 
> I got some feedbacks but didn't work throught them yet.
> 
> Finally, this mailing list should cover only people with a non-default status 
> at the bugtracker.

Seems all very reasonable to me.


>>3. We need a contact address for requests, like joining the team,
>>reporting errors with mantis, etc. I suggest to use bugs at typo3.[com/org]
> 
> 
> bugs at typo3.org would be fine. Robert, can you make this a forwarder to this 
> list (equally to the security list).
> 
> However note to add some policy for the people: This address must not be used 
> for reporting bugs (or do you want that?).

This is what I'l like an autoresponder for: Somebody writes to 
bugs at typo3.org, gets an automated response ("If you want to submit a 
bug, use the f*cking bugtracker!!!1", and the mail is forwarded to
a) here, b) you (as moderator)...


> Let's say it's just a contact to this team. Nobody should ask to get a higher 
> status - I like the current policy to invite people when we see that they are 
> very active. Agreed?

Yep.


>>4. Please proofread http://typo3.org/teams/bug-filter/ and subpages,
>>make suggestions, flame me, etc.
> 
> 
> I think it needs some information about how we select the bugs...

Um, how do we select bugs? By severity (I don't), by attached diff 
(maybe once this is implemented in view_all), by sponsoring offers, by 
chance (this is the most widely used strategy I guess)?

I'd be glad to write more about this, and the upcoming possibility for 
sponsoring.

Greetings,
Michael