Codeberg/Community
62
386
Fork
You've already forked Community
12

Policy on private repositories for other non-profit organizations #2828

Open
opened 2026年07月01日 21:50:59 +02:00 by filmroellchen · 0 comments

Comment

I’m representing a small church/congregation (codeberg org: https://codeberg.org/EmK-Rems-Murr ) on technical matters and we’d like to have the usage policy for private repositories clarified. More specifically, we have quite a bit of older code, mostly for websites, that we don’t want to publish (right now/ever). In my reading the ToS don’t really clearly forbid most uses of private repositories, except media and cloud storage, which we’re obviously not trying to do. In my opinion, it would be great if you explicitly allowed a more extended use of private repositories for non-profit organizations. I fully understand however that you’re trying to avoid abuse and want to stay away from commercial users too. As you can see in the org I linked, we publish most of our newer projects (and plan to publish a few older projects) anyways.

In case you’re wondering why we don’t self-host: there’s an internal Git forge for some of the larger organizations in our church, mostly for devops, but individual congregations don’t have access to that (mostly because it’s not publically accessible, so it’s not suitable for our public repos anyways). I have provided some feedback about this situation, but it’s unlikely to change.

### Comment I’m representing a small church/congregation (codeberg org: https://codeberg.org/EmK-Rems-Murr ) on technical matters and we’d like to have the usage policy for private repositories clarified. More specifically, we have quite a bit of older code, mostly for websites, that we don’t want to publish (right now/ever). In my reading the ToS don’t really clearly forbid most uses of private repositories, except media and cloud storage, which we’re obviously not trying to do. In my opinion, it would be great if you explicitly allowed a more extended use of private repositories for non-profit organizations. I fully understand however that you’re trying to avoid abuse and want to stay away from commercial users too. As you can see in the org I linked, we publish most of our newer projects (and plan to publish a few older projects) anyways. In case you’re wondering why we don’t self-host: there’s an internal Git forge for some of the larger organizations in our church, mostly for devops, but individual congregations don’t have access to that (mostly because it’s not publically accessible, so it’s not suitable for our public repos anyways). I have provided some feedback about this situation, but it’s unlikely to change.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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/Community#2828
Reference in a new issue
Codeberg/Community
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?