• Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • core

      It has been pointed out multiple times that some of the terminologies in Jenkins have been confusing especially for new users. 2.0 is a great opportunity to take a fresh look on the terminology and try to sort them out.

      This is a blanket ticket to track what we are taking on, what are rejected, and what are pushed out of scope.

      See the linked tickets for individual proposed items.

      This epic is likely the one that drives most bikeshedding. So inputs are welcome, but I suspect at some point we'd make a decision and stick with it.

          [JENKINS-31095] 2.0: Jenkins terminology sweep

          Patrick Wolf added a comment -

          ci_jenkinsci_org Should we make this an epic and make the related tickets stories under this epic?

          Patrick Wolf added a comment - ci_jenkinsci_org Should we make this an epic and make the related tickets stories under this epic?

          Liam Newman added a comment -

          ci_jenkinsci_org Would you object to us doing as Patrick suggested?
          Tracking high level stories linked to this as an epic, with tasks and issues linked to the appropriate stories, will be easier to understand and summarize.

          Liam Newman added a comment - ci_jenkinsci_org Would you object to us doing as Patrick suggested? Tracking high level stories linked to this as an epic, with tasks and issues linked to the appropriate stories, will be easier to understand and summarize.

          Nik Reiman added a comment -

          Has there been any overall progress on this issue? It seems that most (if not all?) of the sub-issues haven't been touched in years.

          My company is doing a terminology sweep and Jenkins is included in this effort. We'd really appreciate to see consistent and accurate terminology reach Jenkins one day.

          Nik Reiman added a comment - Has there been any overall progress on this issue? It seems that most (if not all?) of the sub-issues haven't been touched in years. My company is doing a terminology sweep and Jenkins is included in this effort. We'd really appreciate to see consistent and accurate terminology reach Jenkins one day.

          Daniel Beck added a comment -

          nre_ableton Feel free to submit pull requests for any occurrences of offensive terms you're still seeing, especially when it's in documentation, localizable/localized UI, or log messages. (Changing internal class and field names is typically a breaking change, depending on component, so these need to be done with care.)

          With the "long tail" of plugins I doubt we'll get done any time soon when it's just the usual contributors working in this area.

          Daniel Beck added a comment - nre_ableton Feel free to submit pull requests for any occurrences of offensive terms you're still seeing, especially when it's in documentation, localizable/localized UI, or log messages. (Changing internal class and field names is typically a breaking change, depending on component, so these need to be done with care.) With the "long tail" of plugins I doubt we'll get done any time soon when it's just the usual contributors working in this area.

          Nate Bunton added a comment -

          Our company is also looking to do a terminology sweep, this would be helpful.

          Nate Bunton added a comment - Our company is also looking to do a terminology sweep, this would be helpful.

            kohsuke Kohsuke Kawaguchi
            kohsuke Kohsuke Kawaguchi
            Votes:
            4 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: