Closed stadmill closed 1 month ago
what does sdk stand for?
The name of the repo does not matter so much as long as you keep
pip install osipi
and
import osipi
On the other hand you don't want to keep changing it all the time so its probably worth a discussion at EMB level rather than a quick change. The naming of the repos on the OSIPI github organisation is not very consistent
TF2.3_Python_Package
Prof. Steven Sourbron, PhD Chair in Medical Imaging Physics University of Sheffield, UK https https://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron https://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron Sheffield abdominal imaging research page https://www.sheffield.ac.uk/medicine/research/research-themes/medical-imaging/medical-imaging-research/abdominal-imaging Open source initiative in perfusion imaging http://www.osipi.org Magnetic resonance imaging biomarkers for chronic kidney disease https://renalmri.org/
On Thu, 14 Mar 2024 at 23:19, stadmill @.***> wrote:
The current name 'pypi' is confusing. Suggest renaming our repo to osipi_sdk. Need to also update webpage name and documentation to reflect the change.
— Reply to this email directly, view it on GitHub https://github.com/OSIPI/pypi/issues/14, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOFKA6J5P2KFILF3GKNSKLYYIWBBAVCNFSM6AAAAABEW75VAKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4DONBTHA2TIOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I think just naming it "osipi" will be fine. SDK stands for software development kit, but I think that's implied. I also think that this is going to be a more general repository, not TF 2.3 specific so I'd like to avoid the TF nomenclature.
Agree. This is just a name change of the repo, not the package. And SDK makes it clear what it is. I don't want to add TF prefixes, there are too many of these repos already.
The current name 'pypi' is confusing. Suggest renaming our repo to osipi_sdk. Need to also update webpage name and documentation to reflect the change.