| 16 | | The {\emph ossie-discuss} mailing list and the \#ossie IRC channel on |
| 17 | | Freenode are probably the methods of discussing end-user problems and |
| 18 | | solutions. For development-oriented issues, Trac tickets and the {\emph |
| 19 | | ossie-dev} mailing list are best. See Section ~\ref{section:irc} for more |
| 20 | | information on the IRC channel and Section ~\ref{section:mailinglists} for |
| 21 | | details on the mailing lists. |
| | 16 | The {\it ossie-discuss} mailing list and the \#ossie IRC channel on Freenode are |
| | 17 | probably the methods of discussing and collaboratively solving end-user problems. |
| | 18 | For development-oriented issues, Trac tickets and the {\it ossie-dev} mailing |
| | 19 | list are probably best. See Section ~\ref{section:irc} for more information on |
| | 20 | the IRC channel and Section ~\ref{section:mailinglists} for details on the |
| | 21 | mailing lists. |
| 25 | | and really get involved is to help by fixing bugs or adding features. Other work |
| 26 | | such as writing documentation is also appreciated. They can generally be sent to |
| 27 | | us through Trac or the mailing list. For those interested in making continuing |
| 28 | | contributions, Subversion repository access may be available. |
| | 25 | and really get involved is submit patches that fix bugs or add features. |
| | 26 | Other work such as writing or revising documentation would also naturally be |
| | 27 | appreciated. Patches can generally be sent to us through Trac or the mailing |
| | 28 | list. Write access to the subversion repository can be given to contributers |
| | 29 | who have proven their reliability. |