Re: FreeBSD bugzilla, bureaucracy and obstacles

Tatsuki Makino wrote: > Hello. > > Graham Perrin wrote on 2023/08/05 03:33: >> On 04/08/2023 15:43, void wrote: > > An example of just a maintainer case hangs here. > All ports which I am a maintainer use the same email address as this email. > The email address I use for my FreeBSD Bugzilla acco

Re: FreeBSD bugzilla, bureaucracy and obstacles

Hello. Graham Perrin wrote on 2023/08/05 03:33: > On 04/08/2023 15:43, void wrote: An example of just a maintainer case hangs here. All ports which I am a maintainer use the same email address as this email. The email address I use for my FreeBSD Bugzilla account is the same as this email. And

Re: FreeBSD bugzilla, bureaucracy and obstacles

On 04/08/2023 15:43, void wrote: On Tue, Jul 18, 2023 at 08:02:08AM +0100, Graham Perrin wrote: [..snip] Related - when a PR is submitted in bugzilla, does this act send an email to the maintainer? or does one have to submit the PR *and then flag it* ? A previously given example might help.

Re: FreeBSD bugzilla, bureaucracy and obstacles

On Tue, Jul 18, 2023 at 08:02:08AM +0100, Graham Perrin wrote: [..snip] Related - when a PR is submitted in bugzilla, does this act send an email to the maintainer? or does one have to submit the PR *and then flag it* ? --

Re: FreeBSD bugzilla, bureaucracy and obstacles

On 19/07/2023 00:28, Chris wrote: On 2023-07-18 00:05, Fernando Apesteguía wrote: On Tue, Jul 18, 2023 at 9:02 AM Graham Perrin wrote: On 18/07/2023 07:29, Fernando Apesteguía wrote: > … Would you say that requesting maintainers-feedback when reporting an > issue with a port is common sense

Re: FreeBSD bugzilla, bureaucracy and obstacles

On 2023-07-18 00:05, Fernando Apesteguía wrote: On Tue, Jul 18, 2023 at 9:02 AM Graham Perrin wrote: On 18/07/2023 07:29, Fernando Apesteguía wrote: > … Would you say that requesting maintainers-feedback when reporting an > issue with a port is common sense? … Yes. Common sense, and automate

FreeBSD bugzilla, bureaucracy and obstacles: fixing documentation

On 18/07/2023 07:29, Fernando Apesteguía wrote: … When conflicting instructions are present, then we should fix the documentation. … True. The silence, or near-silence, in Phabricator is sometimes deafening. To the people who wonder why is no

Re: FreeBSD bugzilla, bureaucracy and obstacles

On Tue, Jul 18, 2023 at 9:02 AM Graham Perrin wrote: > On 18/07/2023 07:29, Fernando Apesteguía wrote: > > … Would you say that requesting maintainers-feedback when reporting an > > issue with a port is common sense? … > > Yes. > > Common sense, and automated sense, because in the vast majority o

FreeBSD bugzilla, bureaucracy and obstacles

On 18/07/2023 07:29, Fernando Apesteguía wrote: … Would you say that requesting maintainers-feedback when reporting an issue with a port is common sense? … Yes. Common sense, and automated sense, because in the vast majority of cases (i.e. commonplace), the request is automated. Worth menti

Re: FreeBSD bugzilla, bureaucracy and obstacles (was: Can someone please post a concise list of things maintainers are supposed to do?)

On Tue, Jul 18, 2023 at 8:18 AM Graham Perrin wrote: > On 17/07/2023 08:04, Stefan Bethke wrote: > > … conflicting instructions … bureaucratic … > > I pay relatively little attention to ports tree-related bug reports. > This is not wilful ignorance; it's mostly because the doc tree is/was a > foc

FreeBSD bugzilla, bureaucracy and obstacles (was: Can someone please post a concise list of things maintainers are supposed to do?)

On 17/07/2023 08:04, Stefan Bethke wrote: … conflicting instructions … bureaucratic … I pay relatively little attention to ports tree-related bug reports. This is not wilful ignorance; it's mostly because the doc tree is/was a focus. BRs that catch my eye, that I speed-read without changing t