Title: Apache™ FOP Development: General Information $Revision: 1298724 $ # Introduction # {#intro} These pages contain information that should be helpful for those developing Apache™ FOP. This certainly includes programmers, but may also include those contributing to the project in other ways. For basic and user information on FOP, please visit the [Apache™ FOP homepage](http://xml.apache.org/fop) . # Development # {#lines} The main development happens on "FOP Trunk". The SVN repository URL for the trunk is:

`http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/` # Getting Involved # {#involved} ## Understand Apache Roles ## {#apache-roles} Review the [Apache Project Roles and Responsibilities](http://xml.apache.org/roles.html) document for an understanding of the various roles of contributors within the community. ## How you can help ## {#fop-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. ## Understand FOP-related standards ## {#fop-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](../resources.html#specs) . ## Review the Developer Documentation ## {#doc} ## Understand FOP's Design ## {#design} The design for FOP is specified under the [Design](design/index.html) section. This is where the information on how FOP is developed and designed internally will be kept. Another place where we write design documentation is the [FOP Wiki](http://wiki.apache.org/xmlgraphics-fop/DeveloperPages) . Our design documentation may not always be up to date! ## Subscribe to the fop-dev Mailing List ## {#mail-fop-dev} Use this forum to discuss topics related to FOP development, including patch submissions, bug reports, and design issues. Please *do not* use it for XML support, XSLT support, XSL-FO support, or even FOP support. Appropriate mailing lists for these topics can be found on the [FOP Mailing List](../maillist.html) page. - To review the archives, you have several options: - The [Apache Mailing List archive (mod_mbox)](http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/) . - The [Apache Mailing List archive (gzipped mbox files)](http://xmlgraphics.apache.org/mail/fop-dev/) . - The [Mailing list ARChives](http://marc.theaimsgroup.com/?l=fop-dev&r=1&w=2) (MARC) at the AIMS group (search). - [The Mail Archive](http://www.mail-archive.com/fop-dev%40xmlgraphics.apache.org/) . - The [GMANE](http://dir.gmane.org/gmane.text.xml.fop.devel) archive. - The [Nabble](http://www.nabble.com/FOP---Dev-f352.html) archive. - The [MarkMail](http://fop-dev.markmail.org) archive. - Before posting questions to any list, see " [General Information](../maillist.html#general) ". - See [Apache XML Graphics Mailing Lists](http://xmlgraphics.apache.org/mail.html) for detailed subscription information. - To subscribe (digest only): Send email to [fop-dev-digest-subscribe@xmlgraphics.apache.org](mailto:fop-dev-digest-subscribe@xmlgraphics.apache.org) . - To subscribe fully: Send email to [fop-dev-subscribe@xmlgraphics.apache.org](mailto:fop-dev-subscribe@xmlgraphics.apache.org) . - For standard help: Send email to [fop-dev-help@xmlgraphics.apache.org](mailto:fop-dev-help@xmlgraphics.apache.org) . - To unsubscribe: Send email to [fop-dev-unsubscribe@xmlgraphics.apache.org](mailto:fop-dev-unsubscribe@xmlgraphics.apache.org) . ## Subscribe to the fop-commits Mailing List ## {#mail-fop-cvs} 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. - To review the archives, you have several options: - The [Apache Mailing List archive (mod_mbox)](http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-commits/) . - The [Apache Mailing List archive (gzipped mbox files)](http://xmlgraphics.apache.org/mail/fop-commits/) . - The [Mailing list ARChives](http://marc.theaimsgroup.com/?l=fop-cvs&r=1&w=2) (MARC) at the AIMS group (search). - [The Mail Archive](http://www.mail-archive.com/fop-commits%40xmlgraphics.apache.org/) . - The [GMANE](http://dir.gmane.org/gmane.text.xml.fop.cvs) archive. - The [MarkMail](http://fop-commits.markmail.org) archive. - Subscribe by sending an email to [fop-commits-subscribe@xmlgraphics.apache.org](mailto:fop-commits-subscribe@xmlgraphics.apache.org) . ## Download and Use the Developers' Code Using Subversion ## {#dev-code} Between releases the newest code can be accessed via SVN. To do this you need to install a SVN 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://xmlgraphics.apache.org/repo.html](http://xmlgraphics.apache.org/repo.html) . More information can be found on the [Tools page](tools.html) . ## Submitting Patches ## {#patches} If you have useful changes to source code (bugfixes or enhancements), test files, or documentation that you would like to contribute to the project, please do the following: - If your changes include source code, make sure that it does not break FOP (i.e. make sure that FOP still compiles with your changes). - If your changes include test files, review the [Testing page](testing.html) . - [Create a patch file](tools.html#patches) for the differences to be applied to the existing code. - [Create a new bugzilla issue](../bugs.html#issues_new) for the patch. Include the text "[PATCH]" at the beginning of the description. Attach the patch file to the issue. One of the committers will test your patch and consider its implications for the project. They will then either commit it to the repository or explain on the issue why they did not. Depending on the work load and skill-sets of the various committers, it may take some time before a a submitted patch is addressed.