...
- Time: 9:00am PDT / Noon EDT
ZOOM connection: https://notredame.zoom.us/j/94030214208
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)Expand title Click to view telephone/H.323/SIP connection instructions Meeting ID: 940 3021 4208
One tap mobile
- +13017158592,,94030214208# US (Germantown)
- +13126266799,,94030214208# US (Chicago)
Dial by your location
- +1 301 715 8592 US (Germantown)
- +1 312 626 6799 US (Chicago)
- +1 646 558 8656 US (New York)
- +1 253 215 8782 US (Tacoma)
- +1 346 248 7799 US (Houston)
- +1 669 900 6833 US (San Jose)
Meeting ID: 940 3021 4208
Find your local number: https://notredame.zoom.us/u/aPls29JbL
Join by SIP 94030214208@zoomcrc.com
Join by H.323
- 162.255.37.11 (US West)
- 162.255.36.11 (US East)
- 115.114.131.7 (India Mumbai)
- 115.114.115.7 (India Hyderabad)
- 213.19.144.110 (EMEA)
- 103.122.166.55 (Australia)
- 64.211.144.160 (Brazil)
- 69.174.57.160 (Canada)
- 207.226.132.110 (Japan)
Meeting ID: 940 3021 4208
Agenda
(meeting notes below)
...
- Heather is interested in direct outreach, communication to institutions
- How do we address short-term things as long-term progress is made?
- Often, people feel it is easier to make local changes than contribute upstream. Upstream has a longer review process, more back-and-forth.
- This can frustrate regular contributors, leading to feelings of burnout.
- Julie wants to tackle outstanding issues in Hyrax.
- Some issues may be handled by the Hyrax maintenance working group.
- For others, may reach out to institutions who may have already solved the issue
- Core Components Maintenance working group and other groups have had mixed success
- Coding for the community regularly means producing configuration that would not be necessary at the local institution
- Open Source is not always a high priority for an institution
- This is an issue that Partners, Steering will need to address
- Developers are not leadership
- Hard for developers to drum up community contributions and lead development
- Developers can push a perspective that the work isn't done until it's merged upstream
- Burnout issues will lead to difficulty in retaining (or replacing) tech lead, other positions
- Also, we want to care for those in our community taking on roles which have historically been highly prone to burnout
- Examples of successful contributions are useful for others to follow
- Idea to thank people on slack when they contribute upstream or close issues
- Large code base, but few contributors
- Exacerbates the issue, and leads to code rot.
- Dev congresses have been successful
- May be useful to have the community manager help organize and schedule
- Getting a schedule would help with institution resource planning.
- Hyrax roadmap was useful as a schedule.
- Dev congresses need a host, so usually were tacked on to another event.
- Some have been focused on a single issue or product, others are more scattered.
- Idea to have more dev congresses
- Idea to have a dev congress that's only focused on pairing to get developers set up with a hyrax dev environment and close a small issue
- Idea to individually approach partner institutions to ask them to contribute developer time
...