Open Splines opened 10 months ago
If we want a lab to test our library, we should release a (pre-)version first, so they can pin it in their requirements.txt
file such that every team member has the same version on their system.
If we not only create a GitHub release, but also release to PIP, this makes the user experience even better for the people installing the lib. Otherwise, they might not want to use it if it's too much of a hassle to install.
We might want to consider asking people in scientific environments what solutions they use right now for the problem this library tries to solve. This would also allow us to find out what their needs are. Maybe we are overlooking a crucial application for real-life work just because we don't have the scientific background in labs etc. We could also ask people to test our library to then give us feedback.
Sidenote: This could also be a great way to socialize with people in labs in our institution and find out what fields they are researching :)