cross-posted from: https://infosec.pub/post/46083169
Hello,
I’m here to ask for guidance on an ongoing project. A number of years ago I wrote an Articles of Association for a worker’s cooperative as I think it should run. The main difference between a conventional co-op and mine is that a conventional co-op tends to have no hierarchy while in mine there is a CEO who gets elected periodically based on their business plan. The theory is that this brings democratic ideals into the workplace without sacrificing the productivity gains that result from hierarchical teamwork. You can read more detailed information on my Beehaw Post.
To put it into practice I need to create an open-source enterprise application server with applications specifically designed for the management of these companies. I created a block diagram to show you what I envision (attached to the post), and this represents my ideal “wish list” for what it should include.
The controls listed at the bottom will determine the permissions everyone has on the network and will be used to design GUI screens. I was going to draw connectors to each of the services but it would have turned into spaghetti.
I’m pretty decent with local programming including database and GUI design, but I lack experience with network programming.
So far I think I need to use XMPP for the messaging client and SSH for the rest. Since I’m most comfortable in Python I was going to look into Paramiko.
So my question is, where should I go in my research? Is there a particular component in the diagram you think I should try to build first?
Thanks in advance for any help, Juniperus
Sorry I know that's a bit unclear. The "staff roles" and "managers" are roles that the CEO is able to assign to staff through the software. In other words, it's the mechanism the CEO uses to construct their hierarchy. Same with performance metrics, those are written expectations that would be entered into the system for each person's role.