Proposal for user removal and wave management

[devnullius @ googlewave.com]

I posted below here:
http://www.google.as/support/forum/p/wave/thread?tid=526fc20294ce21f8&hl=en&fid=526fc20294ce21f8000479c5600f3fcc
.

I would like to have some feedback!

Ik zou graag wat feedback hebben! Hoe moet gebruikersbeheer voor
Google Waves plaatsvinden...? Ik ben HEEL BENIEUWD naar jullie
ideeen :)

Peace ende Vrede,

Devvie!

My Ideas.... (English only - sorry)

Also.... About removing regular users...

How about some kind of cascading pyramid-scheme?

At first, the one that creates the wave becomes the Big One
(superowner).

The next two or three members are all made Administrators.

These first ones can assign - to will - new administrators.

All users can assign new users to the wave (to keep it flexible).

The Big One should be able to tagg an option if a wave "may" be
published to internet public or not. By default, this option should
be: pub...@a.gwave.com MAY NOT be added. Only after careful
consideration, this bit should be turned off.

If the Big One decides to Unfollow the wave, this should only be
possible if he first assigns a new Big One.

Now the cascading kicks in: the wave also needs new Administrators.
After the leaving of Administrator(s) or even the Big One, new
Administrators should be assigned automatically. The first one to join
the wave and hasn't have administrator rights yet, should be assigned
those administrator rights.

An option could be to define the amount of administrators for a wave.

For organizations it would be great if this assigning of
administrators (from the pyramid) could be truly branched. So that a
local office has it's own assigned administrator(s). To achieve this,
administrators must be able to assign more administrators as they see
fit. Each new assigned administrator is it's own connected pyramid,
with it's own hierarchy and it's own cascading administrator and user
system - but slave to the main wave pyramid (or: a local pyramid does
not have a Big One user). This way, whenever a Wave falls low in
administration users, the wave will dynamically update it's managers
group. All under the supervision of the Big One. The Captain that
shouldn't leave his ship : )

An option could be to define the maximum amount of administrators that
may be assigned by one same-leveled administrator group.

The rest of the details are for Google Wave team, it's Think Tank and
it's SImulators :) - I just was thinking a little while watching a
dumb movie and deceided to write some stuff and ideas down while the
movie finishes...

Happy to receive feedback!

Peace!

Devvie

~~~ devvi...@googlewave.com ~~~

Conare nullius momenti videri fortasse missilibus careant
------
All spelling mistakes are my own and may only be distributed under the
GNU General Public License! - (© 1995-1 by Coredump; 2002-9 by
DevNullius)