Hydra Partner Meeting Functions
- Bill Branan
Functions needed |
Plus |
Minus |
Sum |
|---|---|---|---|
social cohesion |
10 |
0 |
10 |
collaboration opportunities |
10 |
0 |
10 |
architectural working sessions |
8 |
0 |
8 |
community roadmapping |
8 |
0 |
8 |
cross partner updates |
8 |
0 |
8 |
techical roadmapping |
7 |
0 |
7 |
skills sharing |
7 |
1 |
6 |
working sessions |
7 |
3 |
4 |
hackfest |
6 |
4 |
2 |
resource coordination |
6 |
0 |
6 |
scheduling next meetings |
5 |
0 |
5 |
Hydra vis a vis other projects |
4 |
0 |
4 |
rotating release managers |
4 |
2 |
2 |
administration (project) |
3 |
2 |
1 |
PR, communications, etc. |
3 |
3 |
0 |
input to duraspace |
3 |
1 |
2 |
community maintenance + growth |
2 |
0 |
2 |
process definition |
2 |
1 |
1 |
outreach |
1 |
0 |
1 |
adoption |
1 |
3 |
-2 |
training |
1 |
6 |
-5 |
Implications for Hydra Partner Meetings:
- value in having stakeholders of all types (devs, managers, architects, analysts) together
- plenary sessions useful for social cohesion, setting up collab
- tracked sessions useful for working sessions, coding, resource coord
- project admin can be relegated to Hydra Steering or other smaller groups
Other Meetings:
Open Repositories
- Outreach, Collaboration opportunities
Hydra Camp
Skills sharing, Training
LibDevConX
- Hydra vis a vis other projects
- Outreach
- Skills sharing
Code4Lib/Access
- Skills, Training, Adoption
We need to ask the people who aren't here as well, are the meetings too frequent? Location? Coincide with other conferences? (Richard)