public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@cygnus.com>
To: Overseers List <overseers@sourceware.cygnus.com>
Subject: FOM for everybody ?
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <873dqw3h5s.fsf@cygnus.com> (raw)

Today I looked at setting up FAQ-O-Matic for all sourceware projects,
and not just gcc.

It looks pretty easy to do.

I thought before doing it I would run the plan by the Gods of
Sourceware, since this is (potentially) my first non-trivial
sourceware hack.

According to the fom FAQ:

  http://www.dartmouth.edu/cgi-bin/cgiwrap/jonh/faq.pl?file=409

the best way to do this is to make one copy of `fom.cgi' per project.
So I propose making one subdir per project in cgi-bin (eg
/sourceware/www/cgi-bin/automake, /sourceware/www/cgi-bin/java, etc),
and copying fom.cgi there.  (gcc we would leave as-is, of course.)

Instead of keeping the fom meta-data in the cgi directory (which seems
ugly to me), I'd rather make a new `fom-meta' directory in
/sourceware/www, with per-project subdirs there.  (Or I could do
something else, in tune with the "sourceware philosophy", whatever
that might be.)

Projects will use a URL like `/cgi-bin/automake/fom'


Actually, I know there is more to do than that (at least set up and/or
tweak the cron job referred to in the instructions), but I don't have
permissions to look in gcc/cgi-bin/fom-meta :-(


Did we send a postcard to the FOM guy?

Tom

             reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Tom Tromey [this message]
2000-12-30  6:08 ` Jeffrey A Law
2000-12-30  6:08   ` Jim Kingdon
2000-12-30  6:08     ` Jeffrey A Law
2000-12-30  6:08       ` Jim Kingdon
2000-12-30  6:08         ` Jason Molenda
2000-12-30  6:08     ` Tom Tromey
2000-12-30  6:08       ` Someone
2000-12-30  6:08   ` Tom Tromey
2000-12-30  6:08 ` Jason Molenda
2000-12-30  6:08   ` Tom Tromey
2000-12-30  6:08     ` Jason Molenda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873dqw3h5s.fsf@cygnus.com \
    --to=tromey@cygnus.com \
    --cc=overseers@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).