as discussed in the core session at BSDCan.
Please see review D10413 if you want to suggest any further changes.
Approved by: core
Differential Revision: https://reviews.freebsd.org/D10413
several different meanings and it can be unclear which exactly we
intend. The paragraph is clear enough without it.
Submitted by: hps
Approved by: core (emaste, gnn)
Update the Committer's Guide
- section 21 covers much of the same areas as the new Code of
Conduct, but the CoC is authoritative. Update wording where
there is some disagreement.
- Add a new section on Privacy and Confidentiality which was felt to
be too committer specific to go into the general Code of Conduct.
With hat: core-secretary
Reviewed by: gjb, core
Approved by: core
- All ref* machines are reference machines with similar
hardware configurations (excluding ia64, sparc64).
- We don't need to list administrative (infrastructural)
machines, so they're removed. If anyone wants to know,
it's in DNS.
- Hub is deprecated. Yay.
- Remove the 'type' column for various machines. People
that are interested (and have access) can check dmesg(8).
- Remove a site-specific reference, as we have many sites
now, and this page is not the right place to thank the
generous bandwidth/power/facility providers for our many
sites.
With hat: admins
Sponsored by: The FreeBSD Foundation
new committer proposals to:
- Provide more details on the contents of a suitable proposal, including
a request for evidence of constructive engagement with the mentor (e.g.,
through successfully completed patch cycles).
- Be more overt about identifying community participation (but also more
open about what it means -- mention BSD-conference talks, for example).
- Suggest contacing core@ informally first if there are worries about
whether there is sufficient contribution or concern about a proposal
failing.
- Expand thinking on 'vendor commit bits' -- both the responsibilities of
the mentor, and also the hope that such contributors will broaden their
interests over time.
Approved by: core
hardware refreshes since this list was last updated.
Remove the ports build machines for now, the existing specs and hosts are
very outdated but I don't know enough about the ports build infrastructure
to refresh it at the moment. I plan to update this in the coming days.
outdated, and two of the internal links return 404 for data that
likely will not be returning anytime soon.
Submitted by: erwin
Sponsored by: The FreeBSD Foundation
It has suffered hardware from more hardware failure than is
reasonably feasible to restore the machine to a working state.
If it were a horse, it would have been turned into glue years
ago.
Sponsored by: The FreeBSD Foundation
