Announcement discussions

[ragtek]

Why do most admins seperate announcements and discussions?

Isn't it strange having 2 threads? 1 with the announcement and a second with "discuss foobar announcement"

 

[Peggy]

I like the separation.

 

[Russ]

I think keeping announcements by themselves keep things much more professional, rather than having outsiders seeing post like: "first", "this update sucks" ect ect.

 

[ragtek]

I think keeping announcements by themselves keep things much more professional, rather than having outsiders seeing post like: "first", "this update sucks" ect ect.

But if the discussion forum is visible for guests, they can see it

 

[Shelley]

I think keeping announcements by themselves keep things much more professional, rather than having outsiders seeing post like: "first", "this update sucks" ect ect.

Couldn't agree with you more. I always felt announcements should be posted for announcements and the associated topic to discuss that announcement in forum X.

 

[Paul B]

I prefer the separation.

It keeps the announcement threads clean, tidy and professional.

 

[Ingenious]

I prefer the separation too.

 

[Digital Doctor]

I think Annoucements should be in a more formal location such as a Developer's Blog (comments could be enabled or disabled). I also think that new Blog entries should show up in "What's New" searches. I also think people should be able to Subscribe to the Developer's Blog and receive an Alert when new entries occur.

 

[tmb]

Never thought to ever separate things but I'm just a lazy admin.

 

[Forsaken]

Never thought to ever separate things but I'm just a lazy admin.

I had an add-on where it would create a discussion thread whenever a new announcement was made.

 

[Carlos]

I think keeping announcements by themselves keep things much more professional, rather than having outsiders seeing post like: "first", "this update sucks" ect ect.

There you go. That's a really good response.