Konrad Malawski: Contact the core team to request a GitHub repository for the workgroup.
Tibor Bödecs: Provide the adoption blog post.
Konrad Malawski: Reflow the incubation-process document and circulate it to the group.
Repository request for worklog
Franz proposed requesting a GitHub repository in the Swiftlang organization so the workgroup can host a worklog or project board instead of using private repositories.
Konrad volunteered to contact the core team to request the repository and to inquire about a group name for the repository.
Konrad noted Android uses a project board and said he will ask for a repository.
Action items and blog posts
Simon reviewed missed actions from the previous meeting and asked for updates on the adoption blog post assigned to Tim and Tibor.
Tim reported that another related blog post will go up in the near future and Franz said a PR has been submitted that is expected to be merged soon.
Franz raised that multiple requests for compression libraries have appeared recently and proposed adding a brainstorming agenda item to define requirements for a potential centralized compression package, and the group agreed to add that item to the agenda-list for future discussion.
Incubation process proposal
Konrad presented a proposal to replace the current level-based incubation pipeline with a package-index driven approach that awards badges for specific checks such as SwiftPM use, CI, license, maintainers, governance, and security policy.
Konrad explained that automated existence checks could be used where possible and that manual reviews would be available for criteria that cannot be auto-checked, with packages requesting specific badges via issues and reviewers granting timed badges that indicate when checks were verified.
Participants identified problems with the current pipeline, including projects stagnating at levels and potential UX issues if many individual badges are shown on the Swift Package Index, and they proposed solutions including an SSWG-recommended aggregated badge, a nutrition-label style breakdown on click-through, timestamped yearly re-evaluation of recommendations, and hosting the list in a public repository for the workgroup.
The group agreed to refine and reflow the document, to request a server/workgroup repository, to circulate the updated proposal, and to share the approach with other workgroups; Konrad committed to reflow the doc and to proceed with next steps.
Docs migration and reviews
Joe reported that a swift.org/docs repository has been created and that three initial guides (building, testing, packaging) were migrated, with the building guide prepped for review and more content queued in the pipeline.
Joe asked how to request reviewers and whether the group wants to be used as code owners for the docs repository, and participants recommended using the server workgroup as code owners and agreed to configure reviews accordingly.
Joe noted that some PR review configuration appeared broken and said he would follow up with Michelle to resolve the review pings, and Joe invited others to help with reviews and edits so content can be iterated and approved more quickly.
Konrad Malawski: Contact the core team to request a GitHub repository for the workgroup.