Index: doc/src/sgml/external-projects.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/external-projects.sgml,v
retrieving revision 1.10
diff -c -r1.10 external-projects.sgml
*** doc/src/sgml/external-projects.sgml	10 Mar 2006 19:10:47 -0000	1.10
--- doc/src/sgml/external-projects.sgml	15 Jul 2006 02:22:02 -0000
***************
*** 1,29 ****
  <!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.10 2006/03/10 19:10:47 momjian Exp $ -->
  
   <appendix id="external-projects">
!   <title>External Projects</title>
  
    <para>
     <productname>PostgreSQL</productname> is a complex software project,
!    and managing it is difficult. We have found that many
     enhancements to <productname>PostgreSQL</productname> can be more
!    efficiently developed separately from the core project. Separate
!    projects can
!    have their own developer teams, email lists, bug tracking,
!    and release schedules. While their independence makes
!    development easier, it makes users' jobs harder. They have to hunt
!    around looking for database enhancements to meet their needs.
!    This section describes some of the more popular externally
!    developed enhancements and guides you on how to find them.
    </para>
  
    <para>
!    Many <productname>PostgreSQL</productname>-related projects are
!    hosted at either 
!    <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
!    or <ulink url="http://pgfoundry.org"><productname>pgFoundry</></ulink>.
!    There are other <productname>PostgreSQL</productname>-related projects that are hosted
!    elsewhere, but you will have to do an Internet search to find them.
    </para>
  
   <sect1 id="external-interfaces">
--- 1,34 ----
  <!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.10 2006/03/10 19:10:47 momjian Exp $ -->
  
   <appendix id="external-projects">
!   <title>PgFoundry and External Projects</title>
  
    <para>
     <productname>PostgreSQL</productname> is a complex software project,
!    and managing the project is difficult. We have found that many
     enhancements to <productname>PostgreSQL</productname> can be more
!    efficiently developed separately from the core project. 
!   </para>
!   
!   <para>
!    To help our community with the development of their external projects,
!    we have created the <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink>.
!    <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink> is built using the
!    GForge software project and is similar to SourceForge in its feature set. If
!    you have a PostgreSQL related Open Source project that you would like to 
!    develop and need project management resources such as mailing lists, forums,
!    bug tracking, and CVS, please feel free to create a new project.   
    </para>
  
    <para>
!    Secondly, many <productname>PostgreSQL</productname>-related projects are
!    still hosted at <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>. 
!    GBorg is the original external community developer site, and while it is 
!    currently closed to new projects in favor of PgFoundry, it still contains 
!    many active and relevant projects. There are other popular <productname>PostgreSQL</productname> 
!    related projects that are hosted independently as well at other community 
!    sites such as <ulink url="http://www.sf.net">SourceForge</ulink>. You should 
!    google if you don't find the project you are looking for.
    </para>
  
   <sect1 id="external-interfaces">
***************
*** 36,46 ****
    <para>
     <productname>PostgreSQL</productname> includes very few interfaces
     with the base distribution. <application>libpq</> is packaged because
!    it is the primary <application>C</> interface and many other
!    interfaces are built on top of it. <application>ecpg</> is packaged
!    because it is tied to the server-side grammar so is very dependent
!    on the database version. All the other interfaces are independent
!    projects and must be installed separately.
    </para>
  
    <para>
--- 41,50 ----
    <para>
     <productname>PostgreSQL</productname> includes very few interfaces
     with the base distribution. <application>libpq</> is packaged because
!    it is the primary dependecy of most interfaces available to PostgreSQL.
!    We also package <application>ecpg</> because it is tied to the 
!    server-side grammar. All other interfaces, such as PHP, Perl, Python,
!    and Ruby, are external projects.
    </para>
  
    <para>
***************
*** 52,115 ****
       <listitem>
        <para>
         This is the most common interface for <application>Windows</>
!        applications.
!       </para>
!      </listitem>
!     </varlistentry>
! 
!     <varlistentry>
!      <term>pgjdbc</term>
!      <listitem>
!       <para>
!        A <application>JDBC</> interface.
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>Npgsql</term>
       <listitem>
        <para>
!        <application>.Net</> interface for more recent
!        <application>Windows</> applications.
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>libpqxx</term>
       <listitem>
        <para>
!        A newer <application>C++</> interface.
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>libpq++</term>
       <listitem>
        <para>
!        An older <application>C++</> interface.
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>pgperl</term>
       <listitem>
        <para>
!        A <application>Perl</> interface with an <acronym>API</> similar
!        to <application>libpq</>.
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>DBD-Pg</term>
       <listitem>
        <para>
!        A <application>Perl</> interface that uses the
!        <acronym>DBD</>-standard <application>API</>.
        </para>
       </listitem>
      </varlistentry>
--- 56,112 ----
       <listitem>
        <para>
         This is the most common interface for <application>Windows</>
!        applications. <ulink url="http://odbc.postgresql.org/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>ODBCng</term>
       <listitem>
        <para>
!        Another ODBC driver for PostgreSQL. 
!        <ulink url="http://projects.commandprompt.com/public/odbcng/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>pgjdbc</term>
       <listitem>
        <para>
!        A <application>JDBC</> interface.
!        <ulink url="http://jdbc.postgresql.org/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>Npgsql</term>
       <listitem>
        <para>
!        <application>.Net</> interface for more recent <application>mono/C#</> applications.
!        <ulink url="http://pgfoundry.org/projects/npgsql/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>libpqxx</term>
       <listitem>
        <para>
!        A newer <application>C++</> interface.
!        <ulink url="http://thaiopensource.org/development/libpqxx/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>DBD::Pg</term>
       <listitem>
        <para>
!        A <application>Perl</> DBI driver for PostgreSQL.
!        <ulink url="http://search.cpan.org/dist/DBD-Pg/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
***************
*** 119,151 ****
       <listitem>
        <para>
         A newer version of the <application>Tcl</> interface.
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>pgtcl</term>
!      <listitem>
!       <para>
!        The original version of the <application>Tcl</> interface.
!       </para>
!      </listitem>
!     </varlistentry>
! 
!     <varlistentry>
!      <term>PyGreSQL</term>
       <listitem>
        <para>
!        A <application>Python</> interface library.
        </para>
       </listitem>
      </varlistentry>
- 
     </variablelist>
- 
-    All of these can be found at
-    <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
-    or <ulink url="http://pgfoundry.org"><productname>pgFoundry</></ulink>.
     </para>
  
   </sect1>
--- 116,136 ----
       <listitem>
        <para>
         A newer version of the <application>Tcl</> interface.
+        <ulink url="http://gborg.postgresql.org/project/pgtclng/projdisplay.php">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
  
      <varlistentry>
!      <term>Pyscopg</term>
       <listitem>
        <para>
!        A <application>Python</> interface library that is DB API 2.0 compliant.
!        <ulink url="http://www.initd.org/">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
     </variablelist>
     </para>
  
   </sect1>
***************
*** 175,182 ****
    <para>
     There are several administration tools available for
     <productname>PostgreSQL</>. The most popular is
!    <application>pgAdmin</>, and there are several commercially
!    available ones.
    </para> 
  
   </sect1>
--- 160,167 ----
    <para>
     There are several administration tools available for
     <productname>PostgreSQL</>. The most popular is
!    <application><ulink url="http://www.pgadmin.org/">pgAdmin III</ulink></>, 
!    and there are several commercially available ones as well.
    </para> 
  
   </sect1>