John
Alex I don't think you understand my position. I have the option to add specs to my sig and I chose not too. I was addressing only your question of why I don't have them in mine. What you have in yours is your business.  

For the third time John I said "advising". I wouldn't force anybody to do what they don't want to do. I'm not arguing about your right not to include a signature at all.

John
Mike thats not what is in the OP. Some of it is but I also added more specifics and I added the need to stick around for answers. Also it can't hurt to make the point again. 
 
Mike I should tell you the hosts help write the COC.  
 

Well if the hosts helped write it I'm surprised you didn't make mention of it. By your very posting in the first place implies that this is an area where there is a shortcoming when it fact it's already well provided for and you now say you were involved in its original writing. It's certainly far more concise than what you wrote in your first post.

But actually we're talking about the Cakewalk Product Handbook not the Code of Conduct. You do know they are 2 entirely different documents (threads). Still whoever wrote it the information in your first post is concisely addressed in Cakewalk Product Handbook in it entirety.

Great Alex!

Does this thread really need to get nutsoid? We've got a whole pile of new users, I'm assuming because of the new Sonar and it's general attraction. This is straightforward advice for solving tech problems via the in place p2p system.
 
Let it stand as is so those new folks can read it without the shizshow. That helps noone.
 
And that is NOT directed at anyone because you are all my friends. I can just feel this taking a turn for the worse already.
 
Peace, love and granola bars.

I'm up late (or early) so send over a granola bar or two. Thanks.

*fingers on temples*
 
*COMMENCING GRANOLA WAVE TRANSMISSION*
 
*trippy fax modem type noises*

mudgel
So if members and forum hosts aren't familiar with what's in the current lot of sticks why should we have an expectation that new users will read the sticky before posting.

Maybe our access should be suspended each year until we pass re-certification exams

Beepster
Does this thread really need to get nutsoid? We've got a whole pile of new users, I'm assuming because of the new Sonar and it's general attraction. This is straightforward advice for solving tech problems via the in place p2p system.
 
Let it stand as is so those new folks can read it without the shizshow. That helps noone.
 
And that is NOT directed at anyone because you are all my friends. I can just feel this taking a turn for the worse already.
 
Peace, love and granola bars.

After reading through this thread, I actually forgot what it was about.  LOL

John
Mike thats not what is in the OP. Some of it is but I also added more specifics and I added the need to stick around for answers. Also it can't hurt to make the point again. 
 
Mike I should tell you the hosts help write the COC.  

 

mudgel
Well if the hosts helped write it I'm surprised you didn't make mention of it. By your very posting in the first place implies that this is an area where there is a shortcoming when it fact it's already well provided for and you now say you were involved in its original writing. It's certainly far more concise than what you wrote in your first post.

But actually we're talking about the Cakewalk Product Handbook not the Code of Conduct. You do know they are 2 entirely different documents (threads). Still whoever wrote it the information in your first post is concisely addressed in Cakewalk Product Handbook in it entirety.

Cakewalk wrote it. We just threw in clarification in areas that were missing. I lobbied hard for the last major revision as the initial document was pretty confusing to say the least. Almost... all my points got in there (all to do with problem reports) apart from the forum name change, suggestions from other hosts were put in there as well, I say 'we' because I was a host at that period of time.

It's a reasonable document as it stands now but there's always room for improvement, although I hear there may be changes soon which means the problem reports forum may end up being wound up for good. If it means Cakewalk is going more for a public tracker/integrated ticket solution I wholeheartedly support it, forum software isn't really cut out for this sort of thing as there is no workflow.

BobF

mudgel
So if members and forum hosts aren't familiar with what's in the current lot of sticks why should we have an expectation that new users will read the sticky before posting.

Maybe our access should be suspended each year until we pass re-certification exams

That's why I think the document that exists is adequate for purpose. It's pretty clear from the many first and early posts I have read and contributed too that most if not all failed to give any evidence that they'd read the Cakewalk Product Handbook. Could placing the sticky higher up help. I doubt that even surrounding it with flashing lights would draw people to it any more. I think the way the questions get handled is OK. I read manuals when I want to get info others come to the forum. That's just the way it is.