Codeberg/Community
54
325
Fork
You've already forked Community
12

LaTeX template and (personalized) outputs; preferred (and acceptable) licenses? #1969

Open
opened 2025年05月30日 19:57:00 +02:00 by mycroftw · 0 comments

Comment

Hello. I am considering moving my projects to Codeberg, and have read your documentation on acceptable licenses. I think I have an odd (but not unique) situation, and am wondering if the following is acceptable here:

  1. There is a LaTeX style (for a graphic form) and template (which, when completed, will fill in the form) I have written and maintain. Discussions in the past have pointed out that LaTeX documents aren't really code and aren't really documentation, and generally fall through the cracks of relevant licenses.
  2. My issue is that I want people to use the form if they wish (and modify it, to at least some extent - "the reason for the form" mandates the general structure, you can modify it to break that structure if you wish, but then the outputs aren't acceptable for intended use), but my uses of it (and theirs) are individualized (they have our names on it, and are a record of our agreements other people are allowed to rely on). So "fill out your own forms, but don't change mine (or anyone else's) while still having our names on them".
  3. In my current hosting I have resolved this by making the style file CC-BY-SA, the template and example CC-BY (so that other users can fill in the form and keep the filled-in-form immune to manipulation by others).
  4. But my filled-in forms are CC-BY-SA-ND, which is not allowed by your license.

However, as any change wished by another person can be done simply by filling out their own form (or by copying my filled-in form and changing any needed values - as long as the names are also changed to theirs!) this does not remove any rights any other user may have (except to present a form "claiming" that our agreements are not what they actually are).

I can provide (names-changed) examples of the filled-out LaTeX template and output document if this will help make my intentions clear.

### Comment Hello. I am considering moving my projects to Codeberg, and have read your documentation on acceptable licenses. I think I have an odd (but not unique) situation, and am wondering if the following is acceptable here: 1. There is a LaTeX style (for a graphic form) and template (which, when completed, will fill in the form) I have written and maintain. Discussions in the past have pointed out that LaTeX documents aren't really code and aren't really documentation, and generally fall through the cracks of relevant licenses. 2. My issue is that I want people to use the form if they wish (and modify it, to at least some extent - "the reason for the form" mandates the general structure, you can modify it to break that structure if you wish, but then the outputs aren't acceptable for intended use), but my uses of it (and theirs) are individualized (they have our names on it, and are a record of our agreements other people are allowed to rely on). So "fill out your own forms, but don't change mine (or anyone else's) while still having our names on them". 3. In my current hosting I have resolved this by making the style file CC-BY-SA, the template and example CC-BY (so that other users can fill in the form and keep the filled-in-form immune to manipulation by others). 4. But my filled-in forms are CC-BY-SA-ND, which is not allowed by your license. However, as any change wished by another person can be done simply by filling out their own form (or by copying my filled-in form and changing any needed values - as long as the names are also changed to theirs!) this does not remove any rights any other user may have (except to present a form "claiming" that our agreements are not what they actually are). I can provide (names-changed) examples of the filled-out LaTeX template and output document if this will help make my intentions clear.
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 Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, 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#1969
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?