Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on The homework dumps are coming - how about a network-wide policy?

Parent

The homework dumps are coming - how about a network-wide policy?

+10
−0

I'm starting to see the first signs of the inevitable "homework dumps" on Software Development as the site is gaining traffic a bit. The criteria for a homework dump is roughly:

  • A raw copy/paste of a school assignment. It is not necessarily even asking a question, it could as well be a work order: "your task is to-...".
  • There is no effort or background research at all made by the OP.
  • The OP is unresponsive to any comments or feedback, they just want their homework done by someone else.

Dropping your homework as-is on top of unpaid volunteers and expecting them to do it for you free of charge is of course terribly rude and thereby violates our "be nice" Code of Conduct.

These are a problem & a constant source for conflicts over at SE - they never managed to solve the problem. So I was hoping we could deal with them more sternly than they do, because simply closing & deleting the questions isn't working out very well. They never managed to get the word out that "posting your homework on site x will get you banned". (Even though this ultimately happens because of various secret algorithms looking at new question reception.)

I was about to propose on Software Dev that we deal with these by letting the moderators or even trusted users hand out 1 week ban from the site, as a first reprimand, to signal that this behavior is absolutely not ok.

Then I realized that this will be just as big a problem on the other technical/scientific communities, in particularly Mathematics, Physics and Electrical Engineering. It would be great if we could moderate these consistently across all sites. So how about coming up with a network-wide moderation policy for how to deal with "homework dumps"?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

General (1 comment)
Do we need a policy about this? (3 comments)
Post
+3
−1

I'd actually love the idea of having such a policy when it comes to homework questions. We could start off though with how SE could deal with such homework questions, apart from closing them and deletion of dumps.

Here's my draft of such policy:

Homework guidance

If you're willing to ask a question that's your homework, please do the following before posting:

  • Re-address your question by specifying the actual problem you're facing. This helps others to answer your question.
  • At least try solving it yourself. This is a huge role when it comes to these. If you decided to post the question without trying to solve it, then it would end up being subjected to getting closed, or worse, deleted. Show what you've tried as it is proof you have tried answering it.
  • State all the specifics. To be able to solve a question, you need to identify the key factors on what the problem could be or why it happens. State all the descriptions of the question you're trying to answer by adding the topics you're learning, adding additional info that's crucial to the question, and other helpful additions.

That's all that I'd do for now, but these are a good start on the policy. If a new user joins the network, they can be greeted with a message asking if they're a student so we could send them to the policy link by a new tab, I suppose. Though this could be a bit of a problem to handle, as it is indeed likely for the students to simply ignore the message and ask right away.

I have a solution for this. Let's say we warn them that next time they ask a question, they might want to read the policy. Again, they might ignore it, so we might as well invite them to the chat so we can tell them about it and hope they'd understand (I was about to say listen. lol).

Note: This is only the beginning on how we can stage such policy, and we can go further once the devs can take care of the situation alongside us.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

2 comment threads

Current policy on Software Dev. (2 comments)
Information (2 comments)
Current policy on Software Dev.
Lundin‭ wrote over 2 years ago

Currently we have this at Software Development (from here): "Off-topic - questions asking for implementing a certain feature (or homework). You should include your (partially working) trials in the post". I like your more detailed post though. If we are to make it a network-wide policy, we could include such a page below Help on communities where it applies. Instead of each community coming up with their own flavour of it, like the quote above.

Monica Cellio‭ wrote over 2 years ago

Lundin‭ in case this helps: the guidance at the top of the "ask question" page is customizable per community. If Software Dev wants to add something (such as policy links), we can do that. Ideally, work out a draft on SD meta and ping a team member when it's ready.