from Juniperus@infosec.pub to programming@programming.dev on 19 Jun 22:45
https://infosec.pub/post/48245849
Hello everyone, you may remember I dropped by a while back concerning my cooperative management project.
The idea has evolved to building an open-source Enterprise Resource Planning application specifically for worker’s cooperatives. While most ERP software focuses on driving top-down directives, the goal of this project is to enable the cooperatives to work, make decisions, and resolve disputes more efficiently than basically any other type of company.
Current tech stack: Docker, postgres, nginx, SQLAlchemy, gunicorn, jinja2, Flask, Alembic, and Redis.
Please check out the repository documentation if this sounds like something you may be interested in. The docs include the foundational philosophy document called “Hierarchy by Consent” and there is also a template for an Articles of Incorporation that I intend to include as the first default document template in the software.
I’m still pretty early in the process but most of the tables are set up and I’ve made notes in the the classes explaining the requirements and workflows.
I’ve also got some issues started on Codeberg, mostly related to the front-end, which is where I need the most help at the moment. I will certainly be glad for help elsewhere as well.
It’s an open-source project so there is no immediate financial incentive. Part time contributors are certainly welcome.
There’s a discussion room on Matrix and here is the Repository.
Thanks folks
#programming
threaded - newest
This looks interesting, though a mighty undertaking. Any reason why not take an existing project and fork it? Or even just an ERPNext module? Would help cover a bunch of potential issues rather than start from scratch. Alternatively, have you thought of what would the MVP be to test it out? That way won’t fall into the do-everything-now trap (been there, done that, don’t recommend). Also, it looks very US-centric, so not gonna ask about GDPR, data security, etc. Instead, re: FE - for prototyping, don’t need design, just functional HTML + forms. Or, can try and poke at some premade or quick-assemble templates. Have you thought about functional (not design) requirements for the user experience, AKA how you imagine the users of this would use it? That is, full day in the office VS checking it once-monthly VS yearly for taxes, etc.
Sieze the spreadsheets of production