Comment 1 Steffen Pingel 2006-07-06 22:19:59 EDT

Trac currently uses the following naming schema:

  Trac Connector
  - 1..n Task Repository
  -> Trac Client Manager
    - 1..n Trac Client (TracXmlRpcClient, Trac09Client)

Comment 2 Steffen Pingel 2006-07-30 12:04:18 EDT

When the renaming is done all *Trac09* classes should be renamed to *TracWeb* to avoid confusion with the access method and version of the repository.

Comment 3 Mik Kersten 2006-12-07 15:20:42 EST

We focused on fixing naming for the Tasks framework.  Connectors are still largely in internal packages and naming will need to be fixed post 1.0.

Comment 4 Steffen Pingel 2007-02-22 20:49:30 EST

Renamed Trac classes as per comment 2.

Comment 5 Steffen Pingel 2007-02-22 20:49:32 EST

Created attachment 59622 [details]
mylar/context/zip

Comment 6 Mik Kersten 2007-02-22 20:55:23 EST

Great.  I'll try to go through the other connectors before 2.0M2 ships, so that we set a good example for connector implementors.

Comment 7 Steffen Pingel 2007-05-07 01:45:08 EDT

I am considering renaming of JiraServer to JiraClient for consistency with TracClient and BugzillaClient. Opinions?

Comment 8 Robert Elves 2007-05-07 14:04:41 EDT

 (In reply to comment #7)
> I am considering renaming of JiraServer to JiraClient for consistency with
> TracClient and BugzillaClient. Opinions?
I agree.

Comment 9 Mik Kersten 2007-05-07 15:24:06 EDT

Yes, I think that's a good idea because it names the class for what it is (a client to the JIRA server) and not what it abstracts (the JIRA server).  If the class were a data type it would be fine to name it for what it abstracts, but it's a connectivity mechanism.  I also thing that JiraServerFacade is a good name.  It sounds more complicated so I prefer JiraClient.  Also, JiraClient parallels the naming that we inherit from HttpClient.

Steffen: if you make this rename could you add a note to the Integrator Reference on this naming convention?

Comment 10 Steffen Pingel 2007-05-07 15:33:40 EDT

Alright. I did not understand your comment regarding JiraServerFacade though. That class is essentially a facade to JiraServerManager (which would be renamed to JiraClientManager). 

Comment 11 Mik Kersten 2007-05-08 12:35:05 EDT

 (In reply to comment #10)
> Alright. I did not understand your comment regarding JiraServerFacade though.
> That class is essentially a facade to JiraServerManager (which would be renamed
> to JiraClientManager).

Yes, the rename to JiraClientManager sounds right.  I was referring to the fact that "FooServerFacade" was an alternative naming convention to "FooClient", but I think that we've all settled on the latter.

Comment 12 Steffen Pingel 2007-05-08 20:34:49 EDT

Renaming done. Anything left to do here?

Comment 13 Steffen Pingel 2007-05-08 20:35:20 EDT

Created attachment 66390 [details]
mylar/context/zip

Comment 14 Mik Kersten 2007-05-09 02:15:26 EDT

This should do it.  

Comment 15 Mik Kersten 2007-05-09 02:15:57 EDT

Done.