Lazarus undead repository?

[PascalDragon]

Codeberg bans AI-generated code—a deal-breaker for me.

For me, that's a deal maker 🥰

[CM630]

Any idea if this info is still valid:

Unfortunately, at this moment Sourceforge doesn't support restricting access to SVN to only a subtree of the complete repository.

[ALLIGATOR]

https://radicle.dev/
It seems like this is something that truly won't die as long as there's at least one person still alive

[ALLIGATOR]

distributed source code repository

[Mike.Cornflake]

https://radicle.dev/
It seems like this is something that truly won't die as long as there's at least one person still alive

The Napster approach :-). I like it!

[CM630]

@sh17, can you check if GitLab/Hub provide supports variable user access in subtrees of the repositories? This might give a hint what approach and repository provider to use?

[sh17]

I checked this. Neither GitHub nor GitLab really uses directory-level permissions as its normal Git access model. Both have CODEOWNERS and protection mechanisms, and GitLab can get quite close to path-based write protection, but that requires Premium/Ultimate.

This actually seems to be another argument for one repository per project inside a common organisation. Then each project can have its own maintainers and write permissions without complicated subtree rules.

[paweld]

Unlike SVN, GIT does not allow you to grant users permissions to specific subdirectories within the repository.

[Dankan1890]

GitLab / GitHub allow groups/organizations (just like FPC) to group individual repositories (projects). Since permissions are inherited, a user simply needs to be granted read-only permissions for the group and write permissions for the individual repository.

Or am I missing something? 

[paweld]

As you wrote, it does allow it, but in the context of the entire repository, not individual subdirectories within that repository.

[Dankan1890]

@paweld: In fact, referring to the first message in the thread, which mentioned the RichMemo component, which is hosted in a repository "https://github.com/skalogryz/richmemo/" (if I'm not mistaken), it would be enough to create an "Undead Components" group with a related repository underneath. If CM630 were hypothetically the developer/maintainer of that component, it is sufficient to follow what I said before (CM630 in the group in read-only mode, with write permissions only on RichMemo).

PS: If I misunderstood what was discussed, I apologize.