Dear OpenOffice.org community, This is a repeat of the monthly reminder of important things to know about the dev@documentation.openoffice.org and/or the [EMAIL PROTECTED] mailing lists. We, the project leads of the OpenOffice.org Documentation project, would like to give you some general information to help you with your questions, suggestions and commnents.
*** ==================================================================== *** Contents *** -------------------------------------------------------------------- 1. Appropriate Mailing List 2. Document templates and Style Guide 3. Form of your Messages 4. Support Questions 5. Reporting Defects *** ==================================================================== *** 1. Appropriate Mailing List *** -------------------------------------------------------------------- Not all questions are strictly documentation issues. Please find the most appropriate mailing list for your question. You can find the mailing lists on the Documentation project page. The list of the various mailing lists can be found on http://tinyurl.com/2orcut. *** ==================================================================== *** 2. Document templates and Style Guide *** -------------------------------------------------------------------- Remember, this is a list of volunteers, not a support forum. We like to help you, but we cannot do the footwork for you. The style guide and template can be found here: http://tinyurl.com/34mkay Please note the online help lists. *** ==================================================================== *** 3. Form of your Messages *** -------------------------------------------------------------------- Please use an appropriate form for your messages: - quote as much as is necessary to make context understandable, NOT more - do NOT put a full quote below your message - do NOT use HTML mails - do NOT attach documents - do NOT ask NEW questions in reply to existing threads By breaking these rules, do not wonder if your message remains unanswered, most likely even unseen due to mail filters. If you have additional data, like a document or a longer source code, please provide us a link where we can download these. You might upload such documents to the ProjectUpload repository under Documents & files: http://tinyurl.com/344cgl As far as I know, everybody can do that, you might need an OpenOffice.org account. As the responsible project lead, I just have to approve the files to get published. But keep in mind: the more a volunteer has to read the longer it takes to publish. *** ==================================================================== *** 4. Support Questions *** -------------------------------------------------------------------- Please keep in mind that we writers cannot always answer specific questions or even implement features for you. This is NOT a support forum in the sense of guaranteed help. If we have a solution in mind, we will help you. But if it costs us too much time, and it is a specific problem, we might not be able to spend the time on your issue. On the other hand, we try to answer all questions. And we need the support of other community members. But even as somebody who has only questions yet, you can already contribute to the Documentation project. If you had a question or suggestion and it was answered to your satisfaction it would be great if you post a summary to the list dev@documentation.openoffice.org This avoids having to answer the same questions over and over again. Thanks for your contribution! IMPORTANT: Please avoid sending mails personally to the project leads, unless you are explicitly asked to do so. We do not offer direct support by personal email. *** ==================================================================== *** 5. Reporting Defects *** -------------------------------------------------------------------- If you are pretty sure that you found a defect in a document, please file an issue with Issue Tracker: http://qa.openoffice.org/issue_handling/project_issues.html Some hints for reporting defects: (1) Be sure to give specific and unambiguous information on which document the defect is in. When possible, the filename is better than the document's title (giving both is even better, as a cross-check), and a direct link to the file is best. (While this may not be so easy for reporting defects in Help, providing as much detail as possible will assist the on-line help team to locate the defect.) (2) If the defect is in one of the documents produced by OOoAuthors, please report it to the OOoAuthors list, [EMAIL PROTECTED], instead of using Issue Tracker. All OOoAuthors documents have the list address on the copyright page (under Feedback). If you do use Issue Tracker for defects in OOoAuthors docs, please assign the issue to jeanweber. NOTE: If you choose the wrong project and/or component/subcomponent, your issue might be delayed. Please do not misuse Issue Tracker as a support tool. It is not and your issue will simply be rejected. If you want to report bugs or change requests or use special features of the OpenOffice.org websites, you need an account. You can apply for this here: http://www.openoffice.org/servlets/Join -- PLEASE KEEP MESSAGES ON THE LIST. OpenOffice.org Documentation Co-Lead http://documentation.openoffice.org/
smime.p7s
Description: S/MIME cryptographic signature