Cooperative Bug Isolation Project

[Tim Daly]

Jeremy,

re: communication at redhat.

to succeed you need to lead.
to lead you need to motivate.
motivation is driven from stating and pursuing long term goals.
people can derive their own tasks if given clear goals.

fc1 and fc2 seem rather eclectic and short-term goals.
what are the goals for fc(n)?
what's the 3, 5, 10 year goal?

how will community developed projects integrate? 
not details, just vision. will yum move toward apt-get install?
i've listened and read yet i see no vision, just handwaving about
"extras".

can we get a community resource for compile/testing/integrate?
this involves a compile farm, testing standards, and recognition
and support for test leaders (similar to the linux's project leads).
they should have a recognized relationship with fedora (e.g. nothing
gets accepted until they accept it for their subsystems). what are
the subsystems? who are the leads? in particular, who is considered
the "linus of fedora"? the "morton of fedora"? will redhat support
one "linus of fedora" fulltime?

how will fedora be branded? will redhat feature it on their site?
will there be a branding team with a recognized lead? will there
be an established relationship with cheapbytes or other copy makers?

will fedora establish joint goals with other teams such as SUSE,
Debian, etc? can we take a lead role in trying to re-merge the
various forks, at least getting agreement on "the standard subset"?
there is, quite frankly, no obvious reason not to merge some redhat
tools with other distros (eg rpm and apt, this would open rpm to
the whole debian codepile).

in the spirit of a community-driven project the point should probably
be made that whatever leadership and organization fedora has at the
moment it has failed to paint "the grand dream". 

who is the "linus of fedora"?

t