Subject: Re: XSLT templates to eliminate duplicated information
To: Hubert Feyrer <firstname.lastname@example.org>
From: Pavel Cahyna <pavel@NetBSD.org>
Date: 06/17/2007 20:23:46
On Mon, May 28, 2007 at 12:49:45AM +0200, Hubert Feyrer wrote:
> On Sun, 27 May 2007, Pavel Cahyna wrote:
> >I have done a step in this direction. In the list of developers, a person
> >may have <group> tags under his entry indicating to what groups (s)he
> >belongs (see htdocs/People/developers.xml). Under
> >htdocs/People/groups, there is a list of groups with their members.
> >I have created XSLT templates to autogenerate the latter from the former
> >when htdocs/People/groups/index.html is recreated. This way, it will be
> >necessary to update group membership in only one place. I have also
> >separated the list of developers from developers.xml to a new file,
> >developerlist.xml. There is also a XSLT template totext.xsl, which creates
> >a textual list suitable for insertion into src/distrib/notes/common.
> Doesn't our "welcome" document already suggest some file(s?) that new
> users should add themselves too (I forgot the name)? If so, maybe we can
> make that our central "user (developer) database" where "everything" is
> created from.
Yes, htdocs/People/developers.xml (and htdocs/share/xml/developers.ent).
This is what becomes the central developer database in my scheme (only
with rename to htdocs/people/developerdb.xml).
> No idea what "everything" exactly is, but investigating this a bit more
> before rushing it in may be worthwhile in the long run.
There is also the list in src/distrib/notes/common/main, and I have a
XSLT script to generate it from htdocs/people/developerdb.xml, but I
dont think it is too useful. It is not a big problem to update those
three files after one becomes a developer, IMHO. It is more interesting
to autogenerate lists that change more often, such as the group
membership or list of portmasters.