Date: Sat, 10 Sep 2022 23:29:04 +0200 From: Sergio Carlavilla <carlavilla@freebsd.org> To: Mason Loring Bliss <mason@blisses.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Simple bugs with image impact for the project... Message-ID: <CAFwocyP-mbZikjrpEnzFd6NcFxoKazGQXtB0nTRpM3AHWrvQhA@mail.gmail.com> In-Reply-To: <Yxz9rsIelM5CJ52b@blisses.org> References: <Yxz9rsIelM5CJ52b@blisses.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000ce5eb905e8595ac2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Sorry for the top posting, I'm using my phone. It's true that this error can be fixed easily, but the idea is to teach other committers how to handle this. Graham will fix this so soon :) Sorry for the inconvenience. Btw, the documentation code is in our git at cgit.FreeBSD.org If you want to learn how to upgrade our website/documentation portal, please ping me. Bye! El s=C3=A1b., 10 sept. 2022 23:12, Mason Loring Bliss <mason@blisses.org> escribi=C3=B3: > I'd noted FreeBSD 13.0's end of life on IRC a couple times, and then open= ed > a bug to have it removed from the freebsd.org front page. Between my live > mentions and opening a bug, Graham Perrin opened his own, and found more > things to correct, so his is the right one to drive forward. But here we > are, September 10th, heading towards two weeks of 13.0 no longer having > formal support, and the main page still notes 13.0 as being supported. > > This feels like something that ought to be so trivially easy to correct a= s > to not warrant mention, but instead it seems to be dragging on, and it > seems like a problem that the project can't post correct and up to date > information about itself on the web site, despite at least a couple peopl= e > interested in seeing it updated, one of whom (Graham) has a commit bit, a= s > I understand it. > > What's missing? > > Please take this as a desire to understand the current state and to see > process improvement, not as a complaint about volunteers not doing work o= n > a schedule. (That said, I'd volunteer if that'd make it happen. I updated > the Torrents wiki page, moving 13.0 out of current releases, because I > could, but I (appropriately, since I'm not formally tied to the project) > don't have access to update the main web site.) > > -- > Mason Loring Bliss (( If I have not seen as far as others, it is becau= se > mason@blisses.org )) giants were standing on my shoulders. - Hal > Abelson > --000000000000ce5eb905e8595ac2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Hi,<div dir=3D"auto"><br></div><div dir=3D"auto">Sorry fo= r the top posting, I'm using my phone.</div><div dir=3D"auto"><br></div= ><div dir=3D"auto">It's true that this error can be fixed easily, but t= he idea is to teach other committers how to handle this. Graham will fix th= is so soon :)</div><div dir=3D"auto"><br></div><div dir=3D"auto">Sorry for = the inconvenience.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Btw, = the documentation code is in our git at <a href=3D"http://cgit.FreeBSD.org"= >cgit.FreeBSD.org</a></div><div dir=3D"auto"><br></div><div dir=3D"auto">If= you want to learn how to upgrade our website/documentation portal, please = ping me.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Bye!</div></div= ><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">El s= =C3=A1b., 10 sept. 2022 23:12, Mason Loring Bliss <<a href=3D"mailto:mas= on@blisses.org">mason@blisses.org</a>> escribi=C3=B3:<br></div><blockquo= te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so= lid;padding-left:1ex">I'd noted FreeBSD 13.0's end of life on IRC a= couple times, and then opened<br> a bug to have it removed from the <a href=3D"http://freebsd.org" rel=3D"nor= eferrer noreferrer" target=3D"_blank">freebsd.org</a> front page. Between m= y live<br> mentions and opening a bug, Graham Perrin opened his own, and found more<br= > things to correct, so his is the right one to drive forward. But here we<br= > are, September 10th, heading towards two weeks of 13.0 no longer having<br> formal support, and the main page still notes 13.0 as being supported.<br> <br> This feels like something that ought to be so trivially easy to correct as<= br> to not warrant mention, but instead it seems to be dragging on, and it<br> seems like a problem that the project can't post correct and up to date= <br> information about itself on the web site, despite at least a couple people<= br> interested in seeing it updated, one of whom (Graham) has a commit bit, as<= br> I understand it.<br> <br> What's missing?<br> <br> Please take this as a desire to understand the current state and to see<br> process improvement, not as a complaint about volunteers not doing work on<= br> a schedule. (That said, I'd volunteer if that'd make it happen. I u= pdated<br> the Torrents wiki page, moving 13.0 out of current releases, because I<br> could, but I (appropriately, since I'm not formally tied to the project= )<br> don't have access to update the main web site.)<br> <br> -- <br> Mason Loring Bliss=C2=A0 ((=C2=A0 =C2=A0If I have not seen as far as others= , it is because<br> =C2=A0<a href=3D"mailto:mason@blisses.org" target=3D"_blank" rel=3D"norefer= rer">mason@blisses.org</a>=C2=A0 =C2=A0))=C2=A0 =C2=A0giants were standing = on my shoulders. - Hal Abelson<br> </blockquote></div> --000000000000ce5eb905e8595ac2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFwocyP-mbZikjrpEnzFd6NcFxoKazGQXtB0nTRpM3AHWrvQhA>