public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: Hugo Gayosso <hgayosso@gnu.org>
Cc: gnats-devel@sources.redhat.com, savannah-hackers@gnu.org
Subject: Re: Web interface for GNATS administration?
Date: Sun, 08 Apr 2001 11:28:00 -0000	[thread overview]
Message-ID: <87elv39rk4.fsf@zamazal.org> (raw)
In-Reply-To: <87ofuqbvpj.fsf@wildebeest.penguinpowered.com>

>>>>> "HG" == Hugo Gayosso <hgayosso@gnu.org> writes:

    HG> I know that gnatsweb helps in creating, viewing, editing PRs,
    HG> but what about GNATS administration?

    HG> Is there plans to develop such interface? (either inside
    HG> gnatsweb or a completely independent one).

AFAIK it's very unlikely.

As for savannah, the quickest solution is probably to write your own
simple system now.

In longer run, however, I'd prefer moving GNATS closer to already
existent "configuration via Web" systems (don't ask me which ones, I
don't know and use them, but I suppose they exist).  For instance, one
my friend would like GNATS could have stored its configuration in LDAP
so that he could use his general LDAP management system for GNATS
configuration.

Particularly, if anybody wanted to create a Python API to GNATS, please
let me know.  I've already attempted to create one in gnats2w but did it
in a wrong way (it doesn't fit the flexibility of GNATS 4).

Milan Zamazal

-- 
Wasting somebody else's time strikes me as the height of rudeness.
						      Bill Gates

  reply	other threads:[~2001-04-08 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 14:11 Gnats 4 install howto Yngve Svendsen
2001-03-24 15:17 ` Web interface for GNATS administration? Hugo Gayosso
2001-04-08 11:28   ` Milan Zamazal [this message]
2001-04-27 16:51   ` Yngve Svendsen

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=87elv39rk4.fsf@zamazal.org \
    --to=pdm@zamazal.org \
    --cc=gnats-devel@sources.redhat.com \
    --cc=hgayosso@gnu.org \
    --cc=savannah-hackers@gnu.org \
    /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).