Create a Trac component for T@H #1245
Comments
Author: tom[at]compton.nu 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 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 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 Replying to [comment:3 tom[at]compton.nu]:
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.
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 I propose
|
Author: tom[at]compton.nu Done. |
Reporter: chriscf
[Submitted to the original trac issue database at 8.50pm, Wednesday, 8th October 2008]
It is currently not clear where T@H issues go. There is more than one component where they could go, but none is an ideal fit.
I propose that a 'tah' component is created in Trac to keep all of this together.
The text was updated successfully, but these errors were encountered: