This page intends to establish some minor ordinances surrounding project ideas and showcases. cbrtl was created with the intent of promoting the spirit of Open Source. Often times, some of the most interesting Open Source projects live in lesser known corners of GitHub, collecting dust on a lonesome profile with 3-5 followers and an occasionally active commit graph.

Cbrtl is an attempt at stringing together these unrelated projects into a web of resources and dev-logs that might be of use to on-lookers.

To avoid noisy applications and tutorial cut-pastes, we enforce a standard and a few (lax) rules.

What constitutes showcase-worthy software?

Anything that serves a clear purpose. A project can be showcased if it satisfies the following criteria:

  • Has a proper github README.md
  • Is not a tutorial follow-through. So anything along these lines is generally discouraged:
    • “todo app in react”
    • “planner app in vue”
    • “terminal tic-tac-toe with C”
    • and so on…
  • Is being actively worked on by it’s developer(s). It is OK even if it’s in infancy when the project is first showcased.
  • Is open to contribution from people.
  • Is not a lazy fork (Forks that are some-what different from the parent repos are absolutely okay).

Examples

Here’s a few examples to show what we mean by “showcase-able projects”. Note that not all of them are from the members of cbrtl, since we’re just starting out.

  • levk: A 3D Game engine written in C++ and Vulkan. Author: karnage
  • SocioMark: A social media platform with plagiarism and attack-proof authenticity checks for user uploaded content. Author: Aitik Gupta
  • Vyse: A fast, dynamically typed and interpreted programming language. Author: srijan_ (cough self-plug)
  • locc: A C++ utility to count lines of code in a project. Author: karnage
  • Lume: A Lua library for gamedev. Author: rxi

Getting your project showcased.

You have made something, or at least the skeleton of something that will go on to become a full fledged project. How do you put your code and product on cbrtl?

  1. Reach out to us either on the mailing list, or on the discord server.
  2. Have the following ready:
    • A GitHub repo with a well set-up README
    • A (short) write-up describing the scope, aim, tech-stack and architecture of your project.
  3. Shoot any moderator with the aforementioned and we’ll give you:
    • A GitHub repo symlink (symlink?) on the cbrtl org page.
    • A community showcase.
    • A blog post referencing the content from your write-up, describing the project.
    • Encourage other members to collaborate and contribute.

A good place to start getting involved can be our Discord server.

Have an idea? Want a team?

It is not so uncommon for programmers to get an idea but not have enough time commitment (or knowledge) to drive the idea to fruition. If that’s how things end up for you, then we might be able to help with pointing you in the right direction.

We may be able to help turn your solo idea into a collaborative work environment. You can choose to have the repo be on the org, or on your GitHub profile.