I'd like us to have a standard list of software we examine when we want to decide how to model things. I'm going to start the list here, and please comment if you have more items and I'll add them :) also comment if you think some items should be removed.

Proprietary software may be listed. Not because we want to appeal to them or anything; simply because they may have features we'd want to have in the free software community and to support in ForgeFed, and those features could eventually appear in libre software too. They may also happen to be used by many people/organizations and represent/demonstrate the actual needs that many people have. I don't endorse those proprietary things at all, I don't use them, and I very highly recommend that you don't use them either, and use the libre ones.

Version control systems

• Git
• Darcs
• Fossil (worth checking the issue/wiki/etc. features it supports)

Forges

• GitLab CE
• Gitea
• DarcsDen
• Pagure
• Sourcehut
• Phabricator

Proprietary: gitlab ee, github, bitbucket

Plain repo hosting

• cgit
• gitweb
• gitolite

Ticket tracking

• Trac
• Ikiwiki
• OpenProject
• Redmine

Proprietary: jira

authentication

• https://reclaimid.gitlab.io/

Feneas forum thread only for discussion, the actual list is only here in the issue

Pagure, which uses a different model than "user/repo".

pagure has name-spaces - repos URLs can be either "/user/repo", "/team/repo", or "/repo"

but even if it had only a single flat name-space (some others may, present or future), it just means that forge-fed should not specify or presume any specific URL schema