Update FAQ #166

Merged
n merged 2 commits from fnetX/codeberg-documentation:fnetx-faq into main 3 months ago
fnetX commented 3 months ago
Collaborator

... open question: what about moving this to the "Getting started" section or at least up?

Also, I think we might want to elaborate and / or describe more stuff in the FAQ, like, "Find an article on how to change your email settings here" etc

... open question: what about moving this to the "Getting started" section or at least up? Also, I think we might want to elaborate and / or describe more stuff in the FAQ, like, "Find an article on how to change your email settings here" etc
fnetX added 1 commit 3 months ago
n reviewed 3 months ago
content/faq.md Outdated
## Is Codeberg well funded?
Codeberg is primarily funded by donations. As of July 2020, with all expenses frozen, we have a runway of ~12 years.
Codeberg is primarily funded by donations. As of July 2020, with all expenses frozen, we have a runway of ~12 years, so you don't have to worry that our service suddenly disappears.
Still, we can make good use of donations, they can be used to invest in more features or to extend the service behind scaling (e.g. to support completely new services).
n commented 3 months ago
Poster
Collaborator

Not sure what is meant by 'behind scaling'

Not sure what is meant by 'behind scaling'
fnetX commented 3 months ago
Poster
Collaborator

Well, I meant: Go beyond scaling the service and taking the money not only for this very first job, but adding new features (and growing for them, not only for more users) ...

A better expression would be good, my main intention is to assure users our service won't simply disappear, but not saying we don't need any money - we can always make good use of donations.

Well, I meant: Go beyond scaling the service and taking the money not only for this very first job, but adding new features (and growing for them, not only for more users) ... A better expression would be good, my main intention is to assure users our service won't simply disappear, but not saying we don't need any money - we can always make good use of donations.
content/faq.md Outdated
We are hosted in Germany by netcup GmbH as well as on own hardware in a rented facility in Berlin, Germany.
## Is it allowed to host non-free software?
Our mission is to support the development and creation of Free Software, thus we only allow those repos licenced under an OSI/FSF-approved license.
n commented 3 months ago
Poster
Collaborator

licenced --> licensed

`licenced` --> `licensed`
fnetX marked this conversation as resolved
content/faq.md Outdated
## Is it allowed to host non-free software?
Our mission is to support the development and creation of Free Software, thus we only allow those repos licenced under an OSI/FSF-approved license.
Please do not use custom licenses, they are usually a bad idea and often result in legal trouble.
n commented 3 months ago
Poster
Collaborator

It might be good to mention license proliferation and legal uncertainty as reasons to avoid custom licenses.

It might be good to mention [license proliferation](https://en.wikipedia.org/wiki/License_proliferation) and legal uncertainty as reasons to avoid custom licenses.
fnetX commented 3 months ago
Poster
Collaborator

linked to this wikipedia thread in a dirty manner. Elaborating is out of scope for me now. Want to rush this in for Gitea 1.15 deployment.

Having some educative resources about licensing (how to (do it the right way), issues to be aware of etc, which licenses are not really free ...) would be really awesome haha

linked to this wikipedia thread in a dirty manner. Elaborating is out of scope for me now. Want to rush this in for Gitea 1.15 deployment. Having some educative resources about licensing (how to (do it the right way), issues to be aware of etc, which licenses are not really free ...) would be really awesome haha
fnetX marked this conversation as resolved
content/faq.md Outdated
## Is it allowed to host non-free software?
Our mission is to support the development and creation of Free Software, thus we only allow those repos licenced under an OSI/FSF-approved license.
Please do not use custom licenses, they are usually a bad idea and often result in legal trouble.
However, we sometimes tolerate repositories that aren't perfectly licensed correctly and focus on spreading awareness on the topic.
n commented 3 months ago
Poster
Collaborator

focus on spreading awareness on the topic

What topic?

> focus on spreading awareness on the topic What topic?
n marked this conversation as resolved
content/faq.md Outdated
However, we sometimes tolerate repositories that aren't perfectly licensed correctly and focus on spreading awareness on the topic.
## Can I host private repositories?
Codeberg is primarily intended for public and free content. However, as of our [Terms of Service](https://codeberg.org/codeberg/org/src/TermsOfUse.md#repositories-wikis-and-issue-trackers), "Private repositories may be used for example to store keychains in build systems and continuous integration tools, or as staging areas for pre-alpha tests within limited groups.". As usual, common sense applies, so you can also use it for notetaking or internal team communication, if the resource demand stays reasonable.
n commented 3 months ago
Poster
Collaborator

However, as of our --> However, as per our

`However, as of our` --> `However, as per our`
n commented 3 months ago
Poster
Collaborator

notetaking --> note-taking

`notetaking` --> `note-taking`
fnetX marked this conversation as resolved
fnetX added 1 commit 3 months ago
Poster
Collaborator

Thank you for the review. Please check my updated wording for the two open conversations.

Thank you for the review. Please check my updated wording for the two open conversations.
n approved these changes 3 months ago
n left a comment

Looks good now. Thanks for fixing.

n merged commit 779f959db8 into main 3 months ago
n referenced this issue from a commit 3 months ago
Poster
Collaborator

Sorry for not really checking this after the updated commit 🙈

Sorry for not really checking this after the updated commit 🙈

Reviewers

n approved these changes 3 months ago
The pull request has been merged as 779f959db8.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.