Want to help out with the Fedora Project, but can't code a lick? Well
fear not my dear friends. There are many ways you can help the cause
and today I am pleased to announce a brand new way you can help
contribute. Join the Fedora BugZappers!
Who are the BugZappers?
The BugZappers, (http://www.fedoraproject.org/wiki/BugZappers) are the
official triage team of the Fedora Project. The main goal of the team
is to triage, or do a first pass, of bugs in Bugzilla and ensure that a
number of parameters are satisfactorily met. Basically what that means
is that the BugZappers will go through bugs as they come in and try and
make sure the bugs are valid (i.e. not a duplicate), sane and contain
enough information to be escalated to developers. If you have ever
reported a bug and wondered why it took so long to get fixed, well then
BugZappers is the right project to join.
Tell Me More!
The BugZappers aim to be the primary line of defense for Fedora Quality
Assurance (QA). The BugZappers will begin running Bug Day events, every
alternating week, usually on Wednesdays. Bug Day events are when the
team gets together to concentrate our focus on certain subsections of
the project which need work. Triage should continue on though, and
remember kids, "Every day should be a Bug Day!"
So, if you are tired of hearing complaints about things not working,
pieces being broken or just plain want to help Fedora be the best dang
Fedora it can be, then join the BugZappers team and help the developers
make the most of their coding time. It's fun, it's easy, you don't need
much experience to start and we are willing to show you the path of the
righteous, should you choose to accept this mission.
What's in it for me?
Glad you asked. First of all there is candy. OK, so there is no candy,
but there is free stuff. The team is working on some giveaways and run
contests during Bug Day events. You also get to work on triaging things
that annoy you first, so your problems get fixed sooner; kernel problems
anyone? Also, a wise man once said, much fame and fortune come to he
who close many bugs. OK, it really wasn't a wise man buy you get the
point.
How Do I Join?
Step 1: Sign up for the mailing list at:
http://www.redhat.com/mailman/listinfo/fedora-triage-list
Step 2: Join us on IRC
We live in #fedora-bugs on Freenode
Step 3: Read/Modify/Enhance the wiki
Our wiki is located at http://www.fedoraproject.org/wiki/BugZappers .
Additionally, we have more information available on the wiki at:
http://www.fedoraproject.org/wiki/BugsReports and
http://www.fedoraproject.org/wiki/Bugs .
More content will be added as we get the project off the ground and
moving.
Also, be sure to look for our announcement of the first Bug Day event
coming soon to an Inbox near you!
Thanks,
Jack
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
See the commentaries in the images in attachments.
It would be very, very interesting that these alterations are made until
next release of Fedora Core.
Thanks!!!
- --
+================================================+
RODRIGO PADULA DE OLIVEIRA
(o- MESTRANDO EM ENGENHARIA DE SISTEMAS
//\ LINHA DE PESQUISA: BANCO DE DADOS
V_/_ COPPE/UFRJ
PostgreSQL - PHP - WML - Linux
+================================================+
Embaixador do Fedora Core no Brasil
http://www.projetofedora.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFD/LgZPg3HAC1vlg4RAoWQAJ9VkSg7KmSkYRKJXgObxgQ6LynkLACePO67
ag4tDAHidw+7edObxsGTFFs=
=GjC2
-----END PGP SIGNATURE-----
Hello there,
We're on the last thousand of package updates before Fedora Core 5 hits
the shelves of FTPs and torrent trackers everywhere! Meanwhile, bugs are
creeping into bugzilla and trying to slow down developers from making
the best Fedora release ever.
Until the end of this week, let's provide special attention to nautilus
bugs. There are 137 open bugs now; here is the link to Red Hat bugzilla
query:
https://bugzilla.redhat.com/bugzilla/buglist.cgi?query_format=advanced&shor…
Please go through them and test on FC5testX/rawhide to see if they are
still valid. If it works for you, close as WORKSFORME and ask the
reporter to reopen if it's still an issue for him after updating to
FC5testX/rawhide. However, don't rush with this as some bugs are
triggered only in unusual cases (especially segfaults). Sometimes it
might not happen to you, but the bug it's still there.
If bug is still valid, would be useful to search upstream for the same
bugs and add an External Bugzilla Reference to GNOME Desktop bug if
found. Here's the link:
http://bugzilla.gnome.org/query.cgi?format=advanced
(please select nautilus* packages and click search. GNOME Bugzilla seems
down for me)
Is there anything you could do to help fixing it faster? (provide
additional info if requested by developer, testcase, screenshot etc)
Remember to add yourself as CC to all bugs you modify (including
closing), in order to get notices of further changes.
Additional info: The Fedora Bug Squad
http://fedoraproject.org/wiki/BugZappers
Success!
--
Marius Andreiana