Regarding your case number 10724899 [ ref:_00D00hhzl._5004V11emZL:ref ]
ralf-mardorf at riseup.net
Sat Sep 26 11:35:35 UTC 2020
On Fri, 25 Sep 2020 05:24:18 -0400, Jerry wrote:
>On Fri, 25 Sep 2020 08:44:52 +0200, Ralf Mardorf commented:
>>You are aware that sending this mail to a support is spam to the
>>mailing lists that have got nothing to do with this support?
>>On Thu, 24 Sep 2020 22:46:34 -0700, David Christensen wrote:
>>>What is the URL for the ISO file for SeaToolsBootable[snip]?
>>>What is the URL for the source code for [snip] any [snip]
>>>GPL v2 code distributed with SeaToolsBootable [snip]?
>>This kind of nitpicking is the reason that some vendors never ever
>>will support FLOSS operating systems. Without this nitpicking way more
>>vendors would use and/or support FLOSS operating systems.
>>Most of the times it will not result in hosting the source codes on a
>>vendor's server, it more likely will end up with dropping FLOSS
>I had a talk with a technician from Brother USA several years ago
>regarding them directly supporting FreeBSD as they do some other FOSS
>distributions. What you just mentioned was one of their concerns. There
>were others, a lot of others, but it all came down to it was not
>financially feasible for them to do it.
From a vendor's point of view there indeed could be way more issues,
hence nitpicking about hosting source code, that already is hosted by
upstream, is counter-productive regarding one and the other goal.
Sometimes a "please follow the rules as close as possible", is way more
constructive, than following rules without any considerations.
Sure, way to much traffic could become an issue for upstream, while a
rich company might profit for free as in beer, OTOH an altruistic,
philanthrope project might become impossible, even while not causing
an issue for upstream.
The résumé is "balance" is required, but "nitpicking" is
More information about the freebsd-questions