> 6. nov. 2022 kl. 21:32 skrev i...@tutanota.com:
> 
> I am the sysadmin at our company responsible for the OpenBSD
> based projects. When I read about the problems at FreeBSD, after
> which I wrote to their list, I was sure that the process was different
> in OpenBSD, to which several users on FreeBSD replied, that
> OpenBSD doesn't do code review on each commit, yada yada.

I would not treat statements by one or more random users of a different 
operating system on a mailing list for that system as anywhere near 
authoritative on what OpenBSD developers do or do not do.

As others have already indicated, you will get a more complete picture by 
looking up the issues on tech@ and bugs@ as well as the platform-specific 
lists. But keep in mind that there will occasionally be situations where the 
review is by private channels, such as when dealing with security issues under 
embargo.

But in the general case, yes, review via tech@ is required, commits without OKs 
will have a high risk of being reverted.

I would suggest that if your colleagues need information on project goals and 
methods, https://www.openbsd.org/goals.html would be a useful place to start.

- Peter

PS the first link in my .signature leads on to among other things articles that 
might be of interest while you put off posting the next message to this thread.


—
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.







Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to