speedie/speedie-page
Archived
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Add new blog post, number 60. Modify credits to reflect the Gitea

Browse source 
migration made.

Also fix typo in the last blog post causing <code> tag to not be closed. I'm
on Matrix too much apparently.
This commit is contained in:
speedie 2023-06-08 12:20:58 +02:00
parent c92dd074a8
commit 30d0db9d5d
5 changed files with 62 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
articles/post59.php
View file

@ -13,7 +13,7 @@
<h2>Yet another update post.</h2>
<h4>2023-06-03</h4>
<p>Wow, look at that. Even more junk to fill my catalog and make it look like I've done more writing than I actually have. Oh well. I'll get straight to the point. At approximately 02:32 I quickly made the decision to move from cgit to Gitea for hosting my Git repositories and projects. For this reason, links to the old Git repositories need to be changed. This mainly applies to those of you that are using speedie-aur, or speedie-overlay. I'm assuming that's quite few of you, but just in case I'm putting this out there.</p>
<p>If you're using speedie-aur, you'll need to edit <code>/etc/pacman.conf</code> and change the <code>Server</del> to <code>Server = https://git.speedie.site/speedie/speedie-aur/raw/branch/master/$arch</code> If you're using speedie-overlay you'll want to remove the overlay and add it again. See <a href="https://git.speedie.site/speedie/speedie-overlay">the repository</a> for more information. The Arch wiki article has been updated to reflect these changes as well, and so has the overlay.xml.</p>
<p>If you're using speedie-aur, you'll need to edit <code>/etc/pacman.conf</code> and change the <code>Server</code> to <code>Server = https://git.speedie.site/speedie/speedie-aur/raw/branch/master/$arch</code> If you're using speedie-overlay you'll want to remove the overlay and add it again. See <a href="https://git.speedie.site/speedie/speedie-overlay">the repository</a> for more information. The Arch wiki article has been updated to reflect these changes as well, and so has the overlay.xml.</p>
<p>I have also moved over a lot of GitHub repositories to my Gitea instance, such as my Gentoo kernel for my ThinkPad and desktop, multiple OpenCore configurations, and more, but all Codeberg and GitHub repositories are still accessible. It should be noted though, that I plan on moving all website development to the Gitea instance rather than Codeberg.</p>
<p>What you may be screaming right now is WHY? I'll tell you why. Cgit is an excellent Git viewer, but that's all it is. A git viewer. It doesn't handle your repositories, no issue tracking, no pull requests, no users, nothing. This is fine when you're the only one working on a project, as you're going to do most work locally on your computer anyway, and then push using Git from the command line.</p>
<p>The problem is when you want to have any kind of collaboration, which is something I realized today (and yesterday). As some of my projects are becoming increasingly complex, I need a way for people to submit bug reports and fix issues. Emailing isn't convenient for the user, and it isn't convenient for me either. Now that I'm using Gitea, any user may create an account and simply create an issue or pull request. There's not any more to it, just simple. If you're familiar with GitHub or even one of the public Gitea instances like Codeberg, this is likely nothing new to you.</p>

33
articles/post60.php Normal file
View file

@ -0,0 +1,33 @@
<!DOCTYPE html>
<html>
<head>
<?php include '../php/header.php';?>
<title>You don't need to justify your decisions.</title>
<meta charset="UTF-8">
<meta name="description" content="I often hear people following my blog or just know me for one reason or another, but you don't need to justify your use of software to me.You don't need to justify your use of software or hardware, that is a personal decision you are making. I am not going to make that for you, and while I may not agree with your decision, it is not mine to make.">
<meta name="author" content="speedie">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="content">
<h2>You don't need to justify your decisions.</h2>
<h4>2023-06-08</h4>
<p>I often hear people following my blog or just know me for one reason or another, and usually it goes something like this:</p>
<blockquote>
<p>Hello speedie I enjoy reading your blog.</p>
</blockquote>
<p>Thanks!</p>
<blockquote>
<p>I’m using X nonfree software or Y desktop environment, sorry about that.</p>
</blockquote>
<p>This is the problem. I see far too many people apologize for their choices in technology, but I want to make one thing clear. I am not here to judge your technology choices. If you want to read my blog on Windows and/or Mac, use nonfree programs, hate my software or ideas, or do something else I’m not <em>personally</em> a fan of then you are 100% free to do so. You don’t need to justify your use of software or hardware, that is a personal decision you are making. I am not going to make that for you, and while I may not agree with your decision, it is not mine to make.</p>
<p>I may <strong>suggest</strong> replacements for the software you’re
using if I believe it’s something you would benefit from (such as learning Vim or getting into tiling window managers), but I’m never going to force you to use/do something, or shame you for using the nonfree software or software I simply don’t like. I am also never going to force you to believe the same thing as me, that’s idiotic, and the definition of an echo chamber, something I’m very against. I don’t want 15 speedie clones, you should have your own ideas, and I should have my own ideas. If we agree then we do, if we don’t, then we don’t. I make decisions you may find stupid, you make decisions I may find stupid, and if we don’t debate each other’s ideas, we lose the ability to think for ourselves.</p>
<p>That’s not to say it’s harmful to criticize the choices others make, but you need to be willing to see both sides of the coin, and like it or not you need to accept the choice the other person is making, whether you approve of it or not. That’s just a short blog post for today, as I see this far too often, and I think it’s important to say this. I’m probably going to talk about Wayland development, Wayland libraries, Wayland protocols and Wayland implementations next time now that I’ve truly given Wayland development a fighting chance to win me over. That’s it for me, have a good day!</p>
</div>
</body>
<footer>
<?php include '../php/footer.php';?>
</footer>
</html>

2
blog.php
View file

@ -23,6 +23,8 @@
<li><a href="rss-archived-01.xml">Blog post archive feed (1-36)</a></li>
</ul>
<h3>Articles</h3>
<h4 id="60">Posts 60-69</h4>
<h5><a href="articles/post60.php">You don't need to justify your decisions.</a>, written 2023-06-08</h5>
<h4 id="50">Posts 50-59</h4>
<h5><a href="articles/post59.php">Yet another update post.</a>, written 2023-06-03</h5>
<h5><a href="articles/post58.php">Swedish man rants about licenses again</a>, written 2023-05-23</h5>

6
credits.php
View file

@ -3,7 +3,7 @@
<head>
<?php include 'php/header.php';?>
<meta charset="UTF-8">
<meta name="description" content="Credit where credit is due.">
<meta name="description" content="Credit for the speedie.site page and services I run.">
<meta name="author" content="speedie">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Credits</title>
@ -14,9 +14,9 @@
<p>Credits for this website and all services I run.</p>
<ul>
<li>speedie.site</li>
<p>The initial concept for this site was designed by <a href="https://donut.eu.org">donut.eu.org</a>. I have expanded on it and rewritten a lot of the styling since. Thank you!</p>
<p>The initial concept for this site was designed by <a href="https://donut.eu.org">donut.eu.org</a>. I have expanded on it significantly and rewritten a lot of the styling since. Thank you!</p>
<li>git.speedie.site</li>
<p>Favicon and logo was designed by <a href="https://donut.eu.org">donut.eu.org</a> in scalable vector format. git.speedie.site is a cgit instance.</p>
<p>git.speedie.site is a Gitea instance.</p>
<li>ls.speedie.site</li>
<p>ls.speedie.site is a fork of <a href="https://github.com/lorenzos/Minixed">MINIXED</a> with mostly styling changes.</p>
<li>speedwm.speedie.site, spmenu.speedie.site, wiki.speedie.site</li>

24
rss.xml
View file

@ -509,7 +509,7 @@
<description>
<![CDATA[
<p>Wow, look at that. Even more junk to fill my catalog and make it look like I've done more writing than I actually have. Oh well. I'll get straight to the point. At approximately 02:32 I quickly made the decision to move from cgit to Gitea for hosting my Git repositories and projects. For this reason, links to the old Git repositories need to be changed. This mainly applies to those of you that are using speedie-aur, or speedie-overlay. I'm assuming that's quite few of you, but just in case I'm putting this out there.</p>
<p>If you're using speedie-aur, you'll need to edit <code>/etc/pacman.conf</code> and change the <code>Server</del> to <code>Server = https://git.speedie.site/speedie/speedie-aur/raw/branch/master/$arch</code> If you're using speedie-overlay you'll want to remove the overlay and add it again. See <a href="https://git.speedie.site/speedie/speedie-overlay">the repository</a> for more information. The Arch wiki article has been updated to reflect these changes as well, and so has the overlay.xml.</p>
<p>If you're using speedie-aur, you'll need to edit <code>/etc/pacman.conf</code> and change the <code>Server</code> to <code>Server = https://git.speedie.site/speedie/speedie-aur/raw/branch/master/$arch</code> If you're using speedie-overlay you'll want to remove the overlay and add it again. See <a href="https://git.speedie.site/speedie/speedie-overlay">the repository</a> for more information. The Arch wiki article has been updated to reflect these changes as well, and so has the overlay.xml.</p>
<p>I have also moved over a lot of GitHub repositories to my Gitea instance, such as my Gentoo kernel for my ThinkPad and desktop, multiple OpenCore configurations, and more, but all Codeberg and GitHub repositories are still accessible. It should be noted though, that I plan on moving all website development to the Gitea instance rather than Codeberg.</p>
<p>What you may be screaming right now is WHY? I'll tell you why. Cgit is an excellent Git viewer, but that's all it is. A git viewer. It doesn't handle your repositories, no issue tracking, no pull requests, no users, nothing. This is fine when you're the only one working on a project, as you're going to do most work locally on your computer anyway, and then push using Git from the command line.</p>
<p>The problem is when you want to have any kind of collaboration, which is something I realized today (and yesterday). As some of my projects are becoming increasingly complex, I need a way for people to submit bug reports and fix issues. Emailing isn't convenient for the user, and it isn't convenient for me either. Now that I'm using Gitea, any user may create an account and simply create an issue or pull request. There's not any more to it, just simple. If you're familiar with GitHub or even one of the public Gitea instances like Codeberg, this is likely nothing new to you.</p>
@ -519,5 +519,27 @@
]]>
</description>
</item>
<item>
<title>You don't need to justify your decisions.</title>
<link>https://speedie.site/articles/post60.php</link>
<guid>https://speedie.site/articles/post60.php</guid>
<pubDate>Thu, 08 Jun 2023 00:00:00 +0100</pubDate>
<description>
<![CDATA[
<p>I often hear people following my blog or just know me for one reason or another, and usually it goes something like this:</p>
<blockquote>
<p>Hello speedie I enjoy reading your blog.</p>
</blockquote>
<p>Thanks!</p>
<blockquote>
<p>I’m using X nonfree software or Y desktop environment, sorry about that.</p>
</blockquote>
<p>This is the problem. I see far too many people apologize for their choices in technology, but I want to make one thing clear. I am not here to judge your technology choices. If you want to read my blog on Windows and/or Mac, use nonfree programs, hate my software or ideas, or do something else I’m not <em>personally</em> a fan of then you are 100% free to do so. You don’t need to justify your use of software or hardware, that is a personal decision you are making. I am not going to make that for you, and while I may not agree with your decision, it is not mine to make.</p>
<p>I may <strong>suggest</strong> replacements for the software you’re
using if I believe it’s something you would benefit from (such as learning Vim or getting into tiling window managers), but I’m never going to force you to use/do something, or shame you for using the nonfree software or software I simply don’t like. I am also never going to force you to believe the same thing as me, that’s idiotic, and the definition of an echo chamber, something I’m very against. I don’t want 15 speedie clones, you should have your own ideas, and I should have my own ideas. If we agree then we do, if we don’t, then we don’t. I make decisions you may find stupid, you make decisions I may find stupid, and if we don’t debate each other’s ideas, we lose the ability to think for ourselves.</p>
<p>That’s not to say it’s harmful to criticize the choices others make, but you need to be willing to see both sides of the coin, and like it or not you need to accept the choice the other person is making, whether you approve of it or not. That’s just a short blog post for today, as I see this far too often, and I think it’s important to say this. I’m probably going to talk about Wayland development, Wayland libraries, Wayland protocols and Wayland implementations next time now that I’ve truly given Wayland development a fighting chance to win me over. That’s it for me, have a good day!</p>
]]>
</description>
</item>
</channel>
</rss>