From a7e9d3f37d5e9fba4b9acaa43e7c12b6d9a669ae Mon Sep 17 00:00:00 2001 From: Mike Hommey Date: Thu, 8 Jun 2006 10:59:26 +0200 Subject: Load /tmp/libxml2-2.6.26 into libxml2/branches/upstream/current. --- doc/help.html | 26 ++++++++++++-------------- 1 file changed, 12 insertions(+), 14 deletions(-) (limited to 'doc/help.html') diff --git a/doc/help.html b/doc/help.html index 5559007..a660a87 100644 --- a/doc/help.html +++ b/doc/help.html @@ -7,19 +7,17 @@ H1 {font-family: Verdana,Arial,Helvetica} H2 {font-family: Verdana,Arial,Helvetica} H3 {font-family: Verdana,Arial,Helvetica} A:link, A:visited, A:active { text-decoration: underline } -How to help
Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
Made with Libxml2 Logo

The XML C parser and toolkit of Gnome

How to help

Main Menu
Related links

You can help the project in various ways, the best thing to do first is to -subscribe to the mailing-list as explained before, check the archives and the Gnome bug -database:

  1. Provide patches when you find problems.
    2. -
  2. Provide the diffs when you port libxml2 to a new platform. They may not - be integrated in all cases but help pinpointing portability problems - and
    3. -
  3. Provide documentation fixes (either as patches to the code comments or - as HTML diffs).
    4. -
  4. Provide new documentations pieces (translations, examples, etc - ...).
    5. +How to help
    Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
    Made with Libxml2 Logo

    The XML C parser and toolkit of Gnome

    How to help

    Main Menu
    Related links

    You can help the project in various ways, the best thing to do first +istosubscribe to the mailing-list as explained before, check the archives and the Gnomebugdatabase:

    1. Provide patches when you find problems.
      2. +
    2. Provide the diffs when you port libxml2 to a new platform. They + maynotbe integrated in all cases but help pinpointing + portabilityproblemsand
      3. +
    3. Provide documentation fixes (either as patches to the code commentsoras + HTML diffs).
      4. +
    4. Provide new documentations pieces (translations, examples, etc...).
    5. Check the TODO file and try to close one of the items.
      6. -
    6. Take one of the points raised in the archive or the bug database and - provide a fix. Get in touch with me - before to avoid synchronization problems and check that the suggested - fix will fit in nicely :-)
      7. +
    7. Take one of the points raised in the archive or the bug + databaseandprovide a fix. Get in + touch withmebefore to avoid synchronization problems and check that + thesuggestedfix will fit in nicely :-)

    Daniel Veillard

    -- cgit v1.2.3