[Logo] SpagoWorld Forums
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing  
[Groups] Back to home page  [Moderation Log] Moderation Log   [Register] Register /  [Login] Login 
Messages posted by: cazzin
Forum Index » Profile for cazzin » Messages posted by cazzin
Author Message
Dear all,
I'm sorry for everything raised doubts about the SpagoBI present and future.
Last year was a great year for us, and we made some internal changes to be ready for new challanges.
We have now new SpagoBI Labs in Belgrado and Rome, and we enlarged our consultancy capabilities with new data scientists into the team.
We also worked to make SpagoBI available in the cloud (it is already available on Azure), even working with Canonical (SpagoBI is now a charm of Juju) and FIWARE (SpagoBI is a GE of the FIWARE platform now).
So, the answer is YES, SpagoBI is live and the 5.2 version will be released in February with interesting novelties such as:
- Metamodel lifecycle management
- new data sets (ckan, rest, etc)
- olap improvements
Engineering confirms the engagement on SpagoBI, that is and remains 100% open source software.
The roadmap for 2016 will be available early in February, but I can say that this is the year of a new main release (6.0), after the summer: that means great changes and, as you know, relevant changes take time to be ready
Sorry for our delay in communication and thanks for this solicitation.

Grazia Cazzin
The KPI engine doesn't use Highchart. It uses extJs to display kpi trends and a simple JS chart for meter.

Grazia
Dear users,
we are currently managing a periodical check of SpagoBI licensing compliance and the results will be available soon, in the next SpagoBI release.
It will include a detailed list of licenses of third parties libraries used by SpagoBI suite: stay tuned with upcoming SpagoBI communications.
All third party libraries currently used by SpagoBI are open source, except of HighChart: therefore, you can use SpagoBI suite as an entirely open source suite released under LGPL license.
Referring to HighCart, it is released under a CC by-nc license that is not OSI approved. As a consequence, we are making some updates:
- in last SpagoBI 3.4 releases you have a new chart engine based on ext-JS that is SpagoBI compatible: you can use this one as open source
- also in the workseet engine you can now use both extJS and HighChart graphics depending on your configuration: you can configure the worksheet in order to use only ext-JS graphics
- next SpagoBI release will not include the HC chart engine in the standard distribution; it will be available only as an option.
Finally, the use of Highcharts JS code is allowed for non-commercial purposes: this means that you can freely use the SpagoBI Hchart engine based on Highchart JS for your personal use.
If you use the SpagoBI Hchart engine based on Highchart JS for commercial purposes you must buy an Highsoft commercial license.

Grazia Cazzin
Dear users,
we have updated SpagoBI license webpage (http://www.spagoworld.org/xwiki/bin/view/SpagoBI/Licenses) and detailed the licensing terms for each SpagoBI engine included in the standard distribution (please refer to the all-in-one package, <external-tool>.LICENCE.txt file available in each webapp). Have a look also at the COPYING.LESSER file included in the all-in-one-package.

The general rule is:
- every SpagoBI original code is released under the LGPL, either 2.1 version of the license or any later version
- each engine integrating external tool maintains the attendant license of the specific tool.

This doesn't mean that the licence of any third-party tool allows the free use of the software for any purpose. You must identify the SpagoBI components compatible with your goals also from the licensing point of view.

Referring to Highchart, we have recently faced the issue with Highsoft team in order to clarify their initial permission to use their software within the HChart engine of SpagoBI suite. As a result, they explained that any usage of HChart software by commercial companies has to be covered by their commercial license.
Briefly:
- everyone can freely use SpagoBI Hcart engine based on Highchart JS for his/her personal use
- any use of SpagoBI Hcart engine for commercial purposes (including usage by a commercial company) requires the purchase of a Higchart commercial license.
Nevertheless, anyone can use the other SpagoBI chart engine based on JFreeChart.

In order to confirm our steady path towards a full FLOSS adoption, I've the opportunity to inform you that next February, within SpagoBI 3.4 version, we'll release a new and totally free-to-use chart engine, including the same Hchart engine functionalities.
Thanks for your advices, we are very pleased to grow taking the cues coming from the community.

Grazia Cazzin

Dear users,
I appreciate your advice, we will modify our website soon (http://www.spagoworld.org/xwiki/bin/view/SpagoBI/Licenses), better explaining the licences each engine has and how it can be used.
See you soon
Grazia
Dear users,
the whole SpagoBI code is released under the LGPL licence, so no problem at all with that.
For the engines that use external libraries/tools, those maintain their original licence and all of them enable the usage in production environment.
So, don't worry, you can use it.
Grazia Cazzin
Dear user,
SpagoBI is the only 100% open source business intelligence platform, released through a single stable version. No enterprise or professional edition at all.
Commercial services are related to support, training and professional services with no lock-in for users.
This allows us to use Highcharts as "free for non-profit projects". It's related to software itself: anyone can study, use, modify, distribute it just corresponding to the open source licensing provisions.
Referring to legal matters we use to be very careful: we asked explicit use permission to Highsoft and they allowed us to do it (we recorded this in our files)
Thank you for your question
Grazia Cazzin
Hi all,
following the Arod's proposal, we've created many forums, one for each main analytical area covered by one or more SpagoBI engine. Please, post you message in the right forum.

Grazia
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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  • 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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  • 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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  • 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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  • 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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  • 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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  • 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:
    - "Help!"
    - "Problem"
    - "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:
    - OS
    - 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.
  •  
    Forum Index » Profile for cazzin » Messages posted by cazzin
    Go to:   
    Powered by JForum 2.1.9 © JForum Team