From: William Victor Mote Date: Tue, 15 Apr 2003 01:54:06 +0000 (+0000) Subject: Move fop-dev mailing list from the user docs to the dev docs, to reduce risk of cross... X-Git-Tag: Root_Temp_KnuthStylePageBreaking~1616 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=8cb6c38cb5993947fb7ce831c188af979dcb246a;p=xmlgraphics-fop.git Move fop-dev mailing list from the user docs to the dev docs, to reduce risk of cross-posting, and to reduce noise in the user section. Organizational changes to dev/index.xml. git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196265 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/src/documentation/content/xdocs/dev/index.xml b/src/documentation/content/xdocs/dev/index.xml index cfc932124..68dbef625 100644 --- a/src/documentation/content/xdocs/dev/index.xml +++ b/src/documentation/content/xdocs/dev/index.xml @@ -25,42 +25,96 @@ This certainly includes programmers, but may also include those contributing to
Getting Involved -

Review the Apache Project Roles and Responsibilities document for an understanding of the various roles of contributors within the community.

-

There are many different ways that you can help with FOP development. -The development of FOP and the related plans and tasks are discussed on the dev mailing list. -Users can help or get issues resolved by contributing information and examples to the developers. -

+
+ Understand Apache Roles +

Review the Apache Project Roles and Responsibilities document for an understanding of the various roles of contributors within the community.

+
- Get familiar with the FOP-related standards -

At the moment FOP is mainly a tool to render XSL-FO files to pdf. Therefore if you want to contribute to FOP you should become familiar with these standards. You can find links at Specifications.

+ Understand FOP Development Tasks +

There are many different ways that you can help with FOP development. The following is a non-exhaustive list of ways that non-programmers can help. Remember that an hour spent on the tasks below is an hour that a programmer can devote to fixing bugs or adding features instead:

+
    +
  • Answer questions on the fop-user mailing list.
    • +
  • Contribute examples that are useful to other users.
    • +
  • Contribute test cases.
    • +
  • Submit well-written feature requests.
    • +
  • Submit well-written bug reports.
    • +
  • Review open issues to see if you have any insight into them that might help a programmer solve the problem faster. Add comments and test cases as appropriate.
    • +
  • Test newly-closed issues to make sure they are truly closed.
    • +
  • Submit patches to the documentation.
    • +
+

Of course, we're glad to have programmers help as well. Here are some additional tasks that would require programming ability:

+
    +
  • Fixing bugs.
    • +
  • Implementing new features.
    • +
- FOP's Design + Understand FOP-related standards +

At the moment FOP is mainly a tool to render XSL-FO files to pdf. Therefore if you want to contribute to FOP you should become familiar with these standards. You can find links at Specifications.

+
+
+ Review the Developer Documentation +
+
+ Understand FOP's Design

The design for FOP is specified under the Design section. This is where the information on how FOP is developed and designed internally will be kept.

-
- Subscribe to the fop developers list -

You can subscribe to fop-dev@xml.apache.org by sending an email - to fop-dev-subscribe@xml.apache.org +

+ Subscribe to the fop-dev Mailing List +

+Use this forum to discuss topics related to FOP development, +including patch submissions, bug reports, and design issues. +

+
    +
  • +To review the archives, you have several options: +
      +
    • The Mailing list ARChives (MARC) at the AIMS group (search). +
      • +
    • +The Apache Eyebrowse archive (search, list by date, author, subject, or thread). +
      • +
    • +The Apache Mailing List archive. +
      • +
    +
    • +
  • Before posting questions to any list, see "General Information".
    • +
  • +See Apache XML Mailing Lists +for detailed subscription information. +
    • +
  • +To subscribe (digest only): Send email to fop-dev-digest-subscribe@xml.apache.org. +
    • +
  • +To subscribe fully: Send email to fop-dev-subscribe@xml.apache.org. +
    • +
  • +For standard help: Send email to fop-dev-help@xml.apache.org. +
    • +
  • +To unsubscribe: Send email to fop-dev-unsubscribe@xml.apache.org. +
    • +
+
+
+ Subscribe to the fop-cvs Mailing List +

When changes are committed to the code repository, a record of the diffs is emailed to the fop-cvs mailing list. FOP developers are encouraged to subscribe to this list because it helps in following the progress of the project.

-

Sending bug reports and feature requests to the list is a welcome and important contribution to - developing FOP.

-

Read also the archive - of the discussion list fop-dev to get an idea of the issues being discussed.

+
    +
  • Subscribe by sending an email to fop-cvs-subscribe@xml.apache.org.
    • +
- Look at the developer's code using cvs + Download and Use the Developers' Code Using CVS

Between releases the newest code can be accessed via cvs. To do this you need to install a cvs client on your computer, if it is not already there. An explanation how to connect to the FOP source repository can be found at http://xml.apache.org/cvs.html. An introduction into cvs and the cvs manual can be found in the reference library.

-

All changes to the code repository are sent to a special mailing list. After a cvs commit the diffs are automatically sent to this list. You can subscribe - to fop-cvs@xml.apache.org by sending an email to - fop-cvs-subscribe@xml.apache.org. If you want to contribute to the development of FOP you should subscribe, - because it is important that you follow changes being made.

Submitting Patches diff --git a/src/documentation/content/xdocs/resources.xml b/src/documentation/content/xdocs/resources.xml index 339c90778..a2a36fa04 100644 --- a/src/documentation/content/xdocs/resources.xml +++ b/src/documentation/content/xdocs/resources.xml @@ -61,45 +61,6 @@ To unsubscribe: Send email to - FOP Developer Mailing List -

-Use this forum to discuss topics related to FOP development, -including patch submissions, bug reports, and design issues. -

-
    -
  • -To review the archives, you have several options: -
      -
    • The Mailing list ARChives (MARC) at the AIMS group (search). -
      • -
    • -The Apache Eyebrowse archive (search, list by date, author, subject, or thread). -
      • -
    • -The Apache Mailing List archive. -
      • -
    -
    • -
  • Before posting questions to any list, see "General Information".
    • -
  • -See Apache XML Mailing Lists -for detailed subscription information. -
    • -
  • -To subscribe (digest only): Send email to fop-dev-digest-subscribe@xml.apache.org. -
    • -
  • -To subscribe fully: Send email to fop-dev-subscribe@xml.apache.org. -
    • -
  • -For standard help: Send email to fop-dev-help@xml.apache.org. -
    • -
  • -To unsubscribe: Send email to fop-dev-unsubscribe@xml.apache.org. -
    • -
-
XSL:FO Mailing List (at W3C)