HRWiki talk:Talk page etiquette

From Homestar Runner Wiki

Revision as of 03:40, 14 February 2007

Notes

Reminders to myself: When is it necessary to note an edit conflict. When is it undesirable. What are some options when you get a conflict. — It's dot com 05:59, 22 January 2007 (UTC)

Even though Dot com's just talking to himself over here, it makes for good conversation. We all tend to put "edit conflict" in our summaries or even our edits themselves when we get cut off, mostly because of how annoying it is. But in the end, we probably shouldn't be doing it; everyone's just trying to edit the same page and we already know. — Lapper (talk) 06:10, 22 January 2007 (UTC)

While that is not the reason for my developing this, I agree, it is unnecessary. - Qermaq - (^T/C)  06:12, 22 January 2007 (UTC)

Yeah, I didn't exactly know about the discussion taking place on the Main talk until Qermaq brought that to my attention just moments ago. I guess it would have been better posted there. — Lapper (talk) 06:21, 22 January 2007 (UTC)

More notes: Something like: Good posts are written to flow from one to the next and with an eye toward the creating a discussion that stands up over a long period of time. Getting an edit conflict is frustrating, especially if you get several in a row, but it is usually unnecessary to note the fact that you experienced any as you were editing a talk page. Noting a conflict breaks up the flow of a discussion and ignores the fact that talk pages are read minutes, hours, days, or even years after the fact. If you do get an edit conflict, often whatever you had to say could simply be posted (perhaps with one additional colon) right in the thread. Or maybe you could rewrite part of what you wrote to reflect the fact that someone else has just said something very similar. You could even agree with the post that caused the edit conflict. ... And then some more words or something. — It's dot com 06:28, 22 January 2007 (UTC)

This could say all that. But how's what I have now? Short, sweet, to the point. Sure, it doesn't go as far into why or give alternatives, but that can be easily figured out. - Qermaq - (^T/C)  17:24, 22 January 2007 (UTC)

Well, a few days have passed. There is one open question above - is what I have currently sufficient on the topic of edit conflicts, or should there be more detail as Dot com wondered? Of course, if other users have comments, pro or con, they are welcome. - Qermaq - (^T/C)  22:25, 26 January 2007 (UTC)

I like it for the most part. I do agree with Dot Com that edit conflict should be it's own point with a more involved comment similar to what he included. - ISTC 22:31, 26 January 2007 (UTC)

I believe the edit conflict part should be changed a bit. I don't agree with the advice to never note edit conflicts (I find it's sometimes helpful), and I have no reason to believe the community's consensus is against noting them when they're helpful. Heimstern Läufer 22:50, 26 January 2007 (UTC)

In what way are they helpful? - Qermaq - (^T/C)  23:01, 26 January 2007 (UTC)

As I've said a few times, I note them whenever there is a break in the logic of the conversation. This is probably only one in five or six times, but when it happens, I'll usually write {edit conflict; written after Lapper's post} Not always necessary, but sometimes useful. Heimstern Läufer 23:07, 26 January 2007 (UTC)

But is that better than simply writing {reply to Lapper's post}? I don't propose the community consensus is that they are not wanted, but I can't accept that it means there's consensus for using them just because it's how we've been doing things. Consensus comes from thought and reason, not mere habit, and I suspect most people who note edit conflicts do so out of habit. Perhaps we should move this to a more central location to discuss whether there is or is not any consensus on either that edit conflict notes are useful or that they are an interruption. - Qermaq - (^T/C)  23:12, 26 January 2007 (UTC)

I have a habit of writing Edit Conflict whenever I get one, but that's because I thought we were supposed to. When I was a new user (oh so long ago), I saw that people would note their edit conflicts and that's what I thought I should do too. Honestly, it doesn't really do anything besides expressing frustration and disrupt conversation, just like everyone else said. -Brightstar Shiner 23:16, 26 January 2007 (UTC) Ironicly, I got an edit conflict after this post...

{replying to Qermaq after edit conflict} I'm an explanatory person; for me, it makes most sense to know why someone's post doesn't fit the chronology. At any rate, I would prefer wording such as "it's usually not necessary to note edit conflicts", similar to what Dot com wrote above. Saying "don't do it" just doesn't seem at all necessary to me. Heimstern Läufer 23:25, 26 January 2007 (UTC)

I can live with that wording, unless there is objection. - Qermaq - (^T/C)  23:27, 26 January 2007 (UTC)

Time

Something should probably be noted about replying to really old posts. I've seen that done alot. - The Joe^(Talk) 22:31, 26 January 2007 (UTC)

The only issue I see with that is there have been a couple of occasions where an old comment seemed unanswered to me and I felt the need to bring it back up. So if we want to say something about the time issue, maybe it can be worded such as "Please do not reply to posts in outdated discussions, if you feel the topic is still in need of discussion please begin a new line of discussion stating the subject again in your own words with nothing more than a general reference to the previous discussion if needed." Just some thoughts - ISTC

Kinda like what I just wrote? - Qermaq - (^T/C)  22:41, 26 January 2007 (UTC)

EDIT CONFLICT :-P - ISTC 22:45, 26 January 2007 (UTC) (yea, exactly, Great Jorb on this BTW.)

Even for very old conversations, I don't agree that a new thread should always be started. Sometimes threads just get forgotten, but can easily be picked up where we left off. — It's dot com 23:20, 26 January 2007 (UTC)

I've reworded some. I agree, there are times when it's done. Can you think of any concrete examples of when it would be appropriate to post in an ancient thread? - Qermaq - (^T/C)  23:26, 26 January 2007 (UTC)

Every now and then, I see things like, "This is an old thread, but we never really reached a conclusion here." Standards for deletion, for example. — It's dot com 23:30, 26 January 2007 (UTC)

Plus, I think that newer users should be given the opportunity to respond to old posts because they may have good points.-LordQuackingstick 23:33, 26 January 2007 (UTC)

While I fully agree all users have valuable input, sometimes the old thread is simply dead. The usual faux pas here is to join in the chorus of "me too"s or "no way"s in a years-old thread - which you'll agree is silly, as the item was discussed, decided, and it's done. However, if the item was diced, sliced and dealt out and you think due to more recent information that it was in error, then definitely bring that up. Still, normally old threads are to be left as a record, with only a few exceptions. - Qermaq - (^T/C)  23:37, 26 January 2007 (UTC)

I've always felt it's good in this case to begin with something like "To bring up an old discussion..."; otherwise it looks like you weren't paying attention to timestamps... might that be worth mentioning? Heimstern Läufer 23:38, 26 January 2007 (UTC)

Might be worthwhile. - Qermaq - (^T/C)  23:43, 26 January 2007 (UTC)

EDIT CONFLICT TWICE! Ha ha! Anyways, while I've been guilty of "me toos" myself, I agree they are silly. But I was referring to when they actually have something to say.-LordQuackingstick 23:44, 26 January 2007 (UTC)

Sure. If the item is open and has not been settled, certainly post in that thread. If the item has come to some sort of closure, however, it's best to start a new thread. After all, there are likely more users who haven't been here that long, and starting a new thread tends to (in my observation) get a ball rolling a lot better than opening a new thread. If a closed issue needs reopening, I think that merits a new thread. - Qermaq - (^T/C)  23:48, 26 January 2007 (UTC)

Propose move

This seems to have settled. Propose move to HRWiki namespace. Alternately, encourage further discussion on what needs to be done to that end. - Qermaq - (^T/C)  03:17, 14 February 2007 (UTC)

I support the move, as this page is clearly helpful, and the HRWiki namespace is where it should be. I also suggest that we add a notice at the top, stating that it's a draft. I'm sure some points need discussion. For my taste, some of the listed guidelines are too restrictive, while others could be more restrictive. I'm sure the move will speed up discussions. Loafing 03:40, 14 February 2007 (UTC)