Re: Gitlab Migration

[Daniel Fleischer <danflscr@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]

Eli Zaretskii [2021-08-28 Sat 10:30]  wrote:

> The list of issues we filed with GitLab was mostly about email-based
> workflow and other relevant features, because the Web-based workflow
> was supported by GitLab already.  It sounds like we now need to
> augment that list by the requirements from the Web-based workflow,
> since SourceHut and other platforms might lack them.
>
> Would someone like to come with a list of such requirements?

Here are some points:

1. Issues page; collection of bug report, feature suggestions and
general discussions, with or without code commits associated with them.
Ability to tag and search, including closed issues. Ability to define
"projects" which are short term goals and associate issues and PR with
them. Ability to assign issues to specific users. Ability to pin issues
at the top for easy discoverability.

1. PR page; since anyone can clone the project locally and make
modifications, PR page is a list of suggested changes, merges between
some branch in contributors' "local" projects and the original (usually
master) branch. Technically it's a patch. Ability to view the diff.
Ability to have discussions around the PR. Ability to continue modifying
the suggested code by all parties and the diff is kept up to date.
Indications of CI tests pass/fail. ADVANCED: ability to do quick code
edits and commits on the web.

1. Code exploration; view code with syntax highlighting for most file
types. Being able to jump to function definitions and usages (at least
in github). Many people explore code in the web before possibly cloning
it locally so it's an important QOL feature.

*Daniel Fleischer*