Announcement

Collapse
No announcement yet.

IBM Clarifies Stance On Developers Working On Open-Source Projects In Off-Hours

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • IBM Clarifies Stance On Developers Working On Open-Source Projects In Off-Hours

    Phoronix: IBM Clarifies Stance On Developers Working On Open-Source Projects In Off-Hours

    Earlier this week was a surprising Linux kernel networking commit that removed an IBM engineer as one of the driver maintainers for the IBM Power SR-IOV Virtual NIC driver. Seemingly at issue with this VNIC driver work was the developer using his personal email address in working on the driver in his off-hours. IBM has now clarified their stance on such work...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    So, is the developer reinstated on the project? Has the manager that caused the issue been "retrained"?

    Comment


    • #3
      As expected then. IBM clarified rather quickly and the overzealous manager needs to learn some social skills...

      Comment


      • #4
        Originally posted by macemoneta View Post
        So, is the developer reinstated on the project? Has the manager that caused the issue been "retrained"?
        I dont think he was ever prevented from contributing. He was told to use his IBM ID when contributing.

        It may have something to do with SLAs and support contracts. I know nothing of the field, but the manager may have wanted IBM's role acknowledged/recorded. (If a paying customer requires IBM to fix something but an independent ID is used to fix it, do IBM get paid?)

        Comment


        • #5
          Originally posted by macemoneta View Post
          So, is the developer reinstated on the project? Has the manager that caused the issue been "retrained"?
          As an IBM manager, you are not allowed to discourage other IBM employees from doing work in any way. You are not allowed to make our reputation plummet and discourage our employees to work. You are a honest manager 100% of the time. Please remove yourself completely from the company. I grant you a 1 time exception on IBM to make this change.
          Last edited by tildearrow; 22 April 2021, 01:54 PM.

          Comment


          • #6
            Shit trying to save face.

            Comment


            • #7
              Originally posted by tildearrow

              Well, that's tedious and takes time. Nobody wants to be switching between accounts just to make a contribution in non-work time.
              If the contribution is useful, why does that even matter?
              Maybe you should ask the employee that, because originally he had the IBM account in before he felt the need to switch over to his personal account for some reason. It apparently mattered to him?

              Comment


              • #8
                Originally posted by tildearrow
                Then if they welcome contributions regardless of whether it is the work or home email, IBM should give the person who was pissed off and simply didn't know how to let his/her stress out a reprimand (or even fire him/her, who knows).

                Did they really have to make a "we welcome contributions" page just to hide the truth?
                Well done Lijun Pan for showing the truth about this company!
                https://web.archive.org/web/20200416...ce/enterprise/

                tildearrow we do have the wayback machine that say this was first detect April 2020. This is a fairly new policy at IBM could simple be out of date manager. The page did 100 percent exist before this blow up.

                What the wayback machine tells at times can be fairly useful that the policies at IBM on more flexible open source commits are about 12 months old. This would also align with alter to company internal policies to take in Redhat staff without major problems.

                I was right to think it was something about IBM employment contracts. There is a big difference in the IBM employment contracts before April 2020 and after April 2020.

                Comment


                • #9
                  Originally posted by oiaohm View Post

                  https://web.archive.org/web/20200416...ce/enterprise/

                  tildearrow we do have the wayback machine that say this was first detect April 2020. This is a fairly new policy at IBM could simple be out of date manager. The page did 100 percent exist before this blow up.

                  What the wayback machine tells at times can be fairly useful that the policies at IBM on more flexible open source commits are about 12 months old. This would also align with alter to company internal policies to take in Redhat staff without major problems.

                  I was right to think it was something about IBM employment contracts. There is a big difference in the IBM employment contracts before April 2020 and after April 2020.
                  this can be considered as git bisection ...well wayback bisection

                  Comment


                  • #10
                    This was a one off disagreement that should not have gone public as there are internal guidelines to resolve it.
                    Translation: We weren't supposed to see how IBM'ers really talk to each other behind the curtain

                    Comment

                    Working...
                    X