Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
E
extensions.typo3.org
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 59
    • Issues 59
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • services
    • T
      t3o sites
  • extensions.typo3.org
  • extensions.typo3.org
  • Issues
  • #202

Closed
Open
Opened Sep 01, 2017 by Thomas Mayer@thomas303

Show alternatives to outdated extensions

What kind of feature do you want?

In the detail view, alternatives to an outdated extension could be shown up.

For instance, I'll leave open how this can be done.

One way to do this would be to use the tags and to determine a notion of similarity towards other extensions.

Another way would be to let maintainers explicitly specify which extensions can be migrated to their extension (similar to the specification of incompatibility). The latter should then also take versions into account (from_version/to_version) which maybe overcomplicates this approach.

Another way to do this is to use frequent pattern mining based upon the sequence of page visits, thereby answering which (alternative) extension is likely to be downloaded after visiting an outdated extension.

An easy catch would be to just point to the TER search page, thereby querying for the tags of the outdated extension.

What are the benefits?

  • Show up that there is an alternative.
  • Trick users into supported extensions which receive security updates.

Add some use case

E. g. the outdated extension tq_seo can be seemlessley upgraded to metaseo via a documented migration path.

Edited Sep 01, 2017 by Thomas Mayer
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: services/t3o-sites/extensions.typo3.org/ter#202