Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 19220

Summary: The Gentoo Linux Mailing List Netiquette Guide
Product: Websites Reporter: Alex Combas <ghetto_samurai>
Component: [OLD] DocumentationAssignee: Docs Team <docs-team>
Status: RESOLVED WONTFIX    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Alex Combas 2003-04-13 00:45:48 UTC
I have a sudgestion for an improvement that could be made to the "Gentoo Linux
Mailing List Overview" document.

The following line should be added to the document:

"Before posting to any Gentoo Linux Mailing List please read this document,
especially section 3. http://www.ietf.org/rfc/rfc1855.txt"

If a more thourough guide is required, then I would be happy to try to write up
a document called "The Gentoo Linux Mailing List Netiquette Guide".

But of course, without duplicating the work of our current "Gentoo Linux Mailing
List Overview" document in anyway.
Comment 1 Daniel Armyr 2003-04-28 12:00:42 UTC
In response to comments about the excessive volume of mail on the -dev list, I propose an addition to the description of said list:

-General Gentoo developer discussion mailing list
+Discussion list devoted to the development and extension of Gentoo. 
+If you have a problem with some component you are not actively developing, 
+feel free to adress the gentoo-user list.

This is probably a bit too long, but it is perhaps a start.
//Daniel Armyr

PS I hope you don't mind me hijacking your bug. I felt it was related. DS
Comment 2 Wesley Leggette 2003-07-17 01:00:06 UTC
How about:

-General Gentoo developer discussion mailing list
+Discussion list devoted to the development and extension of Gentoo. 
+A forum for active developers of Gentoo Linux components. Please use 
+gentoo-user for troubleshooting requests.
Comment 3 Ken Nowack (RETIRED) gentoo-dev 2003-07-22 18:54:03 UTC
While this would be more descriptive in the overview, list usage is addressed primarily on the lists themselves. Also, requiring an RFC read just to subscribe to a list (while well intentioned in spirit) will undoubtedly scare more users off than produce a more useful list.

I've found the lists helpful and people have generally pointed me in the right direction if I was addressing the wrong list. 

Lastly, Adding a further description to the -dev list would make me have to write expanded descriptions for all the other lists. And that I'm not going to do since the current descriptions suffice to get users generally to the right area.


Marking this WONTFIX.