3rd Rock Grid Community Charter - OneCore

The OneCore part of the community charter defines how community core and the structures, items, and areas found in community core are managed. Furthermore, the OneCore plan links the functions offered by the community to structures and areas in community core. The OneCore plan comprises:

• Definitions of community property and ownership

• A list of community functions and function groups

• A list of structures/areas in community core

• A function group zone allocation map

• A function to location matrix

• A structure/area to location matrix (ownership register)

• A list of basic requirements each location/area poses

The OneCore plan aims to:

• Define ownership and authority in community core

• Enable and facilitate all designers/builders interested in improving community core

The OneCore plan should be used in conjunction with:

• The Community Charter (main text)

• Community procedures

Community property

The 3RG community core is owned and governed by the 3RG community, as defined in the main text of the community charter. Building in community core, and/or working on structures, items, or areas in community core, is regulated as follows:

• Permission for working in community core is required, and can be granted by:

  • a community Elder, or a Senior acting on behalf of the Elder

  • a teacher or educator for work in educational sandboxes

  • a community decision

• Permission will be granted for the duration of a project only

• The community will own all structures/items built/placed in community core, except:

  • structures/items in areas allocated to temporary housing

  • structures/items created in educational sandboxes

  • when community and owner/creator agree differently before the project commences

When structures or items are donated to the community to be stored, used, or given away in community core:

• Ownership of the copy of said structures/items must be transferred to the community

• The community understands that the donor is acting properly as the owner

• Where a donor acts at the behest of a creator, the donor accepts liability for any issue that arises concerning their right to donate the item.

Ownership of structures/items by the community is defined as follows:

• The community will be the owner of a copy of the structure/item concerned:

  • the copyrights on the original template remain with the donor

• Considering the exemptions below, the community has a right to:

  • move or relocate any structure/item within community core

  • copy any structure/item for use elsewhere in community core

  • modify any structure/item as it sees fit

• The following exemptions may be made at the discretion of the donor/builder

  • Script source code may be protected (no-mod)

  • Textures may be protected (no-mod, no-copy)

  • So called 'freebie' items may be protected as the creator/donor sees fit

• Further exemptions to the move/copy/modify rules may be:

  • agreed between community and donor/builder when the donor/builder has reasonable grounds for applying for any such exemption.

• The community reserves the right to remove any structure/item from community core

• The community will NEVER sell or give away structures/items it owns, except

  • items designated to be given away for free (so called 'freebies')

The community are custodians of all the structures/items donated to the community.

• Designers/builders are requested to respect the legacy of those before them

• Existing structures/items that cannot be re-used or relocated:

  • will be stored in the 3RG museum

  • are available to all designers/builders for re-use in community core

The specific procedures to be used around community property can be found in the document “Community Charter – Procedures”.

Community functions

The community offers, or aims to offer functions in the following function classes:

• Education/Arts

• Entertainment

• Information

• Property

• Reception

This list follows the division of operational governance in portfolios as found in the charter and defines which Community Elder will be responsible.

Function Groups

Many functions form logical groupings. Specific aspects of the community, like a welcome center, even demand a specific grouping of functions. Equally the location of each group in community core in relation to other groups invites consideration and planning.

Using a top-down approach, the following function groups are defined (descriptive list):

• Welcome (arrival new citizens, greeting, freebies, etc)

• Science and Arts park (education, art)

• Rock village (temporary housing new citizens)

• Pebble Beach (beach area with activities, hangout, and more)

• Game park (relexation area with simple games (chess, tetris, ...))

• Culture park (cultural displays from around the world)

• Entertainment park (music, fairground, plays, and more)

• Roleplay Land (structured activities allowing long term participation)

• Adventure Land East (themed area for adventure/exploration, designer specifies)

• Adventure Land West (themed area for adventure/exploration, designer specifies)

The following basic zone allocation map has been drawn around these groups:

Please note the following:

• The 16 regions on the outside of community core are:

  • low prim regions (1.000 prims)

  • border on regions not controlled by us; a waterway as border is prefered

• The inner ring of 8 regions are medium prim (7.500 prims)

• The central region, Our Town, is high prim (15.000 prims)

• The map is drawn on region borders for brevity, this is not a strict requirement

• Within reason we may petition management to increase the prim allowance

Function list

The function list of the 3RG community is split into:

• Functions we currently offer

• Function we may like to offer in the future

Current functions

The community currently offers the following functions:

• Community information

• Community meeting

• Core overview map (needs update)

• Course listing

• Courses (classes/workshops)

• DJ music

• Ferry services

• Freebies

• Greeting services

• Hangout

• Property development

• Relaxation

• Visitor information

Future functions

The community aims to offer the following functions:

• Adventure/Exploration

• Art exhibitions

• Ballooning

• Community bank

• Community core map

• Cultural displays

• Dance

• Discussion

• Event listing

• Fashion show

• Games

• Grid overview map

• Group listing

• Live music

• Movies

• Orca racing

• Plays

• Property storage

• Sailing

• Shop directory

• Visit directory

• Weddings

Structures (areas)

The structures/areas list of community core is split into:

• Structures/areas we currently have

• Structures/areas we like to have in the future

Current structures/areas

• Adventure/Exploration area

• Animal park

• Arboretum

• Arrival area

• Art exhibition area

• Cafe

• Classroom

• Community corner

• Conference center

• Dance hall

• Fairground

• Freebie area

• Information area

• Lake

• Meeting area

• Movie theatre

• Museum

• Parkland

• Path

• Railway

• Railway station

• Restaurant

• Road

• Scating rink

• Speakers corner

• Temp. Housing

• Waterway

Desired structures/areas

• Airport

• Bank

• Beach

• Bumper cars

• Club

• Cultural displays

• Edu sandbox

• Festival area

• Game area

• Harbor

• Hospital

• Offices

• Prison

• Role play area

• Theatre

• University

• Warehouse

• Wedding chapel

Registers

This chapter contains the two registers the community maintains in the context of the OneCore plan.

Function to location table <<to be completed>>

The Function to Location table aims to:

• Inform where in community core each function is offered

The fields in the table are:

• Function: the function being described

• Location: where the function is offered, using the '<region>/x/y/z' format as in SLURLs

• Structure: the name of a structure or area the function is associated with

• Group: the function group of this instance of the function

• Remark: optional remarks

Structure/area to location list (ownership register) <<to be completed>>

The Structure/Area to Location table aims to:

• Inform where in community core each structure is located

• Show who donated the structure and when

The fields in the table are:

• Structure: name of the structure or area

• Location: the location where the structure can be found (SLURL format)

• Donated: the date the structure was donated to the community (yyyy-mm-dd)

• Donor: the name of the previous owner of the structure

• Ex: Exemptions – agreed exemptions to the move (m), copy (c ), or modify (x) rules

• Remark: optional remarks

Requirements

<< to be completed >>