From: "Josh Berkus" <josh@agliodbs.com>
To: rhdb@sources.redhat.com
Subject: Developer wanted for SF-PUG meeting
Date: Wed, 29 Jan 2003 18:15:00 -0000 [thread overview]
Message-ID: <web-2615437@davinci.ethosmedia.com> (raw)
RHDB developers & users:
Hey! I'm Josh Berkus, whom several of you probably already know. I'm
e-mailing this list because among other "hats" I run the San Francsico
PostgreSQL User's Group (SFPUG).
SFPUG would be interested in having and RHDB development team member,
or someone who has done a large RHDB/Advanced Server implementation,
come to one of our meetings to talk about RHDB. Is there anyone on
the RHDB/Advanced Server team in Northern California?
Or is there someone at Red Hat I should contact? Keeping in mind that
this is a "geek" meeting, and we don't want an RHAS salesperson.
(BTW, if anyone wants to *join* SFPUG, just e-mail me. All RHDB users
in the greater SF Bay Area are welcome!)
Our upcoming meetings will be:
February 12, 7pm, Oakland
March 11, 6:30pm, San Francisco
Please e-mail me directly, as I will not be subscribed to this mailing
list indefinitely.
-Josh Berkus
Aglio Database Solutions
San Francisco
reply other threads:[~2003-01-29 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=web-2615437@davinci.ethosmedia.com \
--to=josh@agliodbs.com \
--cc=rhdb@sources.redhat.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).