Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Enhancement request: Product as part of another product

Aperta
  • Qualcosa non va?
#87 3 commenti 1 reazione 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@DennisClark ci sta già lavorando.

Dal 1/5/2024.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

design needed enhancement

Is your enhancement request related to a problem? Please describe.
It can happen that a software is both released as a standalone product A and simultaeously as part of a bigger product B. Ideally the package dependencies would not have to be added and reviewed for the product B a second time, but rather product A can be included in product B.

What are the benefits of the requested enhancement?

  • No need to update entries twice (or more) on multiple products that use product A
  • No risk of inconsistent data in products that make use of product A
  • Review steps only have to be done once for product A
  • Ability to create hierarchy of products

Describe the solution you would like

  • Option 1: Components pretty much cover the hierarchy and nesting, but do not allow to import SBOMs like products
    • Implement SBOM import for components, much like with products
    • User can then add the software as a component
      • For product A we would simply add the component to the inventory and nothing else (standalone)
      • For product B we would add the component among other components and packages to the inventory (bigger product)
    • Export of the SBOM for a product with components must properly include everything that the components depend on (I haven't tested that yet, may already be the case)
  • Option 2: Add a nesting and hierarchy feature to products (much like with components)
    • This might make less sense, because then there is even less distinction between components, though products would still be for software that we produce, while components are those that we consume

Additional notes
I have asked about this on gitter and was directed to the issue tracker. I may have misunderstandings what components should be used for so apologies if the suggestion goes against the intended design. I'm also not entirely sure why the package associated with components seem to be handled differently with regard to permissions when compared to products. Components seem to be fairly locked off and only editable by the data admins.

Lingua principale
Python
Stelle
52
Fork
30
Merge medio
4h 57m
PR unite (30g)
21

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aboutcode-org/dejacode

Tutte le issue di aboutcode-org/dejacode

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.