From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- .../20110928/a4ec7217/attachment-0001.html | 177 +++++++++++++++++++++ .../attachments/20110928/a4ec7217/attachment.html | 177 +++++++++++++++++++++ 2 files changed, 354 insertions(+) create mode 100644 zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html create mode 100644 zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html (limited to 'zarb-ml/mageia-bugsquad/attachments/20110928') diff --git a/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html new file mode 100644 index 000000000..e6face780 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment-0001.html @@ -0,0 +1,177 @@ + + + + + + 
(Thanks Manuel, for improving what I wrote and thanks Dan for asking for examples.
+ 
I'll try to expand and improve this document - maybe even with screenshots - for use in the new wiki.)
+ 
+
+ 
Any suggestions (from anybody!) are welcome.
+ 
+But please don't look at the current triage guide now.
+I don't want you to concentrate on that guide, but I would like you to concentrate on what you know or learned by experience.
+Later on the triage guide can be compared with this document and they can be fused into a guide that contains the best of both  :-)  
+ 
+
+ 
Op 28-09-11 00:33, Manuel Hiebel schreef:
+
+ 
Le mardi 27 septembre 2011 à 23:08 +0200, Marja van Waes a écrit :
+
+
+ 
+
+
+
+ 
+
+ 
EASY THINGS TO BEGIN WITH:
+
+PACKAGE REQUESTS:
+
+ 
+
+
+
+ 
Search bugzilla for package requests that haven't been assigned yet
+https://bugs.mageia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=REOPENED&component=New%20RPM%20package%20request
+
+Some requesters forget to give a link to where the software can be
+found.
+
+
+ 
+ 
+
+
+ 
+
+
+ 
If they haven't given a link at all, you can ask them to give the
+upstream link to the package. If they say: it is a Mandriva package,
+you can say: not all our packagers are familiar with Mandriva, so
+please give an upstream link.
+
+
+ 
+
+
+ 
+
+
+
+ 
Or they put the link in the description field, which is good,
+but the link should also go in the URL field. Like
+https://bugs.mageia.org/show_bug.cgi?id=1067  You can copy the link to
+the url field, if you want to
+
+
+ 
+You can also complete the field RPM package, and make an precise summary
+if that is not enough (like removing: "I'd like to see this package in
+mageia"
+
+ 
and replace it
+
+ 
with "$name-of-the-package, $a very short description"
+
+ 
+
+ 
BUGS:
+
+Not all steps ar easy, you can start doing what is easy for you and leave the rest to others.
+No bugs should be assigned to a maintainer before all necessary steps are taken (unless, of course, the maintainer chooses to grab the bug)
+
+
+Step 1
+
+
+
+
+
+ 
+Look at the
+new bugs that are reported and use bugzilla to find out whether one is
+a duplicate of an existing bug. If you are not used to searching
+bugzilla: play around with it first. And don't forget to try the
+advanced options https://bugs.mageia.org/query.cgi (choose right tab:
+advanced search)
+
+
+
+ 
Step 2a
+
+Dit the reporter give the needed  basic information about the Mageia release he uses and what steps to take to reproduce the bug?
+
+ADD:(examples of reports with and without needed info)
+
+
+step 2b (often not so easy, if you don't know how to do it: leave it to others and watch what they do)
+
+Check wether the reporter gave needed backtraces, if he didn't: ask for them and tell him how to get them if he doesn't know
+
+ADD: (examples)
+
+
+Step 3
+
+
+
+
+ 
+If someone has the same version of Mandriva as you and reports a bug
+in a program you are familiar with, you can try to reproduce the bug. 
+
+
+
+
+
+ 
But often other Mageia users report that they have the same bug, so then they reproduced it.
+ 
If it can't be reproduced, than it isn't a bug and the bug should be closed
+(but please tell the user he can find help for his problem on https://forums.mageia.org/en/)
+ 
+Step 4
+
+
+ 
+
+
+ 
+You can also add a maintainer like what I do here:
+https://bugs.mageia.org/show_bug.cgi?id=2856
+
+https://bugs.mageia.org/show_activity.cgi?id=2856
+
+check the src.rpm:
+  	:src claws-mail with sophie (on irc or sophie.zarb.org)
+or	urpmq --sourcerpm claws-mail 
+
+then search the maintainer:
+	:maint claws-mail
+or 	search on the txt list: http://pkgsubmit.mageia.org/data/maintdb.txt
+
+then search the email of the maintainer: julien on the page
+http://www.mageia.org/wiki/doku.php?id=packaging#list_of_registered_people
+
+or just type the id, sometime it's work (like for misc, tmb,...),
+sometimes not (like here, there is two id) :)
+
+
+ 
OLD BUGS:
+
+
+ 
+We must check that for all 'old' bug.
+Here is a saved-search for all bug assigned to bugsquad:
+https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20not%20triaged%20%28excl%20new%20RPM%20requests%29&sharer_id=35
+
+
+
+
+ 
+
+
+ 
+
+ + diff --git a/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html new file mode 100644 index 000000000..e6face780 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/attachments/20110928/a4ec7217/attachment.html @@ -0,0 +1,177 @@ + + + + + + 
(Thanks Manuel, for improving what I wrote and thanks Dan for asking for examples.
+ 
I'll try to expand and improve this document - maybe even with screenshots - for use in the new wiki.)
+ 
+
+ 
Any suggestions (from anybody!) are welcome.
+ 
+But please don't look at the current triage guide now.
+I don't want you to concentrate on that guide, but I would like you to concentrate on what you know or learned by experience.
+Later on the triage guide can be compared with this document and they can be fused into a guide that contains the best of both  :-)  
+ 
+
+ 
Op 28-09-11 00:33, Manuel Hiebel schreef:
+
+ 
Le mardi 27 septembre 2011 à 23:08 +0200, Marja van Waes a écrit :
+
+
+ 
+
+
+
+ 
+
+ 
EASY THINGS TO BEGIN WITH:
+
+PACKAGE REQUESTS:
+
+ 
+
+
+
+ 
Search bugzilla for package requests that haven't been assigned yet
+https://bugs.mageia.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=REOPENED&component=New%20RPM%20package%20request
+
+Some requesters forget to give a link to where the software can be
+found.
+
+
+ 
+ 
+
+
+ 
+
+
+ 
If they haven't given a link at all, you can ask them to give the
+upstream link to the package. If they say: it is a Mandriva package,
+you can say: not all our packagers are familiar with Mandriva, so
+please give an upstream link.
+
+
+ 
+
+
+ 
+
+
+
+ 
Or they put the link in the description field, which is good,
+but the link should also go in the URL field. Like
+https://bugs.mageia.org/show_bug.cgi?id=1067  You can copy the link to
+the url field, if you want to
+
+
+ 
+You can also complete the field RPM package, and make an precise summary
+if that is not enough (like removing: "I'd like to see this package in
+mageia"
+
+ 
and replace it
+
+ 
with "$name-of-the-package, $a very short description"
+
+ 
+
+ 
BUGS:
+
+Not all steps ar easy, you can start doing what is easy for you and leave the rest to others.
+No bugs should be assigned to a maintainer before all necessary steps are taken (unless, of course, the maintainer chooses to grab the bug)
+
+
+Step 1
+
+
+
+
+
+ 
+Look at the
+new bugs that are reported and use bugzilla to find out whether one is
+a duplicate of an existing bug. If you are not used to searching
+bugzilla: play around with it first. And don't forget to try the
+advanced options https://bugs.mageia.org/query.cgi (choose right tab:
+advanced search)
+
+
+
+ 
Step 2a
+
+Dit the reporter give the needed  basic information about the Mageia release he uses and what steps to take to reproduce the bug?
+
+ADD:(examples of reports with and without needed info)
+
+
+step 2b (often not so easy, if you don't know how to do it: leave it to others and watch what they do)
+
+Check wether the reporter gave needed backtraces, if he didn't: ask for them and tell him how to get them if he doesn't know
+
+ADD: (examples)
+
+
+Step 3
+
+
+
+
+ 
+If someone has the same version of Mandriva as you and reports a bug
+in a program you are familiar with, you can try to reproduce the bug. 
+
+
+
+
+
+ 
But often other Mageia users report that they have the same bug, so then they reproduced it.
+ 
If it can't be reproduced, than it isn't a bug and the bug should be closed
+(but please tell the user he can find help for his problem on https://forums.mageia.org/en/)
+ 
+Step 4
+
+
+ 
+
+
+ 
+You can also add a maintainer like what I do here:
+https://bugs.mageia.org/show_bug.cgi?id=2856
+
+https://bugs.mageia.org/show_activity.cgi?id=2856
+
+check the src.rpm:
+  	:src claws-mail with sophie (on irc or sophie.zarb.org)
+or	urpmq --sourcerpm claws-mail 
+
+then search the maintainer:
+	:maint claws-mail
+or 	search on the txt list: http://pkgsubmit.mageia.org/data/maintdb.txt
+
+then search the email of the maintainer: julien on the page
+http://www.mageia.org/wiki/doku.php?id=packaging#list_of_registered_people
+
+or just type the id, sometime it's work (like for misc, tmb,...),
+sometimes not (like here, there is two id) :)
+
+
+ 
OLD BUGS:
+
+
+ 
+We must check that for all 'old' bug.
+Here is a saved-search for all bug assigned to bugsquad:
+https://bugs.mageia.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Bugs%20not%20triaged%20%28excl%20new%20RPM%20requests%29&sharer_id=35
+
+
+
+
+ 
+
+
+ 
+
+ + -- cgit v1.2.1