| Table of Contents | ||
|---|---|---|
|
...
- Posting agendas and minutes from meetings
- Publishing position papers describing proposed functionality
Documentation for resources such as the Roadmap
Marketing logos and branding documents
...
- Bug reports may come from other tools (for instance, a Discuss post or a dialog on Slack). Whenever possible, provide a link to the original source of the bug report.
- Describe the issue concisely in the Summary (Standard Bug Write-Up Format) and Description fields. Use Comments for further detail.
- Set the “Development Team” according to the wiki’s team vs module responsibility matrix so the Product Owner can triage and prioritize it.
- Additionally, if this is a bug that is affecting folks in production, set the “Epic Link” to SUP-12 and the SS will prioritize it.
Follow up in other fora for any lengthy discussion. Then summarize into further issue tracker comments. Provide links in both directions.
See also
| Anchor | ||||
|---|---|---|---|---|
|
...
Most SIG online meetings and other FOLIO-related online meetings will be held using the Zoom meeting software (https://zoom.us/). See FOLIO Meetings with Zoom for the default password. The Open Library Foundation holds a license to Zoom and sets up meetings on behalf of the project. Information about times and joining SIG meetings is generally provided by the SIG on their wiki space. Requests for setting up special meetings should be sent to the OLE Project Manager at hlm7@cornell.edu.
Some teams meet in their Slack channel using Slack calls.
...
A visual overview is available at https://www.openlibraryenvironment.org/archives/date/2016/09 - Go to the “Participation Channels in FOLIO - How to Engage” session.
...