Codeberg/Documentation
42
199
Fork
You've already forked Documentation
161

Update FAQ #166

Merged
n merged 2 commits from :fnetx-faq into main 2021年08月29日 09:27:34 +02:00
Owner
Copy link

... 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
content/faq.md Outdated
@ -9,2 +9,3 @@
## 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).
Contributor
Copy link

Not sure what is meant by 'behind scaling'

Not sure what is meant by 'behind scaling'
Author
Owner
Copy link

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
@ -14,0 +14,4 @@
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.
Contributor
Copy link

licenced --> licensed

`licenced` --> `licensed`
fnetX marked this conversation as resolved
content/faq.md Outdated
@ -14,0 +15,4 @@
## 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.
Contributor
Copy link

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.
Author
Owner
Copy link

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
@ -14,0 +16,4 @@
## 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.
Contributor
Copy link

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
@ -14,0 +19,4 @@
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.
Contributor
Copy link

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

`However, as of our` --> `However, as per our`
Contributor
Copy link

notetaking --> note-taking

`notetaking` --> `note-taking`
fnetX marked this conversation as resolved
Author
Owner
Copy link

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 2021年08月29日 09:27:03 +02:00
n left a comment
Copy link

Looks good now. Thanks for fixing.

Looks good now. Thanks for fixing.
n referenced this pull request from a commit 2021年08月29日 09:27:34 +02:00
Author
Owner
Copy link

Sorry for not really checking this after the updated commit 🙈

Sorry for not really checking this after the updated commit 🙈
Sign in to join this conversation.
No reviewers
n
Labels
Clear labels
Codeberg Pages
Issues affecting Codeberg Pages
Documentation Usability
Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator
This is related to the generation of the documentation, not to the content itself
Priority: High
The priority is high
Priority: Low
The priority is low
Priority: Medium
The priority is medium
Reviewed: Confirmed
Something has been confirmed
Reviewed: Duplicate
Something exists already
Reviewed: Invalid
Something was marked as invalid
Reviewed: Wontfix
Something won't be fixed
Status: Blocked
Status: Help wanted
Contributions are welcome!
Status: In progress
Work is in progress
Status: Needs feedback
Feedback is needed
Status: Ready for Review
Work is completed
Status: Review
Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Documentation!166
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch ":fnetx-faq"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?