Date: Mon, 13 Nov 2000 07:50:57 -0800 (PST) From: opentrax@email.com To: billf@chimesnet.com Cc: freebsd-doc@FreeBSD.ORG Subject: Re: docs/22042: spelling error Message-ID: <200011131550.HAA05762@spammie.svbug.com> In-Reply-To: <20001112134444.E37870@jade.chc-chimes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 Nov, Bill Fumerola wrote: > On Sun, Nov 12, 2000 at 03:32:31AM -0800, opentrax@email.com wrote: > >> Perhaps, I wasn't clear about how I'm using the word "directly". >> In this context, I mean that the "directly" from FreeBSD-gnats. >> It's well known that XFree86 has a bug reporting system, but >> bugs like this get passed around like a sour apple. People >> knows it's sour, but prefer to have someone else taste it. > > I'm about 1000mi overdue for an oil change and I have a quarter > tank of gas left. I, however, will go to both a quicklube[1] > and a gas station to fix this. Just because both places (gas > station and quicklube / FreeBSD GNATS and XFree86 GNATS) > perform similar functions (putting fluids in an automobile / > fixing errors in man pages) doesn't mean that both are appropriate. > Why not? A gas station can give you oil/fluids just like quicklube can. Gas stations used to be an all-in-one place. Fix and filling your car. It was quite sucessful. Still is when the gas supplier does not own the gas station. > Making local changes to XFree86 without contributing them back > doesn't help XFree86 fundamentally fix the problem, nor does it > make us good citizens. It is also difficult because the changes > will possibly later conflict (we fixed the spelling error, but they > removed the reference, now the patch breaks the build). > I dont' recall advocating that *BSD make any changes for XFree86. Did I somehow give you that impression? > Is it technically possible to fix it? Yes. > Is it the policy of FreeBSD to submit man page fixes back to > the vendor in the hopes that they will be locally adapted? Yes. > So after reading your response it seems that I haven't been clear. I'll reiterate. Errors, such as those in this PR are quite common. Further such errors reflect badly on *BSD. The end user when confronted with a problem, error or obvious solution usally looks for a place to contribute to *BSD or other OpenSource projects. Currently, many projects don't share information. Something that Bill (Gates) and company love. It makes their job easy. In this scenerio, M$ might get a report. If they do report it to the APP maker, then the have the advantage; as now the know how to break the App. In our case, we are looking to help the customter, not lock them in to our software. As such, when a PR enters the system and the person reviewing the PR see it belongs to another community, that person can forward it. However, this does not need to be the case. Another option would be to have a seperate page to enter PRs that go directly to the maintainer. This, of course, would still have it's share of problems, but at least it would move things in a better direction. best regards, jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011131550.HAA05762>