The important changes: --------------new--------------- * [This list] is not primarily a discussion forum for wishlist items for Debian. If you are looking for something to be changed within Debian, there may be more appropriate lists.
* Although the list has some developers reading it, it is not a primary forum for contacting Debian developers. It may be more appropriate to use reportbug or other tools for raising bugs on the Debian bug tracker. * If you have a problem - do try looking with a search engine to see if someone else has had similar issues. If you can't understand what you find, at least if you bring that search criterion to the list, we may have a better idea of where to start. (See also how to ask questions below.) -------------from--------------- 3. People may ask you to run commands to establish what is happening / what hardware you have. Provide the output [...] --------------to---------------- [...] Provide the full output if you can: if you can't provide full output - show what commands you ran and what output (if any) was the result after each command. The history command will help here. Likewise with logs. It may be also be appropriate for you to ask what extra information is needed / may help others solve the problem and then to try to give the extra information requested. Please DO NOT hijack other people's ongoing threads. Raise a separate email. -------------------------------- The full diff -u (minus some header cruft): ============================================================================^ @@ -1,9 +1,9 @@ -Subject: Monthly FAQ for Debian-user mailing list (last modified 20251201) -Date: Mon, 1 Dec 2025 21:13:43 +0000 +Subject: Monthly FAQ for Debian-user mailing list (last modified 20260101) +Date: Thu, 1 Jan 2026 13:08:59 +0000 -Message-ID: <[email protected]> +Message-ID: <[email protected]> @@ -21,6 +21,20 @@ from debian-project. It is also common for people to be posting here when English is not their primary language. Please be considerate. +* It is not primarily a discussion forum for wishlist items for Debian. If + you are looking for something to be changed within Debian, there may be + more appropriate lists. + +* Although the list has some developers reading it, it is not a primary + forum for contacting Debian developers. It may be more appropriate to + use reportbug or other tools for raising bugs on the Debian bug tracker. + +* If you have a problem - do try looking with a search engine to see if + someone else has had similar issues. If you can't understand what you + find, at least if you bring that search criterion to the list, we may + have a better idea of where to start. (See also how to ask questions + below.) + * The list is a Debian communication forum. As such, it is subject to both the Debian mailing list Code of Conduct and the main Debian Code of Conduct @@ -46,8 +60,8 @@ * How to ask questions and read replies. -1. PLEASE Use a subject line that means something - "I need help" is probably -not useful. "I'm having problems with the Debian 10.10 amd64 DVD image" or +1. PLEASE use a subject line that means something - "I need help" is probably +not useful. "I'm having problems with the Debian 12.12 amd64 DVD image" or similar is better - something that sets out one problem / a single issue. 2. Try and write down what steps you have taken / where you have found @@ -56,15 +70,19 @@ them. 3. People may ask you to run commands to establish what is happening / what -hardware you have. Provide the output if you can: if you can't provide the -output - show what commands you ran and what output (if any) was the result. -Likewise with logs. It may be appropriate to ask what extra information is -needed / may help others solve the problem and then to try to give the extra -information requested.. +hardware you have. Provide the full output if you can: if you can't provide +full output - show what commands you ran and what output (if any) was the +result after each command. The history command will help here. +Likewise with logs. It may be also be appropriate for you to ask what extra +information is needed / may help others solve the problem and then to try +to give the extra information requested. 4. The mailing list threads replies. Don't break the thread / raise other issues needlessly . It is as easy to begin a separate email - one per issue. +Please DO NOT hijack other people's ongoing threads. Raise a separate email, +as above + 5. If several people ask similar questions, it may be possible to summarise lots of information in one post. @@ -131,3 +149,4 @@ This FAQ is now archived as a git repository. Contributions and corrections would be welcome. Contact [email protected] for details. ============================================================================$
