I second that. It would be nice to have it clarified as to what the naming convention requirement plans are for fpm packages to be considered for the registry, where the registry and profiles stand, and any formal plans for the future of fpm
a documentation convention for packages?
what new search tools are planned
further plans for preprocessing, including whether conditional processing will be made available for the TOML manifest and/or any more make/Cmake-like features
further subsidized development of fpm or support for managing and moderating the pull requests, …)
or whether the main plan it to continue to grow organically. It appears a little nebulous lately. A clarification of the plan legitimately including the lack of a formal one would be useful.
My impression is the original strict naming rules will have to be followed for packages to be registered. Clarifying where that stands and if so what the exact rules will be and getting an option working that enforces them so people can begin planning for it (if so) should be forthcoming if that is the direction.
I think there is some hesitancy to approach some of those issues as they are being worked on(?). A formal description of what is planned or not (and therefore is freely available to be worked on) would be nice as well, but clarifying the naming convention plans in particular and making it clear they will be optional does seem to be the most pressing.
If it is not possible to discus at this point, surveying the community for what questions and concerns they might have might help direct things; especially information from anyone that would like to adopt it but struck a roadblock preventing adaptation.
we’d like to provide an update on the backend registry project we are currently working on both the Backend (python Flask) and Frontend (React). We have already completed the initial implementation. We expect to finish the implementation phase in the next 1-2 weeks. (T1 and T3) , We would like to have a review of the current implementation at repo : GitHub - henilp105/registry: Registry for Fortran package manager