Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

team.xml 9.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136
  1. <?xml version="1.0" standalone="no"?>
  2. <!--
  3. Licensed to the Apache Software Foundation (ASF) under one or more
  4. contributor license agreements. See the NOTICE file distributed with
  5. this work for additional information regarding copyright ownership.
  6. The ASF licenses this file to You under the Apache License, Version 2.0
  7. (the "License"); you may not use this file except in compliance with
  8. the License. You may obtain a copy of the License at
  9. http://www.apache.org/licenses/LICENSE-2.0
  10. Unless required by applicable law or agreed to in writing, software
  11. distributed under the License is distributed on an "AS IS" BASIS,
  12. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  13. See the License for the specific language governing permissions and
  14. limitations under the License.
  15. -->
  16. <!-- $Id$ -->
  17. <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
  18. <document>
  19. <header>
  20. <title>FOP: Development Team</title>
  21. <version>$Revision$</version>
  22. </header>
  23. <body>
  24. <p>
  25. All lists on this page are in alphabetical order. Some of them may be incomplete.
  26. If you know of an error or omission, please send a message to the
  27. <link href="mailto:fop-dev@xmlgraphics.apache.org">fop-dev</link> mailing list.</p>
  28. <section id="commit-active">
  29. <title>Active Committers</title>
  30. <note label="Important">Please don't write to any developer directly if you need help on using FOP. Only if you submit questions to the <link href="maillist.html#fop-user">FOP User Mailing List</link> will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.</note>
  31. <ul>
  32. <li id="mb"><link href="mailto:max AT berger DOT name">Max Berger</link> (MB) is currently a
  33. PostDoc pursuing an academic career in computer science. His main interest in FOP is to
  34. improve the DocBook to PDF tool-chain to produce high quality output, while still
  35. conforming to given style-guides. See his <link href="http://max.berger.name">home
  36. page</link> for more information.</li>
  37. <li id="cb"><link href="mailto:bowditch_chris@hotmail.com">Chris Bowditch</link> (CB)
  38. is a Java/VB Programmer from England.</li>
  39. <li id="jb"><link href="mailto:jay@bryantcs.com">Jay Bryant</link> (JB) is a
  40. freelance information architect in Austin, TX.</li>
  41. <li id="ac"><link href="mailto:acumiskey@apache.org">Adrian Cumiskey</link> (AC),
  42. is a Java and Perl Programmer from St Albans, United Kingdom.</li>
  43. <li id="ad"><link href="mailto:adelmelle@apache.org">Andreas Delmelle</link> (AD)</li>
  44. <!-- Luca prefers the mail address with "AT", to stop spam, etc. -->
  45. <li id="lf"><link href="mailto:lfurini AT cs.unibo.it">Luca Furini</link> (LF)
  46. is a student of Computer Studies at the University of Bologna (Italy)</li>
  47. <li id="cg"><link href="mailto:chrisg@apache.org">Christian Geisert</link> (CG)
  48. is a software engineer from Stutensee, Germany. He is working at
  49. <fork href="http://www.isu-gmbh.de">ISU GmbH</fork>, a provider of ERP solutions,
  50. where amongst lots of other things he is using FOP to produce nice looking
  51. business documents like order confirmations, quotes, invoices etc.
  52. </li>
  53. <li id="vh"><link href="mailto:vhennebert@apache.org">Vincent Hennebert</link>
  54. (VH), a Java developer from France; with an interest in typography, and in using
  55. Fop as a pdf renderer for book-like documents.</li>
  56. <li id="cl"><link href="mailto:clay@apache.org">Clay Leeds</link> (CL)
  57. is a web/WAP/Palm developer from Laguna Beach, California, USA. A
  58. recent XML/XSL-FO convert, he has been nit-picking FAQs &amp; assorted web
  59. pages since his first webmaster position @brain.com in 1996. Most
  60. important creation? He&apos;s got a couple of cool kids.</li>
  61. <li id="mm"><link href="mailto:manuel@apache.org">Manuel Mall</link> (MM)
  62. is an independant software engineer resident in Perth, Australia. Born a long time
  63. ago in Germany he has been involved in Software Engineering (Informatik) since the
  64. early 70's. Over the last years he has used FOP very successfully in commercial
  65. projects for his customers (currently generating roughly 15000 PDF files each
  66. working day through FOP) and has decided to put some effort back into FOP to
  67. make it even better.
  68. </li>
  69. <li id="jm"><link href="mailto:jeremias@apache.org">Jeremias M&#x00E4;rki</link> (JM)
  70. is an independent software engineer and consultant from Lucerne, Switzerland. He's also
  71. the creator of <fork href="http://barcode4j.sourceforge.net">Barcode4J</fork>.
  72. See his <fork href="http://www.jeremias-maerki.ch">home page</fork> for more information
  73. about him.
  74. </li>
  75. <li id="sp"><link href="mailto:spepping@apache.org">Simon Pepping</link> (SP) came to FOP
  76. from the TeX/LaTeX world. See his <fork href="http://www.leverkruid.eu">home
  77. page</fork> for some of his private projects.</li>
  78. <li id="jp"><link href="mailto:pietsch@apache.org">J&#x00F6;rg Pietschmann</link> (JP)</li>
  79. <li id="mb"><link href="mailto:max AT berger DOT name">Max Berger</link> (MB) is currently a
  80. PostDoc pursuing an academic career in computer science. His main interest in FOP is to
  81. improve the DocBook to PDF tool-chain to produce high quality output, while still
  82. conforming to given style-guides. See his <link href="http://max.berger.name">home
  83. page</link> for more information.</li>
  84. </ul>
  85. </section>
  86. <section id="contribute-active">
  87. <title>Active Contributors</title>
  88. <ul>
  89. <li id="lm">Louis Masters</li>
  90. <li id="mn">Manoj Nair, Currently consulting for Sony Pictures Entertainment in Los Angeles, CA USA. Previously he worked with Java &amp; related technologies specializing in developing n-tier Web applications.</li>
  91. <li id="rr"><link href="mailto:renaud.richardet AT gmail DOT com">Renaud Richardet</link> (RR)
  92. is a Java Programmer interested in XML technologies. See his
  93. <fork href="http://www.oslutions.com">home page</fork> for more information about him.</li>
  94. <li id="ps"><link href="mailto:pascal DOT sancho AT takoma DOT fr">Pascal
  95. Sancho</link> works on software solutions for rendering various
  96. kinds of documents on various output targets. He's more specifically
  97. taking care of PDF generation with FOP.</li>
  98. <li id="ls">Luke Shannon, Java Programmer, Toronto, Canada</li>
  99. </ul>
  100. </section>
  101. <section id="founder">
  102. <title>Founder</title>
  103. <p>FOP was originally created and donated to the Apache Software Foundation by <link href="mailto:jtauber@jtauber.com">James Tauber</link>.
  104. Information about him can be found at <fork href="http://www.jtauber.com">his website</fork>.</p>
  105. </section>
  106. <section id="commit-inactive">
  107. <title>Inactive Committers</title>
  108. <ul>
  109. <li id="fb"><link href="mailto:bckfnn@worldonline.dk">Finn Bock</link> (FB)</li>
  110. <li id="kc"><link href="mailto:kellyc@apache.org">Kelly Campbell</link></li>
  111. <li id="sc"><link href="mailto:gears@apache.org">Steven Coffman</link></li>
  112. <li id="bd"><link href="mailto:bdelacretaz@apache.org">Bertrand Delacretaz</link></li>
  113. <li id="te"><link href="mailto:tore@apache.org">Tore Engvig</link></li>
  114. <li id="sg"><link href="mailto:stanislav@apache.org">Stanislav Gorkhover</link></li>
  115. <li id="ph"><link href="mailto:pherweg@web.de">Peter Herweg</link> (PH)<!-- is helping to
  116. integrate the jfor project's RTF support into the upcoming FOP 1.0 version.
  117. Born in 1978, he has been serving as an application developer for a small
  118. industrial company in Germany since 1999.--></li>
  119. <li id="fj"><link href="mailto:fotis@apache.org">Fotis Jannidis</link></li>
  120. <li id="kl"><link href="mailto:klease@apache.org">Karen Lease</link></li>
  121. <li id="kll"><link href="mailto:keiron@apache.org">Keiron Liddle</link></li>
  122. <li id="gm"><link href="mailto:gmazza@apache.org">Glen Mazza</link></li>
  123. <li id="wvm"><link href="mailto:vmote@apache.org">Victor Mote</link></li>
  124. <li id="jn"><link href="mailto:jordan@apache.org">Jordan Naftolin</link></li>
  125. <li id="as"><link href="mailto:arved@apache.org">Arved Sandstrom</link></li>
  126. <li id="es"><link href="mailto:eschaeffer@apache.org">Eric Schaeffer</link></li>
  127. <li id="ot"><link href="mailto:olegt@apache.org">Oleg Tkachenko</link> (OT)</li>
  128. <li id="aw"><link href="mailto:artw@apache.org">Art Welch</link></li>
  129. <li id="pbw"><link href="mailto:pbwest@apache.org">Peter B. West</link></li>
  130. </ul>
  131. </section>
  132. </body>
  133. </document>