> Planned and completed renames should be posted on the web
> site somewhere for normal users to view (wiki?). In
> addition, renames (even for minor apps) should be included
> in the docbooks under, e.g., "Where did all my 'K' apps
> go?"

I'm updating the help files and user guides. I plan to add a section titled something like "The K and T In App Names." I will explain the history of the naming convention. In that section I could explain the gradual renaming efforts and state the goal is gradual and that renaming is not a priority and only a nice goal.

In recent discussions I mentioned we have no documentation review process. Any renaming necessarily requires a documentation review (and I'm doing just that in my current revisions). Long term, if done correctly, upon release the documentation will reflect the new name and any renaming will require only an announcement in all mailing lists and any "What's New" documents we push with each release.

I notice some in this list still refer to package names with a k rather than the newer t. :)

I'm a long-time user with deeply engrained habits. Yet I don't see major hurdles with renaming. We have to be careful to keep everybody fully informed, that's all. We can change text strings in the sources, but we can't change custom configurations or scripts users have created.

For example, recently I was troubleshooting something and made no progress until I realized I was incorrectly typing kdesu rather than tdesu. Another example is one of my startup scripts failed to work as expected until I realized I had not yet updated from kdm to tdm.

Yes, there will be mental adjustments with any significant renaming. I agree there should be both a forewarning announcement as well as a release announcement. :)

Darrell