Community Guidelines - Guvi Data Science


IITM-DS 1 mon ago
@IITM-DSProfile is locked. Login

We insist you take a few minutes and read through GUVI's Community Guidelines. We are trying to build a community rooted in kindness, collaboration, and mutual respect. GUVI is a platform for professionals as well as complete beginners. Join hands with us in building a community where people feel welcomed and can participate, regardless of their expertise or identity. First and foremost, we request that you please be respectful when interacting with other members of the community and our moderating team.

Before we get started with the guidelines. Here is what the GUVI community enables and why the forum is created for our users.

1. GUVI is a platform where learning is the core. Learning will never be interesting and effective without a furious discussion on why and what.

2. A lot of people will get a few doubts about something while learning. We thought of giving you a place where all your doubts can be addressed and cleared.

3. We wanted to make GUVI a network where we connect students, developers, managers, HRs, etc under a single umbrella that would be beneficial for everyone.

4. We also wanted to have a single place to organize the learner's requests, suggestions, and ideas for improving the GUVI platform.

You can only actively participate in the GUVI’s Community if you are logged in; otherwise, the site is read-only. i.e. you can only browse. Use the appropriate option from Question, Discussion, Posts, Article depending on your content and purpose.

We urge you to go through the following guidelines before you start contributing to the GUVI Community.

General Guidelines for posting content on the community 

  1. All content on should be written in English.

  2. Be kind, patient, civil, and welcoming. If you happen to come across fellow community members seeking help or struggling to find a way in this community, please do come forward to support them. for example, you can also tag @IITM-DS if you are not sure about what you suggest. 

  3. Avoid spamming. Do not clutter the channels with off-topic posts. We will modify or delete posts that don't add value to the discussion.

  4. At GUVI, we are particular about posts to abide by the guidelines shared. This means posts can be removed or moved. Posts will be removed when: you post twice or thrice, share irrelevant or inappropriate posts or comments. Posts will be moved: When your post does not belong to the respective channel.  

  5. Please post content like AI, ML, DL, Data Science, Python, or any other relevant queries.

  6. Once you learn a specific answer or have gained expertise in a particular topic of discussion, please take a moment to help someone out in the Community.

  7. Before you post, please browse through the GUVI community to see if anyone has already asked the same question in a post/discussion. You can use the search feature to look for keywords, and you can narrow down your search to specific categories. You can also use the "Tags" to find related posts.

  8. If you find a post to be helpful, try “Liking” the comment or post or leave a comment. Many of our users and moderators volunteer their free time to help out on the Guvi Community.

  9. Don't solicit likes, comments, or posts. Users should like and comment when they run across something they find interesting—not for promotion.

  10. When including links, please submit the canonical URL. Avoid link shorteners.

  11. Don't be snarky. Have curious conversations; don't cross-examine. Be thoughtful and sure when you comment. Try staying within the topic and avoid deviating from the conversation or sharing irrelevant comments that may not match the post’s intention.

  12. Please don't submit the original source. If a post reports on something found on another site, submit the content or code instead of sharing the link.

  13. Code snippets are intended to provide useful code examples where necessary. Please be sure to include them wherever needed, as they will help in the understanding.

  14.  If you like a post and want to see its comments in the future, try following the post. You will be notified when you follow the post. 

  15. Always reply by mentioning the author’s name: @AuthorName

In case of any help from the moderator, kindly tag @IITM-DS. They will help you with appropriate answers immediately. 

A. Questions

If you have questions, be sure to follow the below-given guidelines. 

  1. Be clear, informative, and stick to the topic. Avoid writing incomplete or unclear questions. Try including relevant code, images, etc, and explain to the point if you are looking for help. 

  2. Avoid duplication of posts or comments. This will help you get correct responses and would not confuse users or moderators who are genuinely trying to help you. 

  3. If your answer consists of code written by another user in the same question thread, be kind to mention the user in the answer.

B. Discussions

With discussions, members can create content with a rich text editor that gives ample space to give a title and a text editor to provide additional details. This allows the members to carry out ongoing discussions with threaded replies.

  1. Kindly participate if: you have a strong interest in the post shared; if you have answers to help; if you want to tag someone who was looking for something similar or if you want to support. Make sure, it is relevant to the post and not random. 

  2. Before sharing your suggestions in the comment section, we request you to read the question or post thoroughly. Share your suggestions or opinions respectfully and if you are to appreciate what the person has shared, try mentioning the @username 

  3. If you have found the answer to the post shared, please share the link of the post as a comment by tagging the person who shared the right answer or copy-paste the answer with due credits 

  4. Be direct. Stay on point. Don’t lose yourself, or your readers, in overly wordy sentences or paragraphs.

  5. If you are to reply to a user’s comment, kindly reply with the @mention of the user’s name so that he or she is notified. 


Please login to comment.