[META] Starshot work tracks

Should there be a track for accessibility testing? Since Starshot is intended to bring in functionality from contrib modules, accessibility compliance isn't necessarily guaranteed.

Thanks. I had raised the quest about accessibility testing/review in a few different places. Although it can’t be guaranteed, maybe there are people who’d still want to focus on this both for the marketing designs and for the user interfaces for each piece (XB, PB, AU, etc). There’s been discussion about usability testing so it seems like a natural fit to have some basic accessibility testing too. Even if things aren’t addressed for the MVP, there can be issues raised for future work.

Updated to indicated assigned status

Thanks! Can you make a note somehow that track 1 is owned by the leadership team?

Would it make sense to rename Starshot -> Drupal CMS on all issues like this?

IMO yes - let's rename this one at least.

Curious if anyone was selected for the multilingual track?

And if other tracks are coming in the next few months?

@kristen pol we had a multilingual track lead but they had to step down. Somewhat as a result we had to deprioritise that recipe for now, and haven't done any recruitment for a new lead yet. Hoping to look at all of that after 1.0 release!

Add 🌱 [meta] Migrations into Drupal CMS Active to the list.

Wondering if Starshot should be replaced by Drupal CMS in the issue summary. Is the former being used as the internal product name?

I think we should close this off, since all of the existing tracks were aimed at 1.0. There is obviously work still ongoing but I think we should start fresh.

I'll work on that, but in the meantime I would not worry about updating this.