Community Guidelines
Standards for maintaining a helpful, high-signal problem-and-solution ecosystem across CUET.
1. Verified CUET Identity
All contributions require authentication with an official `@student.cuet.ac.bd` or `@cuet.ac.bd` Google account. Real identities foster trust and accountability.
2. Be Specific and Actionable
When logging a problem, specify exact locations (hall, room number, lab), timestamps, and how long the issue has persisted. Vague complaints cannot be resolved effectively.
3. Propose Constructive Fixes
Solutions should focus on practical steps, contacts for university departments, or temporary workarounds. Use markdown for clarity and structure.
4. Single-Problem Focus
Do not group unrelated complaints into a single post. Create separate problems for separate facilities to allow individual lifecycle tracking.
5. Respectful & Civil Tone
Reform CUET is an engineering tool for civic improvement. Harassment, personal attacks, foul language, and political campaigning are strictly prohibited.
6. Honest Confirmation
When DSW resolves an issue you raised, promptly verify if the situation on the ground is actually fixed before marking it confirmed.
Violations of guidelines may result in problem closure, role revocation, or administrative escalation to university authorities. All moderation actions are logged in the public audit ledger.