diff --git a/productivity/index.html b/productivity/index.html index 2a706c8..37ed9b1 100644 --- a/productivity/index.html +++ b/productivity/index.html @@ -95,7 +95,7 @@
  • ✅ Macro Workflow: Listing Projects that truly matter
  • ✅ Macro Time Management: Project Priorization and Calendar Scheduling
  • ✅ Micro Workflow: Todo Listing, Contextualizing, and Ordering Tasks
  • -
  • ✅ Collaborative Project Management (Kanban in Gitea)
  • +
  • ✅ Collaborative Project Management (Kanban in Forgejo)
  • ✅ Zero Email Workflow (in Thunderbird)
  • diff --git a/productivity/kanban/29.png b/productivity/kanban/29.png index 31cc440..6cb6ac6 100644 Binary files a/productivity/kanban/29.png and b/productivity/kanban/29.png differ diff --git a/productivity/kanban/index.html b/productivity/kanban/index.html index 790576f..3fdae56 100644 --- a/productivity/kanban/index.html +++ b/productivity/kanban/index.html @@ -8,7 +8,7 @@ - Collaborative Project Management (Kanban in Gitea) + Collaborative Project Management (Kanban in Forgejo) @@ -61,7 +61,7 @@
    Previous Page -

    Collaborative Project Management (Kanban in Gitea)

    +

    Collaborative Project Management (Kanban in Forgejo)

    @@ -79,7 +79,7 @@

    Rather than literally sending them your todo list text files over chat, you guessed it, you need a better, more serious solution. If you are familliar with Git (which is a distributed version control system, used to track versions of files), you may be thinking Github already, it is the biggest service for hosting open source code online, but the problem is that it was acquired by Microsoft in 2018. So if you're like me and you don't want your repositories taken down whenever microsoft feels like it (like what happened to Tornadocash), you need to put your repositories elsewhere:

    -

    Therefore to stay in line with our OPSEC requirements we need to use the FOSS, self-hostable alternative: Gitea. We'll use our Gitea instance for this tutorial, but you can do the same on your own gitea instance.

    +

    Therefore to stay in line with our OPSEC requirements we need to use the FOSS, self-hostable alternative: Forgejo. We'll use our Forgejo instance for this tutorial, but you can do the same on your own Forgejo instance (here's the tutorial on how to setup your own .onion Forgejo instance).

    @@ -118,7 +118,7 @@ welcome to my collaborative project! git checkout -b main git add README.md git commit -m "first commit" -git remote add origin https://git.nowhere.moe/nihilist/my-collaborative-project.git +git remote add origin http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/my-collaborative-project.git git push -u origin main hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all @@ -136,8 +136,8 @@ Switched to a new branch 'main' 1 file changed, 1 insertion(+) create mode 100644 README.md -Username for 'https://git.nowhere.moe': nihilist -Password for 'https://nihilist@git.nowhere.moe':yourpassword +Username for 'http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion': nihilist +Password for 'https://nihilist@git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion':yourpassword Enumerating objects: 3, done. Counting objects: 100% (3/3), done. @@ -145,7 +145,7 @@ Writing objects: 100% (3/3), 250 bytes | 250.00 KiB/s, done. Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 remote: . Processing 1 references remote: Processed 1 references in total -To https://git.nowhere.moe/nihilist/my-collaborative-project.git +To http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/my-collaborative-project.git * [new branch] main -> main branch 'main' set up to track 'origin/main'. @@ -188,7 +188,7 @@ branch 'main' set up to track 'origin/main'. - How to start the emergency shutdown script with a cinnamon keyboard shortcut -

    so let's create an issue for it in gitea:

    +

    so let's create an issue for it in Forgejo:

    In the title of the issue i like to mention the Category of the issue, followed by the todolist title, and in the description i mention the list of tasks that must be done to complete the issue:

    @@ -232,7 +232,7 @@ branch 'main' set up to track 'origin/main'.

    once the labels are added to each issue, you can see the overall progress of the project:

    -

    Now this is a small example, but if you want to see a real sized-project, check out the Opsec project i have on this project board:

    +

    Now this is a small example, but if you want to see a real sized-project, check out the Opsec project i have on this project board:

    And that's it! now you know how to handle a long-term large project. If you want to check out how i welcome collaborations on my opsec blog, check out the tutorial i made here.