There�s an efficient "military-like" format that should work perfectly to report an incident if adapted :

The "1) I am, 2) I see, 3) I did, 4) I ask"...

1) I am : description of the relevant background informations needed to undestand/analyse your problem :
(versions of : OS, Fink, X11, and such information)


2) I see : description of the problem itself :
(what did not work, show installation/execution failure report, maybe the config.log if needed...)


3) I did : how did I try to solve the problem (and if you think it�s important why it did not work - see 2- ) :
( removing conflicting package, re-installing some program, updating some libraries...)


4) I ask : usually straightforward (what do I want ? ):
(I want this program to work, I want to remove that program, I want to ...)
Optional : one can describe here what he�s planing to do next if he does not receive advices, or his hypothesis about the causes of the problem.



Well, I guess this proposal could be expanded and maybe detailed more, but I think this "1) I am, 2) I see, 3) I did, 4) I ask" principle could be useful.




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to