On Fri, Jul 3, 2009 at 10:35 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> On "suggestions for improvement": I need to be able to bookmark the
> commitfest summary list (whichever page is equivalent to the old wiki
> page). The current URL seems to be
> http://commitfest.postgresql.org/action/commitfest_view?id=2
> which is both opaque as can be and not looking like it's intended to
> be stable over the long term. I can also imagine people wanting to
> refer to particular patch entries in email, but those URLs are no
> better. Could we pay some attention to using URLs that are stable
> and self-explanatory?
I'm not sure why you would think that it's not stable. It's not
stable in the sense that it won't always be the open CommitFest, but
it's certainly stable in the sense that it will always be the same
CommitFest that it is now. It's actually MORE stable than the wiki,
since the wiki doesn't permit you to change the name of the CommitFest
without also changing the URL.
I'm also not sure what you would think that it's not self-explanatory,
since it looks pretty self explanatory to me. You've asked to view a
commitfest. The id of that commitfest is 2. What more do you want to
know?
If you're advocating for the use of wiki-style names, where the URL
actually contains the name of the things that it points to, then you
have incompatible requirements, because things can, do, and will
continue to get renamed. If the URL is built around the name, then
the URL will change when the name changes. If you want it to be
stable, a non-natural key is your only option. And I frankly don't
see what's wrong with that. We regularly deal in message-IDs or other
links to the archives, which are certainly totally opaque.
Fortunately, they're links. You can click on them, and then you see
what they are.
...Robert