At the South Side Hackerspace in Chicago, we started off with a set of bylaws that defined how the space was going to be run. The bylaws defined a board of directors, who could appoint members to be responsible for various spaces within our hackerspace (woodshop, electronics bench, 3D printer zone, etc.). These "area captains" take ownership in making sure tools are maintained and things are put away. We believe very strongly in actocracy, but we also believe that there needs to be some structure to keep things moving.
The bylaws allow for members to be banned (this has only come up once). They also allow members to propose rules by which the space must be run. One of the rules defines a means storing half-finished projects in the space, so long as there is the owner's name and date they'll finish the project. If a lot of clutter is building up in the space, a board member can put tags on abandoned projects, take pictures of them, email the membership, and give people a week to respond before projects are thrown out. There's very little email drama around it because people understand the rules.
We believe that most people are generally doing good, and so any leadership from the board is a light touch.
To answer your questions directly:
> How do you organize your hackerspace?
We have a group of 5-7 members who serve on the board of directors. The positions are elected every year, and any member in good standing may run. The board selects members to act as area captains; they're responsible for making sure tools are maintained, the areas are cleaned, and supplies are bought. They spend some of their time at the space taking care of the space.
> Does really anarchy/actocracy work for you or do you have some set of more specific rules?
More specific. Actocracy works well in early stages when a small core of people are building the space, but it doesn't scale well I've found.
> How do you deal with mis-behaving members ?
The board has the power to ban a member, but it's only happened once and after a lengthy series of warnings and uncomfortable conversations. If a member messes up, we talk to them, explain what they did wrong, and help them improve. If they don't want to do better, well, that's a problem.
> How do you deal with equipment having damaged/stolen?
Equipment breaks. We set aside some money to fix it. If we find a member is intentionally damaging equipment, that's a problem that we deal with.
> Do you reward members having put some efforts in hackerpace running or just all members are equal?
We have two tiers of members with keys to the space: Full members donate more money every month; they can vote and get a storage locker. Partial members get keys to the space and access to the tools, but they can't vote or get a locker. The board can, and does, give people membership upgrades to taking on additional responsibilities around the space.
> How do you deal with general mess made by people?
We grumble and clean it up. Area captains spend a couple hours a month making sure their areas are usable. Personally, if I've noticed a lot of tools left out, I'll spend some time working on tool storage rather than my own projects.
> How do you deal with abandoned dust-covered projects whose owner doesn't care about these anymore?
Create a rule that the membership finds reasonable that lets you give a lot of warning that something will be thrown out if the owner doesn't remove it or petition for it to be saved in an entirely reasonable amount of time. Give plenty of warning, and err on the side of leniency, but you can't let your hackerspace become an unusable pile of electronics waste.
Good luck!
-Chris