User:OneKarma/Forum/Demo

'Note: This page exists to present a 'prototype' method of use. The use of a structure such as the following would effectively draft and maintain documents naturally as it is used.


 * View the simple version of this page, which could serve as a 'template' for users who wish to create new pages.

This is the Forum Demo. It demonstrates the structure and process of working pages in a forum. It is intended that this process be scalable, though not actually requiring scale. 'Tiers' would be designed to address various issues within an intuitive and ordered hierarchy. (Working Groups are a first step in creating such an hierarchy, but they might require a minor re-design to effectively implement this proposal.)

In addition to the introduction section (which you are currently reading), every 'Working' page should include the sections exemplified below. The creation of these sections serves as a learning process for authors, while also establishing a readable 'article' on the subject.


 * [This proposal should be aided by: "Support for non-internet enabled collaborators in a time where the primary collaborative method is online".]

Section 1: Argument

 * Introduction to issue and proposed solution
 * Highlight language that may not be commonly defined or that is specifically defined for the proposal.

It is necessary that all actions can be performed by all persons. This requires a simple structure for suggesting, discussing, drafting, and voting.

The main page will be the current draft. To save massive editing confusion, the draft will be open for editing only to the primary author(s). Primary authors are the core group of developers. They should be in constant contact with each other regarding changes to the draft page. To become a primary author, one must be in agreement with the other primary authors upon the intent of the proposal. It is important that the introductory paragraph explains this intent very clearly and very briefly.

In addition to an introduction, the main page will contain the following:

Section 1a: Premise (Problem)
Contains concise and specific bullet points
 * 1) For efficient and fair governance, there must be an open, equally accessible forum
 * 2) All relevant information must be equally available
 * 3) The time-line of making decisions must regard all persons' schedules
 * 4) The current iteration of the GA is not equally accessible


 * The general process leading to a proposal is as follows :
 * 1) One becomes aware of an issue
 * 2) One explores the depth of the issue in pursuit of potential solutions
 * 3) One documents the many aspects of the issue and how a solution might be implemented (draft creation)
 * 4) One requests discussion via greater polis
 * 5) One edits the draft (or creates anew) via greater and greater polis, until accepted by the highest relevant polis


 * Notes
 * 'One' may be more than a single individual. 'One' may choose to privately explore an issue and its potential solutions in the birthing of a draft. When a first draft is complete, it may be presented for review at the first tier. (The 'one' draft author(s) is considered the zeroth tier.)
 * A proposal must pass through varying public approval tiers from the bottom up. (For example, a working group 1. drafts a document, and 2. votes affirmatively to present that document for ratification at a General Assembly.)
 * Each of these tiers will have different requirements to 'pass'.
 * A proposal must be passed by all tiers to which it is effective. (Working groups can create internal working groups for specific issues that fall under the umbrella of the working group. This can help to pull people into areas of interest that are currently being discussed.)
 * A proposal must detail a set of actions to be performed.

Section 1b: Intended Conclusion of this Proposal

 * 1) To design the forum
 * 2) To exemplify and enable the forum on this wiki

Section 2: Proposed Active Solution
This section will contain a description of necessary actions, therefore it will be the largest section of the proposal. This page is merely an example of the proposed structure, and this section is therefore shorter than it would normally be.

To implement this structure, a number of actions must be taken:
 * 1) The GA must agree upon the requirements described on this page (edits should be suggested on the Discussion tab)
 * 2) There must be established an intuitive hierarchy of working groups and methodology

Section 3: Links
Link to all documents, including concepts, examples, meeting minutes, et al.

All relevant documents should be hosted on the wiki. It is important to have both public and private back-ups in various locations, such as personal computers and other internet hosts, like Google Docs.

Section 4: Clarifications
This section summarizes discussion points and how they are addressed in the 'solution'. There may be FAQs, points of information, and links to particularly important discussion points.

Section 5: Contacts
Authors should list their names, contact information, and specific roles regarding the proposal. This could also incorporate a short personal statement.

Section 5a: Primary Authors
Primary authors may approve 'new' primary authors by request.
 * 1) OneKarma 17:39, 7 November 2011 (EST) - Responsible for all concepts, texts, and motivations. I have failed to create a core group of developers due to my strange work schedule, and probably due also to my very critical nature. It has been a difficult task to describe the concepts and to determine the necessary aspects of this proposal.

Section 5b: Secondary Authors
Secondary authors are those who wish to be informed of all updates, but who are not of the original authors.

Section 6: Discussion (on Discussion tab)

 * 1) The discussion tab will serve as the primary meeting place for questions, comments, criticisms, and amendments. The discussion should be summarized and sectioned by issue.
 * 2) If discussion is highly active, it may require hosting on a live-updating site, such as pad.riseup.net. When a discussion evolves into live-updating space:
 * 3) * links must be accurately described, and
 * 4) * the primary author(s) will have absolute rights to modifying the discussion tab. There shall then also be a carbon-copy of this tab so that non-primary contributors may help to direct the discussion. As well as updating the Clarifications section, the primary author(s) will be responsible for updating the discussion tab to match the live-updating version.