User Tools

Site Tools


webteam:meetings:notes:2011-09-01

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
webteam:meetings:notes:2011-09-01 [2011/09/01 15:06] – created jimcranerwebteam:meetings:notes:2011-09-01 [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
 Attending: John, June, Jim, Kathy, Roni, Amy, Steve, Kate Attending: John, June, Jim, Kathy, Roni, Amy, Steve, Kate
  
-** Importance of "Creation of formal website team" recommendation+Importance of "Creation of formal website team" recommendation
  
-Who can change/edit?  Authority? +Who can change/edit?  Authority?
-* Promote people changing/editing/adding content +
-* Who is vetting changes?  Little technical errors get fixed via wiki/commenting mechanisms.  Big changes are arrived at via Web Team consensus with community input where appropriate.+
  
-* Going forward: loosey-goosey or formal team?  Formal team is requirement for the Big changes (implementing centralized platform) but policies/efforts can be formalized +Promote people changing/editing/adding content
  
-* Count the changes Anoop made based on input from the Existing Site Improvement Committee as a big success for our efforts!+Who is vetting changes?  Little technical errors get fixed via wiki/commenting mechanisms.  Big changes are arrived at via Web Team consensus with community input where appropriate.
  
-* Oversight Board?  Governance Committee?  Answer: oversight entities are deliberately going hands-off so don't expect top-down strategy.+Going forward: loosey-goosey or formal team?  Formal team is requirement for the Big changes (implementing centralized platform) but policies/efforts can be formalized 
  
-* Hackfest at annual conference -- Web team spends the year figuring out what could be done by team in a concerted effort at an annual Website Hackfest and what stuff they can just do as small chunks throughout the year themselves.+Count the changes Anoop made based on input from the Existing Site Improvement Committee as big success for our efforts!
  
-* Management spectrumgatekeepers vscheerleaders/facilitators+Oversight Board?  Governance Committee?  Answeroversight entities are deliberately going hands-off so don't expect top-down strategy.
  
-*** Homework: write a 1-4 paragraph narrative of what you see the Web Team's structure, processes/policies, and activities look like going forward.  Submit this to the Web Team list for discussion and comment on everyone else's narrative so that rough consensus is arrived at before our next meeting.+Hackfest at annual conference -- Web team spends the year figuring out what could be done by team in a concerted effort at an annual Website Hackfest and what stuff they can just do as small chunks throughout the year themselves.
  
-*** Next meeting (tentative pending Anoop's ability to attend) is Thursday, September 15th, same time (1100pdt / 1200mdt / 1300cdt / 1400edt).+Management spectrum: gatekeepers vs. cheerleaders/facilitators 
 + 
 +**Homework**: write a 1-4 paragraph narrative of what you see the Web Team's structure, processes/policies, and activities look like going forward.  Submit this to the Web Team list for discussion and comment on everyone else's narrative so that a rough consensus is arrived at before our next meeting. 
 + 
 +Next meeting (tentative pending Anoop's ability to attend) is Thursday, September 15th, same time (1100pdt / 1200mdt / 1300cdt / 1400edt).
  
webteam/meetings/notes/2011-09-01.1314903977.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.