- The danger are low→The danger is low
- on own hardware→on our own hardware
- rackspace→rack space
- awareness on the topic→awareness of the topic
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/450
Reviewed-by: Patrick Schratz <pat-s@noreply.codeberg.org>
Co-authored-by: hippietrail <hippietrail@noreply.codeberg.org>
Co-committed-by: hippietrail <hippietrail@noreply.codeberg.org>
Update contact page
Prefer references to Forgejo, more relevant to users
Updates to Getting Started Pages / FAQ
- a lot of content was outdated and generally rewritten or rephrased
- implement procedure for size limits as determined by annual assembly
2023, see Codeberg-e.V./Discussion#92
- people are sometimes confused wheter you need to be a paying member in
Codeberg e.V. in order to use the platform
Update improving Codeberg guides
- reduce redundancy in code contribution guide and reference the
Contributing Issue Tracker instead
- separate (and ideally more appealing) donation page (deserves even
more love IMHO)
- shorten and strip outdated information
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/394
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: Otto Richter <git@otto.splvs.net>
Co-committed-by: Otto Richter <git@otto.splvs.net>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/380
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: A Frederick Christensen <fauxmight@noreply.codeberg.org>
Co-committed-by: A Frederick Christensen <fauxmight@noreply.codeberg.org>
- Create two sections, "Codeberg's Structures" and "Before I move..."
- Explain that Codeberg is not necessarily *just* a Forgejo instance
by mentioning / crediting more open-source projects in a
non-exhaustive manner.
- Improve wording and phrasing of some questions
- Update Forgejo version instructions
- Private repositories: Split into two questions that are separately
meant for collaborative projects and ordinary users respectively.
- Use words as "most likely" and "probably" in order to *not* make the
reader immediately worry about potentially breaking the rules,
especially as the ToS itself mentions that the platform reserves
the right to take strict action without a warning. If the user
choose Codeberg to begin with, it is very likely that "our" values
align.
- Explain what "fair use" is as far as the repository size is concerned
better.
- Break text into new lines depending on columns and the ideas that
each part of a sentence gets across.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/347
This was added because a user was not sure where they could request an
increase to the repository limit of an organization that they intended
to use for a hackathon.
We may want to consider creating a more detailed page about this later.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/336
Looking of course for feedback on this, as I am not an expert on this at
all. This does capture some of the questions I had when starting to look
into licensing.
