October Contest Thread Suggestion

Hi all,

I’ve noticed the September contest thread is getting hard to follow. Many projects post a new reply every time they push an update, so the actual entries get buried between update posts. That makes it harder for everyone, judges included, to see what’s been submitted.

My suggestion: add a rule for future contest threads (and maybe this one) that:

  • each project posts one entry in the contest thread;
  • updates are edited into that original post, perhaps with a short “Update – [date]” section, rather than posted as new replies;
  • no further replies about the same project go in the thread.

That keeps the thread a clean list of entries, one post per project, with everything about a project in one place.

What do the organizers and others think?

4 Likes

i was just reading the submissions and noticed this also, can become difficult to follow … agree with ur approach

2 Likes

There’s a fairness side to this as well. When one project shows up in the thread again and again, it naturally gets more attention than projects that posted their entry once and left it there. Nobody is doing this on purpose, and I’m sure the council judges carefully. But seeing a project over and over can still shape how it’s perceived. Keeping each project to a single post means every entry gets the same visibility, and judging rests on the work itself.

3 Likes

Love it. I’ll be incorperating these rules into the October announcement post, which will be coming today.

1 Like

One more suggestion: it would help to put a link to the Discord in the contest post (and pin it at the top of the thread). That way participants know where to go for support straight away, rather than asking in the contest thread or waiting for an answer here.

Maybe also mention the specific channel to use (for example the dev or support channel), so questions reach the right people and the contest thread stays limited to entries.

2 Likes

I actually think it was good. I don’t like too much regulation, beside one project msg per thread, that could be edited later (was already suggested).

Some contests are like you need correct formalization and fields typed in and that gives more points to judges than the actual product. Don’t want we to go in that direction.

I think discourse prevent editing “old” posts. Or maybe I just didn’t find how to do it.

No it doesn’t, Click the pencil button on your post/comment and you are allowed to edit. Thanks.
Edit : It doesn’t allow you to edit someone else’s post/comment just yours.
Edit 2 : See it works.

No pencil on my post. Like I said, I’m not sure the exact mechanic but it prevents you from editing “old” posts

Maybe it depends on days but I can see a pencil button on mine.

Edit 1 : My 17 day old contest post also has the pencil button

Overall I don’t think there is a need to spam the contest thread with updates, you can use GitHub readme, GitHub commits or make a new post about your project on the forum and update there.

2 Likes

maybe it’s when post are “buried”

Discourse has an edit time limit that can differ by trust level (post_edit_time_limit for everyone, tl2_post_edit_time_limit for TL2+). That might be why 0xhra still sees the pencil on a 17-day-old post and you don’t: it could be the account’s trust level rather than the post itself. An admin can check both settings (0 = edits allowed forever), which would make the “edit your entry instead of reposting” rule work for everyone.

2 Likes