Enhancement request: Support richer product hierarchies

Open
#188 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No files, tests, or entry points are named. Start by reviewing how the current Product, Component, Package, and version hierarchy is represented, then compare it with the Eclipse Foundation hierarchy described in the issue. Done requires an agreed scope and implementation for richer categorization, navigation, tagging, and reporting.

Written by the indexing model from the issue text.

Description

design needed enhancement

Today, we have a single, flat list of products with this hierarchy:

  • Product
    • Component (optional)
      • Package
    • Package

And each product has versions.

But products have often much richer structures, including product lines, product teams, release trains, and so on. As an open source example, the Eclipse Foundation project provides a good template of a large and rich Product/Project hierarchy, with many packages.

This can be useful to manage compliance and vulnerability at scale to have richer tagging, categorization, navigation and reporting following a product teams, product lines, and related hierarchies.

Dominant language
Python
Stars
53
Forks
32
Avg merge
16h 44m
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/dejacode

All issues in aboutcode-org/dejacode

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.