mirror of
https://github.com/NixOS/rfcs.git
synced 2025-11-08 19:46:12 +01:00
A hybrid approach to be considered by the future team
This commit is contained in:
parent
fa75eec1dd
commit
ee8633c528
1 changed files with 16 additions and 0 deletions
|
|
@ -147,6 +147,22 @@ A typical snippet of `lib.categories` will be similar to:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Hybrid approach
|
||||||
|
[hybrid-approach]: #hybrid-approach
|
||||||
|
|
||||||
|
A hybrid approach for code implementation would be implement two meta
|
||||||
|
attributes, namely
|
||||||
|
|
||||||
|
- `meta.categories` for Appstream-based categories
|
||||||
|
- the corresponding `lib.categories` should follow Appstream closely, with
|
||||||
|
few room to custom/extra categories
|
||||||
|
- `meta.tags` for Debtags-like tags
|
||||||
|
- while being inspired from the venerable Debtags work, the corresponding
|
||||||
|
`lib.tags` is completely free to modify and even divert from Debtags,
|
||||||
|
following its own way
|
||||||
|
- generally speaking, `lib.tags` should be less bureaucratic than
|
||||||
|
`lib.categories`
|
||||||
|
|
||||||
## Categorization Team
|
## Categorization Team
|
||||||
[categorization-team]: #categorization-team
|
[categorization-team]: #categorization-team
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue