Date: Mon, 12 Mar 2001 20:03:56 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Warner Losh <imp@harmony.village.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: The Project and onward [was: Re: cvs commit: src/sys/netinet ip_output.c] Message-ID: <Pine.NEB.3.96L.1010312195859.52981A-100000@fledge.watson.org> In-Reply-To: <200103130020.f2D0KmI41107@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Mar 2001, Warner Losh wrote: > In message <52176.984399203@critter> Poul-Henning Kamp writes: > : Of course, one could *hope* that core would spend time on such > : issues, but hey, I'm not holding my breath... > > Core's charter doesn't include this. When we went through the big > bruhaha to get the new bylaws, it was fairly widely represented as a > dispute resolution system and committer approval body only. Maybe it > should do more than that, but that's what most people said core was as > recent as last October. That was my understanding also. The large majority of technical comments and commits that I make are done with my "committer" hat on, and not my "core" hat. No need to identify which hat is worn when making inane "me too" comments :-). I'm not sure I like the idea of an architectural board per se, because I think that architectural discussions can work fine with our current forums. What might be useful are some sub-system "ownership" hats to do some basic gating of new features and large changes, as well as making it clear just who gets to authorize the forceable backing out of undesirable commits. Having someone who can help coordinate work in a subsystem, as well as point to available work/projects, give advice on the topic of new committers and features, etc, would be useful. The allocation process for said hats is probably at issue--as with most hats, I suspect they should be handed out by core@, but only to volunteers. :-) For example, having someone with a netinet hat to help coordinate the recent security-officer work there, etc, would be very useful. Similarly, someone holding the file system hat who can help SMPng developers figure out who to talk to, and possibly gather opinions from interested parties to make recommendations. I won't push for this idea all that hard, but it's one worth considering. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1010312195859.52981A-100000>