Joined: 16/04/2010 12:52:07
1. Posting guidelines
1.1 Before posting
Read the SpagoBI WIKI and search within it the answer to your problem, there is a good chance that you will find it . We expect that you have at least read the relevant sections in the SpagoBI WIKI before posting
If you can't find the answer in the SpagoBI WIKI, use the "search" functionality on the forum to look for your issue. You may find that your question has already been answered. We expect that you have at least searched the forum for a previous post.
Try to find an answer by inspection or experimentation
Try to find an answer by asking a skilled friend, if you are so lucky to have a friend skilled on SpagoBI of course
If you're a programmer, try to find an answer by reading the source code (the old school way)
1.2 While posting
Be sensitive in choosing where you ask your question:
- DO NOT cross post it to all SpagoBI's forums
- DO NOT post a personal e-mail to a SpagoBI team member
- DO NOT POST it multiple times
Be sure to include a brief description of your issue or question in the title of your thread. This will help other users to understand what you need avoid clicking on threads in which they have no interest. Examples of unacceptable thread titles:
- "What Should I Do?"
Examples of acceptable thread titles:
- "Schedule TALEND JOB SpagoBI 2.1"
- "SpagoBI 2.1 and postgreSQL"
- "Can't display JasperReport's chart"
Write in Standard English
Don't TYPE IN ALL CAPITALS ; this is read as shouting and considered rude
Describe your environment. If you need help, then the forum users need to know what environment is being used. This may be because what you are reporting may have already been fixed in a later build or release. At a minimum:
- SpagoBI server version
- Engine version (if the problem involve an engine)
Describe what you have done so far. The more details you provide the better. Doing this you will help the users that will answer to your question to save their time by narrowing the field of possible causes. At the same time doing this you will prove that you are able and willing to help in the process of developing the solution for your same problem and this is usually a very good start.
Describe the error you get and the log trace. If the error is reproducible give a step by step description of the ativities that generate it
Post only one topic per thread
1.3 After posting
Be patient. The support given on the forums is for free. We do our best to answer to all questions as soon as possible but there are no ensurance on response time. If you want a dedicated support with a clarly defined SLA (service level agreemnet) please check on our main web site the list of our commercial services
If you don't get a response after a while, then feel free to answear to your own message asking again if someone can help. In this way the message will be relocated at the top of the message list. Do this only one time per thread and only after sometime (a week at minimum). Do not repost the same message multiple time.
If the recommended solution has resolved your issue, then a simple thanks is always appreciated. It makes the solution provider feel that they've made a difference and are then more willing to help others. While grating you can also change the subject of the original message appending the tag SOLVED? to it
If while waiting for an answer you find the solution to your problem please post a notification message. If you find also the time to describe the solution you have found you can halp someother user that in the future will face your same problem and improve your KARMA as well
If while waiting for an answer you lose interst in the problem please post a notification mesage. Doing so you will avoid other users to wast their time answering
2. Replying guidelines
If it is clear that the original poster hasn't read the manual or searched the forum, then politely recommend that they read this sticky. If you're feeling kind then provide the link to the WIKI and mention the section number, or link to the forum topic that may resolve their question. Answer in a rude adn unpolite way (RTFM style) are unnacetable when the poster break rules for the first time. After that, if he or she continues to break these guidelines simply ignore him/her (Errare humanum est, perseverare autem diabolicum)
Don't Hijack other people's topics. If you have a new question, and it is not very closely related to the subject of the current topic, please post it in a new topic. Do not post your, somewhat/slightly/not at all related, question in someone else's topic. If you feel that your question is directly related to another topic, say that in your new topic, and link to the related topic
Be gentle. Problem-related stress can make people seem rude or stupid even when they're not
Be humble and honest; if you don't know for sure, say so! A wrong but authoritative-sounding answer is worse than none at all. Don't point anyone down a wrong path simply because it's fun to sound like an expert.