tech-dossiers/ngi0-landing
10
1
Fork 0
Code Issues 14 Pull requests Projects Releases Packages Wiki Activity Actions

Possibility for a health field or status elements on a per-project basis? #12

New issue
Open
opened 2025-11-10 17:17:28 +01:00 by hernani · 3 comments
hernani commented 2025-11-10 17:17:28 +01:00
Member
Copy link

Panos (partner: ISOC-CH/NGI0) just proposed to have a possibility to know when a project was actually tested to practically work for an end-user perspective; it's basically about avoiding to list projects which don't work at all, or that are in a too experimental state.

The projects file src/data/ngi0Projects.ts, where all projects we reference are listed, could be used for this purpose, similarly as with the start and end attributes including their optionality.

Panos (partner: ISOC-CH/NGI0) just proposed to have a possibility to know when a project was actually tested to practically work for an end-user perspective; it's basically about avoiding to list projects which don't work at all, or that are in a too experimental state. The projects file `src/data/ngi0Projects.ts`, where all projects we reference are listed, could be used for this purpose, similarly as with the `start` and `end` attributes including their _optionality_.
puer-robustus commented 2025-11-17 14:49:07 +01:00
Member
Copy link

My notes on this from the 12.11.25 TD meeting:

I think we need different metadata fields:

  • project maturity: alpha, beta, mature
  • target audience: developers, SMEs, government, etc.
  • software type: cloud vs local
  • etc.
My notes on this from the 12.11.25 TD meeting: > I think we need different metadata fields: > - project maturity: alpha, beta, mature > - target audience: developers, SMEs, government, etc. > - software type: cloud vs local > - etc.
hernani self-assigned this 2026-05-04 09:08:19 +02:00
hernani commented 2026-05-04 09:11:22 +02:00
Author
Member
Copy link

I'll try to implement this, in a way the field is of course not required to be defined in the ngi0Projects.ts file where all projects are defined (similarly to the start and end attributes).

Major issue and work will anyways be annotating the individual projects so-then

Maybe an explanatory Maturity level section on projects annotated by this, also to be fair to the devs (if they wonder), should be given.

I'll try to implement this, in a way the field is of course not required to be defined in the `ngi0Projects.ts` file where all projects are defined (similarly to the `start` and `end` attributes). Major issue and work will anyways be annotating the individual projects so-then Maybe an explanatory _Maturity level_ section on projects annotated by this, also to be fair to the devs (if they wonder), should be given.
ijohn commented 2026-06-08 18:33:35 +02:00
Owner
Copy link

If you have any trouble with the implementation I can do it @hernani.

If you have any trouble with the implementation I can do it @hernani.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/use-export
feature/image-fixes
feature/embla-carousel
feature/nix-for-users-dossier
fixes
nix-flake
flake
No results found.
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
stale
May be solved, did not have traction for a while

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
stale
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
hernani
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tech-dossiers/ngi0-landing#12
No description provided.