3 ms·
Here's a solid proposal. One machine per project. Project defined as a source tarball/repo used when building the OS. So all the stuff that comes from FreeBSD b
by toast0 4y ago
Here's a solid proposal. One machine per project. Project defined as a source tarball/repo used when building the OS. So all the stuff that comes from FreeBSD base counts as one project, sorry developer(s) of /usr/bin/cal, you'll have to fight for access with the rest of the FreeBSD team.
Exception policies for shenanigans.
It's not that hard to share a mac among a developer team, so one mac per project is a good start. There's natural downward pressure on the number of upstream projects used, so one for each of those is a good start. If you also make it request based rather than reaching out to send them, the capex won't be too bad; some upstreams won't be interested anyway.