On Sun, Sep 2, 2012 at 09:37:48AM -0400, Bruce Momjian wrote:
> > AFAICT, the last time anybody actually did anything but fix typos in
> > it was in 2008. So I think that "stay in sync" argument is not really
> > relevant.
> >
> >
> > >> Also, it took almost a year for anybody to notice that they weren't
> > >> there, so they're clearly not used very much.
> > >
> > > I think it's not visible enough. We have plenty of new people trying to
> > > understand the PG innards all the time that it remains a useful
> > > resource.
> >
> > Oh, I'm not saying we should get rid of it. Just migrate it to a
> > better position. If we put it "properly on the website" it would
> > probably get *more* exposure, rather than less...
>
> I am ready to work on this. The flowchart has three parts:
>
> 1) the image, with hot clickable areas --- I assume this can't be done
> in a wiki and has to be on our website.
>
> 2) text for clickable links in #1 --- needs either a wiki page for
> every entry or an html 'id' that allows us to scroll to the desired
> entry. This can be done on the wiki. Would be nice to add links to the
> README files in specific directories too.
>
> 3) links from the #2 text to the git source code tree, e.g.
> http://git.postgresql.org/gitweb/?p=postgresql.git;a=tree;f=src/backend/commands
>
> Who can help me setup #1 and I can do #2 and #3? I need a web directory
> to hold the image and the ability to edit the HTML to link properly to
> the wiki.
OK, updated flowchart now online:
http://www.postgresql.org/developer/backend/
While the main page requires a patch to modify, the wiki it links to can
be modified by anyone with a wiki account.
I have removed src/tools/backend from git now that we are hosting it
elsewhere.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +