Date: Tue, 18 Jul 2023 08:29:29 +0200 From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> To: Graham Perrin <grahamperrin@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: FreeBSD bugzilla, bureaucracy and obstacles (was: Can someone please post a concise list of things maintainers are supposed to do?) Message-ID: <CAGwOe2ao3QHttEaYL3=MpQgJ_u64fXLLwdF7o09Jtcbhi5kacA@mail.gmail.com> In-Reply-To: <76ad55a3-46c2-146e-6005-b300dc911e1c@freebsd.org> References: <6D24E23B-1F79-47E9-B533-361188502BEA@lassitu.de> <76ad55a3-46c2-146e-6005-b300dc911e1c@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000453d5f0600bd0ad4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jul 18, 2023 at 8:18=E2=80=AFAM Graham Perrin <grahamperrin@freebsd= .org> wrote: > On 17/07/2023 08:04, Stefan Bethke wrote: > > =E2=80=A6 conflicting instructions =E2=80=A6 bureaucratic =E2=80=A6 > > 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 the > status to open, include those that might have a non-obvious CVE/security > aspect. > > A bigger picture =E2=80=93 not limited to ports =E2=80=93 might help othe= r readers to > put things in perspective. <https://wiki.freebsd.org/Bugzilla>; has ten > public sub-pages (the array at the foot of the page), plus at least two > private sub-pages to which I neither have, nor require, access. > > Given what's in the wiki =E2=80=93 with or without interleaving of relate= d > content in the official FreeBSD Documentation Portal and elsewhere =E2=80= =93 > it's simply impossible to adhere to everything that's suggested or > required. > > Impossible partly because there's conflicting guidance. > > So, in many cases: common sense and brevity apply. > When conflicting instructions are present, then we should fix the documentation. In those cases, the OP can go with either option. The developer/triager can fix the PR later. Now I'm very curious about the "common sense" thing. Would you say that requesting maintainers-feedback when reporting an issue with a port is common sense? I would say so. Just go to the port and copy-paste the email address and you are done, yet many people don't even do that. > > For me, the greatest obstacles to progress are: > > a) absences of FreshPorts URLs =E2=80=93 > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266880>; would be a > start, but not as streamlined as I'd like > In all honesty, I read https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266880 and I have absolutely no idea what you are talking about. Is this the kind of brevity you are encouraging users to apply? > > b) the largely broken/meaningless dashboard =E2=80=93 far less easy to fi= x. > > Back to Stefan's cases: amongst the resources that may be most relevant > is <https://wiki.freebsd.org/Bugzilla/ThePerfectPortsIssue>. > > HTH > > --000000000000453d5f0600bd0ad4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 18, 2023 at 8:18=E2=80=AF= AM Graham Perrin <<a href=3D"mailto:grahamperrin@freebsd.org">grahamperr= in@freebsd.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" st= yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd= ing-left:1ex">On 17/07/2023 08:04, Stefan Bethke wrote:<br> > =E2=80=A6 conflicting instructions =E2=80=A6 bureaucratic =E2=80=A6<br= > <br> I pay relatively little attention to ports tree-related bug reports. <br> This is not wilful ignorance; it's mostly because the doc tree is/was a= <br> focus. BRs that catch my eye, that I speed-read without changing the <br> status to open, include those that might have a non-obvious CVE/security <b= r> aspect.<br> <br> A bigger picture =E2=80=93 not limited to ports =E2=80=93 might help other = readers to <br> put things in perspective. <<a href=3D"https://wiki.freebsd.org/Bugzilla= " rel=3D"noreferrer" target=3D"_blank">https://wiki.freebsd.org/Bugzilla</a= >> has ten <br> public sub-pages (the array at the foot of the page), plus at least two <br= > private sub-pages to which I neither have, nor require, access.<br> <br> Given what's in the wiki =E2=80=93 with or without interleaving of rela= ted <br> content in the official FreeBSD Documentation Portal and elsewhere =E2=80= =93 <br> it's simply impossible to adhere to everything that's suggested or = <br> required.<br> <br> Impossible partly because there's conflicting guidance.<br> <br> So, in many cases: common sense and brevity apply.<br></blockquote><div><br= ></div><div>When conflicting instructions are present, then we should fix t= he documentation.</div><div>In those cases, the OP can go with either optio= n.</div><div>The developer/triager can fix the PR later.</div><div><br></di= v><div>Now I'm very curious about the "common sense" thing.</= div><div>Would you say that requesting maintainers-feedback when reporting = an issue with a port is common sense? I would say so.</div><div>Just go to = the port and copy-paste the email address and you are done, yet many people= don't even do that.<br></div><div>=C2=A0</div><blockquote class=3D"gma= il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2= 04,204);padding-left:1ex"> <br> For me, the greatest obstacles to progress are:<br> <br> a) absences of FreshPorts URLs =E2=80=93 <br> <<a href=3D"https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266880" = rel=3D"noreferrer" target=3D"_blank">https://bugs.freebsd.org/bugzilla/show= _bug.cgi?id=3D266880</a>> would be a <br> start, but not as streamlined as I'd like<br></blockquote><div><br></di= v><div>In all honesty, I read <a href=3D"https://bugs.freebsd.org/bugzilla/= show_bug.cgi?id=3D266880">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id= =3D266880</a> and I have absolutely no idea what you are talking about.</di= v><div>Is this the kind of brevity you are encouraging users to apply?<br><= /div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px= 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> b) the largely broken/meaningless dashboard =E2=80=93 far less easy to fix.= <br> <br> Back to Stefan's cases: amongst the resources that may be most relevant= <br> is <<a href=3D"https://wiki.freebsd.org/Bugzilla/ThePerfectPortsIssue" r= el=3D"noreferrer" target=3D"_blank">https://wiki.freebsd.org/Bugzilla/ThePe= rfectPortsIssue</a>>.<br> <br> HTH<br> <br> </blockquote></div></div> --000000000000453d5f0600bd0ad4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGwOe2ao3QHttEaYL3=MpQgJ_u64fXLLwdF7o09Jtcbhi5kacA>