skip to content

1 engineers on the

The engineers who build the ideas the board picks, for free and in the open. Ranked by the work they have done, counted from the project code on GitHub.

#EngineerCountryBadgesProjectsScoreLast 90 days
1
nellylemmy
@nellylemmyOwner & Founder
Nelson Lemein
🇰🇪 Kenya
298147

How the score works

  • merged pull request5
  • review2
  • commit1
  • issue closed1
  • month active3

The top scorer on each project leads it and gets the director badge. The top 3 overall get the guru badge. "Last 90 days" shows who is active right now. The same formula applies to everyone, including whoever runs this site.

Awards

When giving on the support page covers the running costs, 50% of what is left goes to the top 3 on this list: 50% / 30% / 20% to ranks 1, 2 and 3. Every payout is written in the public ledger with the name of who got it. Nothing is paid quietly.

Join the bench

What you build here does not demo and disappear. It runs in a school office in Kajiado, at a milk plant's cooling tank, on a phone in a market stall, and it keeps running long after the pull request is forgotten. The problems on the board are not waiting for someone far away; the people who can end them are reading this page.

Busy is fine. An hour on a Sunday counts. A review over lunch counts. A minute of your craft is worth more here than anywhere else it could go, and the work carries your name for as long as it runs. Three merged pull requests and you can review. Maintain a nabo and you are named in the file.

If you can ship a fix, you are qualified. There is no interview and no test: sign in with GitHub and you are on the bench. Stuck? Ask in the conversation on the project's nabo; the people building it with you answer there. Every project you ship carries your name, here and on kepas.co.ke.

Sign in with GitHub to join
enabos on GitHub

How to help on a project

  1. 1You do not need permission. Pick the project being built, open an issue on its GitHub page and say you are on it.
  2. 2Keep pull requests small: one change each.
  3. 3Every project has named maintainers. They review and merge.
  4. 4Three merged pull requests and you can review other people's work.
  5. 5Look after a project and your name goes in its maintainers list.
  6. 6The licence on a project never changes. The person who posted the problem chose it.
  7. 7Be decent to the person who posted. They live with the problem.

enabos.com itself is run by KEPAS Technologies and is not open for pull requests, because it holds people's names and emails. Site bugs and ideas: [email protected]