Author: tom[at]compton.nu
[Added to the original trac issue at 8.21am, Thursday, 9th October 2008]

You can propose anything you like, but until such time as the people behind t@h give me a list of the components they want and who should get the tickets for each component nothing is going to happen.

Author: bob[at]cakebox.net
[Added to the original trac issue at 8.57am, Thursday, 9th October 2008]

Can a mailing list be the initial ticket owner for a component? If so I suggest creating a tilesAtHome component with the tilesathome list getting the tickets.

Author: tom[at]compton.nu
[Added to the original trac issue at 9.07am, Thursday, 9th October 2008]

Any email address can be, but using a mailing list is dangerous as it doesn't encourage anyone to "own" the bug - there is a risk that everybody on the list will assume somebody else on the list will deal with it.

Would that apply to the existing osmarender category as well? What exactly is the relationship between t@h and osmarender these days?

Author: bob[at]cakebox.net
[Added to the original trac issue at 10.04am, Thursday, 9th October 2008]

Replying to [comment:3 tom[at]compton.nu]:

Any email address can be, but using a mailing list is dangerous as it doesn't encourage anyone to "own" the bug - there is a risk that everybody on the list will assume somebody else on the list will deal with it.

I think it's better than some person getting all the tickets and everybody expecting him to take care of them all in some way.

Actually I think it can work quite well when a ticket is new and under discussion to clearly show that nobody owns it yet, and it will distribute comments to the entire list.

Would that apply to the existing osmarender category as well? What exactly is the relationship between t@h and osmarender these days?

I'm getting the feeling that we need a new list for osmarender since there will be people who care about osma that don't care about t@h and the other way around. This is something that will need to be discussed with the relevant people though.

Author: spaetz
[Added to the original trac issue at 4.29pm, Thursday, 9th October 2008]

I propose

• "t@h" for all t@h infrastructure related issues (client and server). You can make me the default owner and I'll reroute as necessary.

• "osmarender" for the XSLT code and the style sheet related issues (probably also orp related). All feature X doesn't render, or bridges should be merged would go here...

Author: tom[at]compton.nu
[Added to the original trac issue at 5.00pm, Thursday, 9th October 2008]

Done.