As we progress with the development and user-friendliness of Baler, there's a need to discuss our transition from the current installation method (cloning the repo and setting up dependencies) to packaging Baler for both brew package manager and the Debian repository.
This transition will transform Baler from a repo-specific tool with a definite folder structure to a more globally accessible command-line tool. Users will ideally be invoking it in the format:
However, this move comes with challenges. Our current setup is tightly bound to the repository's specific folder structure. Changing this would mean altering a significant portion of the underlying source code. Before embarking on this, it's crucial we gather opinions and thoughts on:
Potential pitfalls and challenges to anticipate.
Best practices for restructuring without affecting current users.
The roadmap to ensure minimal disruption.
Some other thoughts:
How do we store trained models? Is this up to every user?
Do we remove the workspace option?
Please share your insights, thoughts, or concerns to guide this transition effectively. The goal is to ensure that this doesn't cause too many issues for current use.
Hello,
As we progress with the development and user-friendliness of Baler, there's a need to discuss our transition from the current installation method (cloning the repo and setting up dependencies) to packaging Baler for both brew package manager and the Debian repository.
This transition will transform Baler from a repo-specific tool with a definite folder structure to a more globally accessible command-line tool. Users will ideally be invoking it in the format:
However, this move comes with challenges. Our current setup is tightly bound to the repository's specific folder structure. Changing this would mean altering a significant portion of the underlying source code. Before embarking on this, it's crucial we gather opinions and thoughts on:
Some other thoughts:
Please share your insights, thoughts, or concerns to guide this transition effectively. The goal is to ensure that this doesn't cause too many issues for current use.
Thank you for your input!