|
|
Sponsored Content
Contact Us
Post Here to Contact Site Administrators and Moderators
forum rules
Post 30521 by Kelam_Magnus on Wednesday 23rd of October 2002 11:47:47 AM
10-23-2002
policing ourselves makes the site better.
First let me say, if someone were to read the impetus for the creation of this site, they would understand this site is for the advancement of our KNOWLEDGE of UNIX for the WORKPLACE and for HOME USERS. Practical knowledge to make our jobs easier and for personal advancement of individual knowledge.
Second, doing someone's homework for them is counter-productive and in direct opposition to Neo's reason for creating this site. I would go so far as saying it is tantamount to CHEATING. Like having a Dad do his child's homework. (( Don't take this as any reflection on the intellect of the users )) The person doesn't LEARN, they only imitate what someone has told them the answer is.
Now, as a non-moderator person, let me say that when I see blatant abuse of the no homework policy, I will speak up. Regarding posts that are borderline, I usually give a gentle warning and may give a few hints to the answer if the user is asking politely. Usually posters understand and it isn't a big deal. However, occasionally there are a few who take offense, but only a very few.
I personally don't think it is wrong for non-moderators to take active participation in this site. We are the "neighborhood watch" for this forum.
I have been posting here for over a year now, and I consider this issue to be a matter of everyone policing everyone. As long as it remains civil, I don't see any problem with it.
Thanks for asking.
Second, doing someone's homework for them is counter-productive and in direct opposition to Neo's reason for creating this site. I would go so far as saying it is tantamount to CHEATING. Like having a Dad do his child's homework. (( Don't take this as any reflection on the intellect of the users )) The person doesn't LEARN, they only imitate what someone has told them the answer is.
Now, as a non-moderator person, let me say that when I see blatant abuse of the no homework policy, I will speak up. Regarding posts that are borderline, I usually give a gentle warning and may give a few hints to the answer if the user is asking politely. Usually posters understand and it isn't a big deal. However, occasionally there are a few who take offense, but only a very few.
I personally don't think it is wrong for non-moderators to take active participation in this site. We are the "neighborhood watch" for this forum.
I have been posting here for over a year now, and I consider this issue to be a matter of everyone policing everyone. As long as it remains civil, I don't see any problem with it.
Thanks for asking.
Last edited by Kelam_Magnus; 10-23-2002 at 01:01 PM..
|
|
3 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Possible new rule for the "forum rules" list:
<UL>
<LI>Include as many pertinent details as possible in your post. Useful information usually includes: Vendor and version of Unix you are using, hardware platform, kernel version (if applicable). For hardware related questions include model... (1 Reply)
Discussion started by: PxT
1 Replies
2. What is on Your Mind?
After reading the FAQ for the first time, I noticed Rule # 14 :
:D:D:D
Anyways, I hope to make more use of this forum in future, and also to help others.
Regards
Ook. :) (0 Replies)
Discussion started by: The_Librarian
0 Replies
3. Post Here to Contact Site Administrators and Moderators
Hi, Admin,
because my English is very poor, So I don't understand very well about 4th of Forum Rules, that is “Do not 'bump up' questions if they are not answered promptly. No duplicate or cross-posting and do not report a post”.
My question is:
if I created a new thread, and some people reply... (3 Replies)
Discussion started by: weichanghe2000
3 Replies
LEARN ABOUT DEBIAN
jekyll
JEKYLL(1) User Commands JEKYLL(1) NAME
Jekyll - is a blogaware, static site generator. USAGE
jekyll # . -> ./_site jekyll <path to write generated site> # . -> <path> jekyll <path to source> <path to write generated site> # <path> -> <path> jekyll import <importer name> <options> # imports posts using named import script Configuration is read from '<source>/_config.yml' but can be overridden using the following options: OPTIONS
--file [PATH] File to import from --dbname [TEXT] DB to import from --user [TEXT] Username to use when importing --pass [TEXT] Password to use when importing --host [HOST ADDRESS] Host to import from --site [SITE NAME] Site to import from --[no-]safe Safe mode (default unsafe) --[no-]auto Auto-regenerate --server [PORT] Start web server (default port 4000) --no-server Do not start a web server --base-url [BASE_URL] Serve website from a given base URL (default '/' --[no-]lsi Use LSI for better related posts --[no-]pygments Use pygments to highlight code --rdiscount Use rdiscount gem for Markdown --redcarpet Use redcarpet gem for Markdown --kramdown Use kramdown gem for Markdown --time [TIME] Time to generate the site for --[no-]future Render future dated posts --permalink [TYPE] Use 'date' (default) for YYYY/MM/DD --paginate [POSTS_PER_PAGE] Paginate a blog's posts --limit_posts [MAX_POSTS] Limit the number of posts to publish --url [URL] Set custom site.url --version Display current version AUTHOR
This manual page was written by Youhei SASAKI <uwabami@gfd-dennou.org>, for the Debian GNU/Linux system(but may be used by others). Jekyll 0.11.2 May 2012 JEKYLL(1)