[Tracker-discuss] Feature/Change request handling procedure

["Martin v. Löwis"]

Stefan Seefeld schrieb:
> The reason the issue class name is part of the URL is that roundup provides
> the means to serve multiple entities. For example you may want to change your
> own contact address, which roundup stores as a property of a 'user' class.
> So you may want to access 'http://issues.python.org/user25', or do the same
> by mail using the subject line starting with [user25]. For roundup that is
> conceptually the same as if you changed 'issue12', say.

While that is the technical reason, it is no justification. For users,
there *is* a notion of a "main" class. So it is fine that "user25" is
a valid object id - still "12" could be the id of an object on its
own (namely, "issue12"). If one class is designated the "main" class,
URLs that start with numbers could uniquely identify objects of the
main class - ids of other classes would continue to start with the
class name.

Support for the notion of a "main" class could be in roundup itself,
or it could be in Apache rewrite rules.

Regards,
Martin