fix kanban tutorial + forgejo mentions

This commit is contained in:
nihilist 2025-03-27 16:13:24 +01:00
parent 0a60c9f033
commit ee2c9465db
3 changed files with 10 additions and 10 deletions

View file

@ -95,7 +95,7 @@
<li><a href="macroworkflow/index.html">✅ Macro Workflow: Listing Projects that truly matter</a></li>
<li><a href="macrotime/index.html">✅ Macro Time Management: Project Priorization and Calendar Scheduling</a></li>
<li><a href="microworkflow/index.html">✅ Micro Workflow: Todo Listing, Contextualizing, and Ordering Tasks </a></li>
<li><a href="kanban/index.html">✅ Collaborative Project Management (Kanban in Gitea)</a></li>
<li><a href="kanban/index.html">✅ Collaborative Project Management (Kanban in Forgejo)</a></li>
<li><a href="zeroemail/index.html">✅ Zero Email Workflow (in Thunderbird)</a></li>
</ol>
</div>

Binary file not shown.

Before

Width:  |  Height:  |  Size: 697 KiB

After

Width:  |  Height:  |  Size: 437 KiB

Before After
Before After

View file

@ -8,7 +8,7 @@
<meta name="author" content="">
<link rel="shortcut icon" href="../../../../../../assets/img/favicon.png">
<title>Collaborative Project Management (Kanban in Gitea)</title>
<title>Collaborative Project Management (Kanban in Forgejo)</title>
<!-- Bootstrap core CSS -->
<link href="../../assets/css/bootstrap.css" rel="stylesheet">
@ -61,7 +61,7 @@
<div class="row">
<div class="col-lg-8 col-lg-offset-2">
<a href="../index.html">Previous Page</a>
<h1>Collaborative Project Management (Kanban in Gitea) </h1>
<h1>Collaborative Project Management (Kanban in Forgejo) </h1>
<img src="0.png" class="imgRz">
</div>
@ -79,7 +79,7 @@
<p>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, <a href="https://github.blog/news-insights/company-news/github-and-microsoft/">but the problem is that it was acquired by Microsoft in 2018.</a> So if you're like me and you don't want your repositories taken down whenever microsoft feels like it (like what happened to <a href="https://www.eff.org/deeplinks/2023/04/update-tornado-cash?language=el">Tornadocash</a>), you need to put your repositories elsewhere:</p>
<img src="2.png" class="imgRz">
<p>Therefore to stay in line with our OPSEC requirements we need to use the FOSS, self-hostable alternative: Gitea. We'll use our <a href="https://git.nowhere.moe/">Gitea instance</a> for this tutorial, but you can do the same on your own gitea instance.</p>
<p>Therefore to stay in line with our OPSEC requirements we need to use the FOSS, self-hostable alternative: Forgejo. We'll use our <a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/">Forgejo instance</a> for this tutorial, but you can do the same on your own Forgejo instance (here's the <a href="../../opsec/forgejo-anon/index.html">tutorial</a> on how to setup your own .onion Forgejo instance).</p>
</div>
</div><!-- /row -->
@ -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
<b>Username for 'https://git.nowhere.moe': nihilist
Password for 'https://nihilist@git.nowhere.moe':yourpassword</b>
<b>Username for 'http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion': nihilist
Password for 'https://nihilist@git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion':yourpassword</b>
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
</pre></code>
<p>so let's create an issue for it in gitea:</p>
<p>so let's create an issue for it in Forgejo:</p>
<img src="9.png" class="imgRz">
<img src="10.png" class="imgRz">
<p>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:</p>
@ -232,7 +232,7 @@ branch 'main' set up to track 'origin/main'.
<img src="26.png" class="imgRz">
<p>once the labels are added to each issue, you can see the overall progress of the project:</p>
<img src="28.png" class="imgRz">
<p>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 <a href="https://git.nowhere.moe/nihilist/blog-contributions/projects/1">project board</a>: </p>
<p>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 <a href="http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/blog-contributions/projects/1">project board</a>: </p>
<img src="29.png" class="imgRz">
<p>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 <a href="../../opsec/contribute/index.html">here</a>.</p>