| the Apache XML site |
| Home |
| Development |

# Information for FOP Developers | print-friendly PDF
Introduction Development Lines Getting Involved Understand Apache Roles Understand FOP Development Tasks Understand FOP-related standards Review the Developer Documentation Understand FOP's Design Subscribe to the fop-dev Mailing List Subscribe to the fop-cvs Mailing List Download and Use the Developers' Code Using CVS Submitting Patches ### Introduction These pages contain information that should be helpful for those developing 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 FOP homepage. ### Development Lines There are currently three lines of development on the FOP product: The oldest is the one that releases are currently generated from, and is also called the "maintenance branch". Because of limitations in its design, the FOP committers decided to freeze new development on this branch, and are providing only bug fixes. This branch is tagged as "fop-0_20_2-maintain" in the CVS repository. The main development line is the future of FOP. It was spawned from the "maintenance" branch, but had to quickly be "broken" so that the needed redesign could be dropped into place. It is currently not as mature as the "maintenance" branch, but has far greater long-term prospects. It is also known as the "root" or "trunk" or "redesign". The "Alt Design" is exactly that: an alternative design approach. Because its efforts are largely complementary and parallel to the main development branch, and because it is expected to be merged at some point into the trunk, it is documented separately. The authors of this effort are currently in the process of merging their work into the trunk. Please note that patches for enhancements to the maintenance branch will generally not be considered. Bug fixes are welcome there, but new developers are strongly encouraged to apply their efforts to the trunk development line. Because there is a fair amount of common information between the maintenance and trunk development lines, we attempt to document them together, highlighting differences only where needed. ### Getting Involved #### Understand Apache Roles Review the Apache Project Roles and Responsibilities document for an understanding of the various roles of contributors within the community. #### 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. #### 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-dev Mailing List 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 page. 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. Review the archives at Mailing list ARChives (MARC) at the AIMS group (search). Subscribe by sending an email to fop-cvs-subscribe@xml.apache.org. #### 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. #### Submitting 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. Create a patch file for the differences to be applied to the existing code. Create a new bugzilla issue 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. |

Copyright © 1999-2003 The Apache Software Foundation. All rights reserved.