Tomáš Chvátal <email@example.com> said:
> guys working on tinderbox and reading the logs and opening bugs, if time
> allows also fixes them.
> (all tinderbox bugs will be required to be addressed by maintainer in
> long term)
Not sure how many people know about it, but there is already a git repo
for Diego's scripts:
Having more people run this on different archs and that would be
> guys following on -commits and checking if someone does not break the
> tree :] Usually fixing themselves or slapping maintainer to do so
> (privately not on -dev, everyone has a bad day :])
I like the idea of us more proactively doing code reviews of changes,
but for this to be effective we are going to need a nice sized bunch of
people to do it.
> puritans :] these guys will proactively check the main tree for qa
> issues using various tools and removing everything that does not fit in
> :] (patches/ebuild-coding/whitespace fixes/...).
This is one that I've been trying to do with the help of a few of you,
and its a lot harder than it sounds, but something I see as being
worthwhile as well. If we can cut down on the noise from all of the
simple issues that shouldn't exist, we can start making more interesting
and strict checks.
> Guys responsible for maintaining profiles and removing packages that
> in long-term fails to meet up QA standards.
Samuli already said it, and I agree, that these guys should worry about
packages instead of profiles. The overall QA team should worry about
> guys responsible for unmaintained Gentoo areas. They are not actually
> maintaining the things, but motivating users to work on those areas and
> possibly thanks to those actions the team gets out overtakers overview
Again, another great idea of something we should implement and move
towards motivating others to help us in keeping the tree sane and up to
> scripters, writing all those fancy tools we could use to do above tasks
Not sure if this needs to be its own split out team, or that those that
join the other areas would already have some of those abilities, or
someone in that team already would.
> all of us should provide help and support to fellow devs when they have
> some migration up ahead, and we should promote that they should ask us
> first before trying to do some mass changes
Definitely, and I think we need to expand a bit more on this one, with
regards to big changes and involving QA.
> So what do ya think?
A lot of great ideas. We should probably come up with some well
defined roles for each group, like we do for treecleaners, that expand
upon the above ideas.
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com