docs(rfc): add 0010 user flow #15

Open

BruceMcRooster wants to merge 6 commits from rfc/0010-user-flow into main

BruceMcRooster commented

2026-04-19 14:17:31 +00:00

(Migrated from codeberg.org)

The objective here is to explain the user flow in a way that can inform a more concrete implementation in the future.

Interested in feedback on where this might be unclear or edge cases might exist which I've overlooked.

The objective here is to explain the user flow in a way that can inform a more concrete implementation in the future. Interested in feedback on where this might be unclear or edge cases might exist which I've overlooked.

BruceMcRooster commented

2026-04-19 15:06:17 +00:00

(Migrated from codeberg.org)

Todo: create complete list of features, and map the availability of those features to each of the individual “roles.” This should be clearer on expectations and lead to a more straightforward path to implementation.
Will work on this when I get the chance. In the meantime, open to other comments.

Todo: create complete list of features, and map the availability of those features to each of the individual “roles.” This should be clearer on expectations and lead to a more straightforward path to implementation. Will work on this when I get the chance. In the meantime, open to other comments.

kritdass commented

2026-04-19 21:20:39 +00:00

(Migrated from codeberg.org)

This is super helpful for the API. These roles and permissions map perfectly to SLAC (RFC 0009).

A flowchart for role transitions would be great for clarity too. Once the feature mapping in your todo is ready, we can merge and move straight to implementation (at the API-level, at least).

This is super helpful for the API. These roles and permissions map perfectly to SLAC (RFC 0009). A flowchart for role transitions would be great for clarity too. Once the feature mapping in your todo is ready, we can merge and move straight to implementation (at the API-level, at least).

BruceMcRooster commented

2026-05-24 14:33:59 +00:00

(Migrated from codeberg.org)

I definitely would like another set of eyes to ensure the document is clear, but I feel it now covers the featureset nicely and can provide a straightforward path to implementation, despite not focusing on implementation details.

BruceMcRooster commented

2026-05-26 21:32:27 +00:00

(Migrated from codeberg.org)

Is there anything else (for example, is this something we want to address) we want to do for this RFC? It seems much of the discussion is around how other systems will need to be redefined because of it¹. Is this RFC ready to merge?

Example: https://codeberg.org/ScottyLabs/terrier/pulls/15#issuecomment-15932162 ↩︎

Is there anything else (for example, is [this](https://codeberg.org/ScottyLabs/terrier/pulls/15#issuecomment-15932129) something we want to address) we want to do for this RFC? It seems much of the discussion is around how other systems will need to be redefined because of it[^e.g.]. Is this RFC ready to merge? [^e.g.]: Example: https://codeberg.org/ScottyLabs/terrier/pulls/15#issuecomment-15932162

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin rfc/0010-user-flow:rfc/0010-user-flow

git switch rfc/0010-user-flow

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff rfc/0010-user-flow

git switch rfc/0010-user-flow

git rebase main

git switch main

git merge --ff-only rfc/0010-user-flow

git switch rfc/0010-user-flow

git rebase main

git switch main

git merge --no-ff rfc/0010-user-flow

git switch main

git merge --squash rfc/0010-user-flow