From: Greg Smith <greg@2ndquadrant.com>
To: Steve Lawrence <slawrence@tresys.com>
Cc: Kohei Kaigai <Kohei.Kaigai@EMEA.NEC.COM>,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: Patch Review Process
Date: Mon, 16 May 2011 12:04:05 -0400 [thread overview]
Message-ID: <4DD14AF5.1060609@2ndquadrant.com> (raw)
In-Reply-To: <4DD13501.1060406@tresys.com>
Steve Lawrence wrote:
> Is commitfest custom built by the postgresql community or is it some open source
> project? I can't seem to find any information on what the backend is.
>
Yes to both, sort of. It was built for this purpose, but the result is
an open-source project available for others. Source code is
http://git.postgresql.org/gitweb?p=pgcommitfest.git ; it's a Perl
application aimed to run inside Apache, with a PostgreSQL back-end as
you might expect.
The application was developed after really not finding the workflow of
existing applications like Reviewboard to mesh well with the
requirements for PostgrSQL's development process. The main thing that I
think may not translate well into some other environments, but might
actually work here, is its heavy reliance on mailing list integration.
The main thing stored when you add a new entry to the CommitFest
application is a pointer to a mailing list URL. For the PostgreSQL
lists, that is driven by the message-id of the e-mail sent. The main
data stored is essentially is a list of pointers into the mail archives,
via message-id, with each tagged for what submission they all belong
to. Comments and such actually stored in the web application is
minimal; the idea is that you're using it to track e-mails sent to the
mailing list, where the primary review information is sent to.
Another caveat is that there was already a PostgreSQL single login
service that this hooks into. There's no internal support in the
CommitFest app for account creation/maintenance, it just calls the API
available on postgresql.org for that.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2011-05-16 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 15:14 Patch Review Process Steve Lawrence
2011-05-09 19:21 ` Guido Trentalancia
2011-05-09 19:58 ` Steve Lawrence
2011-05-13 7:53 ` Patch Review Process - Missing patch for selinux_set_mapping Richard Haines
2011-05-13 9:28 ` Patch Review Process Kohei Kaigai
2011-05-13 10:34 ` Guido Trentalancia
2011-05-16 14:30 ` Steve Lawrence
2011-05-16 15:15 ` Kohei Kaigai
2011-05-16 16:04 ` Greg Smith [this message]
2011-05-18 13:31 ` Steve Lawrence
2011-05-09 19:38 ` Guido Trentalancia
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=4DD14AF5.1060609@2ndquadrant.com \
--to=greg@2ndquadrant.com \
--cc=Kohei.Kaigai@EMEA.NEC.COM \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.