❗ IMPORTANT

OFFICIAL COMMUNICATION POLICY: All course communications must take place on Ed Discussion. This policy is strictly enforced.

 

Overview

CS 6035 uses a centralized communication system to ensure efficient, organized, and academically sound interactions. This document outlines all official policies and procedures.

Table of Contents

 

Official Communication Channels

Primary Platform: Ed Discussion

All course questions, clarifications, and announcements must be posted here.

Key Features:

  • Searchable: All posts are searchable by content and post number
  • Pinned Posts: Important announcements and project threads
  • Organized: Project-specific threads for targeted discussions
  • Web-Based: No mobile app – use web interface on all devices

Access Information:

  • Platform: edstem.org (web interface only)
  • Canvas Integration: “Ed Discussion” link in Canvas navigation
  • Ed Lessons: Optional lecture content available (click book icon)

Secondary Channels

Slack is allowed for general communication only.

Permitted:

  • Study group formation
  • Conceptual/prerequisite questions
  • Technology background discussion

Not Permitted:

  • Project-specific questions
  • Direct messages to instructors or TAs

Slack Channel: #cs6035 on omscs-study.slack.com

Prohibited Communication Methods

Strictly Forbidden Channels – Zero Tolerance Policy

Using prohibited channels may result in academic integrity violations.

Do Not Use:

  • Email for course questions
  • DMs to staff for help
  • External study groups with project discussions
  • Discord or other unauthorized platforms
  • Screenshots or code sharing outside Ed Discussion

See Academic Honesty for detailed policies, monitoring procedures, and enforcement guidelines.

 

Asking Effective Questions

Step 1: Search First

Research before posting

Ask yourself: “Will the person reading this have to Google the answer? Have I already searched for it myself?”

Required Research Process:

  • Search Ed Discussion using keywords and post numbers (#123 format)
  • Check course materials (syllabus, project instructions, prerequisites)
  • Try basic online search for error messages or technical issues
  • Review pinned posts for your project

Questions to Avoid:

  • “How do I install Python?” – Answered by documentation
  • “Do you provide VMs for ___ project?” – Answered in syllabus
  • Screenshot + “I’m getting this error” – Search the error message first

Benefits of Research First:

  • Faster answers – well-researched questions get priority
  • Better learning – develop essential research skills
  • Organized Ed Discussion – reduces duplicate posts
  • Staff efficiency – more time for complex questions

Step 2: Validate Question Scope

Course Scope: Some questions fall outside Ed Discussion scope and should be researched independently.

In Scope:

  • Project-specific issues and clarifications
  • Course policy questions not covered in documentation
  • VM-specific problems with provided course materials
  • Academic integrity clarifications

Out of Scope:

  • Basic programming syntax – use online resources
  • General software installation – use documentation
  • Broad programming concepts – use textbooks/online learning
  • Overly specific debugging – use debugging tools

Common Scope Issues:

  • Screenshots only – provide context and what you’ve tried
  • Error messages – search the specific error first
  • Large code blocks – narrow down to specific issue
  • Vague questions – “Why doesn’t my code work?” is too broad

Step 3: Be Clear and Complete

Clear communication required

Complete Questions Get Complete Answers: Include all relevant context without revealing solutions.

Required Elements:

  • Clear, descriptive title – “Liveness Analysis Does Not Terminate” vs “Please Help!”
  • Specific problem description with context
  • What you’ve tried and why it didn’t work
  • Relevant details without showing solutions
  • Text-based content – no screenshots of code/errors

Formatting Requirements:

  • Use Ed code blocks for error messages and code snippets
  • Plain text – everything must be searchable
  • Proper grammar – proofread before posting
  • Relevant details only – remove unnecessary information

Title Examples:

  • Good: “VirtualBox Display Issue After Import”
  • Good: “Gradescope Upload Fails with Large Files”
  • Bad: “URGENT: Please Help!”
  • Bad: “My Code Doesn’t Work”

Step 4: Follow Up

Active Participation: Respond to clarifying questions and mark resolved posts.

Student Responsibilities:

  • Mark as Unresolved if you need official instructor response
  • Accept answers when resolved (gray checkmark)
  • Use follow-ups instead of creating new posts
  • Stay responsive to staff clarifying questions

Response Management:

  • 48 hours maximum response time for guideline-following posts
  • Public posts get faster responses than private posts
  • Project deadlines – posts may not be answered before deadlines
  • Don’t repost – use follow-ups in original thread

 

Ed Discussion Usage Guidelines

  • Access Ed Discussion via Canvas or direct link
  • Click “Show More” below pinned posts section
  • Read all pinned posts – these contain critical course information
  • Bookmark the platform for daily access

Note: Ed Discussion only shows 3 pinned posts by default. Click “Show More” to see all important announcements.

Allowed vs Prohibited Posts

Allowed:

  • Theory and concept discussions
  • Resource sharing (docs, tutorials)
  • Tool usage and setup help
  • Project clarifications (without revealing solutions)

Prohibited:

  • Sharing code or pseudocode
  • Asking for code reviews
  • Solution hints or walkthroughs
  • Screenshots with answers

Project Threads

All project-related questions must be posted in designated project threads.

Thread Structure:

  • Dedicated threads for each project and major component
  • Flag-specific discussions where appropriate
  • FAQ sections within project threads
  • Common issues and solutions compilation

Guidelines for Online Student Conduct and Netiquette

Effective communication in online classrooms requires adherence to established principles of internet etiquette. The following guidelines are intended to facilitate clear and respectful interactions among students and instructors:

  • Review all existing posts and comments on a discussion board before submitting a reply. This practice helps avoid redundant commentary and prevents asking questions that have already been addressed.
  • Use language that is neutral and professional to minimize the risk of misinterpretation in written electronic communication. Humor and sarcasm are often misunderstood; therefore, maintain a matter-of-fact and respectful tone in all posts.
  • Adhere to standard conventions of online communication. Avoid using all capital letters, as this may be perceived as shouting. When appropriate, use emoticons to convey nonverbal cues.
  • Limit the size of attachments. If images must be shared, ensure they are resized to 250 kilobytes or less. Free web-based tools, such as picresize.com, may be used for this purpose.
  • Do not share inappropriate material in any form.

Note: The instructor is responsible for monitoring posts to ensure they are collegial, contribute to the course or project, and comply with the Online Student Conduct and Netiquette guidelines. The instructor may remove posts that do not meet these requirements.

 

Collaboration Guidelines

Permitted:

  • Concept discussions about underlying technologies
  • Resource sharing (documentation, tutorials, general guides)
  • Tool usage explanations and troubleshooting
  • Learning assistance within academic integrity bounds

Not Permitted:

  • Any code sharing
  • Partial solutions or logic
  • Screensharing work-in-progress
  • Walkthroughs or hints

See Academic Honesty for comprehensive academic integrity requirements and prohibited activities.

 

Professional Development

Learning to ask effective questions is key to your success.

Why This Matters:

  • Workplace success: Senior engineers respect well-researched questions
  • Career advancement: Research skills distinguish senior from junior developers
  • Problem-solving: Experience building these skills pays dividends
  • Professional relationships: Thoughtful questions build respect

Professional Question Approach:

  • Research thoroughly before asking
  • Show your work – what you’ve tried and why it didn’t work
  • Be specific – narrow down to the exact issue
  • Provide context – enough background for others to help
  • Follow up – respond to clarifying questions and mark resolved

 

Communication Quick Reference

Situation Platform Use?
Project help Ed Discussion ✅
Course policy questions Ed Discussion ✅
Study coordination Slack ✅
Email instructors/TAs Email ❌
DM for project help Slack/Discord ❌
External project discussions Any platform ❌

 

Academic Integrity and Monitoring

All posts on Ed Discussion are monitored.

Communication-Specific Violations:

  • Posting solutions or code snippets
  • Sharing screenshots that reveal answers
  • Providing step-by-step solution guidance
  • Requesting code review or direct implementation help

Communication Monitoring

Ed Discussion Oversight:

  • All posts monitored for academic integrity compliance
  • Cross-referencing with submitted work for violation detection
  • Pattern analysis of unusual similarities in submissions
  • Proactive intervention to prevent violations when possible

 

Daily Communication Checklist

  • Check Ed Discussion for announcements and updates
  • Monitor pinned posts for important course information
  • Review project threads for new guidance and FAQs
  • Check GaTech email for official Georgia Tech communications

 

Emergency Communication

  • Technical issues: Post in Ed Discussion with detailed description
  • Academic integrity concerns: Private post to all instructors
  • Extension requests: Private post with documentation (see Submissions & Gradescope)