| Table of Contents | ||
|---|---|---|
|
The FOLIO Project has three primary communication channels and several secondary communication channels. Read about the philosophy of the FOLIO communication channels for more background.
The primary communication tools are:
Some general guidelines that apply to all tools:
...
- Posting agendas and minutes from meetings
- Publishing position papers describing proposed functionality
Documentation for resources such as the Roadmap
Marketing logos and branding documents
What to keep in mind when using the Wiki
...
- Anyone is welcome to sign up for an account on the Wiki.
| Anchor | ||||
|---|---|---|---|---|
|
FOLIO uses issues.folio.org (an installation of the JIRA software) to track software development activity, request new features, report bugs in the software, and track tasks that have interrelated parts. The FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix lists the JIRA project for each module.
...
- 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
...
There are a nearly infinite number of secondary communication channels; some of the most used ones are described here. Any significant idea, issue, or discussion that occurs in a secondary channel should be recorded in a primary channel (Discuss, Wiki, Issues, or GitHub) for publication and vetting to the wider FOLIO community.
...
- Not everyone is on all of the time. FOLIO participants work in many different time zones, and so you may not be reaching everyone with your conversation.
- Slack can quickly become overwhelming. The daily commitment of FOLIO participants is a wide range, and significant points may be lost in a large scrollback buffer of text. Distill important points from Slack conversations into discussion posts (see Messages below).
- Slack is not a place to record decisions. Slack's channel logs are the real-time thoughts of the participants (which can change over time). They are difficult to search for a particular point and even harder to summarize. Ideas and decisions should be recorded in Discuss, the Wiki , or Issues, as appropriate.
...
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 #zoom-scheduling Slack channel. Recordings of Zoom meetings are on the Open Library Foundation Recordings site.
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.
...