Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41394

Remove donate button on monitoring page

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Won't Do
    • Component/s: monitoring-plugin
    • Labels:
      None
    • Environment:
      We host a Jenkins server for clients. Our Jenkins server uses the monitoring plugin.
    • Similar Issues:

      Description

      It is not appropriate to have a donate button for the plugin shown to our clients. Remove the donate button from the monitoring page.

      May I suggest instead that you place a Donate link on the plugin help page in Jenkins.org

        Attachments

          Activity

          Hide
          evernat evernat added a comment - - edited

          Hi Ralph,

          The Donate button goes to the donate page:
          https://github.com/javamelody/javamelody/wiki/Donate

          As you can see in that page, donations are not many.
          But they are helpful to pay for backup hardware and for hosting (javamelody.org/stats and demo).
          The clients finding the hosted jenkins server, your job and this plugin useful don't pay you for a work well done?

          Do you know that all that work on the plugin and on javamelody was done for free (like in zero salary involved), except a few dollars in donations? I don't think that it is ethical to remove the donate button. When you go to church or to charities, you don't ask to hide the basket to give money I suppose? (In your country I don't know, but in France there is a basket in churches.)

          That said, you can submit pull requests for bugs and enhancements:
          https://github.com/javamelody/javamelody/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement

          https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20component%20%3D%20monitoring-plugin

          • Emeric
          Show
          evernat evernat added a comment - - edited Hi Ralph, The Donate button goes to the donate page: https://github.com/javamelody/javamelody/wiki/Donate As you can see in that page, donations are not many. But they are helpful to pay for backup hardware and for hosting (javamelody.org/stats and demo). The clients finding the hosted jenkins server, your job and this plugin useful don't pay you for a work well done? Do you know that all that work on the plugin and on javamelody was done for free (like in zero salary involved), except a few dollars in donations? I don't think that it is ethical to remove the donate button. When you go to church or to charities, you don't ask to hide the basket to give money I suppose? (In your country I don't know, but in France there is a basket in churches.) That said, you can submit pull requests for bugs and enhancements: https://github.com/javamelody/javamelody/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20component%20%3D%20monitoring-plugin Emeric
          Hide
          eaglet3d Ralph Navarro added a comment -

          Hi Emeric,

          I see where you are coming from. However, when you go to church, you know you are in a church and where the money is being donated to. In the case of a plugin page, is the money going to only the plugin? What if the landlord of the church wanted to take donations for covering the maintenance on the church grounds? In other words, we may want to take donations for supporting the hardware that runs this Jenkins instance with your plugin. Or maybe Jenkins may want to add a button to donate to Jenkins.

          What do you think about making the donate button more descriptive so that a donor knows what they are donating to before clicking on the button. For example, a button name of "Donate to monitoring-plugin" would avoid confusion.

          Show
          eaglet3d Ralph Navarro added a comment - Hi Emeric, I see where you are coming from. However, when you go to church, you know you are in a church and where the money is being donated to. In the case of a plugin page, is the money going to only the plugin? What if the landlord of the church wanted to take donations for covering the maintenance on the church grounds? In other words, we may want to take donations for supporting the hardware that runs this Jenkins instance with your plugin. Or maybe Jenkins may want to add a button to donate to Jenkins. What do you think about making the donate button more descriptive so that a donor knows what they are donating to before clicking on the button. For example, a button name of "Donate to monitoring-plugin" would avoid confusion.
          Hide
          evernat evernat added a comment -

          The button is displayed in the javamelody monitoring page.
          So I think it is clear enough that donations goes for supporting javamelody and/or the monitoring plugin (that's the same basket).
          Moreover, clicking the button goes to https://github.com/javamelody/javamelody/wiki/Donate which clarifies more.

          (As a side note, the church was just an example. I prefer to not have any religion, like many people in inland France for historical reasons.)

          Show
          evernat evernat added a comment - The button is displayed in the javamelody monitoring page. So I think it is clear enough that donations goes for supporting javamelody and/or the monitoring plugin (that's the same basket). Moreover, clicking the button goes to https://github.com/javamelody/javamelody/wiki/Donate which clarifies more. (As a side note, the church was just an example. I prefer to not have any religion, like many people in inland France for historical reasons.)

            People

            • Assignee:
              evernat evernat
              Reporter:
              eaglet3d Ralph Navarro
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: