The goal is to implement a site builder tool, including a project browser, which abstracts away the manual process of installation, updates, and dependency resolution - handling those items behind the scenes for the site builder. The end product might be a code-base installed-in-place on the server, or it might be a consolidated tar.gz/zip with the complete codebase to be uploaded to a host.
This initiative also has the potential to support the sustainability of the Drupal Association and our community programs, perhaps through the promotion of featured projects (modules, distros, themes) or even hosting providers that the output of the tool could be deployed to.
These changes can help Drupal retain its lower to mid-market users, lower the barrier to entry, and lower the cost of ownership for a Drupal site.
---
---
@Dries has endorsed this idea in a call with DA staff, core maintainers, and community volunteers. The notion of a project browser has been endorsed by many in the community in the past, including @webchick.
Here is the slide deck from the check-in between Core, the DA, and some interested community members about these initiatives.
---
Regular discussion is happening in the slack channel https://app.slack.com/client/T06GX3JTS/C01UHB4QG12.
Weekly meetings over zoom are also happening on Wednesdays at 2pm UTC (see https://www.google.com/search?q=utc+time+to+my+time for help with UTC time). Links to this meeting are posted in slack (sorry I don't have that link to post it here).
Join us :)
---
Sitebuilders, designers, developers are collaborating (with not too much friction) via slack - join us! Read through the chat history, and checkout this MVP document. Yes....
We're defining the MVP, check it out https://docs.google.com/document/d/1oMI9CZMOheiie1-8Xej-WdQLMeG4cVWmxaOT...
And there's also a proof of concept module that's an experimental demonstration of what can be done with the existing drupal.org API, see that module here dgo.to/project_browser.
The API for serving project information (for the browser to consume/utilize) will need some improvements/enhancements. These are being documented at https://www.drupal.org/project/infrastructure/issues/3218285 → .
Fixed
Proposed Plan
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Given that this is a full blown initiative now, we can close of the original idea. Thanks to everyone who offered to help!
Automatically closed - issue fixed for 2 weeks with no activity.