Organization
Organizational discussion about NetGuru .. what are the strengths, what are the weaknesses, what's the membership, what's the leadership?
Strengths
- open discussion
- can explore tangents: enough time..
- appropriate technical level
- appropriate sizing - discussion is fostered by the size
- common problems and commonality of solutions
- campus level focus
- certain size and scale
- 1.5 days - a good amount of time
- can let a "jazz" go.. explore good ideas
- limited structure - gives flexibility
- enable veering off track
- relatively low overhead for organizers
- range of skills and level of responsibility
- cross-pollination of this group with other groups (working groups, etc.)
- this group has no decision-making or policy agenda
- no vendors
- the group can help inform us of what to do in certain circumstances
- "this is useful"
Weaknesses
- some unsure how to make the most of the netguru experience
- forgot that the mailing list existed
- communicating netguru information to the broader community
- need a new name
Leadership
- minimalist
- "group of three": past, current, future meeting leaders
- if you attend, you can be tagged to lead
- should organize conference calls early to develop agenda
Membership
- minimalist
- terms of membership - lead a discussion, edit notes, make a JT presentation, etc
- topics for the meeting - helps identify the participants (should identify early on)
- no more than 2 from single institution
- 30 people is the upper limit
- perhaps 2 meetings per year, different topics
Conclusions
- maintain campus focus
- mailing list
- include more folks
- .edu people
- vet on mailing list if questions arise
Next steps
- Contino - Definition of what we are, options for new name
- Miller - Start an email thread of leader volunteers for next mtg (Sinn, Zeller, Chin, Sinatra)