Opened 11 years ago

Closed 11 years ago

#1245 closed task (fixed)

Create a Trac component for T@H

Reported by: chriscf Owned by: Tom Hughes
Priority: minor Milestone:
Component: admin Version:
Keywords: Cc:

Description

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.

Change History (6)

comment:1 Changed 11 years ago by Tom Hughes

Resolution: wontfix
Status: newclosed

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.

comment:2 Changed 11 years ago by Knut Arne Bjørndal

Resolution: wontfix
Status: closedreopened

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.

comment:3 Changed 11 years ago by Tom Hughes

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?

comment:4 in reply to:  3 Changed 11 years ago by Knut Arne Bjørndal

Replying to tom@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.

comment:5 Changed 11 years ago by spaetz

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

comment:6 Changed 11 years ago by Tom Hughes

Resolution: fixed
Status: reopenedclosed

Done.

Note: See TracTickets for help on using tickets.