[META] Plan/Proposal to Implement Ecosystem

Open on Drupal.org →

Created on 15 August 2023, over 1 year ago

Updated 14 May 2024, 6 months ago

Problem/Motivation

There was a long discussion in the Drupal Slack #project_browser about how to implement and use "Ecosystem" (or "use case") within Project Browser. https://drupal.slack.com/archives/C01UHB4QG12/p1691619831056999

"Ecosystem" (or "use case") was an early idea/discussion point as we started Project Browser, which has persisted. We have been focused on Project Browser for modules and identified early on there was a big need to fix categories. Now that we are getting close to that (for modules). We still have the issue of how to implement the Ecosystem (or "use case") within Project Browser.

This is the {META] Plan issue for this idea and how it would all work - from the implementation to the migration to the ongoing maintenance process.

Proposed resolution

The general consensus in the thread concluded we should create a managed list of Ecosystems (or "use case"), perhaps replacing the existing Ecosystem field on the project content type.

There were already related issues for to this idea, which have been added as child issues, Add filter by project dependencies (ecosystem) ✨ Add filter by project dependencies (ecosystem) Active and Define how to implement Ecosystem for Project Browser ✨ Define how to implement Ecosystem for Project Browser Active .

The anticipated process to develop and create this new ecosystem (or "use case") will also include tasks such as the following:

Define Ecosystem - that idea seemed to change from “This module is compatible with” to “designed to work together” in this thread
Research currently identified ecosystems
Create the plan. Discuss the concept and options for the management/maintenance/technical implementation.
Do it, this will likely include changes on the D.O. infrastructure, and within Project Browser.
Define the Governance model for Ecosystems (or "use case")

Remaining tasks

✅ File an issue about this project
☐ Manual Testing
☐ Code Review
☐ Accessibility Review
☐ Automated tests needed/written?

🌱 Plan

Status

Active

Version

1.0

Component

Other

Created by

🇺🇸United States bsnodgrass

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @bsnodgrass
Comment about 1 year ago →
🇺🇸United States drumm NY, US
Removing taxonomy implementation detail, it is too soon to think about implementation, when the purpose of this data hasn’t been fully decided, as far as I can see.

I’d encourage thinking about moving the labeling away from “ecosystem.” For a novice user, I can’t imagine that labeling being informative.
Comment 6 months ago →
🇺🇸United States bsnodgrass
At DrupalCon Portland 2024, a number of us involved in the Project Browser and Recipes initiative discussed "ecosystem" (or "use case") and how this might be used with search moving forward. I think now is an appropriate time to pick this task up again. I agree with @drumm our first step is to define what this is and how we intend to use it. I modified the Issue Summary.

Also, if I recall, we discussed some research started on the currently defined "ecosystems" displayed as "Project that extend this" in the sidebar on project pages. This research was not noted on this issue.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024