7 ms·

It's amazing to me how much the open source community accomplishes that huge corporations with billions of dollars can't even get close to. Thanks to all the op

It's amazing to me how much the open source community accomplishes that huge corporations with billions of dollars can't even get close to. Thanks to all the open source contributors who give their spare time to make improvements for everybody.

rapsey 5y ago
A huge amount of open source projects are done by people payed to develop them.
- goodpoint 5y ago
  yet the Reproducible Builds project has been started and driven almost entirely by Debian volunteers: https://reproducible-builds.org/who/people/ https://reproducible-builds.org/who/people/
  - cowsandmilk 5y ago
    That page specifically says their work is funded. I’m sure all the core members do a ton of volunteer work for Debian, but I believe they are now being paid for work on reproducible builds.
    - sanxiyn 5y ago
      It's funded by donation to Reproducible Builds project, and donation is managed by Software Freedom Conservancy (free software organization which also manages donation for Git, QEMU, Samba, and Wine). It's not like they are paid by their employers. You can donate yourself. It is tax-deductible in US. They include logos for donation larger than $25,000. Logos are here: https://reproducible-builds.org/who/sponsors/ https://reproducible-builds.org/who/sponsors/. Top sponsor is Google Open Source Security Team.
    - goodpoint 5y ago
      No, funded does not mean that people are paid for every hour of contribution they do or that they do it full-time. Of the entire set of contributors, most are paid zero. Some are paid.
IshKebab 5y ago
I don't know if that's fair. One of the biggest advance in build systems for ages is Bazel and that came from Google.
dub 5y ago
It's no accident that the Google Open Source Security Team is sponsor of reproducible-builds.org: they'd like to get the open source world up to speed with best practices that have been applied widely internally at Google for well over a decade. Blaze (a.k.a. Bazel) rolled out at Google around 2007-ish, and the idea that consistent inputs should produce consistent outputs was fundamental to its philosophy. Build rules like https://github.com/GoogleContainerTools/distroless https://github.com/GoogleContainerTools/distroless to create minimal, reproducible docker images would seem radical and new most people building docker containers these days (almost everyone uses Dockerfile format) but it'd seem perfectly ordinary and very old-fashioned to any Googler.
- dijit 5y ago
  I feel like I’ve hit something really special with Bazel, but there’s almost no ecosystem around it. Im trying to use it for game development, the model fits so perfectly for large monorepo projects with explicit dependencies, but it seems like since there’s no ecosystem that I have to write a lot of my own rules from scratch; and the learning resources are many years old and in the conference format. It’s quite dense to get in. Even the slack requires an @google.com email to get in.
  - SmileyKeith 5y ago
    > Even the slack requires an @google.com email to get in. This shouldn't be the case, I'm in this slack and it's mostly non-google folks. Do you see this at https://slack.bazel.build https://slack.bazel.build ?
    - dijit 5y ago
      I did that page was a log in or sign up page, which required an @google.com email to sign up: someone has fixed it now, it wasn’t working on Friday which was the last time I checked.
  - kristjansson 5y ago
    That seemed shocking, but it doesn’t appear to be true? https://github.com/bazelbuild/rules_swift/issues/536#issuecomment-1030448400 https://github.com/bazelbuild/rules_swift/issues/536#issueco...

rapsey 5y ago

A huge amount of open source projects are done by people payed to develop them.

goodpoint 5y ago
yet the Reproducible Builds project has been started and driven almost entirely by Debian volunteers: https://reproducible-builds.org/who/people/ https://reproducible-builds.org/who/people/
- cowsandmilk 5y ago
  That page specifically says their work is funded. I’m sure all the core members do a ton of volunteer work for Debian, but I believe they are now being paid for work on reproducible builds.
  - sanxiyn 5y ago
    It's funded by donation to Reproducible Builds project, and donation is managed by Software Freedom Conservancy (free software organization which also manages donation for Git, QEMU, Samba, and Wine). It's not like they are paid by their employers. You can donate yourself. It is tax-deductible in US. They include logos for donation larger than $25,000. Logos are here: https://reproducible-builds.org/who/sponsors/ https://reproducible-builds.org/who/sponsors/. Top sponsor is Google Open Source Security Team.
  - goodpoint 5y ago
    No, funded does not mean that people are paid for every hour of contribution they do or that they do it full-time. Of the entire set of contributors, most are paid zero. Some are paid.

IshKebab 5y ago

I don't know if that's fair. One of the biggest advance in build systems for ages is Bazel and that came from Google.

dub 5y ago

It's no accident that the Google Open Source Security Team is sponsor of reproducible-builds.org: they'd like to get the open source world up to speed with best practices that have been applied widely internally at Google for well over a decade. Blaze (a.k.a. Bazel) rolled out at Google around 2007-ish, and the idea that consistent inputs should produce consistent outputs was fundamental to its philosophy. Build rules like https://github.com/GoogleContainerTools/distroless https://github.com/GoogleContainerTools/distroless to create minimal, reproducible docker images would seem radical and new most people building docker containers these days (almost everyone uses Dockerfile format) but it'd seem perfectly ordinary and very old-fashioned to any Googler.

dijit 5y ago
I feel like I’ve hit something really special with Bazel, but there’s almost no ecosystem around it. Im trying to use it for game development, the model fits so perfectly for large monorepo projects with explicit dependencies, but it seems like since there’s no ecosystem that I have to write a lot of my own rules from scratch; and the learning resources are many years old and in the conference format. It’s quite dense to get in. Even the slack requires an @google.com email to get in.
- SmileyKeith 5y ago
  > Even the slack requires an @google.com email to get in. This shouldn't be the case, I'm in this slack and it's mostly non-google folks. Do you see this at https://slack.bazel.build https://slack.bazel.build ?
  - dijit 5y ago
    I did that page was a log in or sign up page, which required an @google.com email to sign up: someone has fixed it now, it wasn’t working on Friday which was the last time I checked.
- kristjansson 5y ago
  That seemed shocking, but it doesn’t appear to be true? https://github.com/bazelbuild/rules_swift/issues/536#issuecomment-1030448400 https://github.com/bazelbuild/rules_swift/issues/536#issueco...