Note - Post all Player Cuts in their OWN thread

[Ypsilanti Undead]

Could I motion that all player drops be announced in their own thread? I know it's been common practice in the past to announce cuts in just the manner that the Swords have above. But someone not too terribly interested in the signing of the Broncos D will have no idea that the Giants D is now available on the market. It's pretty inefficient to have to browse every thread to find out who's being cut. I'm not suggesting this practice be enforced with a rule or anything, but perhaps we could adopt it as a protocol, out of courtesy to our fellow owners?

Am I way on the fringe here?

[Mutts]

Originally Posted by Indiana Undead GM

Could I motion that all player drops be announced in their own thread? I know it's been common practice in the past to announce cuts in just the manner that the Swords have above. But someone not too terribly interested in the signing of the Broncos D will have no idea that the Giants D is now available on the market. It's pretty inefficient to have to browse every thread to find out who's being cut. I'm not suggesting this practice be enforced with a rule or anything, but perhaps we could adopt it as a protocol, out of courtesy to our fellow owners?

Am I way on the fringe here?

I would not mind seeing this happen.:drinktoge

[Preds]

Originally Posted by Indiana Undead GM

Could I motion that all player drops be announced in their own thread? I know it's been common practice in the past to announce cuts in just the manner that the Swords have above. But someone not too terribly interested in the signing of the Broncos D will have no idea that the Giants D is now available on the market. It's pretty inefficient to have to browse every thread to find out who's being cut. I'm not suggesting this practice be enforced with a rule or anything, but perhaps we could adopt it as a protocol, out of courtesy to our fellow owners?

Am I way on the fringe here?

I think it's a great idea myself.. it's very easy to lose track of cuts otherwise. Heck, it would make updating the app easier too... I missed Dodgers GB D cut in the Branch thread, and thought he might be over the roster limit when he wasn't.

BTW, I split this out of the Bronco D thread and moved it into it's own to make it clearer foe everyone. ;)

[Nittany Dodgers]

I'm cool too with having cuts be their own thread.

[Brain Dead Squirrel Chasers]

Thumbs up.

[Ypsilanti Undead]

Originally Posted by Preds

BTW, I split this out of the Bronco D thread and moved it into it's own to make it clearer foe everyone. ;)

Hmmm, guess I failed to take my own advice!

[Liquid Swords]

good idea

[Philadelphia Freedom]

Good idea.

[The Knights of Ni]

i agree

[Royal Hawaiian Opihi]

Guess we're all checking in on this... fine with me... my cuts/promotions will be posted Monday, following this weekend's games.

[Royal Hawaiian Opihi]

Clarification question... If I'm going to cut 4 players tomorrow... do I need to have 4 separate threads, or can I put all 4 cuts in one thread (that's how we've done it in the past on cut-down-day, I believe)?

[Preds]

Originally Posted by Royal Hawaiian Opihi

Clarification question... If I'm going to cut 4 players tomorrow... do I need to have 4 separate threads, or can I put all 4 cuts in one thread (that's how we've done it in the past on cut-down-day, I believe)?

IMO yes, it'll be much easier that way

[Royal Hawaiian Opihi]

Originally Posted by Preds

IMO yes, it'll be much easier that way

:angel

[Royal Hawaiian Opihi]

Originally Posted by Royal Hawaiian Opihi

Clarification question... If I'm going to cut 4 players tomorrow... do I need to have 4 separate threads, or can I put all 4 cuts in one thread (that's how we've done it in the past on cut-down-day, I believe)?

Mike, think we need to reiterate this point again? I think people are taking the "Post all player cuts in their OWN thread" a bit too seriously! The idea was simply not to bury cuts in other threads... right? Listing mulitple cuts in a single thread just seems like good stewardship.