Append [RESOLVED] to your post subject if you got to a working solution

17 views
Skip to first unread message

Ryan Blunden

unread,
Dec 25, 2012, 1:20:20 AM12/25/12
to django...@googlegroups.com
Hi everyone,

After this very revealing post, I want to do what I can to support new people coming to Django. 

Like many Django developers and supporters, I'm busy and so to make it as easy as possible to provide support in this forum, it would be great if you could append [RESOLVED] to your post subject if you got to a working solution.

This allows me and others to quickly scan the discussion list to see what needs attention.

Perhaps there is a better system I'm not aware of? Whatever it is, I just want to be able to provide help to those that need it in the most time efficient way possible.

Cheers,
Ryan

Avraham Serour

unread,
Dec 25, 2012, 3:51:48 AM12/25/12
to django...@googlegroups.com
I oppose adding [RESOLVED] to the subject, this means changing the subject to a complete different string and detaching it from the thread. not sure how this would work for google groups, but many people (me included) read on gmail, it happened to me not long ago (can't remember which mailing list it was), someone added a {RESOLVED] at the end of the subject, meaning I got an email detached from the discussion.

if someone would post a message after they got a solution they could just add RESOLVED to the first line of the body and then post their conclusions on how they got there. problem is that often people go silence when they achieved the solution.

also take in consideration that some posts are discussions like this one, not answers to a specific problem.

avraham


--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/v2w_elHfeL8J.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Ryan Blunden

unread,
Dec 25, 2012, 2:43:56 PM12/25/12
to django...@googlegroups.com
True, it will break the thread if reading via email only.

Can you propose another way that when going to the groups posts page, you can scan and see which topics require further assistance? 

That is the problem I'm trying to solve.

Avraham Serour

unread,
Dec 25, 2012, 3:03:29 PM12/25/12
to django...@googlegroups.com
like I said, one could post "RESOLVED" on the first line on a conclusion post, this way it would pop up on search results.
it is not an ideal solution like having it in the subject like forums use these days but it is the workaround that comes to my mind. my hope is that other people can give their input on this, I'm sure someone out there can come up with a better way


To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/Vs-XR4tF3G0J.

Axel Rau

unread,
Dec 26, 2012, 3:01:16 AM12/26/12
to django...@googlegroups.com

Am 25.12.2012 um 09:51 schrieb Avraham Serour:

> I oppose adding [RESOLVED] to the subject, this means changing the subject
> to a complete different string and detaching it from the thread.
MUAs like Apple Mail or Thunderbird use "references" header (if present) instead of "subject" for threading.

Axel
---
PGP-Key:29E99DD6 ☀ +49 151 2300 9283 ☀ computing @ chaos claudius

Avraham Serour

unread,
Dec 26, 2012, 3:52:06 AM12/26/12
to django...@googlegroups.com
so maybe we should file a bug report to gmail on this


--
You received this message because you are subscribed to the Google Groups "Django users" group.
Reply all
Reply to author
Forward
0 new messages