Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. @SRAZKVT exactly that's why I'm saying we may have to accept some slop near term because we don't have the body of contributors to maintain a fork

@SRAZKVT exactly that's why I'm saying we may have to accept some slop near term because we don't have the body of contributors to maintain a fork

Scheduled Pinned Locked Moved Uncategorized
7 Posts 2 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • azonenberg@ioc.exchangeA This user is from outside of this forum
    azonenberg@ioc.exchangeA This user is from outside of this forum
    azonenberg@ioc.exchange
    wrote last edited by
    #1

    @SRAZKVT exactly that's why I'm saying we may have to accept some slop near term because we don't have the body of contributors to maintain a fork

    srazkvt@tech.lgbtS azonenberg@ioc.exchangeA 2 Replies Last reply
    1
    0
    • R relay@relay.infosec.exchange shared this topic
    • azonenberg@ioc.exchangeA azonenberg@ioc.exchange

      @SRAZKVT exactly that's why I'm saying we may have to accept some slop near term because we don't have the body of contributors to maintain a fork

      srazkvt@tech.lgbtS This user is from outside of this forum
      srazkvt@tech.lgbtS This user is from outside of this forum
      srazkvt@tech.lgbt
      wrote last edited by
      #2

      @azonenberg i WISH after all this shit we maintain a culture of redundancy in our systems, rather than whatever the fuck got us into this mess

      srazkvt@tech.lgbtS 1 Reply Last reply
      0
      • azonenberg@ioc.exchangeA azonenberg@ioc.exchange

        @SRAZKVT exactly that's why I'm saying we may have to accept some slop near term because we don't have the body of contributors to maintain a fork

        azonenberg@ioc.exchangeA This user is from outside of this forum
        azonenberg@ioc.exchangeA This user is from outside of this forum
        azonenberg@ioc.exchange
        wrote last edited by
        #3

        @SRAZKVT and then we'll be stuck on the position of freezing a commit before the slop and back porting security fixes forever (if we can even find the people to do that) or tracking upstream slop and all

        azonenberg@ioc.exchangeA 1 Reply Last reply
        1
        0
        • azonenberg@ioc.exchangeA azonenberg@ioc.exchange

          @SRAZKVT and then we'll be stuck on the position of freezing a commit before the slop and back porting security fixes forever (if we can even find the people to do that) or tracking upstream slop and all

          azonenberg@ioc.exchangeA This user is from outside of this forum
          azonenberg@ioc.exchangeA This user is from outside of this forum
          azonenberg@ioc.exchange
          wrote last edited by
          #4

          @SRAZKVT there is no good option

          1 Reply Last reply
          1
          0
          • srazkvt@tech.lgbtS srazkvt@tech.lgbt

            @azonenberg i WISH after all this shit we maintain a culture of redundancy in our systems, rather than whatever the fuck got us into this mess

            srazkvt@tech.lgbtS This user is from outside of this forum
            srazkvt@tech.lgbtS This user is from outside of this forum
            srazkvt@tech.lgbt
            wrote last edited by
            #5

            @azonenberg "ouhhhh fragmentation is bad yknow" shut the fuck up multiple compatible and replacable implementations isn't fragmentation, it's redundancy, and it exists specifically to prevent issues where one project goes to shit

            azonenberg@ioc.exchangeA 1 Reply Last reply
            0
            • srazkvt@tech.lgbtS srazkvt@tech.lgbt

              @azonenberg "ouhhhh fragmentation is bad yknow" shut the fuck up multiple compatible and replacable implementations isn't fragmentation, it's redundancy, and it exists specifically to prevent issues where one project goes to shit

              azonenberg@ioc.exchangeA This user is from outside of this forum
              azonenberg@ioc.exchangeA This user is from outside of this forum
              azonenberg@ioc.exchange
              wrote last edited by
              #6

              @SRAZKVT free software antitrust?

              azonenberg@ioc.exchangeA 1 Reply Last reply
              1
              0
              • azonenberg@ioc.exchangeA azonenberg@ioc.exchange

                @SRAZKVT free software antitrust?

                azonenberg@ioc.exchangeA This user is from outside of this forum
                azonenberg@ioc.exchangeA This user is from outside of this forum
                azonenberg@ioc.exchange
                wrote last edited by
                #7

                @SRAZKVT but we can't even manage to properly fund sole devs on critical components now, redundancy is a pipe dream.

                Easy pickings for lennart and red hat to swoop in and take over stuff

                1 Reply Last reply
                1
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups