Skip to content

Community Engagement

CodeFloe encourages all forms of community involvement, whether it’s contributing to documentation, infrastructure, or moderation tasks in the forum. There aren't any formal roles nor an official application process. Typically, the path is to "build trust" by being active in the community over time and assisting others.

For infrastructure-related tasks, this process is a bit different due to existing responsibilities, connectivity needs, and overall security. If you’re interested in helping with infrastructure, please reach out to us directly or start a discussion in the forum specifying which areas you’d like to get involved with. We’ll then talk through the next steps and determine what access or permissions might be appropriate1.

Note

Relevant experience with the specific area and general proficiency with Linux systems are required. While CodeFloe values community participation, it isn’t intended as a “learning environment” for those seeking their first experience in this field. Additionally, since everything is managed using OpenTofu and Ansible, you should already be comfortable with these tools—or at least be fully committed to working with them.

Financial Sustainability

CodeFloe is pursuing a hybrid model that blends elements of both foundation and for-profit structures to ensure long-term financial sustainability. The main objective is to secure sufficient funding to cover essential infrastructure expenses, with storage costs expected to be the most significant in the future.

CodeFloe plans to raise funds through two primary channels:

  1. Donations
  2. Paid tiers

Unlike other platforms, the paid tiers on CodeFloe do not restrict access to features. Instead, users are only charged when they require additional resources, such as increased storage or more compute power for CI/CD. This approach aligns with the principle of charging solely for resources that generate direct costs for CodeFloe.

The core assumption behind this model is that a significant portion of users will be willing to support the platform through donations, thereby covering infrastructure expenses. If donations and paid tiers generate a surplus after all costs are met, those maintaining the platform will be eligible for a share of the remaining funds (distributed monthly or yearly). The allocation for each contributor will be determined by factors such as workload, duration of involvement, and level of responsibility.

CodeFloe is committed to providing regular financial updates at appropriate intervals.

Issues & Feedback

To report issues or feedback with the platform, please create a post in the Forum.

If the issues are clearly related to one of the underlying apps (e.g. Forgejo, Crow CI, etc.), please report them directly to the respective project's issue tracker.

  1. The goal is to have a granular RBAC-concept for individuals and groups allowing access to certain parts of the infrastructure and the respective secrets. ↩