Questioning the necessity of high complexity in initial project setup #8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Do we really need to start the project with such a high level of complexity? At this stage, I fail to see the necessity for an embedded CLI within the application, especially since the application will primarily be started by the application server inside the container.
My main concern here is the challenge of explaining to less experienced contributors how to get involved and run the application. A more complex setup might actually be counterproductive, especially if we are aiming to encourage contributions from a wider group.
It might be worth revisiting this decision and considering a simpler approach for the initial phase of the project, to avoid adding unnecessary complexity early on.
@dunossauro The idea you presented is very interesting and shows great potential for our project. It brings a fresh perspective that could bring valuable improvements and add real efficiency. Your approach clearly demonstrates thoughtful consideration, which is much appreciated.
At the same time, please feel free to propose a new, simpler architecture if you believe that could better serve our goals. We encourage creativity and welcome any suggestions that could streamline the project and make it easier to maintain. Your input is highly valued, and we trust your judgment in finding the best solution.
I think we need a kickstart session to refine the initial objectives.
I like the idea of start simple, with an MVP of posting something to the fediverse, and them move forward.
We have some ideias where we want to go, we have some requirements, we have the tools, now we need to focus on what we can do with the team involved in the project.