EpicGames/lore

Learn about Lore: next-generation open source version control

Maintained by Epic Games, Lore is designed for unprecedented scalability of both data and teams. It’s optimized for projects that combine code with large binary assets.

The Lore Version Control System - Lore Developer Documentation

A reference document explaining the rationale, goals, and theoretical design of Lore. This is not a peer-reviewed paper; it is a public-facing standalone description of the system, intended to make the why of Lore - the problems it was built to solve and the design choices that follow from those problems - as legible as a reader can make it without reading the source code.

v2 Editor Manifesto

The manifesto for our brand new rich text editor with version control capabilities, v2. In this post, we describe the basic principles, design decisions and our vision for v2, alongside reflecting on the current state and potential future of knowledge production in society.

Universal Version Control

Building tools to help people explore alternatives, keep track of history, and collaborate better, across all kinds of media.

01 · Universal version control

We believe that simple, powerful, universal version control tools could help all kinds of creators produce better work.

Docs — Turn your team's content into knowledge

Docs is the open-source document editor that turns your team's content into knowledge: real-time collaboration, structured knowledge, and full data ownership. Self-host it anywhere, or try a public instance in seconds.

Software Is Made Between Commits

From the Zed Blog: Agents turned the conversation into the real source of our software. DeltaDB is the version control built for it.

lore.farm — Collectivized Canon for Fictional Worlds

Create fictional worlds and build a shared canon with your community from across the ATmosphere. Includes support for Bluesky, Branchline, and more!

Announcing Changesets v3 | Changesets

A tool to manage versioning and changelogs with a focus on monorepos

panproto/panproto

One engine for schematic version control within and across any schema language.

Home – DVC

Open-source version control system for Data Science and Machine Learning projects. Git-like experience to organize your data, models, and experiments.

panproto | schematic version control

One engine for schematic version control within and across any schema language.

Scientific Content Management System | Curvenote

Create, manage, and publish interactive research with connected workflows, modular content, and built-in provenance. Book a demo

Manuscript submission systems and metadata completeness in Crossref: Patterns and associations

The importance of open research information, particularly publication metadata, is widely recognised. Crossref is one of the most important infrastructures for registering open metadata as part of DOI record registration. It is widely known, however, that the metadata of many publications is far from complete, with many publishers making certain metadata openly available, but failing to do so for other metadata elements. Publishers’ ability to register this metadata with Crossref depends on their capacity to capture and retain this data in their production workflows. Manuscript submission systems are an important, yet largely overlooked, factor in the extent to which publishers make metadata available through Crossref. In this paper, we present the results of an analysis investigating the relation between the level of metadata that publishers deposit with Crossref and the submission systems that they deploy for their journals. We have looked at the 153 publishers with the largest amounts of publications in Crossref and concentrate on the four most commonly used systems: Editorial Manager, ScholarOne, Open Journal Systems (OJS) and eJournalPress. We show that some submission systems appear better suited to capturing certain metadata elements. However, there are always cases where publishers using the same system differ widely in the level of metadata they register, suggesting that technology is not the only prohibiting factor and other considerations are at play.