blob: bc593419a3a0a6aa923eea9ada1ca9e1d47e5cc4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
---
stand_alone: true
ipr: none
cat: std
area: Systems Engineering
wg: OSMORA Standards Group
docname: OAP-0001
title: OSMORA Amelioration Proposals
abbrev: OAPs
lang: en
kw:
- oap
- amelioration
author:
- role: editor
name: Ian M. Moffett
org: OSMORA
city: Washington, DC
region: Southeast
code: 20020
email: ian@osmora.org
--- abstract
Description of OSMORA Amelioration Proposals
--- middle
# Introduction
OSMORA Amelioration Proposals (OAPs) are structured
documents that serve to drive changes imposed by OSMORA
by describing their fundamentals while allowing others to
amend/revise them.
## Purpose
The goal of having OAPs is to provide an organized means of proposing
and improving ideas that contribute to the betterment of society
and technology. These proposals can range from technical improvements
to societal reforms, and they are open to discussion and collaboration
for those who have understood and commited to the OSMORA oath.
## Audience
OAPs are intended for those who are commited to the OSMORA oath. These
proposals MUST only be considered official and binding when they are approved
by a number of OSMORA members and a single OSR (OSMORA Standards Reviewer).
# Requirements Language
{::boilerplate bcp14-tagged}
# Structure
An OAP will typically include the following:
- OAP ID: Incremental document identifier.
- Abstract: A concise summary of the proposal's intent and impact.
- Motivation: Why this proposal matters and the problem it addresses.
# Terminology
{:vspace}
OSMORA:
: See OSMORA.ORG
OSMORA Oath:
: A pledge taken by all members of OSMORA ensuring their commitment
to societal betterment, technological advancement as well as their
loyalty to the grater good, resisting the forbidden fruit dangled
by the suits.
|
