community.xml 2.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. <chapter xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="community"
  2. xmlns:xlink="http://www.w3.org/1999/xlink">
  3. <info>
  4. <title>Spring Security Community</title>
  5. </info>
  6. <section xml:id="jira">
  7. <info>
  8. <title>Issue Tracking</title>
  9. </info>
  10. <para>Spring Security uses JIRA to manage bug reports and enhancement requests. If you find
  11. a bug, please log a report using JIRA. Do not log it on the support forum, mailing list
  12. or by emailing the project's developers. Such approaches are ad-hoc and we prefer to
  13. manage bugs using a more formal process.</para>
  14. <para>If possible, in your issue report please provide a JUnit test that demonstrates any
  15. incorrect behaviour. Or, better yet, provide a patch that corrects the issue. Similarly,
  16. enhancements are welcome to be logged in the issue tracker, although we only accept
  17. enhancement requests if you include corresponding unit tests. This is necessary to
  18. ensure project test coverage is adequately maintained.</para>
  19. <para>You can access the issue tracker at <link
  20. xlink:href="http://jira.springsource.org/browse/SEC"
  21. >http://jira.springsource.org/browse/SEC</link>. </para>
  22. </section>
  23. <section xml:id="becoming-involved">
  24. <info>
  25. <title>Becoming Involved</title>
  26. </info>
  27. <para>We welcome your involvement in the Spring Security project. There are many ways of
  28. contributing, including reading the forum and responding to questions from other people,
  29. writing new code, improving existing code, assisting with documentation, developing
  30. samples or tutorials, or simply making suggestions.</para>
  31. <!-- TODO: Not currently there on SSec 2.0
  32. <para>Please read our project policies web page that is available on
  33. Spring Security home page. This explains the path to become a
  34. committer, and the administration approaches we use within the
  35. project.</para>
  36. -->
  37. </section>
  38. <section xml:id="further-info">
  39. <info>
  40. <title>Further Information</title>
  41. </info>
  42. <para>Questions and comments on Spring Security are welcome. You can use the Spring
  43. Community Forum web site at <uri xlink:href="http://forum.springsource.org"
  44. >http://forum.springsource.org</uri> to discuss Spring Security with other users of the
  45. framework. Remember to use JIRA for bug reports, as explained above.</para>
  46. </section>
  47. </chapter>