Difference between revisions of "User:Shawn/Projectos"

From FreekiWiki
Jump to navigation Jump to search
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
==Website Changeover==
 +
* Decide on new website CMS
 +
* Test and customize new CMS with input from departments
 +
* Move content that we're keeping over
 +
* Create and enter new content
 +
* Make live
 +
 +
===Timeline===
 +
* Get input from everyone for general interests for website, includes scheduling and mtgs. (4 hrs) DONE
 +
* Get input from departments re: what they want relating to their areas on the website
 +
** Focus them on the audience: potential volunteers?  donors?
 +
** Also ask departments to send in favorite/hated websites and why.  Review sites at a meeting.
 +
* Develop colors/general site images/branding DONEish
 +
** Create/invite parties to half-hour discussion of branding DONE
 +
** Invite graphic designer to help DONE
 +
* Get someone experienced in changing Wordpress backends (3+ hrs) DONE
 +
* Create skeleton of new site structure and get input (3 hours) DONE
 +
* Schedule and meet with graphic designer (2 hours) IN PROG
 +
* Port website content and new pages to wiki (3-4 hrs) IN PROG
 +
* Interview all committees (3.5 including indiv. talks) IN PROG
 +
** document input (1.5 hrs) IN PROG
 +
* Assign pages to content updaters/writers (2 hrs)
 +
* Update/write pages (5 hrs)
 +
* Checkin with aaron (1 hr)
 +
* Poke photo takers/take photos (2.5 hrs)
 +
** edit photos for web (2 hrs)
 +
* Check in on volunteers regularly (3 hrs total)
 +
* check design and update 2 or 3 times (1.5 hrs each time)
 +
* Poke staff contributors (1 hr)
 +
* Checkin with committees on content (2 hrs)
 +
** Additional content editing after this input (2 hrs)
 +
* Checkin with aaron - ready for content? (2)
 +
* Port stuff over to /blog (5 hrs)
 +
* Test functionalities with PR/staff (4 hrs)
 +
* Iron out wrinkles (4 hrs)
 +
* Technocrats do something magic to make it go live
 +
* Document how to make changes for admins and volunteers (3 hrs)
 +
 +
==Phones==
 +
* Organize documentation (on wiki and in fgstaff- consult with someone) (2.5 h) IN PROG
 +
* Teach someone how to change greeting and administrate mboxen (2, 2-3 h sessions, then check in) IN PROG
 +
* Teach someone how to configure phone system IN PROG
 +
 
==Internships==
 
==Internships==
 
* Improve experience for volunteer interns
 
* Improve experience for volunteer interns
Line 4: Line 47:
 
* Support staff more through entire process
 
* Support staff more through entire process
 
* Update documentation
 
* Update documentation
 
===Timeline===
 
* Put timeline into calendaring system (2 hours)
 
* Cull old interns: paper and online (.5 h)
 
* Create new filing system to share with Laurel (.5)
 
* Set up RT queue(1 h) DONE
 
* Talk with Laurel about division of labor (1 h) DONE
 
* Talk to departments with Laurel(5 h)
 
** Who's interning right now
 
** How many do you want
 
** How much time should they put in there: weekly and # of weeks
 
** What should they do
 
** How much of a priority is having each of your suggested interns to you?
 
** Clarify type of person they're looking for
 
** Clarify what to expect from me and what they'll need to do
 
* Check in with current interns with departments (4 h)
 
* Cull old interns: paper and online (.5 h)
 
* Refine/develop job descriptions for desired interns with supervisors (2 h)
 
* Update documentation (2-5 hours)
 
* Do outreach (see below)
 
 
 
===Ongoing===
 
===Ongoing===
 
* Remind staff to check in on interns
 
* Remind staff to check in on interns
Line 32: Line 54:
 
* Cull job descriptions
 
* Cull job descriptions
 
* Develop and post new job descriptions
 
* Develop and post new job descriptions
 +
===Intern Outreach===
 +
* Acquire quality interns
 +
====Timeline====
 +
Dependency: New interns are desired and staff is ready for them DONE
 +
* Arrange and talk to Molly of Restore to get ideas on outreach methods (2 h) DONE
 +
* Talk to other non-profits, too?  Ask friends where they'd go to look for volunteer opportunities (1 h) IN PROG
 +
* Create/update online profiles for: (3 h) Always IN PROG
 +
** Craigslist
 +
** Volunteer here
 +
** Idealist
 +
** Volunteer match
 +
** PSU
 +
** PCC
 +
** Reed
 +
** Lewis & Clark
 +
** Hands on Portland?
 +
* Update wiki page for volunteer recruitment: specialized volunteers ONGOING
 +
* Make a spreadsheet of good potential contacts (2.5 h) NEXT
 +
* Create and use calendaring software to stay on top of postings (dude.) Using wiki.
  
 
==Media Kit==
 
==Media Kit==
 
* Create physical and online media kit
 
* Create physical and online media kit
 
 
===Timeline===
 
===Timeline===
====Physical Kit====
 
* Outreach to graphic designers and non-profits about their media kits (10 hours)
 
* Create outline for physical media kit (.5 h)
 
* Create/edit copy for physical kit (4-5 h)
 
* Show to outreach committee, get suggestions on content and organization (2 h)
 
* Make changes as suggested by committee (2 h)
 
* Create graphical design for physical kit -- possibly work with graphic designer (3 h)
 
* Acquire potential supplies for kit (1.5 h)
 
* Create prototypes (1.5 h)
 
* Get input from outreach committee and check w/ graphic designers on design (2-3 h)
 
* Make changes as suggested (2-3 h)
 
* Document overview of contents and printing and updating instructions (2 h)
 
 
 
====Online====
 
====Online====
 
Dependency: New website is closer/decided upon
 
Dependency: New website is closer/decided upon
 
* Possibly get input from non-profits about online kits
 
* Possibly get input from non-profits about online kits
* Create outline for physical media kit
+
* Create outline for online media kit
 
* Consult with Matteo about how to mesh kit with new website
 
* Consult with Matteo about how to mesh kit with new website
 
* Create/edit copy for kit
 
* Create/edit copy for kit
Line 62: Line 89:
 
* Make changes as suggested, consult with Matteo to change backend if necessary
 
* Make changes as suggested, consult with Matteo to change backend if necessary
 
* Document overview of contents and updating instructions
 
* Document overview of contents and updating instructions
 
==Website Changeover==
 
* Decide on new website CMS
 
* Test and customize new CMS
 
* Move content over
 
* Create new content
 
* Make live
 
 
===Timeline===
 
Dependencies: Matteo helps, technocrats approve and do whatever they need to do to make it happen
 
* Look over list of desired features with Matteo (1.5 h)
 
* Matteo makes changes necessary to back end (?)
 
* Make any changes (2 h)
 
* Test 'er out (2 h)
 
* Ask webbies/PR for new feature list and new pages desired (2 h)
 
* Review features and make complete new feature list (1.5 h)
 
* Matteo makes changes to back end (?)
 
* I make changes (2 h)
 
* Test 'er out (1 h)
 
* Get input from webbies/PR (3 h)
 
* Make necessary changes (2 h)
 
* Move content over (6 h)
 
* Technocrats do something magic to make it go live
 
 
 
==Volunteer Outreach==
 
* Acquire quality interns
 
* Acquire some adoption volunteers
 
 
===Timeline===
 
Dependency: New interns are desired and staff is ready for them
 
* Arrange and talk to Molly of Restore to get ideas on outreach methods (3 h)
 
* Talk to other non-profits, too?  Ask friends where they'd go to look for volunteer opportunities (1 h)
 
* Create/update online profiles for: (3 h)
 
** Craigslist
 
** Volunteer here
 
** Idealist
 
** Volunteer match
 
** PSU
 
** PCC
 
** Reed
 
** Lewis & Clark
 
** Hands on Portland?
 
* Update wiki page for volunteer recruitment: specialized volunteers (1.5 h)
 
* Make a spreadsheet of good potential contacts (2.5 h)
 
* Create and use calendaring software to stay on top of postings (dude.)
 
 
==Phones==
 
Dependency: New office coordinator
 
* Organize documentation (on wiki - consult with someone) (2.5 h)
 
* Teach someone how to change greeting and administrate mboxen (2, 2-3 h sessions, then check in)
 
  
 
==Other==
 
==Other==
* Create calendaring system (new project management software? google? paper?)
+
* Create calendaring system (new project management software? google? paper?) DONE
 
* Weekly: create/adjust timeline (1 h)
 
* Weekly: create/adjust timeline (1 h)

Latest revision as of 21:40, 29 April 2008

Website Changeover

  • Decide on new website CMS
  • Test and customize new CMS with input from departments
  • Move content that we're keeping over
  • Create and enter new content
  • Make live

Timeline

  • Get input from everyone for general interests for website, includes scheduling and mtgs. (4 hrs) DONE
  • Get input from departments re: what they want relating to their areas on the website
    • Focus them on the audience: potential volunteers? donors?
    • Also ask departments to send in favorite/hated websites and why. Review sites at a meeting.
  • Develop colors/general site images/branding DONEish
    • Create/invite parties to half-hour discussion of branding DONE
    • Invite graphic designer to help DONE
  • Get someone experienced in changing Wordpress backends (3+ hrs) DONE
  • Create skeleton of new site structure and get input (3 hours) DONE
  • Schedule and meet with graphic designer (2 hours) IN PROG
  • Port website content and new pages to wiki (3-4 hrs) IN PROG
  • Interview all committees (3.5 including indiv. talks) IN PROG
    • document input (1.5 hrs) IN PROG
  • Assign pages to content updaters/writers (2 hrs)
  • Update/write pages (5 hrs)
  • Checkin with aaron (1 hr)
  • Poke photo takers/take photos (2.5 hrs)
    • edit photos for web (2 hrs)
  • Check in on volunteers regularly (3 hrs total)
  • check design and update 2 or 3 times (1.5 hrs each time)
  • Poke staff contributors (1 hr)
  • Checkin with committees on content (2 hrs)
    • Additional content editing after this input (2 hrs)
  • Checkin with aaron - ready for content? (2)
  • Port stuff over to /blog (5 hrs)
  • Test functionalities with PR/staff (4 hrs)
  • Iron out wrinkles (4 hrs)
  • Technocrats do something magic to make it go live
  • Document how to make changes for admins and volunteers (3 hrs)

Phones

  • Organize documentation (on wiki and in fgstaff- consult with someone) (2.5 h) IN PROG
  • Teach someone how to change greeting and administrate mboxen (2, 2-3 h sessions, then check in) IN PROG
  • Teach someone how to configure phone system IN PROG

Internships

  • Improve experience for volunteer interns
  • Gain fewer but better quality interns
  • Support staff more through entire process
  • Update documentation

Ongoing

  • Remind staff to check in on interns
  • Remind staff to complete required paperwork
  • Check if staff have needs
  • If there's room for new intern, ask if anyone wants one
  • Cull job descriptions
  • Develop and post new job descriptions

Intern Outreach

  • Acquire quality interns

Timeline

Dependency: New interns are desired and staff is ready for them DONE

  • Arrange and talk to Molly of Restore to get ideas on outreach methods (2 h) DONE
  • Talk to other non-profits, too? Ask friends where they'd go to look for volunteer opportunities (1 h) IN PROG
  • Create/update online profiles for: (3 h) Always IN PROG
    • Craigslist
    • Volunteer here
    • Idealist
    • Volunteer match
    • PSU
    • PCC
    • Reed
    • Lewis & Clark
    • Hands on Portland?
  • Update wiki page for volunteer recruitment: specialized volunteers ONGOING
  • Make a spreadsheet of good potential contacts (2.5 h) NEXT
  • Create and use calendaring software to stay on top of postings (dude.) Using wiki.

Media Kit

  • Create physical and online media kit

Timeline

Online

Dependency: New website is closer/decided upon

  • Possibly get input from non-profits about online kits
  • Create outline for online media kit
  • Consult with Matteo about how to mesh kit with new website
  • Create/edit copy for kit
  • show to outreach, get suggestions on content and organization
  • Make changes as suggested by committee
  • Put kit up on new website
  • Get input from outreach committee and a graphical designer on design
  • Make changes as suggested, consult with Matteo to change backend if necessary
  • Document overview of contents and updating instructions

Other

  • Create calendaring system (new project management software? google? paper?) DONE
  • Weekly: create/adjust timeline (1 h)