CalStuff: News. Observations

Help Calstuff

Anyone who wants to give us a hand, here are some ways you can help out.
  1. Read CalStuff.
  2. Comment on CalStuff. The posters here are never offering the final level of analysis or reporting on any issue. We read the comments posted here, and it almost always helps give us, and the other readers, a better and more complete view of what we are writing about when our readers help fill in information.
  3. Tell your friends about CalStuff. The more readers the better, both because it helps with number 2 and 4 above and below, and because we tend to write more if there are more readers around to see it. Here are some easy ways to spread the word about CalStuff:
    • Place a link to CalStuff somewhere that a number of Cal students might see it liexamples include a personal website, your AIM profile lithanks to everyone who did this), your facebook profile, a LiveJournal, or anywhere else.
    • Join the Facebook CalStuff group.
    • Tattoo www.calstuff.com onto your forehead, or if you get around a lot, on your genitals...
  4. Provide CalStuff with information. We monitor a variety of sources for Berkeley news, but the most effective way to get information to CalStuff is if you drop us a link about something that is happening around campus. Email us at calstuff [at] gmail dot com or one of the writers directly with the contact information to the left.
  5. Help CalStuff monitor the fire trails. The everpresent threat of rampant marauding gangs of mountain lions is far too large of a danger for CalStuff to monitor on its own, and we are desparate for your assistance.
  6. Write a guest post. One interesting limitations of news coverage is that oftentimes coverage of a story will focus around a central figure, and yet that person only gets a brief quotation in the report about the event. If you're invlived in a news story, or just have an opinion you woold like to express, drop us a line pitching a guest post idea, and we'll let you know if it will fit in here.

Database error