Hi all,

I want to help in the process of cleaning all those old bugs which I think
only are doing noise, because the software has evoluted. Many of them are
simply not closed bugs.

My idea is contact with bug submitters from older bugs to newer. This can be
done semi-automatically. I know some work has been done in order to contact
maintainers. Perhaps contacting submitters would give better results.

My suggestion is doing it for all bugs until June 1999 (18 months) and later
in a month by month basis, allways maintaining the limit of 18 months.

I've written a draft of a procedure in which work. It follows:

----------------------- cut -----------------------
Old Bugs Cleaning
-----------------

1.- Get a group of bugs. (One month, one year, one hundred...)
2.- Send email to every bug-sender with a text like this:
    Subject: Debian bug #xxxxx
    Dear Sir:
    We want to thank you your help to the development effort of Debian
    with the bug(s) you have submitted.

    The bug #xxxxx has been in our Bug Tracking System during a long time,
    during which many changes have happen to the software.

    At the bottom of this message your bug is included.

    May you confirm us that this bug must remain open or must it be closed?

    If you consider it must remain open, do you have more information
    to give to our developers which can help to correct this bug?

    One more time we want to thank you for your colaboration with Free
    Sofware.

    Yours sincerally,
    Debian Quality Assurance Team
    .......
3.- Send mail to maintainers:
    If the user has answered forward answer to maintainer with recomendation
    to close if this is the choice of the user.
    If the user has not answered send recomendation to close.
    If the mail has been bounced send recomendation to close.
--------------------- cut -------------------------

As I stated this is only a draft and I have more questions than answers:
   - Must this emails saved in the BTS?
   - Must this emails be cc-ed to maintainers?
   - What to do when a submitter say bug is still open but don't give any
     other info?

P.S.: If you are thinking you don't remember my name as developer you are
right. I'm an applicant in the New Maintainers queue, so:
    - I may be wrong. I don't know every aspect of debian BTS or QA Team.
    - I would be happy of work on this with any developer which account I
      think will be necessary in order to obtain info from BTS for a period.


Cheers,
-- 
Luis Arocha Hernandez "Data" <[EMAIL PROTECTED]>, Islas Canarias - Spain
        _                      o__o__  o__      O_         O        O  
      o</                      ,>/,>/  ,>/     ,//        ,/\     ,/|  
_____()_\()___________________()_()_\(()_\()__()_\()_____()_<()__()_<()____

Attachment: pgptgkrzyY20i.pgp
Description: PGP signature

Reply via email to