On Wed, Jun 11, 2025 at 11:46 AM Segher Boessenkool < seg...@kernel.crashing.org> wrote:
> On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote: > > On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote: > > >What is not working with the current system? What is this fixing? > > It relies on the someone to shepherd the process and it's something that > > often gets pushed down on my daily todo list. As a result nominations > > don't happen or are extremely delayed. > > > > Additionally there's no visibility into the process. It's a total black > > hole, particularly for cases where I'm on point. > > > > This isn't necessarily a steering committee problem, but a time problem. > > > > If we make things simpler for those cases where it is actually simple > > and increase visibility so that folks know state I think it would be a > > welcome improvement to the process. > > Yup. And it might not be a bad plan to get some people who still are > active onto the GCC steering committee, as well! > > It is as important now as ever that there *is* such a thing as the SC: > all decisions need to be taken responsibiliity for by some final > authority, which we (as a project) have all decided to have that > authority. > The GCC SC needs to remain sufficiently engaged and responsive that it maintains the respect, the responsibility, and the authority delegated from all stakeholders to make and enforce decisions -- both simple decisions and complicated decisions. Without the visible participation in "simple" decisions, the acceptance of complicated decisions may be eroded. Adding GCC SC members is an excellent goal. It is important that GCC and the GNU Toolchain project have a strong pipeline of leadership. Challenges include: 1. Finding nominees with the experience, respect, interest, desire, and commitment to serve on the SC. 2. Finding nominees who can receive the support of all stakeholders needed to approve GCC SC members. Cheers, David
