Basile STARYNKEVITCH <bas...@starynkevitch.net> writes: > I am unfortunately not attending the GCC summit which happens right > now in Montreal. > > But apparently, there seems to be a lack of code reviewers for > GCC. The few people who do review code seems to have a lot of review > in their batch queue. > > Perhaps could be discussed at the summit some way to increase the set > of reviewers, i.e. the set of people able to say Ok to a patch > submitted on gcc-patches@ > > Or is that question a steering committee priviledge? If it is, could > someone ask it to them (the SC members)?
Your e-mail was raised (by Richi) during the SC panel discussion. The discussion in the room was much like the discussion on the list: we would all like to have more reviewers; the problem is finding people who are willing and able to do the job. The SC is not a bottleneck here. During the panel discussion, Mark Mitchell said that if anybody wants to raise an issue with the SC, they can send him e-mail directly and he will raise it. I'm sure that is true of other SC members as well. I believe that the most useful immediate thing we could do to speed up gcc development would be to move to a distributed version control system. That should make it much easier for people to swap patches around. It should make it possible for reviewers to take a patch, make some changes themselves, and send it back to the original submitter for more work. It would make it much simpler for people to reliably test other people's patches, singly or in combination. None of this would eliminate the traditional role of maintainers in the gcc system; however, I believe it would make some decisions simpler. Ian
