On Wed, 27 Feb 2013 04:02:26 -0500 William Morris wrote:
>I am looking for input from current Bugzappers, as we all know our
>group is being folded into the QA group. I want to know first off who
>is still around. I know that we are an inactive group right now, but
>that is okay.
On 02/27/2013 03:02 AM, William Morris wrote:
Hi all,
I am looking for input from current Bugzappers, as we all know our
group is being folded into the QA group. I want to know first off who
is still around. I know that we are an inactive group right now, but
that is okay.
I am also
Em 27-02-2013 09:02, William Morris escreveu:
Hi all,
I am looking for input from current Bugzappers, as we all know our
group is being folded into the QA group. I want to know first off who
is still around. I know that we are an inactive group right now, but
that is okay.
I am also
I am new here (at least relatively :) ).
didn't contribute yet but hope to start soon as time permits.
About your questions I don't have any opinions yet.
Moshe
On Wed, Feb 27, 2013 at 4:02 AM, William Morris wrote:
>
>> Hi all,
>>
>> I am looking for input fro
am looking for input from current Bugzappers, as we all know our group
> is being folded into the QA group. I want to know first off who is still
> around. I know that we are an inactive group right now, but that is okay.
>
> I am also looking for input on a couple of fronts. First is
On 27 February 2013 09:02, William Morris wrote:
> Hi all,
>
> I am looking for input from current Bugzappers, as we all know our group
> is being folded into the QA group. I want to know first off who is still
> around. I know that we are an inactive group right now, but that is
Hi all,
I am looking for input from current Bugzappers, as we all know our group is
being folded into the QA group. I want to know first off who is still
around. I know that we are an inactive group right now, but that is okay.
I am also looking for input on a couple of fronts. First is that I
On Fri, Jan 25, 2013 at 10:13 AM, Kamil Paral wrote:
> I'm not sure it's wise to increase privileges immediately after the welcome
> letter (was it
> meant this way?).
The bugzappers have been doing it that way since I joined. It was
explained to me when I joined that anythi
he didn't
volunteer. I belatedly apologize to brother johnson for that.
> I can draft up the specific changes later, but does this broad outline
> sound reasonable to everyone?
Sounds reasonable to me +1
Speaking only in regard to the bugzappers, a change like this has been
long o
welcome!' and add you to the QA FAS group and send you a little
introductory mail. We could probably give editbugs privs to people in QA
and add all current members of bugzappers/proventesters into the qa
group.
I dont know if you had been hired at the time when we decided to put
down that group i
27; and we say
> > 'welcome!' and add you to the QA FAS group and send you a little
> > introductory mail. We could probably give editbugs privs to people in QA
> > and add all current members of bugzappers/proventesters into the qa
> > group.
>
> I dont know if
;hi, I'd like to join' and we say
> 'welcome!' and add you to the QA FAS group and send you a little
> introductory mail. We could probably give editbugs privs to people in
> QA
> and add all current members of bugzappers/proventesters into the qa
> group.
The w
On 01/25/2013 01:24 PM, Bob Lightfoot wrote:
Hash: SHA1
So Adam let me see if I get it straight.
During my hiatus from testing {known as the F17 acceptance cycle} you
mothballed the ProvenTesters and BugZappers programs, but left some
stray references to them laying around the wikisphere
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So Adam let me see if I get it straight.
During my hiatus from testing {known as the F17 acceptance cycle} you
mothballed the ProvenTesters and BugZappers programs, but left some
stray references to them laying around the wikisphere.
You want to
#x27; process - much like those two, where you just
send a mail to the list saying 'hi, I'd like to join' and we say
'welcome!' and add you to the QA FAS group and send you a little
introductory mail. We could probably give editbugs privs to people in QA
and add all curre
hink it might be nice if we created a
generic QA 'onboarding' process - much like those two, where you just
send a mail to the list saying 'hi, I'd like to join' and we say
'welcome!' and add you to the QA FAS group and send you a little
introductory mail.
Hi all,
I would like to join the Fedora Bugzappers team and have applied for the
same. I have been using Fedora (as my main work system) since late 2009
and I believe I am ready to contribute to the project in my own small
way. I have some experience in C programming, although I have done any
Good afternoon,
I am looking very forward in joining the BugZappers team. I have
experience in Linux since the days of Slackware Linux as well as Fedora
going back to Fedora Core 2. My experience is in web server
administration (Apache Server, mySQL), and I am getting my feet wet with
C
On 07/06/2011 07:40 PM, Athmane Madjoudj wrote:
> Hello,
>
> There's an Template:Autolang loop error in BugZappers page which makes
> the first paragraph appears in Spanish.
>
> Unfortunately I'm not familiar with multi-lang wiki page
>
> See: http://fedoraproject
Hello,
There's an Template:Autolang loop error in BugZappers page which makes
the first paragraph appears in Spanish.
Unfortunately I'm not familiar with multi-lang wiki page
See: http://fedoraproject.org/wiki/BugZappers
--
Athmane Madjoudj
--
test mailing list
test@lists.fedorap
c) in #fedora-meeting.
https://fedoraproject.org/wiki/BugZappers
Come on by, and give us a hand!
Thanks,
-Robyn
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Dne 23.5.2011 06:55, Eric Wright napsal(a):
> Name: Eric
> Experience: Four years with Linux, only use it now. Computer Science
> student.
> Interested in helping in my spare time, probably a few minutes a day.
>
Awesome! Please take a look at https://fedoraproject.org/wiki/
Name: Eric
Experience: Four years with Linux, only use it now. Computer Science
student.
Interested in helping in my spare time, probably a few minutes a day.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Hi, all my beloved BugZappers!
so this is the moment we all eagerly waited for! This is the version 1.0
of bugzilla-triage-scripts. It should come to you just by checking for
updates in about:addons in your Firefox.
The minimal requirement is Firefox >= 4.0.1 (either in Fedora 15, or
f
Hi, all my beloved BugZappers!
If you have Firefox >= 4.0.1 (either in Fedora 15, from spot's F13/F14
repo at http://repos.fedorapeople.org/repos/spot/firefox4/, or using the
upstream binary from http://www.mozilla.com/cs/firefox/), please try to
install
https://fedorahosted.org/
Hi,
sorry for very very late (probably too late for most of you)
announcement, but we will make a brief meeting for all BugZappers who
are willing to come to #fedora-meeting in twenty minutes (21:00 UTC (4
PM EST/1 PM PST)).
See you there,
Matěj
--
test mailing list
test
A quick reminder that we have a Bugzappers meeting scheduled for today
at 2100 UTC (that's 3hrs 20mins from now). Sorry, I don't have an agenda
right now, someone else may supply one. I may only be partially present
as I'm going out tonight. thanks!
--
Adam Williamson
Fedora QA C
This from Matej, who tried to send it a while ago, but who appears to be
unable to post to the mailing list for some reason (I blame Canonical):
Some of leading members of our glorious BugZappers crew presented some
unreasonable requirements, like they would to sleep sometimes and stuff,
but in
On 12/06/2010 11:41 PM, Adam Williamson wrote:
> FESCo can do that. QA can't.
Step ahead of you Adam ;)
I've have open a ticket with FESCO and proposed several improvements
which they are reviewing and and will take up on next meeting.
If applied it will most likely apply to [1].
However I'm n
On Mon, 2010-12-06 at 14:30 -0500, Jan Wildeboer wrote:
> A mantainer who doesn't care about the bugs in his package may be
> everything - but not a maintainer. It is that simple. Maintaining a package
> means caring, not doing sth once in a while.
again, out of the scope of the QA list. The pro
On Mon, 2010-12-06 at 19:46 +0100, Michael Schwendt wrote:
> On Mon, 06 Dec 2010 10:11:25 -0800, Adam wrote:
>
> > > Too many tickets, too many reminders. After six months, the reporter maybe
> > > doesn't even work on the same software anymore.
> >
> > 'I don't use this any more, so let's leave
On Mon, 2010-12-06 at 18:45 +, "Jóhann B. Guðmundsson" wrote:
> On 12/06/2010 06:39 PM, Adam Williamson wrote:
> > the maintainers do get mails. there's not a lot we can do about
> > maintainers who simply don't deal with their bugs.
>
> Yes we can.
>
> For example we can implement a policy t
On Mon, 2010-12-06 at 18:39 +, "Jóhann B. Guðmundsson" wrote:
> Changing bug status to NEEDINFO from reporter should only be done when
> information contained within the bug is incomplete, and additional
> information from the original submitter is required to confirm the bug
> so could the
On Mon, 2010-12-06 at 16:50 +0100, Michael Schwendt wrote:
> On Mon, 06 Dec 2010 10:08:35 -0500, James wrote:
>
> > The alternative is silently
> > closing EOL'd bugs. I don't think silently closing bugs works well with
> > the principle of least surprise.
>
> The alternative is to communicate w
On 09:46:18 pm Monday, December 06, 2010 Jóhann B. Guðmundsson wrote:
> On 12/06/2010 06:11 PM, Adam Williamson wrote:
> > They don't have to. If you filed a bug that you can't follow up on any
> > more, in the general case, you can just say so, and close it. In this
> > case, you don't have to lif
A mantainer who doesn't care about the bugs in his package may be
everything - but not a maintainer. It is that simple. Maintaining a package
means caring, not doing sth once in a while.
Jan
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailm
On Mon, 06 Dec 2010 10:11:25 -0800, Adam wrote:
> > Too many tickets, too many reminders. After six months, the reporter maybe
> > doesn't even work on the same software anymore.
>
> 'I don't use this any more, so let's leave it closed'. Takes three
> seconds.
It takes even less time to delete t
On 12/06/2010 06:39 PM, Adam Williamson wrote:
> the maintainers do get mails. there's not a lot we can do about
> maintainers who simply don't deal with their bugs.
Yes we can.
For example we can implement a policy that strip their packaging rights
and orphan the package, if no one claims the p
On 12/06/2010 06:11 PM, Adam Williamson wrote:
> They don't have to. If you filed a bug that you can't follow up on any
> more, in the general case, you can just say so, and close it. In this
> case, you don't have to lift a finger, because the bug will get
> automatically closed soon anyway. That'
On Sun, 2010-12-05 at 12:18 +0200, cornel panceac wrote:
> however, warning the reporter that the bug is closed is a good thing,
> imho. but i also believe that, when the maintainer didn't ever
> commented the bug report, he should receive a mail too, and this, as
> michael schwendt suggested, sho
; > Is it really so bad? This gentle reminder simply gives the reporter the
> > opportunity to let us know whether the unclosed bug is still present in
> > a later release. I think this info is very useful for the maintainers
> > and bugzappers. Once every 6 months...
>
On 12/06/2010 03:50 PM, Michael Schwendt wrote:
> The earlier automated (!) NEEDINFO request could also be used to point at
> a bug reporting HOWTO once more. And to repeat the request for a comment
> on the reproducibility and how to reproduce a problem.
Probably better to point the reporter to t
On Mon, 06 Dec 2010 10:08:35 -0500, James wrote:
> The alternative is silently
> closing EOL'd bugs. I don't think silently closing bugs works well with
> the principle of least surprise.
The alternative is to communicate with the reporter much earlier.
1) When there is a stable update of the pa
"Jóhann B. Guðmundsson" wrote:
> Ye must realize that maintainers will shit all over reporters claiming
> that they do not respond reports and what not by doing what the
> bugzapper script or abrt is doing.
If you're not willing to look over bug reports for /your/ bugs that are
fixing to be CLOSE
On Mon, 2010-12-06 at 13:56 +, "Jóhann B. Guðmundsson" wrote:
> On 12/06/2010 01:16 PM, James Laska wrote:
> > On Sun, 2010-12-05 at 00:42 +, "Jóhann B. Guðmundsson" wrote:
> >> On 12/05/2010 12:06 AM, Brendan Jones wrote:
> >>> Is it really so bad?
> >> Yes and reporters should be able to
On 12/06/2010 01:16 PM, James Laska wrote:
> On Sun, 2010-12-05 at 00:42 +, "Jóhann B. Guðmundsson" wrote:
>> On 12/05/2010 12:06 AM, Brendan Jones wrote:
>>> Is it really so bad?
>> Yes and reporters should be able to opt out from this process chooses
>> they do so.
> They can. Turn off email
On Sun, 2010-12-05 at 00:42 +, "Jóhann B. Guðmundsson" wrote:
> On 12/05/2010 12:06 AM, Brendan Jones wrote:
> > Is it really so bad?
>
> Yes and reporters should be able to opt out from this process chooses
> they do so.
They can. Turn off email notification for your bugzilla account, or
d
On 12/05/2010 11:11 AM, Alexander Kurtakov wrote:
> On 01:04:02 pm Sunday, December 05, 2010 Jóhann B. Guðmundsson wrote:
>> On 12/05/2010 12:06 AM, Brendan Jones wrote:
>>> Is it really so bad?
>> Yes and reporters should be able to opt out from this process chooses
>> they do so.
> Well, how abou
On 01:04:02 pm Sunday, December 05, 2010 Jóhann B. Guðmundsson wrote:
> On 12/05/2010 12:06 AM, Brendan Jones wrote:
> > Is it really so bad?
>
> Yes and reporters should be able to opt out from this process chooses
> they do so.
Well, how about giving maintainers the power to opt out from having
> > There are so many open bugs - anything which helps us zappers out to
> > maintain some kind of continuity is very welcome in my book. What's a
> > few emails every 6 months?
>
> It isn't "a few".
>
i had many f12 bugs which double filled my inbox at f12 end of life. this
happened before with p
On Sun, 05 Dec 2010 10:58:25 +1000, Brendan wrote:
>
>
> On 12/05/2010 10:30 AM, Michael Schwendt wrote:
> > For issues that persist, a different user will [need to] open a new
> > ticket. And who will pay attention and notice that it's the same issue
> > that was closed WONTFIX N*6 months ago?
On 12/05/2010 10:30 AM, Michael Schwendt wrote:
> For issues that persist, a different user will [need to] open a new
> ticket. And who will pay attention and notice that it's the same issue
> that was closed WONTFIX N*6 months ago?
Understood - but there is a lot of useful info captured in the e
On 12/05/2010 12:06 AM, Brendan Jones wrote:
> Is it really so bad?
Yes and reporters should be able to opt out from this process chooses
they do so.
JBG
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
t us know whether the unclosed bug is still present in
> a later release. I think this info is very useful for the maintainers
> and bugzappers. Once every 6 months...
Too many tickets, too many reminders. After six months, the reporter maybe
doesn't even work on the same software anymor
info is very useful for the maintainers
and bugzappers. Once every 6 months...
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On 12/04/2010 03:15 AM, Adam Williamson wrote:
> he exact same policy and process has been followed for multiple
> releases now, it shouldn't be a surprise to anyone.
I'll go through my EOL list couple of releases back to see when the
first EOL bug set me to needinfo status and closed the bug.
W
ys asks for feedback before doing
it. See
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora14#Fedora_12_EOL_Warning:
"Actions to take on all bugs selected in query above:
Add comment
Set bug to NEEDINFO Reporter "
> Ye must realize that maintainers will shit all ove
Can someone from the bugzapper team please explain to me why reporters
are being flagged with needinfo on their abrt filed report before their
bugs are EOL'ed without the maintainer actually requesting any needinfo
from the reporters?
bug 548359 case in point
What|Removed
# Fedora Triage Team Meeting
# Date: 2010-10-12
# Time: 15:00 UTC
# Location: #fedora-meeting on irc.freenode.net
There is nothing on the meeting agenda page [1], however, we have not
had a meeting in a few weeks so we will be holding one today. If you
have a topic or anything specific you would l
Hi
My name is mark west and I sent a introductory email requesting to
become part of the Bugzappers team. I would really like to get involved
but I would definitely need some mentoring, is their someone who could
point me in the right direction. I am a quick learn and am confident in
my
Hi, folks. Once again, there's a meeting slot tomorrow at the usual
time, 2010-08-31 15:00 UTC. Once again, there's nothing new on the
agenda page -
https://fedoraproject.org/wiki/BugZappers:meeting-agenda-list . Again,
I'll be around in the morning, though, just in case. If anyone would
like to di
Hi, folks. There's a meeting slot tomorrow at the usual time, 2010-08-24
15:00 UTC. There's nothing new on the agenda page -
https://fedoraproject.org/wiki/BugZappers:meeting-agenda-list - and I
can't think of any particularly pressing topics, so we may not need to
have a meeting. I'll be around in
On Tue, Aug 17, 2010 at 10:31 AM, Adam Williamson wrote:
> Event: Fedora Bug Triage Meeting
> Date: 2010-08-17
> Time: 15:00 UTC
> Location: #fedora-meeting on irc.freenode.net
>
> Agenda Items:
> https://fedoraproject.org/wiki/BugZappers:meeting-agenda-list
>
> If anyone has an additional topic t
Event: Fedora Bug Triage Meeting
Date: 2010-08-17
Time: 15:00 UTC
Location: #fedora-meeting on irc.freenode.net
Agenda Items:
https://fedoraproject.org/wiki/BugZappers:meeting-agenda-list
If anyone has an additional topic they would like discussed, please
reply to this email.
= Agenda =
* triag
Event: Fedora Bug Triage Meeting
Date: 2010-07-27
Time: 15:00 UTC
Location: #fedora-meeting on irc.freenode.net
Agenda Items:
https://fedoraproject.org/wiki/BugZappers:meeting-agenda-list
If anyone has an additional topic they would like discussed, please
reply to this email.
= Agenda =
* triag
Event: Fedora Bug Triage Meeting
Date: 2010-07-06
Time: 15:00 UTC
Location: #fedora-meeting on irc.freenode.net
Agenda Items:
https://fedoraproject.org/wiki/BugZappers:meeting-agenda-list
If anyone has an additional topic they would like discussed, please
reply to this email.
= Agenda =
* triag
=
* VERIFIED Bugzilla state
https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#VERIFIED
http://fedorahosted.org/fedora-qa/ticket/91
* triage metrics update
https://fedoraproject.org/wiki/User:Jraber
* open floor
TK009
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https
67 matches
Mail list logo
