[gnomeweb-wml] Update developers info

[Paolo Borelli <pborelli src gnome org>]

commit 687493e43289255da85eb4bfa91aebb82ad61108
Author: Paolo Borelli <porelli gnome org>
Date:   Sun May 3 16:05:17 2009 +0200

    Update developers info
---
 projects.gnome.org/gedit/developers.page |   98 +++++++++++++++++------------
 1 files changed, 57 insertions(+), 41 deletions(-)

diff --git a/projects.gnome.org/gedit/developers.page b/projects.gnome.org/gedit/developers.page
index af1b204..204c65e 100644
--- a/projects.gnome.org/gedit/developers.page
+++ b/projects.gnome.org/gedit/developers.page
@@ -2,46 +2,62 @@
 
 <h2>Developers informations</h2>
 
-<h4>Maintainer</h4>
-<p>The current maintainer of gedit is Paolo Maggi &lt;<a href="mailto:paolo (at) gnome.org">paolo (at) gnome.org</a>&gt;.</p>
-
-<h4>Mailing list and IRC</h4>
-
-<p>A <a href="http://mail.gnome.org/mailman/listinfo/gedit-list";>mailing list</a> [<a href="http://mail.gnome.org/archives/gedit-list";>Archives</a>] 
-is available to discuss developement of gedit itself, of plugins and for any question which regards gedit and its usage. <br />
-You may also join the #gedit channel on irc.gnome.org and have a chat with us.</p>
-
-<h4>Wiki</h4>
-<p>gedit has a <a href="http://live.gnome.org/Gedit";>wiki page</a> on the official GNOME wiki, where you can find useful information about current maintainance work and future developement plans.</p>
-
-<h4>SVN access</h4>
-<p>gedit svn repository is hosted on svn.gnome.org.</p>
-<p>You can get the code from GNOME svn with the following command:</p>
-<p>
-<tt>svn co http://svn.gnome.org/svn/gedit/trunk gedit</tt><br/>
-</p>
-
-Then to build enter the gedit directory and run the usual:
-
-<p>
-<tt>
-./autogen.sh<br/>
-make<br/>
-make install<br/>
-</tt>
-</p>
-
-<p>You can also browse the sources on-line using GNOME's <a href="http://svn.gnome.org/viewcvs/gedit/trunk";>ViewCVS</a> service.</p>
-
-<h4>Bugs and Feature Requests</h4>
-
-<p>gedit bugs are tracked in GNOME's <a href="http://bugzilla.gnome.org";>bugzilla</a>.
-Here is a <a href="http://bugzilla.gnome.org/buglist.cgi?product=gedit&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO";>list</a> of currently open issues.</p>
-
-<h4>Patches</h4>
-
-<p>You can submit patches to the <a href="http://mail.gnome.org/mailman/listinfo/gedit-list";>gedit mailing list</a> or in  <a href="http://bugzilla.gnome.org";>bugzilla</a>. </p>
-
-<br />
+    <h2><a name="Contributing">Contributing</a></h2>
+    <p>gedit development relies on voluntary contributions and everyone 
+       is invited to help.
+    </p>
+    <p>If you are interested in helping us to develop gedit, please contact the
+       <a href="http://git.gnome.org/cgit/gedit/tree/AUTHORS";>developers</a>
+       on <a href="#IRC">IRC</a> and/or
+       send a message to the gedit <a href="#MailingLists">mailing list</a> and offer your help.
+    </p>
+
+    <h2><a name="Repository">Code Repository</a></h2>
+    <p>gedit is hosted on the <a href="http://git.gnome.org";>GNOME
+       Git repository</a> in the <a href="http://git.gnome.org/cgit/gedit";>gedit</a>
+       module.</p>
+
+    <h2><a name="BugReporting">Bug reporting</a></h2>
+    <p>Bugs should be reported to the <a href="http://bugzilla.gnome.org";>GNOME
+    bug tracking system</a>, product <a href="http://bugzilla.gnome.org/browse.cgi?product=gedit";>gedit</a>.</p>
+
+    <p>You will need an email address to register (if you haven't already) 
+       before you can use the system to file a new bug report.</p>
+
+    <p>There are <a href="http://bugzilla.gnome.org/page.cgi?id=bug-writing.html";>guidelines</a>
+       for reporting new bugs, try to make sure you follow them, it helps us help
+       you much more effectively. The use of 
+       <a href="http://bugzilla.gnome.org/describekeywords.cgi";>keywords</a> also
+       helps us prioritize bugs.</p>
+
+    <h2><a name="Patches">Patches</a></h2>
+    <p>Patches should be submitted to the <a href="http://bugzilla.gnome.org";>bug tracking system</a>.</p>
+    
+    <p>If the patch fixes a known bug, add the patch as an attachment to the corresponding bug
+       report. Otherwise, enter a new bug report that describes the problem the patch
+       fixes, and attach it to that bug report.</p>
+
+    <p>Patches should be generated using the <tt>git format-patch</tt> command and should include 
+       a descriptive commit message. See the
+       <a href="http://git.gnome.org/cgit/gedit/tree/HACKING";>HACKING</a> file for more
+       detailed guidelines.
+    </p>
+
+    <h2><a name="MailingLists">Mailing lists</a></h2>
+    <p>You can subscribe to the GtkSourceView mailing list, or change your 
+        existing subscription, visiting the <a href="http://mail.gnome.org/mailman/listinfo/gnome-devtools";>gnome-devtools info page</a>.</p>
+
+    <p>To post a message to all the list members, send an email to
+       <a href="mailto:gedit-lits gnome org">gedit-list (at) gnome org</a>.</p>
+
+    <p> To see the collection of prior postings to the list, visit the 
+        <a href="http://mail.gnome.org/archives/gedit-list/";>gedit-list archives</a>.</p>
+
+    <h2><a name="IRC">Internet Relay Chat</a></h2>
+    <p>You can find the developers on <b>#gedit</b> channel at <b>irc.gnome.org</b>.</p>
+
+    <h2><a name="Wiki">Wiki</a></h2>
+    <p>We have a Wiki for drafting, designing and proposing gedit
+       development available at <a href="http://live.gnome.org/Gedit";>http://live.gnome.org/Gedit</a>.</p>
 
 </page>