The State Worker: Clock starts on deadline for Jerry Brown to appeal state worker furlough case

The State Worker

Chronicling civil-service life for California state workers

August 6, 2012

Clock starts on deadline for Jerry Brown to appeal state worker furlough case

Gov. Jerry Brown must decide by the end of next month whether to keep fighting state engineers and scientists over a recent furlough lawsuit he lost or pay $12 million in back wages to settle accounts.

It's not clear whether Brown will appeal. California Department of Human Resources spokeswoman Lynelle Jolley said this morning that state attorneys hadn't yet discussed the matter.

Brown's window to the appellate court closes 60 days from last Thursday, which was when attorneys for Professional Engineers in California Government and California Association of Professional Scientists filed the final paperwork in PECG v. Brown with Alameda Superior Court Judge Steven Brick.

In June, Brick ruled that some 13,000 PECG and CAPS members were excessively furloughed two days last year. He also decided that about 250 of the unions' members shouldn't have been furloughed at all.

Engineers stand to receive a total $10 million in back pay, said Ryan Endean, who speaks for both PECG and CAPS. Scientists would receive about $2 million total. An appeal by Brown would most likely put the payments on hold while the court fight continues.

IMAGE: www.yolocourts.ca.gov

About Comments

Reader comments on Sacbee.com are the opinions of the writer, not The Sacramento Bee. If you see an objectionable comment, click the "report abuse" button below it. We will delete comments containing inappropriate links, obscenities, hate speech, and personal attacks. Flagrant or repeat violators will be banned. See more about comments here.

What You Should Know About Comments on Sacbee.com

Sacbee.com is happy to provide a forum for reader interaction, discussion, feedback and reaction to our stories. However, we reserve the right to delete inappropriate comments or ban users who can't play nice. (See our full terms of service here.)

Here are some rules of the road:

• Keep your comments civil. Don't insult one another or the subjects of our articles. If you think a comment violates our guidelines click the "report abuse" button to notify the moderators. Responding to the comment will only encourage bad behavior.

• Don't use profanities, vulgarities or hate speech. This is a general interest news site. Sometimes, there are children present. Don't say anything in a way you wouldn't want your own child to hear.

• Do not attack other users; focus your comments on issues, not individuals.

• Stay on topic. Only post comments relevant to the article at hand. If you want to discuss an issue with a specific user, click on his profile name and send him a direct message.

• Do not copy and paste outside material into the comment box.

• Don't repeat the same comment over and over. We heard you the first time.

• Do not use the commenting system for advertising. That's spam and it isn't allowed.

• Don't use all capital letters. That's akin to yelling and not appreciated by the audience.

You should also know that The Sacramento Bee does not screen comments before they are posted. You are more likely to see inappropriate comments before our staff does, so we ask that you click the "report abuse" button to submit those comments for moderator review. You also may notify us via email at feedback@sacbee.com. Note the headline on which the comment is made and tell us the profile name of the user who made the comment. Remember, comment moderation is subjective. You may find some material objectionable that we won't and vice versa.

If you submit a comment, the user name of your account will appear along with it. Users cannot remove their own comments once they have submitted them, but you may ask our staff to retract one of your comments by sending an email to feedback@sacbee.com. Again, make sure you note the headline on which the comment is made and tell us your profile name.

blog comments powered by Disqus