[gentoo-qa] Project layout (what should we do)

[gentoo-qa] Project layout (what should we do)

[Tomáš Chvátal]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have this idea of what areas we as QA should work:

[tinderbox]
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)

[daywatch/nightwatch]
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 :])

[amish]
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/...).

[treecleaners]
Guys responsible for maintaining profiles and removing packages that
in long-term fails to meet up QA standards.

[overtakers]
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

[backbone]
scripters, writing all those fancy tools we could use to do above tasks

[QA]
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

So what do ya think?

Cheers

Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvQJgcACgkQHB6c3gNBRYeqSgCfZpA/QgMCcejiDwnwPh13BvBp
cKoAn3OM0Hht7hCGR0XP9iLaKsv4dXJ0
=6cg7
-----END PGP SIGNATURE-----

Re: [gentoo-qa] Project layout (what should we do)

[Samuli Suominen]

On 04/22/2010 01:33 PM, Tomáš Chvátal wrote:
> I have this idea of what areas we as QA should work:
> 
> [treecleaners]
> Guys responsible for maintaining profiles and removing packages that
> in long-term fails to meet up QA standards.

treecleaners is mostly for maintainer-needed@ packages, and for bugs
where maintainer has ACK'd the removal (or there has been a general
consensus the package is no good). so that's the ebuild aspect.

profiles in other hand have been responsibility of the release@ team,
but since that hasn't lately been really the case... qa@ has been taking
care of it.

my point being: what does treecleaners have to do with profiles?

Re: [gentoo-qa] Project layout (what should we do)

[Tomáš Chvátal]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 22.4.2010 13:49, Samuli Suominen napsal(a):
> On 04/22/2010 01:33 PM, Tomáš Chvátal wrote:
>> I have this idea of what areas we as QA should work:
>>
>> [treecleaners]
>> Guys responsible for maintaining profiles and removing packages that
>> in long-term fails to meet up QA standards.
> 
> treecleaners is mostly for maintainer-needed@ packages, and for bugs
> where maintainer has ACK'd the removal (or there has been a general
> consensus the package is no good). so that's the ebuild aspect.
> 
> profiles in other hand have been responsibility of the release@ team,
> but since that hasn't lately been really the case... qa@ has been taking
> care of it.
> 
> my point being: what does treecleaners have to do with profiles?
> 
Well basicaly i was not sure under what part it fits best.
And i usually cleanup stuff there when i do treecleaning thus i placed
it under them. Basicaly only thing relevant to the outsider should be
"QA is working on profiles" and not really care what subproject is
working on it.

The leveling i wrote here is just for some visual split to see where we
need to get "recruits" :]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvQPsAACgkQHB6c3gNBRYc0dQCgrDcPiL4wkPBeh+kYoi7NdZ2M
8GEAnjNxeHCXjoF9WaWjO7z0VvqVbB7M
=YnPI
-----END PGP SIGNATURE-----

Re: [gentoo-qa] Project layout (what should we do)

[Mark Loeser]

[-- Attachment #1: Type: text/plain, Size: 3036 bytes --]

Tomáš Chvátal <scarabeus@gentoo.org> said:
> [tinderbox]
> 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:

http://git.overlays.gentoo.org/gitweb/?p=proj/flameeyes-tinderbox.git;a=summary

Having more people run this on different archs and that would be
awesome.

> [daywatch/nightwatch]
> 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.

> [amish]
> 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.

> [treecleaners]
> 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
the profiles.

> [overtakers]
> 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
date.

> [backbone]
> 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.

> [QA]
> 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.

-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]