BSD Cafe Billboard

Spun off from (Linux) Fedora Verified: Help Shape a New Way to Recognize Fedora Contributors | BSD Cafe Billboard FreeBSD Project https://framapiaf.org/@tubsta@bsdlab.au/116478621827645455 – redirects to https://social.bsdlab.au/notice/B5jMI1FY3WtTTWqvNA: Something the #FreeBSD core team could consider. This is something that has probably been needed for a while @dch@bsd.network My initial thoughts: it's an awful lot to think about for a project, or team (Core, for example), that already has, I think, too much to think about. Fedora Project From the Proposal: Unanswered Questions for the Fedora Community While we have a framework, there are several major questions we need the community to answer before we move forward. Specifically, we want to know: Validation: Should applicants be approved by grassroots peer vouches, or an elected committee? Fairness: Does this model truly value non-code contributions equally? Progression: How strictly structured should the path to becoming “Verified” be? Maintenance: Should the status expire after 12 months of inactivity? Of those four questions, the first two are huge. https://mastodon.social/@mxenbionix/116478348932821730: … I do have to echo some of the concerns people seem to be raising about being unclear to what this is actually solving. … Also, the commentary at and under https://discussion.fedoraproject.org/t/188603/3.

fix the code location for the doc tree … It doesn't need fixing, we might need to contact them. What works for the src tree (in the first screenshot below) does not work for the doc tree (second shot). [image: 1775276658791-261d9e5a-1b05-4950-9bfd-1e03904d139f-image.jpeg] [image: 1775276700827-ab9776c2-f7cb-4c58-81a7-e0df05aa9caa-image.jpeg] The previous repo URL was the cgit URL. Before I removed it, today, IIRC there was the same red alert: Error: This Code Location is flagged as Do Not Fetch. Please contact us for assistance – with the same status: Step 1 of 3: Downloading source code history (Failed about 2 years ago.) There's an on-screen suggestion to wait twenty-four hours. I will wait, although given the failure about two years ago: I doubt that it'll make a difference. [image: 1775280296655-67daeab0-2790-4c4f-84b3-ed5dd0bf4460-image.jpeg] There's a suggestion of "special handling" in the help forum. There's also no response to a report that someone made more than five months ago, which is not particularly special