Juniperus

joined 1 month ago
[–] Juniperus@infosec.pub 4 points 2 days ago

Dilution should require a vote from owners.

Would it be helpful if that had been written into the company's AoI and server software?

[–] Juniperus@infosec.pub 1 points 2 days ago (1 children)

Yeah I wouldn't mind an experienced dev taking over the architecture, but I will proceed myself if that person doesn't come along. If you were worried about it not being applicable outside the US, stuff like the eligible_1099 field could be converted into a "country_config" object or something like that. I'm already planning on supporting all currencies so it would make sense.

In terms of modularity, I'll have to think about it some more. I'll spend some time looking into those projects and consulting about it with the LLM today.

Now about that spreadsheet and reddit post. That's not just something to consider, that's a person to contact. I would love to see how their ideas have developed in the past 4 years. I'll have to grab a burner today. Thank you!

[–] Juniperus@infosec.pub 8 points 3 days ago

To the office, to fight the corpos!

[–] Juniperus@infosec.pub 4 points 3 days ago (3 children)

Why not use existing projects? A combination of my specific design requirements not existing anywhere else and my lack of software architecture experience. My background is in systems and organizational theory, and while I have experience in mathematics related programming, this is my first server architecture. So that being said, I'm certainly open to ideas as long as that doesn't stop it from working right. I am planning on integrating different tools like messaging, and I'll certainly use something like Continuwuity for that. It's just that for the core database design it really needs to have a specific integrated schema, at least that's my opinion. Like I said I'm open to ideas, my goal is to get the project done.

I'm not familiar with ERPNext but it looks interesting. As you pointed out this is US based, so it looks like I would have to take that into account as well.

In terms of sensitive information, the US does have laws about Personal Identifying Information, so the "Party" table has a corresponding "PartyPii" table with information that isn't subject to audit and can be deleted. Home address, email, phone, etc. It is also stored encrypted, so while I'm sure I don't have it all figured out yet, these things are on my radar.

In terms of MVP, I will certainly be testing out front-end funtionality as I build it. Start with a login page that accepts a default user and brings you to a dashboard page. Get the accounting going so you can make Journal Entries, etc. Prettymuch going by the "Core Design" section at the start of the README and testing in chunks. But in terms of actually seeing if it meets it's intended function, unfortunately that comes down to an actual beta version I think. I will need to host it and invite people to participate with "points" instead of money.

Someone over on beehaw suggested Svelte for front-end mock-up so I've been playing around with the tutorial. It's certainly neat. I should be able to get demo pages going without too much trouble, they just won't look too special.

And yes, I have begun thinking about the day to day. I think non-management members need to have a pretty significant capability with just a mobile version of the pages, since not everyone has an actual computer. But either way I want the information to flow smoothly through the organization.

Thanks for your input!

[–] Juniperus@infosec.pub 1 points 3 days ago

Yeah I'm a big fan of that instant render. I'm sure I'll have questions, thanks again

[–] Juniperus@infosec.pub 1 points 3 days ago (2 children)

Looks extremely useful I'll play around with it tonight. Thanks

 

cross-posted from: 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

 

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

[–] Juniperus@infosec.pub 1 points 5 days ago* (last edited 5 days ago)

Hey thanks for your thoughtful analysis, I didn't know I needed a gimp suit for business! Sounds like those grocery workers certainly had them on! I don't know how people are supposed to live like that.

You certainly make a fair point about capping pay. There should probably be a max ratio for the hourly rate (or monthly/yearly as the case may be). Assuming the officers get an hourly rate like everyone else (which is the way I want it to work), you would want that max pay ratio to be defined explicitly. The bonuses are also voted on so if that gets to be too much the voters can knock it down.

I started a public matrix room for the development of the server software. I'm pretty far along on the database schema now and you can even check out the new and improved Articles of Incorporation I drafted, including an analysis of it after I ran it through an LLM for an objective take. Message me if you can't get it through matrix.

There will also be a set of Bylaws and it's an open question if max pay ratios and bonus rates should go in there or in the AoI. If it goes in the AoI you have to file an amendment with the state, but the Bylaws are just internal votes.

In terms of the software, I'm going to make it so you can do things like anonymously submit or endorse your boss's expulsion from the company, then send it to an anonymous vote. Pretty extreme to be sure but I've had bosses who deserved it. On the technical side I'm confident in my plan for secret votes and other challenges, but I would certainly welcome any input on it.

https://matrix.to/#%2F%21dVwyUzAwiuIflwnpEF%3Amatrix.org%3Fvia=matrix.org

EDIT: And here's the repo if you're interested: https://codeberg.org/Brachylophus/Apoidea

[–] Juniperus@infosec.pub 1 points 1 month ago

Obviously everything is off, we're falling into tyranny. Anybody wants to take action, look in my post history or PM me.

[–] Juniperus@infosec.pub 1 points 1 month ago

Thanks for all the great solutions, I'll be looking into your advice. Like you said it is definitely a massive project for a beginner, I'm going to take it a step at a time, and maybe do a smaller experimental app first to get my bearings. The good thing is I'm not in too much of a rush so I have time to learn.

[–] Juniperus@infosec.pub 1 points 1 month ago

My current thinking is that the vote is electronic but you get a paper receipt with a bar code or something. Not sure how it will turn out, like many of these apps it's a whole project in itself

[–] Juniperus@infosec.pub 1 points 1 month ago* (last edited 1 month ago)

I was thinking lemmy because of the voting structure. Since it's internal discussion it could be used by the management to gauge sentiment in the company. It wouldn't be for federation.

You're probably right about it being too complex though, just not sure if there's a lightweight option that's a closer match than ~~discord~~ discourse (does discourse having voting?). Something to consider.

[–] Juniperus@infosec.pub 1 points 1 month ago

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.

 

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

 

(Crossposting from my Beehaw Post.)

Let’s talk brass tacks. A lot of people I interact with online seem to see top-down reform as the only option for real societal change, and often despair when they see the rampant corruption in our government and private companies as being unsolvable problems.

Similarly, Union organizing efforts have largely stalled despite significant effort from activists. This is simply due to the enormous power wielded by capitalist corporations, who will always protect their own interests above those of their employees. Again, we reach a point where many people despair at an apparently unsolvable problem. Indeed, unionization has faced a steady decline in the US for over 40 years, and is now likely below 10%.

The problem here is that people keep trying to organize against their employer, when in fact there is another option: they could organize without their employer. Put another way, the workers of a company could pool their resources and found a worker’s cooperative which they all operate together through elections and democratic voting. Then they simply quit their old jobs as work in the cooperative becomes available.

However, the problem with worker’s cooperatives is that there are very few successful examples, and I am not aware of their internal documentation being available for review. The best information I could find was this diagram of the Mondragon Corporation, which has similar elements to my organizational diagram, but isn’t descriptive enough to give insight into the inner working of their management.

There simply doesn’t appear to be a standard template on which to construct such an organization, at least not one that I would expect to be successful. This post is the beginning of an attempt to address that shortfall.

Hierarchy by Consent: The concept that a strategic executive at the top of an operational hierarchy should be legitimized in their position through a popular election enfranchising all stakeholders.

Many worker’s cooperatives built in the 19th and early 20th centuries failed because they weren’t as productive as other companies at the time. Researchers have indicated that this is likely due to the lack of hierarchical management in the organizations, which resulted in a “flat” management structure.

I would agree with this analysis, and point out that hierarchical decision making is what gives an organization strategic direction. Without such structured teamwork, productive efforts are less coordinated and as a result suffer from reduced overall productivity. In biology I was taught that a cell is greater than the sum of its constituent parts, but if those parts can’t coordinate properly then I would expect the effect is diminished.

The problem with traditional capitalistic companies, in my opinion, isn’t the hierarchy itself, it’s that the hierarchical management structure results from conditions over which a worker has no control and there is therefore no incentive for the hierarchy to act in accordance with the worker’s best interest.

A person is forced to find work for their own survival, but because there are almost no democratic companies to work for, they’re forced into a traditional company, where the top of the hierarchy could be determined by any number of inappropriate factors including generational wealth, nepotism, favoritism, or other corrupt circumstances. Those decision makers then have no incentive to act in the best interest of the workers who fall under them in the hierarchy. I would call this arrangement Hierarchy without Consent.

By integrating elections into the empowerment of key decision makers, an organization can maintain a healthy, productive work environment while letting the workers have self-determination in their work environment and goals. I believe this will lead to much healthier and more productive workplaces.

Call to Action: Help me Write a Template

Some time ago I started writing a template for an Articles of Association for such an organization, which you can read as an odt or as a pdf. The image on this post is the organizational diagram.

The organization I envisioned is governed by General Conferences, which are meetings to include all of the Owners. The GC first elects a President, who acts as head of the labor union and is the primary facilitator of company business. The GC then elects a CEO who becomes the executive at the top of the operational hierarchy for productive work. The CEO is elected based on their business plan, which is voted on by all owners. Elected leaders serve for a term after which they come up for reelection.

I’m here to ask for input and debate on this template. It has not had a legal review so if you’re a lawyer or co-op expert expect to notice lot of missing legal clauses and the like.

Incentive Structures

To make this work, there should be some sort of incentive for Owners to step up and take on the burden of leadership. To keep things balanced, however, the incentives should provide different objectives to different positions.

In my template, the President receives a percentage of the total payroll as a bonus, while the CEO receives a percentage of the business income (aka “surplus”) that their project generates. In this way, the President seeks to maximize payroll while the CEO seeks to maximize surplus, and in that back and forth the organization will theoretically achieve long-term stability while maximizing the financial return for the Owners. The effect would be similar to the political pendulum metaphor.

Similarly, if the cooperative is big enough to require a Board of Directors, those people would also be eligible for an incentive bonus based on company performance, perhaps including factors such as workplace safety and legal compliance.

Worker payroll could be handled a number of ways, but my current thinking is that it would be an hourly pay scale similar to union payscales, with progression for years of service, but also with performance ranges so that production management can offer performance incentives to all workers.

The bonus rates, the payroll chart with ranges, and performance metrics would all be voted on by the GC.

Equity Control

Another key pitfall of traditional capitalist companies is ownership rules. Most workers own very little or no stock in the company for which they work. They have no opportunity for financial growth except what the hierarchy decides to give them each year, while the investor class, which does no work, makes off with the surplus.

I’m proposing a system of equity control where owners are forbidden from owning more than a single share in the Company’s stock, called an Equal Ownership Share (EOS). Once an Owner has a full share they have full voting rights, but they are not permitted to purchase any more stock.

New and Partial Owners can have a partial EOS during their Provisional Period, during which they will have a corresponding partial vote. The length of the Provisional Period is set by vote, and Equity is awarded to the new Owner incrementally during that time.

Because the Owners have stock in the Company, they are the recipients of all the Company’s declared dividends. This way they are paid twofold, once from their hourly compensation and again from their dividends.

Incorporation

An open question I have is how to legally incorporate such an organization. One strategy might be to incorporate as an S-Corporation, which is a “pass-through” organization, meaning all business income is distributed and reported on the tax returns of the Owners. This may run into trouble due to regulations concerning voting rights, since my template has custom voting.

Another alternative may be to incorporate as a not-for-profit of some type.

I’m not sure about the answer to this one, but I certainly welcome input, especially from any legal or co-op experts.

Team Management Software

I’m in the early stages of developing open-source team management software for this specific type of cooperative. The software will ideally include things like Accounting and Payroll, Secure Voting, Document Control, Chat Functions, Video Calls, and other team management solutions. This is key to making sure these cooperatives can function efficiently right from the get-go.

The software should include multiple users with multiple roles and permissions, and should work over LAN, with the option to run it without being connected to the internet (as it should be resilient).

I have experience with local programming including database and GUI design but I’ve never done anything over a network, so I have some learning to do if I’m taking this all on myself.

I plan to host the files on Codeberg.

EDIT: Further Discussion:

Block Diagram Discussion on Programming.dev

If you or someone you know might be interested in contributing to this software, please let me know.

The Big Picture

The key take away here is that most people seem to be waiting for someone like a politician to come along and make a change for them. Instead, we should be working on reform from the bottom up in the places where we spend the most of our time: our workplaces.

I believe that if we are able to incrementally build up an alliance of these organizations we could begin to fix some of the bigger problems currently facing our society.

If you or someone you know would like to contribute time and effort to this project, please direct them here. Also, feel free to make your own version if you like.

TLDR: Workplace hierarchies traditionally increase productivity at the expense of worker enfranchisement. I’m proposing a new type of worker’s cooperative to include what I call “Hierarchy by Consent” and asking for help realizing it.

Thank you,

Juniperus

view more: next ›