Use case · Open source and open research
Work in the open, with the tracker your team already uses.
A Kaiku project bound to a public repository can be read by anybody: the board, the issues with their comments and files, and the wiki — with no account. Outsiders who want to help ask to take part and file issues. Nobody outside writes in it otherwise, and nothing else of your company opens.
A real one: Math D5
Recorded inside the product, on a copy of Math D5 — a real open research project — and its real public repository; the people are made up for the camera. Sound on for the commentary.
Math D5 is an open research project on Problem 20.84 of the Kourovka notebook: is the fifth dimension subgroup of every group inside the fourth term of its lower central series? The question is not solved, and the project keeps what is proved, what is computed and what is left in public.
- Each open question is an issue under one epic, so its attempts and results are discussed where they belong — the list of open questions on the wiki links every one.
- The wiki holds the overview, the results with their status, the repositories and how to take part.
- Four public GitHub repositories are connected: the computations and the Lean formalisation, the project site, and two related ones.
Open it — no account is needed to read it.
Only an open source project opens
A project is bound to its public repository on GitHub or GitLab — when it is created, or later on its Repositories screen. The host is asked, without an account, whether anybody can read it and under which licence; a private repository cannot be marked. Then the project’s owner opens it, and the window says first how many issues and pages that will show.
The host is asked again every day. If the repository becomes private or disappears, the project closes at once and its lead is told.
What a visitor sees, and what never
A visitor reads at the members’ own addresses: the board, the issues with comments and files, the wiki, formulas included. People’s email addresses, the project’s settings, the assistant and the agents, the money and the company’s other projects are never shown.
Search engines are off until the owner lets them in; then the project’s issues and pages are in the sitemap.
Letting people in
A visitor who is signed in presses Ask to take part. The maintainers decide; let in, the person is a reporter on that project — they file issues and comment, and nothing else of your company opens to them. A newcomer writes a limited amount a day for their first week, so a stranger cannot flood the board.
What it costs
- People of your company who work only on public projects take no seat.
- A company whose every project is public is not made read-only when a period goes unpaid. A new project has three days to be made public.
- Storage, the packs and the add-ons cost what they cost everyone.
Open your project.
Create a workspace, bind the project to its repository, and make it public. The first month is free and needs no card.
Create a workspace