Comet Sprint 37/ Daylight Sprint 9/ Lark Sprint 12 Review

What were the goals of Comet Sprint 37/ Daylight Sprint 9/ Lark Sprint 12?

Comet: We have a number of bugs which have been identified in Bulkrax; we would like to fix these and/or confirm that earlier fixes work. There are a lot of discussions we are hoping to have regarding production stability and staging environments, which we hope will produce more actionable tickets for later in the workcycle.

Daylight: We would like to identify (and start developing) shared components and hone our strategy for deploying them, and we would like to create a process for publishing a backend gem that we can use in our discovery platforms.

Lark: We would like to work our way through the spike to moving to Rails, with the end goal of merging some of the related work around deploying it to production, and ideally (by the end) at least be able to seed some data into Lark through a CI task.

What is the milestone that this sprint is supporting?

Comet: Continuing discussion revolving around the stability of our staging and production environments, and continue to test Bulkrax to identify existing issues that need resolving.

Daylight: The milestone this sprint is supporting the establishment of a shared component library, including identifying shared components, setting accessibility expectations, and creating documentation.

Lark: We want to be able to deploy Lark reliably, leveraging code that we have written for other platforms to provide access controls and other functionality.

Accomplishments of Comet Sprint 37/ Daylight Sprint 9/ Lark Sprint 12 

Comet:

• Engaged on discussions related to deployments/reliability of Comet and agreeing on a syntax for nested resources.
• Resolved 9 bug tickets related to Bulkrax Importer.

Daylight:

• Created comprehensive documentation for the shared component library, including component names, cardinality, and descriptions.
• Established accessibility guidelines, including the use of semantic HTML, ARIA roles, attributes, and keyboard accessibility.
• Recommended tools and practices for accessibility testing, such as SiteImprove's browser extension.

Lark:

• Did a research spike to determine the feasibility of migrating to a Rails codebase.
• Opened additional tickets for future work.

Did we do everything we set out to accomplish? 

Comet: The team made wonderful progress with much-needed discussions, and all Bulkrax Importer bug tickets have been closed, with a few new tickets created as a result of the latest testing.

Daylight: We completed documentation and accessibility guidelines, made progress on the backend gem publishing, but did not continue component development.

Lark: It would have been nice to get further on the Rails migration, but we are in a good place to complete that work in the next sprint.

GitLab link: https://gitlab.com/surfliner/surfliner/-/milestones/117#tab-issues