Jumping Rivers Blog
Header Image for Fundraising Email
Community Meeting
- "Homegrown" Packages
- Getting comfortable with a package that's not maintained if people leave the company
- Resource management for being a robust package (unit tests, more issues for people to take on, etc.)
- Open-source versus internal packages - how do we assess risk (download counts not available, etc.)
- How do we build trust in our internal packages?
- Releasing internal packages to be open-source ({roak})
- Who is responsible for bugs that are found?
- Does this affect reputation?
- Does this hinder the stride toward open-source if people are reluctant to scrutiny like that?
- Trusting the bells and whistles of packages like automatic binning.
- "Black box" methods/functions in validated packages - do we know it's truly validated? What metrics can help make us confident?
- Standard practice versus validation
Action Items
- Set up calendar invite for community meeting
- Community meeting slides (next communications workstream meeting)
Jumping Rivers Blog
Header Image for Fundraising Email
Community Meeting
Action Items