...
Agenda
- Review action items from 2020-04-09 Docs Project Meeting
- Gerrit to GitHub:
(← I hate this; I want to see the link, not a giant icon; Casey Cain, is there a way to disable this on a per-link basis?)Jira showSummary false server Tungsten Fabric serverId 82691efe-91a0-3cff-8e71-932ce5d4700b key TFB-1574 - FYI: VMB out next week (vacation)
Minutes
- Jumping directly in to the GH transition
- Do we move our tickets from Jira to GH Issues?
- VMB sent email to dev@ about this: https://lists.tungsten.io/g/dev/message/619
- Pono: Parallel question; could start thinking about it now
- AT: Thinks GH makes sense for Issues
- VMB will add this to the TSC call agenda for next week
- AT: Put my ticket on hold for now?
Jira server Tungsten Fabric serverId 82691efe-91a0-3cff-8e71-932ce5d4700b key TFB-1455 - VMB: Oh, snap. Yes, please.
- AT will look a different ticket for now.
- The ticket:
Jira server Tungsten Fabric serverId 82691efe-91a0-3cff-8e71-932ce5d4700b key TFB-1574 - Pono says this is a good list to start
- Will add comments about bits that need to be done in Jenkins
- Gating on +1s may be a for-pay feature
- Will need to add bullet item for defining code owners
- Pono says this is a good list to start
- Moving forward
- Break TFB-1574 into an epic
- Pono will make RlsEng Jira tickets and link them to our epic
- Will need to start thinking about the workflow/social part of this as well
- Hard part will be getting folks outside of Docs to test the new workflow
Action items
- Daniel Pono Takamoriwill send GH code owners doc to the docs@ list