The basics of issue tracking as well as the basics of contributing to wikis are still missing, hence this is still WIP.
Feedback on tone and overall idea is warmly welcome :)
Closes #26
The basics of issue tracking as well as the basics of contributing to wikis are still missing, hence this is still WIP.
Feedback on tone and overall idea is warmly welcome :)
I have decided to not write an article about the basics of contributing to a wiki right now, as I have no experience with Gitea wikis so far. Maybe someone might want to contribute. But I don't think that wiki basics are critical enough to block the rest of the guide.
So, this is ready for review now :)
I have decided to not write an article about the basics of contributing to a wiki right now, as I have no experience with Gitea wikis so far. Maybe someone might want to contribute. But I don't think that wiki basics are critical enough to block the rest of the guide.
So, this is ready for review now :)
By the way, I have created accounts for "Knut" on both codeberg-test and codeberg now, just so that noone tries to register to our documentation's test user, trolling people or the like 😄
If we decide to keep Knut as our documentation "mascot" and demo account (much like GitHub's octocat account), I could provide access to the accounts to Documentation contributors (if allowed and possible). We'd need a safe way to do so though.
By the way, I have created accounts for "Knut" on both codeberg-test and codeberg now, just so that noone tries to register to our documentation's test user, trolling people or the like :smile:
If we decide to keep Knut as our documentation "mascot" and demo account (much like [GitHub's octocat account](https://github.com/octocat)), I could provide access to the accounts to Documentation contributors (if allowed and possible). We'd need a safe way to do so though.
If we decide to keep Knut as our documentation "mascot" and demo account (much like GitHub's octocat), [...]
There has been a trade mark debate around the Berlin Zoo, if you have some time maybe check the EUIPO database to be sure
> If we decide to keep Knut as our documentation "mascot" and demo account (much like [GitHub's octocat](https://github.com/octocat)), [...]
There has been a trade mark debate around the Berlin Zoo, if you have some time maybe check the EUIPO database to be sure
Thanks for the heads up - I really didn't expect yet another legal landmine there!
Am I the only one who thinks it's a bit weird to trademark a real animal? 😅
But oh well, DPMA Register yields only non-active/revoked/rejected/deleted trademarks for "Knut Eisbär" and a search for "Knut" brought up no active trademarks that match our use of the name Knut AND be in the same Nizza class, in my layman opinion.
Thanks for the heads up - I really didn't expect yet another legal landmine there!
Am I the only one who thinks it's a bit weird to trademark a real animal? :sweat_smile:
But oh well, DPMA Register yields only non-active/revoked/rejected/deleted trademarks for "Knut Eisbär" and a search for "Knut" brought up no active trademarks that match our use of the name Knut AND be in the same Nizza class, in my layman opinion.
Another small investigation into this reveals that protection of the various Knut der Eisbär brands appears to have expired on or around 2017.
Additionally, I couldn't find the brand "Knut" on the website of the Berlin Zoo. There are some mentions of him in various articles, but I couldn't find any Knut products being sold there. There are various Knut-branded articles on Amazon, though they seem to be either not "official" or old-stock and so far I couldnt find one having to do with software or education.
Based on this information I as a layman think that the formely registered Knut brand is expired and will not collide with our use of the name Knut.
Nevertheless, I think we can come up with a better, more unique name than Knut. The more I think about the name Knut, the less appropriate I think it is to use that name for our mascot, given that it is name of a dead animal (even if it was famous once). It also might be hard to pronounce for English speakers.
So I think we could in principle merge this under the working title "Knut" but open a new issue in /Community or /Design looking for a proper mascot :)
Another small investigation into this reveals that protection of the various Knut der Eisbär brands appears to have expired on or around 2017.
Additionally, I couldn't find the brand "Knut" on the website of the Berlin Zoo. There are some mentions of him in various articles, but I couldn't find any Knut products being sold there. There are various Knut-branded articles on Amazon, though they seem to be either not "official" or old-stock and so far I couldnt find one having to do with software or education.
Based on this information I as a layman think that the formely registered Knut brand is expired and will not collide with our use of the name Knut.
Nevertheless, I think we can come up with a better, more unique name than Knut. The more I think about the name Knut, the less appropriate I think it is to use that name for our mascot, given that it is name of a dead animal (even if it was famous once). It also might be hard to pronounce for English speakers.
So I think we could in principle merge this under the working title "Knut" but open a new issue in /Community or /Design looking for a proper mascot :)
We should avoid using WebP for now, since Safari does not render it yet ([Gitea has support for Safari](https://docs.gitea.io/en-us/#browser-support)).
https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types
Safari 14 will support WebP, according to the release notes of the beta.
Does Safari auto-update? In that case, I think it would be okay to just wait and let time solve this problem, because if the Beta is out now, the final release can't be too far out.
The alternative would be to replace everything with png/jpeg, have much larger file sizes and thus much more traffic for the majority of our users.
Safari 14 will support WebP, according to the release notes of the beta.
Does Safari auto-update? In that case, I think it would be okay to just wait and let time solve this problem, because if the Beta is out now, the final release can't be too far out.
The alternative would be to replace everything with png/jpeg, have much larger file sizes and thus much more traffic for the majority of our users.
With Safari, updates are bundled with the OS. People would have to update to iOS 14 and macOS Big Sur before they can see WebP images.
With Safari, [updates are bundled](https://support.apple.com/en-us/HT204416) with the OS. People would have to update to iOS 14 and macOS Big Sur before they can see WebP images.
I feel very reluctant to change all the images on the site just because of Apple not keeping up. But I guess we have no choice, unless we want to exclude Mac and iPhone users, of which there are many.
In that case I will also have to change out the screenshots (and photo) of my 2FA guide. That will take some time, I can have a look at it in the evening.
Thanks for letting me know about that potential caveat! :)
I feel very reluctant to change all the images on the site just because of Apple not keeping up. But I guess we have no choice, unless we want to exclude Mac and iPhone users, of which there are many.
In that case I will also have to change out the screenshots (and photo) of my 2FA guide. That will take some time, I can have a look at it in the evening.
Thanks for letting me know about that potential caveat! :)
The red circles don't look very good. Perhaps we can use zoom and blur effects to draw focus instead, similar to how GitHub's guide does.
The red circles don't look very good. Perhaps we can use zoom and blur effects to draw focus instead, similar to [how GitHub's guide](https://guides.github.com/features/pages/) does.
Agreed, but let's change that with a separate PR, because then we'd unify image highlighting everywhere on Codeberg Documentation, not just in the Getting Started Guide.
Right now, I'd say we take it how it is, because changing the highlighting would be quite time-consuming and it's probably better to have a slightly imperfect guide than none at all.
Agreed, but let's change that with a separate PR, because then we'd unify image highlighting everywhere on Codeberg Documentation, not just in the Getting Started Guide.
Right now, I'd say we take it how it is, because changing the highlighting would be quite time-consuming and it's probably better to have a slightly imperfect guide than none at all.
- **Dashboard (1)** is the screen you're looking at right now. It gives you an overview of the newest activity
of you, the people you follow and in your or your organization's projects.
- **Issues (2)** and **Pull Requests (3)** These are overviews over issues and pull requests that you are either involved in or that are part of one of the organizations you belong to.
- **Dashboard (1)** is the screen you're looking at right now. It gives you an overview of the newest activity
of you, the people you follow and in your or your organization's projects.
- **Issues (2)** and **Pull Requests (3)** These are overviews over issues and pull requests that you are either involved in or that are part of one of the organizations you belong to.
- **Codeberg Issues (4)** This is currently the prime communication channel withing the Codeberg Community. Here, you can ask questions, report bugs and suggest changes to Codeberg. You're also welcome to browse these issues and contribute your solutions, if you want to support Codeberg even more.
We could link to an article here describing what free software is for those who don't know. Perhaps [the article on the Simple English Wikipedia](https://simple.wikipedia.org/wiki/Free_software) will suffice?
I will incorporate the changes into the PR (except for the SVG and WEBP thing, let's discuss that above).
I'm glad you like the mascot idea 😊 I was a bit worried at first about whether a mascot will resonate well.
Thank you for your comments! 👍
I will incorporate the changes into the PR (except for the SVG and WEBP thing, let's discuss that above).
I'm glad you like the mascot idea 😊 I was a bit worried at first about whether a mascot will resonate well.
I added an optimized version of Knut and I found a way to provide a fallback for browsers that don't support webp while giving all other browsers the advantages of webp using the picture tag.
Fallback for 2FA article is already merged to master.
@n - please feel free to merge, unless something else needs to be improved/fixed! :)
I added an optimized version of Knut and I found a way to provide a fallback for browsers that don't support webp while giving all other browsers the advantages of webp using the `picture` tag.
Fallback for 2FA article is already merged to master.
@n - please feel free to merge, unless something else needs to be improved/fixed! :)
Closes #26
The basics of issue tracking as well as the basics of contributing to wikis are still missing, hence this is still WIP.
Feedback on tone and overall idea is warmly welcome :)
I have decided to not write an article about the basics of contributing to a wiki right now, as I have no experience with Gitea wikis so far. Maybe someone might want to contribute. But I don't think that wiki basics are critical enough to block the rest of the guide.
So, this is ready for review now :)
WIP: Getting Started Guideto Getting Started Guide 2 years agonice! @n -- would you like to review+merge+deploy?
By the way, I have created accounts for "Knut" on both codeberg-test and codeberg now, just so that noone tries to register to our documentation's test user, trolling people or the like 😄
If we decide to keep Knut as our documentation "mascot" and demo account (much like GitHub's octocat account), I could provide access to the accounts to Documentation contributors (if allowed and possible). We'd need a safe way to do so though.
There has been a trade mark debate around the Berlin Zoo, if you have some time maybe check the EUIPO database to be sure
Thanks for the heads up - I really didn't expect yet another legal landmine there!
Am I the only one who thinks it's a bit weird to trademark a real animal? 😅
But oh well, DPMA Register yields only non-active/revoked/rejected/deleted trademarks for "Knut Eisbär" and a search for "Knut" brought up no active trademarks that match our use of the name Knut AND be in the same Nizza class, in my layman opinion.
Another small investigation into this reveals that protection of the various Knut der Eisbär brands appears to have expired on or around 2017.
Additionally, I couldn't find the brand "Knut" on the website of the Berlin Zoo. There are some mentions of him in various articles, but I couldn't find any Knut products being sold there. There are various Knut-branded articles on Amazon, though they seem to be either not "official" or old-stock and so far I couldnt find one having to do with software or education.
Based on this information I as a layman think that the formely registered Knut brand is expired and will not collide with our use of the name Knut.
Nevertheless, I think we can come up with a better, more unique name than Knut. The more I think about the name Knut, the less appropriate I think it is to use that name for our mascot, given that it is name of a dead animal (even if it was famous once). It also might be hard to pronounce for English speakers.
So I think we could in principle merge this under the working title "Knut" but open a new issue in /Community or /Design looking for a proper mascot :)
Really nice, except for some minor issues. 🙂
I especially like the idea of a mascot!
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
We can minify the image:
https://paste.sr.ht/blob/72a7fd0d677b63ca45ebf4a866eb44d0ba71befb
With gzip encoding already being enabled in docs.codeberg.org, how much would we save?
We'd save about 1.3kB.
Okay, that is indeed significant. I will have a look at it in the evening. Thanks! :)
---
## Registering at Codeberg.org

We should avoid using WebP for now, since Safari does not render it yet (Gitea has support for Safari).
https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Image_types
Safari 14 will support WebP, according to the release notes of the beta.
Does Safari auto-update? In that case, I think it would be okay to just wait and let time solve this problem, because if the Beta is out now, the final release can't be too far out.
The alternative would be to replace everything with png/jpeg, have much larger file sizes and thus much more traffic for the majority of our users.
With Safari, updates are bundled with the OS. People would have to update to iOS 14 and macOS Big Sur before they can see WebP images.
I feel very reluctant to change all the images on the site just because of Apple not keeping up. But I guess we have no choice, unless we want to exclude Mac and iPhone users, of which there are many.
In that case I will also have to change out the screenshots (and photo) of my 2FA guide. That will take some time, I can have a look at it in the evening.
Thanks for letting me know about that potential caveat! :)
## Orienting yourself on Codeberg
After successfully registering on Codeberg, you should see this screen:

The red circles don't look very good. Perhaps we can use zoom and blur effects to draw focus instead, similar to how GitHub's guide does.
Agreed, but let's change that with a separate PR, because then we'd unify image highlighting everywhere on Codeberg Documentation, not just in the Getting Started Guide.
Right now, I'd say we take it how it is, because changing the highlighting would be quite time-consuming and it's probably better to have a slightly imperfect guide than none at all.
Agreed!
Great, #52 will track the issue.
- **Dashboard (1)** is the screen you're looking at right now. It gives you an overview of the newest activity
of you, the people you follow and in your or your organization's projects.
- **Issues (2)** and **Pull Requests (3)** These are overviews over issues and pull requests that you are either involved in or that are part of one of the organizations you belong to.
Overviews of would sound better here.
Do you mean "overviews of issues and pull requests"?
Sorry, missed your quote above - I'll fix it 👍
- **Dashboard (1)** is the screen you're looking at right now. It gives you an overview of the newest activity
of you, the people you follow and in your or your organization's projects.
- **Issues (2)** and **Pull Requests (3)** These are overviews over issues and pull requests that you are either involved in or that are part of one of the organizations you belong to.
- **Codeberg Issues (4)** This is currently the prime communication channel withing the Codeberg Community. Here, you can ask questions, report bugs and suggest changes to Codeberg. You're also welcome to browse these issues and contribute your solutions, if you want to support Codeberg even more.
You might mean
primary
. 🙂️I think
for
might better suit the context.Agreed, will change :)
#### Be (reasonably) patient
Please remember that many project maintainers work on their free software projects
in their free time. Some maintainers may answer you within minutes, others within days.
Don't be discouraged if there won't be an immediate answer.
suggestion:
won't be
-->isn't
👍
Codeberg is a community-driven, non-profit software development platform operated
by Codeberg e.V. and centered around Codeberg.org, a Gitea-based software forge.
On Codeberg you can develop your own Free Software projects, contribute to other
We could link to an article here describing what free software is for those who don't know. Perhaps the article on the Simple English Wikipedia will suffice?
Absolutely! 👍
Thank you for your comments! 👍
I will incorporate the changes into the PR (except for the SVG and WEBP thing, let's discuss that above).
I'm glad you like the mascot idea 😊 I was a bit worried at first about whether a mascot will resonate well.
I added an optimized version of Knut and I found a way to provide a fallback for browsers that don't support webp while giving all other browsers the advantages of webp using the
picture
tag.Fallback for 2FA article is already merged to master.
@n - please feel free to merge, unless something else needs to be improved/fixed! :)
ecc47f425c
into master 2 years agoIt's live!
Thank you! :)
Reviewers
ecc47f425c
.