NS8 NethForge applications index

Feature
21

not really…

i always come back to this, every time i need to assign an app category.

22

I noticed there are apps without assigned category. So it is not mandatory.

23

Should have category or. Maybe a default category called uncategorized, otherwise when the list of apps grows… Mayhem

24

That was/is an issue with RPMs, too–they’d want (but not require) a Group: field in the .spec file, but there was no canonical list of suitable groups. As a result, that field is pretty much useless in categorizing RPMs.

25

@oneitonitram if you’re curious, I got the list from the source code (translation strings):

1 Like
26

nice one, i had no idea where to look, i guess i was just lazy or something.

i think that list could us more

27
  • entertainment
  • media
  • miscellaneous

The last one especially to serve as a “catch all” ‘if <> defined == miscellaneous’, so an app always has a category no matter what.

28

I have been looking into implementing homelab solutions into Nethserver. The Arr stack. Sonarr, etc. And many others, but am not really sure, since the storage issue, and some of these apps needs to share folder. So Nethserver 8 might not be a great solution for homelab and entertainment. Rather stick with casaos truenas scale and others. Unless there is a storage solution in future.

29

With the increased Apps and categories of apps, could we have the list of available or supported categories, added, or increased before the next core relase? or by 8.2 version when we have the new software centre?

2 Likes
30

I miss:

  • Productivity
  • Finance
    and maybe more, let’s make a list o chew on…

Here is a draft list.

2 Likes
31

I agree, more categories are needed!

At this stage, we can expand the existing list. If an app falls under multiple categories, you can set them in the metadata.json file.

@LayLow’s proposal looks good! Feel free to open a PR for the file already pointed out by Dnutan.

32

In addition: The development status (alpha, beta, production) should be prominently displayed.

33

Example on the wiki.

34

The development status depends on the point of view:

  • Developers: It’s ready for production!
  • Users: This sucks, it’s alpha software!

When an application is submitted to a public software repository, it must be reviewed before publishing. It may be considered incomplete (beta) but still ready for production. In such cases, the application name can simply include the word “Beta.”