Requesting clarification on what a "Project" is in Terms of the new ToS #2950

New issue

Open

opened 2026-07-27 23:57:10 +02:00 by Crystalkey · 0 comments

Crystalkey commented

2026-07-27 23:57:10 +02:00

Comment

Hi there, I am the maintainer of this org.
We are collecting and scraping publicly available data from law proceedings of German parliaments, and making it available centrally in a human and machine-readable way.

Question

I was wondering how the new policy relates to our case:
Is a "project" a singular repository? Can it be a whole org? What steps should we take to ensure compliance?

Context

Our repositories interact and are not really usable in any other context than the project in question: The scrapers cannot interact with any other backend than the one we developed, the website is developed to only request data from that backend etc.
In my terms, all of this is one "project".

We rely on volunteer force to develop and maintain scrapers for each parliament, which in part use generative AI to generate large parts of the scraper code; This of course leads to a select few repositories being almost entirely generated.

However most of the project is still written by people, and that is especially true of the core parts: the backend, the scraper infrastructure, the API specifications and the vast majority of scrapers, which make up most of the LOC; we have no intention to change that. On the other hand, we also do not want to introduce an additional hurdle to contributors that can provide valuable additions in maintaining a relatively simple scraper that is very confined in what data comes in, and what data comes out.

More Context

In the ToU "projects" is a somewhat undefined term, although this line:
(§2.2) [...]Private repositories are only allowed for things required for FLOSS projects implies that projects are broader than one repository,
while this example: (§2.6) [...] Maintainers of a project can enforce stricter rules, for example by adding an easily discoverable Code of Conduct as a file in the repository root [...] rather implies that they can be equivalent.
thanks in advance^^

### Comment Hi there, I am the maintainer of [this org](https://codeberg.org/PaZuFa). We are collecting and scraping publicly available data from law proceedings of German parliaments, and making it available centrally in a human and machine-readable way. ## Question I was wondering how the new policy relates to our case: Is a "project" a singular repository? Can it be a whole org? What steps should we take to ensure compliance? ## Context Our repositories interact and are not really usable in any other context than the project in question: The scrapers cannot interact with any other backend than the one we developed, the website is developed to only request data from that backend etc. In my terms, all of this is one "project". We rely on volunteer force to develop and maintain scrapers for each parliament, which in part use generative AI to generate large parts of the scraper code; This of course leads to a select few repositories being almost entirely generated. However most of the project is still written by people, and that is especially true of the core parts: the backend, the scraper infrastructure, the API specifications and the vast majority of scrapers, which make up most of the LOC; we have no intention to change that. On the other hand, we also do not want to introduce an additional hurdle to contributors that can provide valuable additions in maintaining a relatively simple scraper that is very confined in what data comes in, and what data comes out. ## More Context In the ToU "projects" is a somewhat undefined term, although this line: (§2.2) `[...]Private repositories are only allowed for things required for FLOSS projects` implies that projects are broader than one repository, while this example: (§2.6) `[...] Maintainers of a project can enforce stricter rules, for example by adding an easily discoverable Code of Conduct as a file in the repository root [...]` rather implies that they can be equivalent. thanks in advance^^

No milestone

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#2950

No description provided.

Rows
Columns