User:OneKarma/Forum/Demo: Difference between revisions

Latest revision as of 01:06, 1 December 2011

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

For efficient and fair governance, there must be an open, equally accessible forum
1. All relevant information must be equally available
2. The time-line of making decisions must regard all persons' schedules
The current iteration of the GA is not equally accessible

The general process leading to a proposal is as follows:

One becomes aware of an issue
1. One explores the depth of the issue in pursuit of potential solutions
2. One documents the many aspects of the issue and how a solution might be implemented (draft creation)
One requests discussion via greater polis
1. 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

To design the forum
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:

The GA must agree upon the requirements described on this page (edits should be suggested on the Discussion tab)
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.

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)

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.
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:
- links must be accurately described, and
- 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.

User:OneKarma/Forum Table of Contents

User:OneKarma/Forum - an introduction to the concept of an open forum, and utilizing this wiki as such
User:OneKarma/Forum/Functions - the functions that an open forum should perform in order to be successful
User:OneKarma/Forum/Demo - a 'prototype' for how working pages can be organized in an open forum

@@ Line 1: / Line 1: @@
-The Forum Demo will serve as a demonstration of the (currently proposed) structure of a proposal regional/global forum.
+'''''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.
-==Argument==
+:''View the [[User:OneKarma/Forum/Demo/Simple|simple]] version of this page, which could serve as a 'template' for users who wish to create new pages.''
-introductory statement/paragraph
-highlight certain language that may not be commonly defined or that is specifically defined here.
+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.)
-It is necessary that all actions can be performed by any and all persons. This requires a simple structure for suggesting, discussing, drafting, and voting.
+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.
-The main page will be the '''current draft.''' To save massive editing confusion, the draft will be open for editing '''only''' to the primary authors. Primary authors are the core group working on the proposal. they should be in constant contact with each other regarding making 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.
+:''[This proposal should be aided by: "[[User:OneKarma/Forum/Supporting the Disabled|Support for non-internet enabled collaborators]] in a time where the primary collaborative method is online".]''
-===premise (problems)===
+__TOC__
-very concise and specific bullet points
+==Section 1: Argument==
-# for efficient and fair governance, there must be an equally accessible forum
+* Introduction to issue and proposed solution
-## all relevant information must be equally available
+* Highlight language that may not be commonly defined or that is specifically defined for the proposal.
-## the time-line of decision-making must regard all persons' schedules
-# the current iteration of the GA does not grant equal access
-===intended conclusion===
+It is necessary that all actions can be performed by all persons. This requires a simple structure for suggesting, discussing, drafting, and voting.
-# we must design the forum
-# we must exemplify the forum here
-==Solution==
+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.
-this section is the meat of the proposal.
-as this is merely an example of the proposed structure, this 'solution' section is only a part of the whole solution. other proposals will use this section to describe the necessary actions
+In addition to an introduction, the main page will contain the following:
-==Relevant Documents==
+===Section 1a: Premise (Problem)===
-link to all documents, including meeting minutes, etc.
+Contains concise and specific bullet points
-all documents should be hosted on the wiki, and may be backed-up in various locations, such as other internet hosts and personal computers.
+# For efficient and fair governance, there must be an open, equally accessible forum
+## All relevant information must be equally available
+## The time-line of making decisions must regard all persons' schedules
+# The current iteration of the GA is not equally accessible
-==Clarifications==
+;The general process leading to a proposal is as follows<nowiki>:</nowiki>
-FAQs, points of info(?), etc. this section serves primarily to summarize discussion points and how they are addressed in the 'solution'.
+# One becomes aware of an issue
+## One explores the depth of the issue in pursuit of potential solutions
+## One documents the many aspects of the issue and how a solution might be implemented (draft creation)
+# One requests discussion via greater [[wikipedia:Polis|polis]]
+## One edits the draft (or creates anew) via greater and greater polis, until accepted by the highest relevant polis
-==Contacts==
+;Notes
-===primary authors===
+* '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.)
-and their specific roles regarding the proposal (maybe a very short personal statement)
+* 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.
-===secondary authors===
+===Section 1b: Intended Conclusion of this Proposal===
-those who wish to be informed of all updates but are not of the original authors. a secondary author may become a primary author by request to existing primary authors. the primary authors may set requirements for approval at their discretion.
+# To design the forum
+# To exemplify and enable the forum on this wiki
-==Discussion Tab==
+==Section 2: Proposed Active Solution==
-the discussion tab will serve as the first meeting place for questions, comments, criticisms, and amendments. if the discussion section becomes popular and therefore requires live-updating, it must be divided, summarized, and linked by topic.
+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:
+# The GA must agree upon the requirements described on this page (edits should be suggested on the Discussion tab)
+# 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.
+# [[User:OneKarma|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)==
+# The [http://wiki.occupyboston.org/wiki/Talk:Forum_Demo_-_Proposals discussion tab] will serve as the primary meeting place for questions, comments, criticisms, and amendments. The discussion should be summarized and sectioned by issue.
+# 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:
+#* links must be accurately described, and
+#* 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.
+----
+----
+{{:User:OneKarma/ForumTOC}}