[OOTB-hive] [GOV] [INFRA] roles, resposibilities, rights on OOTB assets and resources

Heiko Robert heiko.orderofthebee.info at ecm4u.de
Tue Feb 17 10:18:01 GMT 2015


Dear bees, dear OOTB board,

when setting up the server infrastructure I realised that there are some 
issues if there is no official registered association for the bees:

  * Only real persons, organisations can order, register assets like
    servers, domains, paid or unpaid services
  * OOTB can't own anything because it does not officially exist and
    therefore can't act in any official way to protect the interests of
    the bees

Specific issues we should find some rules and answers for are:

Infrastructure

  * The bees refuse money. If one real person or organisation rents a
    server, buys a service for the bees, the party who orders will be
    liable for any damage or any breach of law which is determined by
    the country of the orderer and/or of the vendor. Therefore the
    orderer should really take care whom to give access to these
    resources and wants to make everybody accountable working with these
    resources when things are misused somehow. The bees should support
    the orderer by defining and monitoring rules like any other
    organisation will apply to
      o limit the number of persons having (full) access to the
        infrastructure
      o determine the identity of every person having access to the
        infrastructure
      o grant and deny rights and permissions following the "need to
        know" or "need to have" principles
      o implement roles and responsibilities
      o define a list of persons who may grant roles and rights to others
      o monitor/log activities

Assets

  * By now the assets are ownend by volunteers and sponsors and this may
    cause trouble some day because in that case they're the owner with
    all consequences - not the bees
  * It's not possible to contribute to the bees or at least there will
    be no official party which can advocate/defend/execute the rights of
    the bees. Of course technically any project can be forked in the bee
    github project

For the next months I don't expect any issue with that but it would help 
to agree on a common understanding like

  * if there will be a registered organisation the assets will be handed
    over without any restriction to that organisation at no cost
  * license requirements for contributions should be defined and checked
    to be able to provide a honeycomb edition including contributions

*Are there any volunteers to work this out and prepare/moderate a proposal?*




For the most bees this shouln't be an issue at all. They expect to read 
the rules somewhere and want to cowork in their role on assets and 
services they have access to. To make this happen we need to know the 
use cases and roles we should provide.
These use cases should be collected in another thread.

Thanks
Heiko

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.xtreamlab.net/pipermail/ootb-hive/attachments/20150217/3865f40f/attachment.html>


More information about the OOTB-hive mailing list