Difference between revisions of "Netiquette for ns-3-users mailing list"
(→Ns-3 Users Netiquette)
m (Vedranm moved page Ns-3-users-netiquette to Netiquette for ns-3-users mailing list: Wiki page name cleanup)
Revision as of 14:36, 10 February 2013
Ns-3 Users Netiquette
Ns-3 Users is a Google group, i.e., a very wide mailing list. There is no explicit moderation policy beside some spam filters. Hence, all the posters shall behave nicely and follow the general Internet netiquette rules.
The Internet Netiquette rules are summarized in RFC 1855. Read it and understand it.
Moreover, the following applies to ns-3 Users group in particular:
- ns-3 is an open-source simulator. Very few people are paid to develop it and, more specifically, to post on ns-3-users. Answers/discussions are on a best effort basis, and it may not be possible to respond to everything.
- If you don't get a reply to your post in a reasonable time (more or less one week) you may politely bump your previous post; however, see the above point.
- ns-3 users are presumed to have C++ or Python coding skills. Post your questions *after* trying your best to fix the issue. If you have very basic C++ problems the reply might be not so pleasant.
"Trying your best to fix the issue" includes (but is not limited to):
- Do not post code. Use a pastebin to share any non-trivial length of code (if needed) and include a link.
- Be precise in the topic/subject line. "Need help, plz" is not a good topic.
Also, the following two very important points are mandatory:
- Do *not* search for help if your problem is about a task assigned for a class by your professor. He/she might follow the group as well.
- If your problem is not trivial and you found the solution, spend 10 minutes to write a HowTo or to send us a documentation patch. Please also follow up on the ns-3-users group with your solution.
HowTo formatting is the very same as the ones here: http://www.nsnam.org/wiki/index.php/HOWTOs Please edit the wiki yourself (contact the wiki maintainer if you need an account), post documentation patches to the tracker, or send the patch or update to the documentation maintainer.