The Community Solid Server (CSS) is an open source tool for Solid developers and researchers to test their apps, to check out experimental features, to encourage rapid prototyping, to set up pods, and to influence the Solid specifications in an implementation-driven manner. Since its release, its increased popularity has warmed our hearts: the GitHub repository already received 260 stars and 60 forks, sparking the interest of governmental organizations, industry players, hobbyists as well as academic researchers. That is not a coincidence: CSS is designed as an excellent companion for developers and researchers alike, and is part of a landscape of compatible Solid implementations such as the Enterprise Solid Server.

Today, we launch the CSS Association (CSSA). Under the umbrella of the Open Knowledge Belgium nonprofit organization, the CSSA will ensure the sustainability of this project.

The goals behind the CSSA are twofold. First of all the goal is to make sure the future maintenance and support of CSS can be guaranteed. Therefore, through board meetings, the sponsoring partner will get a say in the roadmap of the CSS. A core maintainer may try to get funded by other projects partially funding core maintenance. During 2022-2023, SolidLab Flanders will be such a first project that will dedicate developers to take on core maintenance tasks. This will allow the CSSA to be kickstarted.

The second goal is to have core maintainers funded to bring successful experimental features implemented in the CSS to the official Solid specifications. In case there is discussion about certain Solid features, the flexibility of the server makes it an ideal platform to introduce one or even multiple implementations. These can then be used to showcase what the impact would be of certain ideas. When new pull requests arrive to the repository, a core maintainer will verify that the functionality and implementation align with the CSS vision, and will bring developers together to establish a consensus in case this is not clear.

By paying a recurring membership fee, that organization is co-funding one of the core maintainers. The core maintainers work for the CSSA board, and a sponsor will have a vote in the recurring board meetings. In these meetings, which will take place every 2 months, we will discuss which features are being worked on and which issues need to be resolved, based on the needs of all parties involved.

The plan is to have these meetings every two months with the following agenda template:

There are several possible membership levels, each of which has an impact on how many hours of work are funded. This includes both any development work necessary, and the work done by core maintainers to manage the related repositories. Core maintenance is important to make sure the CSS repository keeps the current high level of quality that it has by reviewing the quality of suggested solutions and keeping track of all issues.

Another way to fund development work on the server is to open a bounty on a specific issue, providing a monetary reward for developers who build a solution. This would then allow developers to work on that issue for the agreed upon price. By attracting developers to work on issues this also grows the network of people working on CSS, thereby increasing its future stability and potentially finding new maintainers.