From 997186a3d27345441dcb235dc28c7589f861c389 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?benjamin=20melan=C3=A7on?= Date: Sat, 25 Jan 2025 20:41:55 -0500 Subject: [PATCH] Link the linkable links, add instructions about new users, and existing agarics --- tools/git-agaric-com-forgejo.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/tools/git-agaric-com-forgejo.md b/tools/git-agaric-com-forgejo.md index b812e51..abd9065 100644 --- a/tools/git-agaric-com-forgejo.md +++ b/tools/git-agaric-com-forgejo.md @@ -2,7 +2,7 @@ Create an organization for each client (Forgejo does not support sub-groups). - - https://git.agaric.com/org/create + - [git.agaric.com/org/create](https://git.agaric.com/org/create) - **Organization name** should be what you want in the URL— all lowercase, with dashes instead of any spaces (an "Organization full name" can be set in the organization settings later). - **Visibility** should be either **Public** or **Private** ("Limited" makes no sense for Agaric's diverse clients and initiatives). - For Drutopia and some other clients, the organization made for them should be public. @@ -17,11 +17,17 @@ Then migrate or make a new repository project (**New migration** or **New reposi - Be sure to check off what you want to migrate in addition to the code. - **Visibility** can have "Make repository private" left unchecked to keep it public. In this case it is worth noting why in the **Description**, for example "As a Drutopia project we hope others can learn from and emulate, this project is public." +Add members of Agaric who will be involved in the project to the **Owners** team (for example at `https://git.agaric.com/org/example/teams/owners`) at least until this feature request gets added to Forgejo: [#2712 - [FEAT] Common team(s) fo multiple organizations - forgejo/forgejo - Codeberg.org](https://codeberg.org/forgejo/forgejo/issues/2712) + ## User account creation and adding people to a project As of now, do *not* invite users by e-mail address directly from a Team tab but instead: -1. Create user at https://git.agaric.com/admin/users/new +1. Create user at [git.agaric.com/admin/users/new](https://git.agaric.com/admin/users/new) + - Leave **Authentication source** as "Local". + - Leave **User visibility** as "Private". + - Leave **Require user to change password** checked. + - Checkmark **Notify about registration via email** 2. Return to the team tab for the organization (`org/example-organization/teams` 3. Click into ('View') the 'Owners' team `/org/example-organization/teams/owners` (or create) the team named after the client (so `/org/example-organization/teams/example`) 4. Use the search user bar to find that user account and then—only if it autocompletes and you select the user—the "Add Team Member" button.