Semble Sourced
Reviewed by the crowd.
Open source lets anyone read the code. Semble Sourced adds the room: the project is brought into a Semble by the builder who made it, and the builders present review it together. What they find, and who they were, stays on the record.
Why it is safer
A named builder, in the room
The person who made it brought it. You can ask them, there, and they can show you.
Reviewed by people who were present
The builders in the Semble read it, run it and ask about it, together. Not one reviewer alone, not a bot.
A record of who checked what
The Sourced page keeps the project, the Semble it came through, and who was in the room. Provenance you can read.
Nothing taken on trust from a screen
A repository can say anything. A room cannot. What was checked was checked by people who met.
How it goes
- 01
Bring it
When you start a Semble, add the project link and choose to list it on Semble Sourced.
- 02
Review it in the room
The builders present read it, run it, and ask. The room decides what it thinks.
- 03
Record it
The project stays on Semble Sourced with the Semble it came through and the builders who were there.
- 04
Certified, next
Semble Certified is the mark a project earns from that review. It is on the roadmap, and Semble Sourced is the record it will stand on.
Open source, and Semble Sourced
| Open source | Semble Sourced | |
|---|---|---|
| Who reads it | Anyone, anywhere, alone | Builders you met, together |
| Who vouches | A username | A person in the room, and the people with them |
| What is kept | The code | The code, the Semble, and who was present |
| What you can ask | An issue tracker | The builder, across the table |
Bring what you are building
Start a Semble, add the project link, and list it. The room does the rest.