I will no longer be able to assist with development nor debugging actual issues with the software… Quite juvenile behavior from the devs. It stemmed from this issue where the devs continuously argued in public by opening and closing an issue. Anyway, thought I would keep y’all apprised of the situation, since these are the people maintaining the software you are currently using.

  •  snowe   ( @snowe@programming.dev ) OP
    51•1 year ago

    My first comment directly discusses the issue at hand. It wasn’t off topic. It’s clear you didn’t want any feedback on the issue because it makes you look bad. I explicitly talked about how client side scheduling is a bad idea that does not accomplish the goal of scheduling. And then I gave feedback directly concerning the exact issue I was commenting on of how your conduct was unfitting of lead devs of a major software project, where you squabbled in public in a really weird way, and you refused to even think about discussing the topic (closing the issue over and over again when your coworker had opened it and asked for discussion? Really dude?). Then you finally banned me without any warning or discussion of why.

    And no, it’s not going to teach me any lesson, all it did was teach the entire community you have no clue how to run an open source software project. No warning, no explanation, just juvenile marking of comments as off topic (they weren’t), closing of the issue your main dev opened and then boom banned.

    •  mark   ( @mark@programming.dev ) 
      24•1 year ago

      This isnt the first time Nutomic has reacted in such a egotistical way, especially when someone points out a flaw in the software. I’ve seen a few issues that were actual issues with the software–not feature requests–that he’s closed and dismissed. One of the issues were mine. He definitely needs help with maintaining the software but I dont know how he expects anyone to help with the way he’s been acting.

    •  nutomic   ( @nutomic@lemmy.ml ) 
      23•1 year ago

      My comment about scheduling in clients was from January and that option was already discarded by dessalines on the next day. No use in rehashing the same thing ten months later. All you are doing is creating pointless notifications for everyone. I know its not ideal to close and reopen an issue, but really why is it a big deal? We closed hundreds of issues recently which were outdated, invalid or already fixed. I accidentally closed one that still needs to be implemented and dessalines reopened it, so everything is fine. Certainly not a “squabble”, and your comments added nothing at all.

      Its true that I shouldnt have given a warning first, but most likely you would have responded with another offtopic complaint so I didnt see any use in that. If you want to complain then do it somewhere else, not on the issue tracker which is meant for getting work done.