This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.0 Status Report (2005-02-03)
On Wednesday 09 February 2005 01:21, Mark Mitchell wrote:
> Steven Bosscher wrote:
> > On Thursday 03 February 2005 20:49, Mark Mitchell wrote:
> >>Therefore, we will use the same proposal-based procedure that we used
> >>(late) in the GCC 4.0 timeframe. If you have already completed, or
> >>are planning to complete, a substantial project that you would like to
> >>include in GCC 4.1, please send me the following information:
> >
> > Can that information go the the mailing list instead?
> >
> > IMVHO sending everything to you does not fit the "Open Development
> > Environment" that the SC has in its mission statement.
>
> I didn't in any way imply that people couldn't spread the word more
> widely. I certainly don't mind if people send it elsewhere, but a copy
> certainly needs to go to me.
I would appreciate, and probably other people would appreciate too, to
know what is proposed, so I can adjust my own plans accordingly, and
maybe get involved with projects that are interesting to me but that
lack man power to meet deadlines.
You could just say, "Just send the proposals to the list *and* to me",
and people can react to the proposals and plot their own roadmap based
on the extra information.
As for decisions, AFAICT making them is orthogonal to submitting the
proposals. Those proposals are just extra information for those who
are interested in working on GCC. Having them public only provides
you with feedback for the community. A win-win situation, I'd say.
> And, yes, I want to be open -- but I do not think that means exposing
> every decision to public discussion. My role is to make decisions that
> advance the overall state of the compiler. Sometimes, it yields better
> results to make certain decisions in smaller groups. I sometimes make
> decisions by consulting privately with experts whose opinions I value,
> and I will continue to do that.
I respectfully disagree agree with your description of your role as
RM: "to make decisions that advance the overall state of the compiler".
It is not your decision to make, or the small group you value. Your
description is almost a quote from "http://gcc.gnu.org/steering.html":
"Its primary purpose is to make major decisions in the best interests
of the GCC project (...)", which makes it clear where those decisions
should be made: in the SC. Those decisions should be based on input
from as many relevant people as possible. My understanding is that we
have the mailing lists for that.
Just to be clear, I don't want to leave the impression that this is a
big deal to me. I know how the decision to merge the tree-ssa branch
was made last year, and that went pretty well. But I believe that you,
as the RM, should not leave an impression that you make the decisions
at your discretion. That is not how it is supposed to be IMHO.
Gr.
Steven