public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: the <the.guard@mail.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Can we get users more involved in specific testing?
Date: Fri, 15 Nov 2013 09:51:58 +0400	[thread overview]
Message-ID: <5285B67E.1020906@mail.ru> (raw)
In-Reply-To: <loom.20131114T153336-815@post.gmane.org>

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

On 11/14/13 18:48, James wrote:
> hasufell <hasufell <at> gentoo.org> writes:
> 
> 
>>>> I have often had a hard time to get some random users comment
>>>> on certain packages or even assist on some runtime tests. I
>>>> don't even know how many people use the package I maintain.
> 
>>> When a new package is installed or upgraded, there are notes
>>> that the installer is optioned (and notified upon installation)
>>> about the package.  Might it be a good idea to put your testing
>>> pleadings in the notes for those how install the package
>>> (stable, testing, experimental or overlay) about how to contact
>>> whoever related to the specific testing you want done? I. E.
>>> "eselect news" or is this a bad idea?
> 
>> I think people will not like having that in eselect news. There
>> could be a similar thing like:  eslect test-requests but the
>> question is if that will get bloated and other stuff I'm not sure
>> about.
> 
> Other than news, folks will not read it. As long as the
> announcement is short!: TESTERS_WANTED (url to details), then you
> hit the specific group, actually using the software; responding
> because they care. It affects them directly. Futhermore, they can
> quickly become the best testers, because most will use the target
> package, frequently.
> 
> 
>> The easiest thing I can think of is a project site on our wiki
>> which would also point to relevant bugs. Then again... who really
>> wants to maintain that.
> 
> This approach will fail, because it is a blunt instrument. Too many
> will get the managerie of info about things they can little for
> (zippO)....
> 
>> All other ideas are even more advanced. I wonder if we could add
>> a keyword on bugzie like REQUSERTEST... so bored users could
>> easily get a list of such bugs. But who would really use that?
> 
> Bugzilla is a wonderful, but BLUNT instrument, hence few bother
> with filling bugs.   Gentoo devs are very picky about what get's
> filed so for Gentoo issues, FOCUS on where the actual users can be
> reached, with a focused message, imho. I. E. request testers from
> the pool of folks that actually install a given package. Ya don't
> have to get folks to test things like portage, cause we all use it
> and care about it and bitch about it (that is until Zac took it
> over and slaid the deamon_portage.
> 
> A given ancillary package usually has few users, so find a way to 
> communicate with those packages_installers as the pool for
> potential testers, with whatevery instrument you like.
> Mathematically, blunt instruments fail more than 99% of the time,
> particularly the tigher the desired end result is.......
> 
> 
> Besides, most do not read the ebuild notes availabe in the 'eselect
> news', imho.
> 

A seperate mailing list?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJShbZ9AAoJEK64IL1uI2hacEEH/iJDHtzTzpI+KBJ4Ji3xrZ6z
y54y4syVVV5w61oVXoLvc9BaJYvpwtefhmabocMNZ83vbn7HXcz/vdRpqVlVH5+d
AzhNNfqvFEWotxW6zXic4sjIWqsTcZeMwsKWP7ex+q4a7bgwP51Zl2mo46QffiIw
A9zVoEl3NMJVABPHIeaQvNBN1+XXXFq+TNLCmrQ+NNm3yR99Z1rbJUjP7G1GlZAU
kn9MLFxNEs7Re7BEOtm0sDRwd1hPdwhNuQAoW6x1ljizb5yPClarmsantuBgEs8b
xsF8VJ8R0Qzli3PgVyP2iv6KsdheZ0LoQzaFm9JpMnmaS6bEo6r03ITm9Ja9LBo=
=zld0
-----END PGP SIGNATURE-----


      reply	other threads:[~2013-11-15  5:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10 14:38 [gentoo-user] Can we get users more involved in specific testing? hasufell
2013-11-10 15:22 ` gottlieb
2013-11-10 17:35 ` the
2013-11-10 21:54 ` Philip Webb
2013-11-13 23:21 ` [gentoo-user] " James
2013-11-14 14:28   ` hasufell
2013-11-14 14:48     ` James
2013-11-15  5:51       ` the [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5285B67E.1020906@mail.ru \
    --to=the.guard@mail.ru \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox