Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
E
extensions-directory
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Extensions
  • extensions-directory
  • Issues
  • #56

Closed
Open
Opened Dec 24, 2020 by ayduns@ayduns

Cleaning up the Extensions Directory?

The role of the Extensions Directory has evolved a bit. I'm not sure whether we have a good description of what it is or should be beyond the intro on the page:

"Extensions are installable packages which give CiviCRM new functionality, and this directory provides a centralized list of extensions which the CiviCRM community has created."

https://lab.civicrm.org/extensions says:

CiviCRM extensions repositories. See also the official extension directory on civicrm.org. | ExtDir meta

But it really doesn't look very 'official'!

There are many other extensions not in this directory so it is not a centralized list of all extensions. It seems to be evolving towards a somewhat curated list of extensions that are installable in-app or in some way approved. This is the place we point to if people want to see what else they can do with Civi and forms part of our marketing.

How do we clean up the directory?

We have things like notify-speakers listing compatibility as 4.2, status of alpha and with a broken download link. This one looks like it may have been an example from Tim at some point but that's just one and there are a many others that could be culled. How do we get rid of these?

We also have many without a meaningful summary, even on the first page of the directory.

Maybe a simple start would be to mail all maintainers of extensions in that directory including links to the edit pages, asking them to review whether the extension should still be listed at all, and if so, to make sure the summary is useful to those browsing the directory.

Thoughts?

Edited Dec 24, 2020 by ayduns
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: extensions/extensions-directory#56