community.xml 2.6 KB

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