October 25

Attendees:

Revised workflow for critical vulnerabilities (taken over from security interest group which is on hiatus)
added the fact that it should be advertised when updates get made
why patches only on Wednesdays? (and not Monday and Tuesday) - no change - makes it so people know when to expect it
suggestion for creating a specific list where people who are wanting to be alerted first - added to workflow
PR version on the Islandora page so it is easy to see that we "have" a security update policy
vote to approve in chat - 9 yes - 3 abstain

Release workflow - while releasing - we're free to pull from the release branch in dev so no need to do multiple pull requests
Query about the use of tags? - we do use tags to tag master and only resort to branches if you have to backport a fix
useful to mention when a pull request goes stale? - it is mentioned re: languishing in the text - also it has been modified to allow closing pulls for users that have ghosted -- should we have a way to allow a submitter to adopt a ghosted pull request - that gets handled by the new submitter to create a replacement pull request that supersedes the original orphaned request
should there be a way to officially dismiss pull requests that are not in line with the will of the community? - partially addressed in the social dynamics sections, but admittedly it is a challenge to deal with - in favor of keeping it light - trying to address with policy tends to back people into corners. (agreed) - add the code of conduct as a link
once approved - we need to also make sure this shows up
vote to approve in chat - 10 yes - 1 abstain

Seems like Slack has pulled in the majority of the community and IRC has waned. It has broadened the community significantly: (adding an auto-invite)
Propose that we vote to deprecate IRC where possible
vote to approve in chat - 9 yes - 2 abstain

⚠️ This wiki is an archive for past meeting notes. For current minutes as well as onboarding materials, click here.