diff options
author | Bruce Momjian | 2006-12-22 22:42:36 +0000 |
---|---|---|
committer | Bruce Momjian | 2006-12-22 22:42:36 +0000 |
commit | d31ccb6c3e73901c44865bfce3f5dd20774f7a89 (patch) | |
tree | 9e4a237ba34cb1b207bcde6e0306524e1d04781c /doc/FAQ_DEV | |
parent | 03d2a1c688cf00cbfeb513f33094965a3ae41ff0 (diff) |
Add a link to the developer's FAQ for my article about how companies can
work effectively with open source communities.
Diffstat (limited to 'doc/FAQ_DEV')
-rw-r--r-- | doc/FAQ_DEV | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV index 63ae1b28f5..9bac5dfeb1 100644 --- a/doc/FAQ_DEV +++ b/doc/FAQ_DEV @@ -1,7 +1,7 @@ Developer's Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Wed Dec 20 11:21:55 EST 2006 + Last updated: Fri Dec 22 17:41:41 EST 2006 Current maintainer: Bruce Momjian (bruce@momjian.us) @@ -100,7 +100,9 @@ General Questions both the internal implementation method you plan to use, and any user-visible changes (new syntax, etc). For complex patches, it is important to get community feeback on your proposal before starting - work. Failure to do so might mean your patch is rejected. + work. Failure to do so might mean your patch is rejected. If your work + is being sponsored by a company, read this article for tips on being + more effective. A web site is maintained for patches awaiting review, http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are |