Add source code link, license and language/platform tag to all entries #73

New Issue

GiteaMirror · 2025-11-06T16:44:14-06:00

GiteaMirror commented

2025-11-06 16:44:14 -06:00

Originally created by @nodiscc on GitHub (Oct 9, 2022).

Contribution guidelines have been updated (https://github.com/awesome-foss/awesome-sysadmin/blob/master/.github/PULL_REQUEST_TEMPLATE.md) and now include:

Format your submission as follows, where Demo and Clients are optional. Do not add a duplicate Source code link if it is the same as the main link. Keep the short description under 80 characters and use sentence case for it, even if the project's webpage or readme uses another capitalisation. Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`

The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.

All software added before this guideline, should now be updated to mention the source code URL, the Free/Open-source license they use, as well as the main server-side requirement.

There is no main license list, but SPDX identifiers (e.g. GPL-3.0, MIT, Apache-2.0 ...) should be used when possible.

If the software is installed though a language/platform-specific package manager (npm, pip, gem, composer, docker pull...), the language tag should probably be the corresponding language/platform (Nodejs, Python, Ruby, PHP, Docker ...). Programs that can be deployed as a single binary executable can use their respective language tag (C, Go, Rust...).

This will help moving the list towards a machine-readable format https://github.com/awesome-selfhosted/awesome-selfhosted/issues/1038

You can refer to the results of the latest Github actions workflow for a list of entries that do not respect the correct syntax.

Originally created by @nodiscc on GitHub (Oct 9, 2022). Contribution guidelines have been updated (https://github.com/awesome-foss/awesome-sysadmin/blob/master/.github/PULL_REQUEST_TEMPLATE.md) and now include: > - Format your submission as follows, where Demo and Clients are optional. Do not add a duplicate Source code link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. Demo links should only be used for interactive demos, i.e. not video demonstrations. > ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` > - The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. All software added before this guideline, should now be updated to mention the source code URL, the Free/Open-source license they use, as well as the main server-side requirement. There is no main license list, but [SPDX identifiers](https://spdx.org/licenses/) (e.g. `GPL-3.0`, `MIT`, `Apache-2.0` ...) should be used when possible. If the software is installed though a language/platform-specific package manager (`npm`, `pip`, `gem`, `composer`, `docker pull`...), the language tag should probably be the corresponding language/platform (`Nodejs`, `Python`, `Ruby`, `PHP`, `Docker` ...). Programs that can be deployed as a single binary executable can use their respective language tag (`C`, `Go`, `Rust`...). This will help moving the list towards a machine-readable format https://github.com/awesome-selfhosted/awesome-selfhosted/issues/1038 You can refer to the results of the latest [Github actions workflow ![](https://github.com/awesome-foss/awesome-sysadmin/actions/workflows/ci.yml/badge.svg)](https://github.com/awesome-foss/awesome-sysadmin/actions/workflows/ci.yml?query=branch%3Amaster++) for a list of entries that do not respect the correct syntax.

GiteaMirror added the curation help wanted labels 2025-11-06 16:44:14 -06:00

GiteaMirror closed this issue

2025-11-06 16:44:14 -06:00

GiteaMirror commented

2025-11-06 16:44:17 -06:00

@nodiscc commented on GitHub (Mar 28, 2023):

Issue description updated.

You can now refer to the results of the latest Github actions workflow for a list of entries that do not respect the correct syntax.

@nodiscc commented on GitHub (Mar 28, 2023): Issue description updated. You can now refer to the results of the latest [Github actions workflow ![](https://github.com/awesome-foss/awesome-sysadmin/actions/workflows/ci.yml/badge.svg)](https://github.com/awesome-foss/awesome-sysadmin/actions/workflows/ci.yml?query=branch%3Amaster++) for a list of entries that do not respect the correct syntax.

GiteaMirror commented

2025-11-06 16:44:17 -06:00

@nodiscc commented on GitHub (Sep 4, 2023):

Fixed in latest master.

@nodiscc commented on GitHub (Sep 4, 2023): Fixed in latest master.

GiteaMirror referenced this issue

2025-11-06 16:46:39 -06:00

[PR #73] [MERGED] Add iF.SVNAdmin #159

GiteaMirror referenced this issue

2025-11-19 21:00:32 -06:00

[PR #73] [MERGED] Add iF.SVNAdmin #790

Sign in to join this conversation.