Please explain here how they meet our current criteria.
The foss.heptapod.net will be the public mirror for the logilab development repository, which is located on our own server.
Knowing this can help in case there are constraints on resources and/or administrators availability at the time of the request. It can also help us suggest the right solution for the needs of the project.
The project is officially released and used in several projects. One of the most well known project using CubicWeb is data BnF.
The project is, for now, not really used outside the Logilab projects. But almost every Logilab projects are using CubicWeb as core framework. We maintain these projects daily and contribute to CubicWeb regularly. A new CubicWeb version is published approximately every 3 months.
There is no dedicated team to maintain CubicWeb, but there are between 3 and 5 regular contributors, meeting each week for our ritual weekly sprints which happens every Tuesday afternoon.
We are hosting CubicWeb on our proper heptapod instance: https://forge.extranet.logilab.fr/cubicweb/cubicweb We use the issue tracker, the review system and CI/CD. We are planning to keep using this instance for the every-day development and use a mirror on foss.heptapod.net as a public repository to exchange with community.
What would you like to have?
We would like to have a group since CubicWeb is the main project but we have separated some part as other project, such as YAMS, RQL, CubicWeb API and more globally other features available through cubes in a dedicated subgroup. If we can have mirrors for all of these projects, it would be very convenient.