Create guide for people choosing to archive media content on Codeberg #443
Labels
No labels
Codeberg Pages
Documentation Usability
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator
Priority: High
Priority: Low
Priority: Medium
Reviewed: Confirmed
Reviewed: Duplicate
Reviewed: Invalid
Reviewed: Wontfix
Status: Blocked
Status: Help wanted
Status: In progress
Status: Needs feedback
Status: Ready for Review
Status: Review
Status: Stale
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Codeberg/Documentation#443
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
This will be a bit tricky to get right - if anyone wants to take up on this, we have to find "good and bad" examples before we suggest "best practices" to people.
We sometimes get asked about our space requirements because we are a non-profit: Codeberg-e.V./requests#291
This causes some concern among people that are wary of using up our resources - but that's kind of what we're there for. Codeberg/Community#515 (comment)
We can manually increase size limits if there is a reason for it. Using a forge for an archive, perhaps a media archive, is from my POV valid. Sometimes, other platforms may be better suited for that, but I find that "open access" and "archival" of free and libre content is something that suits our goals. How do we advise people how to do it right?
Examples
Are there any case studies for scenarios where the size limit has been increased or not?