You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @vincefn . This refers to our process for taking our pacakages to the new group standards for CI, linting and releasing. We used to call this process "cookiecutting" because we were using the cookiecutter package, but we are moving towards writing a paper and a package to help other scientific python groups adopt similar strategies, so now the process is called scikit-package.
The exemplar package is diffpy.utils if you want to take a look. For pyobjcryst, we could do it where we merge the cookiecutting work into a branch called cookie or package or whatever we decide, and you can make sure that everything meets your approval before anything is merged into main.
All of our diffpy packages we have been putting into the diffpy namesspace (so they are called diffpy.<package-name>. Pavol started this process, but we are conforming everything else. We could decide if we want to do this or not for pyobjcryst. Since it has a fairly large user-group we probably don't want to change how it is installed and used, or at least to allow it to continue to be installed as it is. Our cookiecutting process can do it either way. One advantage of doing it is just standdardizing the release management across our family of packages. But let's discuss this.
No description provided.
The text was updated successfully, but these errors were encountered: