Do FreeBSD OS developers discuss before huge changes?

fel1x

fel1x

When we summit patches the process is
  1. There is a bug on bugzilla.freebsd.org
  2. Someone creates a patch, and committers review it on reviews.freebsd.org
  3. When the patch seems okay, a committer commits a patch.
However, if someone made a huge change, such as changing OS structure, adding shells and commands (i.e. adding zsh, ksh, or openrc) (I'm not sure that the word "huge" is appropriate for this case) In this case, do developers have meeting or discussion before he or she starts working on or decided to accept or discard on reviews.freebsd.org like patches?
 
The mailing lists is your go to. The ones I tend to watch are the -current, -hacker, -arch lists. The committers tend to discuss matters on phabricator as well, which is pretty enlightening. Hope that helps.
 
In short, big and fundamental changes are usually discussed for years (specially on the private developer mail lists). In some circumstances, the discussion take so long at the end not changing isn't ever realistic anymore (no one, users or developers, have been using the old "thing" but the new for long time). :)
 
drhowarddrfine said:
Does anyone think they are never discussed and just done by a lone developer without telling anyone?
Click to expand...
Yes, I bet all the SMP work in 5.x was done on the sly,never ever discussed in arch. ( that was sarcasm for those that have trouble discerning it ).

At a bare minimum there are notifications when things are committed, so anyone with a commit bit will be "outed" for merging something to a branch. If others think "why did they do that"? I'd bet lots of discussion around the why happen.
 
You must log in or register to reply here.
Back
Top