1. 20
  1.  

  2. 25

    That last comment is a prime example of how not to treat OSS maintainers.

    1. Needlessly aggressive and confrontational
    2. Demanding the maintainers take on extra work
    3. Drawing comparisons to other significantly more popular packages in an attempt to guilt the maintainers into doing #2
    1. 3

      “Last comment” is something that changes over time, you might want to be more specific.

    2. 11

      As in many other things, I’ve always been impressed by Twisted Python’s approach to platform support. You Too Can Have A Tier-1 Platform, if you provide a build agent on that platform for the continuous integration system, and as long as somebody’s around to help other contributors whose contributions accidentally break that platform.

      No matter how much work you do up-front, it’s not reasonable to expect upstream to carry and maintain your patches forever after, if it’s not code they would have ever gotten around to writing themselves.

      1. 24

        Hi, I’m the person doing the port. Just for context as I know scrolling up is not nice. I notified upstream on September 02 2015 that I intend to provide & support a full OpenBSD port and asked on how they want to coordinate the effort. I wasn’t asked a single time to provide a build platform/host or to maintain the code but I was willing to do both. So please don’t imply that I wanted the upstream to carry my work for me. This ticket is 3 years old and I had a fully working OpenBSD port of the runtime (without dartium), a person with a working FreeBSD runtime and a person willing to do a NetBSD port.

        1. 13

          As someone who has worked on V8/Chromium fork and put patches upstream.. it really feels that both of those projects are open source but definetly not open develoment. Patches and issues that Googlers were not actively working on just got ignored most of times.

          Dart team is mostly (?) old V8 people, probably brought the attitude with them.

          1. 1

            As an outsider, I guess I don’t see the problem with adding bsd support in general. Yes cross platform invokes “problems” when you add new things, but my quick read of that issue they already rely on procfs on linux.

            I’d hope they would be more willing to take this time as a way to reflect to fix the builtin linux-isms to their code and how they can avoid making it less portable in future.

          2. 2

            Contributions are a two-way street, and I admire the Twisted Python project because they cover both directions pretty well. Good on you for holding up your end of the bargain, and shame on Google for not being prepared to handle platform-support contributions.

            That said, I think the headline here is click-baity, suggesting that Google has something against BSD in particular, rather than just third-party-supported platforms in general.