Content License

Eduskript uses two licenses with a simple boundary:

Source code (everything in the git repository) → AGPL v3
Content (everything stored in the database) → CC BY-NC-SA 4.0

The storage medium is the boundary. Code, configuration, and documentation in the repository are AGPL. Skripts, pages, and all user-created content in the database are CC BY-NC-SA. Content that exists in both (such as documentation imported into the platform) is dual-licensed — AGPL in the repo, CC BY-NC-SA in the database.

What CC BY-NC-SA 4.0 Means for Your Content

You retain ownership

You own the content you create. The license governs how others may use it — it does not transfer ownership.

No commercial use

Nobody may use your content for commercial purposes. Paid courses, commercial textbooks, and for-profit training materials built from your work are not permitted.

Anyone who builds on your content must license their version under the same terms. Your work stays open — it cannot be turned into a closed, proprietary product.

Attribution

Anyone who uses or builds on your content must credit you. On Eduskript, the platform handles this automatically — forked skripts display a "Forked from" link to the original. No manual attribution needed.

Forking and Copying

Eduskript allows teachers to fork each other's published work. When you fork a skript:

You get your own independent copy to edit freely
The original stays unchanged
Your version inherits the CC BY-NC-SA license (required by the share-alike clause)
A "Forked from" link is shown automatically, satisfying the attribution requirement

This makes it easy to build on anyone else's work — colleague, complete stranger, teacher in another country. Adapt a lesson to your class, translate it, extend it with new exercises, or take it in a different direction entirely. The original author doesn't need to know you or grant permission; the CC BY-NC-SA license already covers it.

Provenance

Every forked skript stores a link to the skript it was forked from — similar to how GitHub tracks forks. This serves two purposes:

Discovery — you can see where a skript originated and find the upstream version
Attribution — the fork link satisfies the CC BY-NC-SA attribution requirement, both on-platform and as a reference for anyone taking content off-platform

Only the immediate parent is stored. If someone wants to trace further back, they follow the links.

What You Can Do

Action	Allowed?
Fork anyone's published skript and modify it	Yes
Use forked content in your classes	Yes
Share your fork with other teachers on Eduskript	Yes
Publish your fork on your Eduskript page	Yes

What You Cannot Do

Action	Allowed?
Sell content from Eduskript	No
Include it in a paid product	No
Remove the CC BY-NC-SA license from a fork	No
Republish off-platform without attribution	No

Collaboration Roles

When you share a skript with a colleague for editing, you choose between two roles:

Author

Co-authors share joint copyright ownership of the skript. All authors have equal legal rights to the work, regardless of how much each person contributed. Choose this for true co-creation where both parties are building the skript together from the start.

Contributor

Contributors can edit the skript just like authors, but their edits are licensed to the existing author(s) under CC BY-NC-SA 4.0. Contributors do not gain copyright ownership. Choose this when a colleague is helping improve your work — fixing errors, adding an exercise, translating content.

In short: Authors co-own the work. Contributors help with it.

Both roles have the same editing permissions on the platform. The difference is purely about who owns the resulting content.

When It Matters

The distinction matters if content leaves the platform or if collaborators part ways:

Authors can independently fork, republish, or distribute the joint work (under CC BY-NC-SA)
Contributors retain no ownership claim after their access is removed
When forking a co-authored skript, all authors' consent is reflected through the CC BY-NC-SA license

When adding a collaborator, the UI will show:

"Authors share ownership of the content. Contributors help edit but don't gain ownership."

Why These Licenses?

AGPL v3 for code — anyone can fork and run their own Eduskript instance, but must share their modifications. This keeps the platform open source.

CC BY-NC-SA 4.0 for content — widely used and legally tested across jurisdictions. It provides:

Low friction — the platform automates attribution, so forking is seamless
Protection — commercial use and closed-source derivatives are prohibited
Ecosystem stays open — the share-alike clause ensures derivatives remain open
Provenance — fork links maintain a traceable history of where content originated

Someone forking the Eduskript codebase gets the software under AGPL (including any docs in the repo). Someone reading content on the platform gets it under CC BY-NC-SA. The two licenses cover different domains and don't conflict.

Summary

Eduskript's code is AGPL v3, content is CC BY-NC-SA 4.0. The boundary is the storage medium — repo vs database. You keep ownership of your content. Others can fork and adapt your work for non-commercial purposes, with attribution handled automatically by the platform. The ecosystem stays open.