Profiles: API planning
Following a chat with with @askhl and @argon214 :
Development and application of ASE profiles has progressed a lot since #512 with several GenericFileIOCalculators implemented and more in the works. Still, some details are in flux especially relating to the use of site configuration files (#589, !2048 (closed) !2886 (merged) !2898 (closed) )
Targeting 3.23.0 as the first ASE release in some time, containing quite a few features that have been sitting on master
and a recent spree of maintenance activity, there is a risk that we will commit to a Profile API that is regretted/broken in following releases.
Prior to this release, we should either
- agree a detailed plan/API for Profiles and make sure the release version is consistent with this
- develop API plans/discussion enough that we can be confident the released version will not cause too much trouble.
I think the second of these is the more reasonable goal but if we accidentally achieve the first that would also be nice!