Translate

Wednesday, March 04, 2015

Beyond Mundane social organization?

Thinking about the mechanics of doing my own appreciation awards, I'm glad to see that I could do it, work out a plan, and pull it off for this year, but if there are going to be more, of course it has to be more social! Which means, not just my opinion, but the opinion of some organization with voting members.

So for 2016, the nominees and awards would need to be decided by some organization and right now I'm debating with myself on a name.

Like maybe: Beyond Mundane Socials?

Work in progress...

However, one of the cool things I realized is that I have a template for a social media organization with my Globloc idea, where it could be established as an open source project. The first application then would be Beyond Mundane Coders, which would be made up exclusively of coders for the Globloc template.

The Beyond Mundane Coders, or BMC would be the core around which the Beyond Mundane social organization would build, where each coder would get, say, 100 invites to give to anyone they wished, in or outside the tech industry. And those invitees, would get, say 5 invites. But membership would be capped at a prime number called the Prime Cap.

For instance if it's me and 3 other developers, there would be 400 invites possible. Each of those invitees could invite 5 people, so 2000 more, but those people couldn't invite anyone else as the first Prime Cap is 2011 members.

Annually there would be organization votings for things like nominees for the BMSA's, and the winners, and also would be the option to raise the Prime Cap with a two-thirds majority, where every member gets a single vote. So yeah, the core developers would have their voting power diluted, by design.

The Prime Cap can be reduced at any time by a simple majority of votes, as long as it's not then less than the number of current members.

Of course, the organization might never even reach the cap. And if it gets started but flames out--plenty of ideas do--then there is a KeyStone Member who has the final option to dissolve the organization, with a termination vote with any remaining members which becomes an option when there is only a single developer on the project, who then would be admin of course, and at most 100 remaining with a Prime Cap then of 101.

New categories would also be subject to vote, where a two thirds majority would be necessary to add any new categories with at most 3 added per year.

Newly added categories can be removed by a simple majority as long as no awards have been given, or by two thirds majority if any have, though awardees would retain awards.

The base 5 categories are permanent and cannot be removed.

Rescinding an award requires a two thirds majority vote for finality, though a governing committee can be elected to authorize one immediately for cause.

Getting this thing started just means I find some other people who want to sign on for a new project, which of course would be at SourceForge. I can of course start one at any time, but I want three coders along. Would need a network expert, as I know nothing about networks. Would need a database expert but everyone would need to be able to handle databases. Oh yeah, and someone good with servers! And hosting for the first implementation of Globloc would be important as well. And each would also need to be well versed in social media, have public profiles as could be a very public position, and be exceptional coders in their own right.

So that seems like some quick ideas that could be one path to getting input from others which is necessary for more social awards. May toss out a few ideas here and there as I continue to process how well these social awards worked. It was quite a bit of work! Which is ok, but it's fascinating to me that even when it's just me and my opinion, picking best for social takes a good bit of thinking. It's not an obvious thing.


James Harris
Post a Comment