Upload draft of specification process for review

process/OpenHW-Specification-Process.md

@@ -0,0 +1,152 @@
+# OpenHW Process Document: Specification Process, States and Format
+
+## Revision History
+
+This document desbribes OpenHW's specification process and format.
+It was adopted by consensus in the TWG meeting of July 2023.
+
+The V1.0 of this document reflects the agreements made at that meeting and adds additional details. 
+
+| Date        | Version | Notes                                                 |
+| :---------- | :------ | :---------------------------------------------------- |
+| 22 Jan 2024 | 1.0     | Formal draft reflecting July 2023 google docs			|
+
+## Specification Process
+
+### Overview
+
+OpenHW uses a lightweight specification development process to produce specification documents that are developed and frozen in a designated Task Group, then ratified and released by TWG.
+
+### Requirements for OpenHW Specification Process
+
+
+#### Basics
+
+| Number 	| Issue 									| Comment                                               							|
+| :---		| :------ 									| :-------------------------------------------------------------------------------- |
+| 1 		| Nature of the specification				| A collective derivative work from the individual member contributions, together with staff contributions	|																			
+| 2 		| Editors of the specification				| OpenHW via its members and staff													|
+| 3 		| Contributions by non-members				| For further study				|
+| 4 		| Eclipse Specification Process				| Not used				|
+
+#### Contributions into the Specification
+
+| Number 	| Issue 									| Comment                                               							|
+| :---		| :------ 									| :-------------------------------------------------------------------------------- |
+| 1    		| License options for contributions: 		|																					|
+| 1.1		| Apache 2.0								| As per OpenHW Member Agreement 													|
+| 1.2		| Solderpad 2.1								| As per OpenHW Member Agreement 													|
+| 1.3		| Commons Attribution Share Alike 4.0 International license | Agreed by OpenHW CEO April 2023									| 
+| 2			| Patent Grant included in contribution license:  | 																				|
+| 2.1		| Apache 2.0								| Yes 																				|
+| 2.2		| Solderpad 2.1								| Yes																				|
+| 2.3		| Commons Attribution Share Alike 4.0 International license | No																| 
+| 3			| Essential patents must be disclosed by contributor | No 																		| 
+| 4			| Contribution Process 						| EDP/ Committers merging pull requests	/ Contributors sign ECA or MCCA				| 			 
+
+
+#### Publication of the Specification
+
+| Number 	| Issue 									| Comment                                               							|
+| :---		| :------ 									| :-------------------------------------------------------------------------------- |
+| 1 		| Specification published by				| OpenHW on Github and/or ReadtheDocs and/or website								|
+| 2 		| Copyright holder on specification			| OpenHW on behalf of contributors (member), who hold the copyright jointly. 		|
+| 3			| License used for publication 				| Same license as used for contributions 											|
+| 4			| Copyright Grant included in specification publication 	 | As per publication license:										}	
+| 5.1		| Apache 2.0								| Yes 																				|
+| 5.2		| Solderpad 2.1								| Yes 																				|
+| 5.3		| Commons Attribution Share Alike 4.0 International license | Yes																|								
+| 6			| Patent Grant included in specification publication 	|	As per publication license											|
+| 6.1		| Apache 2.0								| Yes 																				|
+| 6.2		| Solderpad 2.1								| Yes 																				|
+| 6.3		| Commons Attribution Share Alike 4.0 International license | No 																|								
+| 7			| Essential patents disclosed by OpenHW		| No																				|
+| 8 		| License text included within the specification text |  No - referall only 													|
+| 0			| "No-warranty" or disclaimer				| Required																|
+
+
+### Specification States
+
+The ratification or completion state ais meant to be written in each OpenHW specification so that a reader will be aware of the state of completion of the Specification
+These are the OpenHW Specification States:
+
+- “OpenHW Specification - In Development"
+- "OpenHW Specification - In Review"
+- "OpenHW Specification - Released"
+
+#### "OpenHW Specification - In Development"
+
+When the specification is initiated, all drafts will be labelled as “OpenHW Specification - In Development"
+
+Revision numbers should be of the form 0.Y.Z
+
+
+#### "OpenHW Specification - In Review"
+
+When the specification is frozen for technical review, all drafts will be labelled as "OpenHW Specification - In Review"
+
+Revision numbers should be of the form 0.Y.Z
+
+#### "OpenHW Specification - Released"
+
+When the specification is published, the publication copy will be labelled as "OpenHW Specification - Released"
+Revision numbers should be of the form X.Y.Z, starting with 1.0.0 as the initially released version.
+
+#### "OpenHW Specification Revision"
+
+Process for labelling and numbering released specifications in revision to be decided.
+
+
+## Specification Format
+
+The following sections must be included in the OpenHW Specification
+
+### Title
+
+The Title should be of the form "OpenHW Specifciation: Title"
+
+### Revision History
+
+Prior to release a table of draft revisions should be included, which can included description of content in each draft
+
+Upon release and subsequently, the Revision History should list only released specification versions, starting with 1.0.0.
+The table should include Revision, Date, and Description. The Description should include a high level description of the content.
+
+### Specification States
+
+The specification state must be listed, e.g. 
+
+'The state of this specification is "OpenHW Specification - Released"'
+
+
+### License
+
+The Publication License is listed, together with a URL link to the source of the license. 
+
+
+The following is an example of an appropriate license statement:
+
+"
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+### No-warranty
+The following no-warranty text is included:
+
+"Unless required by applicable law or agreed to in writing, this Specification and any accompanying software or hardware distributed under the License are distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License."
+
+### Copyright
+The following opyright text is included:
+
+"Copyright ©  YEAR OF PUBLICATION OpenHW Group. You may use, copy, modify, and distribute this work under the terms of the License, subject to the conditions specified in the License."
+
+### Footer
+
+In cases where the specification is rendered in PDF format, a footer should be included on each page, including OpenHW “Specification Title” and "Copyright © YEAR OF PUBLICATION OpenHW Group"		
+
+
+
+
+
+