A few weeks ago, we introduced the concept of "tracks" as the next step in progressing the Drupal Starshot project. Tracks are smaller, focused parts of the project that allow for targeted development and contributions.
At the same time, we put out a call for Starshot track leads, and were overwhelmed by the response. We received nearly 65 submissions, showcasing a wide range of expertise and ambitious vision that made for a difficult review process.
Announcing new track leads
We are proud to announce the newest track leads, who bring to the Starshot team an impressive depth of experience both in Drupal and in their respective track space:
- Laurens Van Damme from Dropsolid will be leading the Blog recipe track
- Jürgen Haas from LakeDrops will lead the Privacy track
- Christian López Espínola and Matthew Tift from Lullabot will lead the Dashboard track
- Jim Birch from Kanopi and John Doyle from Digital Polygon will lead the Sitewide SEO recipe track
- Jamie Abrahams from FreelyGive will lead the AI track
- Tony Barker from Annertech will lead the Media management track
- Baddy Sonja and the team at 1xinternet will lead the Advanced search track
- Gareth Alexander from Zoocha will lead the Accessibility tools track
- Dharizza Espinach and the team at Evolving Web will lead the Analytics track
- Pavlos Daniel from Acquia will lead the Multilingual content track
Although we announced the concurrent editing track, this is an aspirational feature that we would love to see but have postponed because it will depend heavily on Experience Builder.
Further opportunities with tracks
If you've read the Starshot strategy that Dries shared, you may have noticed that there are capabilities listed that do not yet have a track. We will be creating more tracks ongoing, to align with this strategy as the need arises (and as our capacity allows!).
There are also three existing tracks that we have not yet assigned a lead:
If you are interested in leading one of these, make sure to review the issues for information about what we are aiming for, as well as the track lead role description. Your vision for the track, which need only be a short summary of how you plan to approach it, should take these into account when you submit an application.
Next steps for tracks
For most tracks, the initial work will be to put together a proposal, which may require research to define the key requirements for our target persona and determine what feature parity with market leaders looks like. The proposals will be shared with the community for consultation.
We also expect track leads to provide regular progress updates, with the format and frequency still to be determined.
If you want to contribute to one of the tracks, or just follow along, keep an eye on the meta issues in the Starshot queue or post a comment to put your hand up.