Source and contribution
Create or import Git repositories, use smart HTTP and LFS, publish selected source, and accept organization-owned forks from contributors outside the core team.
Git-first source controlMozaic brings Git contribution, exact-revision review, isolated .NET pipelines, traceable NuGet packages, governed work, and living knowledge into one coherent workspace for small open-source teams.
Git-first. .NET and NuGet first. Deliberately focused while the product is in beta.
Mozaic carries the context forward. Review, checks, merge policy, package publication, work, and documentation can all point back to the exact revision that earned trust.
Move through source, review, automation, release, work, and knowledge without rebuilding the project’s identity and permission model in every tool.
Create or import Git repositories, use smart HTTP and LFS, publish selected source, and accept organization-owned forks from contributors outside the core team.
Git-first source controlPin pull-request snapshots, hold line and general conversations, collect reviews, and evaluate checks and branch policy against the exact proposed revision.
Immutable proposal evidenceResolve repository-owned YAML into an immutable plan and run .NET restore, build, test, and pack steps in bounded rootless Podman jobs.
Controlled untrusted executionPublish and consume NuGet v3 feeds with immutable package bytes, scoped credentials, lifecycle controls, and provenance for verified releases.
.NET and NuGet firstTrack bugs, features, and tasks with workflows, boards, milestones, assignments, relations, public issues, private security reports, and project activity.
Work connected to deliveryEdit durable project knowledge collaboratively, keep working state separate from published checkpoints, and connect pages to source, work, checks, and packages.
Documentation beside the workMozaic is designed around named organizations, private-by-default resources, deliberate publication, strong authentication, and execution grants that apply only to the revision and plan a maintainer reviewed.
Keep the maintainer core governed without turning every reader or occasional contributor into a full organization member.
Define the project home, publication posture, governance, and durable knowledge contributors need to understand the work.
Govern repositories, proposals, execution grants, branch policy, work, releases, and documentation in one workspace.
Use an explicitly named organization for a fork and propose work to a public project without joining its core team.
Read published knowledge, browse public source, inspect permitted builds and releases, and follow visible project work.
Mozaic’s beta tests one complete contribution-to-release-and-knowledge path. It does not present future platform breadth as current functionality.
Create a verified account, secure privileged actions, and name the organization that will own your project work.