This is the process for dealing with EurekaLog bug reports generated by
ModesXML clients:

(1) Report and ELF file etc received on [email protected] address.
(2) If ELF generated by a member of DevComm/SDG, they should check against the
tasklist, and either create a new bug report or amend an existing one.  In
either case, the bug report should refer to the ELF having been sent.
(3) AG (or ultimately a.n.other volunteer) will carry out (2) for any ELFs sent
in by 'real' users or non-SDG members.  AG/a.n.other will also keep the
submitting user informed about progress.
(4) AG files the ELF (or ELFs if more than one) on the gopher folder as
explained below.

The gopher site is all under gopher://sdf.lonestar.org/1/users/tyneside, within the 'modesbugs' folder.  Here you will find three folders:

identified - open bugs, matched against a corresponding tasklist report (possibly a newly-created one)

new - temporary space for ELFs before they have been investigated further (ie before stage (2) above)

fixed - where ELFs for fixed bugs will be dumped (until my gopher quota is full up, then they'll be removed)

Within 'identified', folders are simply numbered with reference to the tasklist
bug report.  Within these subfolders, there will either be a clutch of
eurekalog files (ELF, INI/XINI and PNG screenshot), or there may be further
subfolders for each eurekalog submission (if there has been more than one),
named after datte/time of the email.  Programmers can either go back to the
relevant email(s) for background information, or readme files could be created
alongside the ELFs if more convenient.

You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.