From 0f6a7699a1df53d5719b5b59f2d53ebe2fa273d9 Mon Sep 17 00:00:00 2001 From: Toshaan Bharvani Date: Tue, 5 Jul 2022 16:19:24 +0200 Subject: [PATCH] updates after collaborative charter work Signed-off-by: Toshaan Bharvani --- Makefile | 0 charter.tex | 18 ++++---- content.tex | 119 ++++++++++++++++++------------------------------- glossaries.tex | 4 +- 4 files changed, 55 insertions(+), 86 deletions(-) mode change 100755 => 100644 Makefile mode change 100755 => 100644 charter.tex diff --git a/Makefile b/Makefile old mode 100755 new mode 100644 diff --git a/charter.tex b/charter.tex old mode 100755 new mode 100644 index 7c2a172..526da09 --- a/charter.tex +++ b/charter.tex @@ -1,6 +1,6 @@ \documentclass[a4paper,12pt]{report} -% packeges +% packages \usepackage[a4paper]{geometry} \usepackage{fancyhdr} \usepackage{lastpage} @@ -47,11 +47,11 @@ pdfmenubar=false, %bookmarks=false, pdfproducer={OPF Template Generator}, - pdfcreator={OPF POWER ISA TWG}, + pdfcreator={OPF POWER HUB SIG}, pdfauthor={Toshaan Bharvani }, - pdftitle={OpenPOWER Foundation ISA TWG Charter}, - pdfsubject={OpenPOWER Foundation ISA TWG Charter}, - pdfkeywords={OPF,OpenPOWER,POWER ISA,ISA,charter} + pdftitle={OpenPOWER Foundation HUB SIG Charter}, + pdfsubject={OpenPOWER Foundation HUB SIG Charter}, + pdfkeywords={OPF,OpenPOWER,POWER HUB,HUB,charter} } % page layout @@ -75,7 +75,7 @@ \input{glossaries.tex} -% real begining +% real beginning \begin{document} \pagenumbering{arabic} @@ -96,13 +96,13 @@ \includegraphics[width=4cm]{opf-logo.png} } \fancyhead[R]{ - OpenPOWER Foundation Workgroup Charter + OpenPOWER Foundation Work Group Charter } \fancyfoot{} \fancyfoot[L]{ \begin{tiny} - OPF Workgroup Charter + OPF Work Group Charter \end{tiny} } \fancyfoot[C]{ @@ -122,4 +122,4 @@ \printglossary[type=\acronymtype,title=List of Acronyms] -\end{document} +\end{document} \ No newline at end of file diff --git a/content.tex b/content.tex index e6dce0b..dcce327 100644 --- a/content.tex +++ b/content.tex @@ -1,46 +1,32 @@ -%%% +\section{\acrfull{WG} name} -\section{Workgroup name} - -HUB \acrfull{STIG} +HUB \acrfull{SIG} \section{Definitions} -Reference the OpenPOWER Foundation \acrshort{IPR} Policy and OpenPOWER WorkGroup Process for additional term definitions. +Reference the OpenPOWER Foundation \acrfull{IPR} Policy and OpenPOWER Work Group Process for additional term definitions. \begin{enumerate} \item -``Provider" is an Eligible participant of the workgroup that has been elected by Full Majority Vote to provide OpenPOWER resources -to the Open Source community for the purpose of enabling, promoting, converting, porting, and testing open source on OpenPOWER. -\item -``" +``Provider" is a WG Member that has been elected by Full Majority Vote to provide resources to the open source community, via the OpenPOWER HUB, for the purpose of enabling, promoting, developing, converting, porting, testing and maintaining open source on POWER. \end{enumerate} \section{Description} -The HUB \acrshort{STIG} is a workgroup whose purpose is to enable the process of porting to OpenPOWER, -this \acrshort{STIG} will enable the porting, conversion, and testing of open source on OpenPOWER. -This \acrshort{STIG} will provide resources for these efforts by levering Providers to enable open source to gain access to -OpenPOWER resources for the purpose of porting, converting, and maintaining open source resources to be enabled on OpenPOWER.\par +The HUB \acrshort{SIG} is a Work Group whose purpose is to enable the process of porting to and developing open source on POWER. +This \acrshort{SIG} will collaborate with Providers to enable open source developers to gain access to POWER resources and technology for the purpose of enabling, and promoting, the porting, converting, testing, maintaining and developing of open source on POWER.\par -The HUB \acrshort{STIG} will create processes, documentation, code and how-to guides to assist in OpenPOWER enablement. -In addition to these documents, the HUB \acrshort{STIG} will provide resources that enable the porting, conversion and maintance -throught Providers that have resources available to assist open source in this effort.\par +The HUB \acrshort{SIG} will create processes, documentation, code and how-to guides to assist in open source on POWER enablement. In addition to these documents, the HUB \acrshort{SIG} will provide machine resources that enable the developing, porting, conversion, testing and maintenance through Providers that will have resources available to assist open source developers in this effort.\par -The purpose of the HUB is to be a central place where a public open source project can reach out to for help. -It is up to the HUB to assist these projects in their endavour to OpenPOWER.\par +The purpose of the HUB is to be a central place where public open source projects can reach out to for access to POWER resources and technology. It is up to the HUB to assist these projects in their open source on POWER enablement.\par \section{Scope} -The scope of the HUB \acrshort{STIG} is the creation of a central place for OpenPOWER porting. -The \acrshort{STIG} will do this by providing documentation, code, and resources to enable the porting, converting, and maintaining -of open source on OpenPOWER.\par +The scope of the HUB \acrshort{SIG} is the creation of a central place for open source on POWER development and porting. The \acrshort{SIG} will do this by providing documentation, code, and machine resources to enable the developing, porting, converting, testing and maintaining of open source on POWER.\par -The HUB \acrshort{STIG} will create documentation on how to enable open source on OpenPOWER. -It will do this in a way to enable all features, and options available on OpenPOWER. -This documentataion will be made publically available and be distributed within several open source communities.\par +The HUB \acrshort{SIG} will create documentation on how to enable open source on POWER. It will do this in a way to enable all features, and options available on POWER. This documentation will be made publicly available and be distributed within several open source communities.\par -In addition to the documentation, the HUB \acrshort{STIG} will work with Providers to make resources, such as but not limited to +In addition to the documentation, the HUB \acrshort{SIG} will work with Providers to make available resources, such as but not limited to: \begin{itemize} \item Cloud Server Hardware @@ -55,50 +41,49 @@ Software distributions \end{itemize} \par -In addition the HUB \acrshort{STIG} will be a workgroup that evangalises the adoption of OpenPOWER -through technical documentation and resource availability.\par +In addition the HUB \acrshort{SIG} will be a Work Group that evangelises the adoption of POWER +through technical documentation and resource availability via the OpenPOWER HUB.\par \section{Similar Activities} \begin{itemize} \item -Accelerator Workgroup : may work with to define the requirements for open tooling needed to complete the implementation of OpenPOWER +Accelerator Work Group : defines Acceleration requirements for POWER \item -Memory Workgroup : defines the requirements for OpenPOWER Memory adoption, such as OMI +Memory Work Group : defines Memory requirements for POWER \item -HW Architecture Workgroup : maintains the hardware architecture specifications that may be needed for new development +HW Architecture Work Group : maintains the hardware architecture specifications that may be needed for new development on POWER \item -System Software Workgroup : owns definition, documentation, and maintenance of the firmware, Linux and other software on OpenPOWER +System Software Work Group : owns definition, documentation, and maintenance of the firmware, Linux and other software on POWER \item -Development Platform Workgroup : defines the reference architecture of future OpenPower systems \end{itemize} \section{Users} -Any open source project that plans to run on OpenPOWER. +Any open source project that plans to run on POWER. \section{Work Product} \begin{itemize} \item -Documentation for adoption of, porting to, converting to OpenPOWER +Documentation for development on, adoption of, porting to, converting to POWER \item -Code, such as patches for OpenPOWER, to be pushed to the upstream project +Code, such as patches for POWER, to be pushed to upstream project(s) \item -Ensure maintaining open source enablement of OpenPOWER +Ensure testing and/or maintaining of open source on POWER \end{itemize} \section{Projects} \begin{itemize} \item -Build documentation on adoption of, porting to, converting to OpenPOWER +Build documentation on development on, adoption of, porting to, converting to POWER \item -Assist in code patching of open source to OpenPOWER +Assist in code patching of open source to POWER \item -Assist in maintenance of open source on OpenPOWER +Assist in testing and/or maintenance of open source on POWER \item -Provide resources for open source to OpenPOWER +Provide machine resources for open source development on POWER \end{itemize} \section{Participation} @@ -107,9 +92,8 @@ Public\par Participation and voting right requirements are as outlined per the OpenPOWER Work Group Process.\par -A minimum of two Eligeble Participant will be required to be a Providers. -Providerss will have the responsibility to make resources available for open source to consume for the purpose of -porting, adopting, maintaining, or enhancing OpenPOWER.\par +A minimum of two WG Members will be required to be Providers. +Providers will have the responsibility to make resources available for open source to consume for the purpose of porting, converting, testing, maintaining, adopting or developing on POWER.\par \section{Work Group Convener} @@ -119,7 +103,7 @@ Lance Albertson (OSU) - Toshaan Bharvani (VanTosh) Lance will convene the first meeting.\par -The first meeting will be at 18:00 CET on the second Thursday after the TSC and BoD approve the formation of the SIG. +The first meeting will be at 18:00 CET on the second Thursday after the TSC and BoD approve the formation of the \acrshort{SIG}. Subsequent meetings will be held bi-weekly alternating between 18:00 CET Thursday and 00:00 CET Tuesday to accommodate participants in all time zones. \section{Participants} @@ -129,25 +113,25 @@ Subsequent meetings will be held bi-weekly alternating between 18:00 CET Thursda Oregon State University \begin{itemize} \item - Lance Albertson () + Lance Albertson (lance@osuosl.org) \end{itemize} \item -Raptor Computing Systems +VanTosh \begin{itemize} \item - Timothy Pearson (tpearson@raptorengineering.com) + Toshaan Bharvani (toshaan@vantosh.com) \end{itemize} \item -VanTosh +Raptor Computing Systems \begin{itemize} \item - Toshaan Bharvani (toshaan@vantosh.com) + Timothy Pearson (tpearson@raptorengineering.com) \end{itemize} \item IBM \begin{itemize} \item - Paul Lecocq (lecocq@us.ibm.com) + Bob Szabo (rszabo@us.ibm.com) \end{itemize} \item Yadro @@ -159,7 +143,7 @@ Yadro \section{Balloting Approval Requirements} -Standard WG Process applies with the following specific requirements with respect to Providers : +Standard OpenPOWER Work Group Process applies with the following specific requirements with respect to Providers: \begin{itemize} \item Election of Providers will be by Full Majority Vote. @@ -174,7 +158,7 @@ Member organization support will be confirmed as part of the approval process. \section{Anticipated Contributions} -none +None \section{IPR, Confidentiality \& Licensing} @@ -192,17 +176,11 @@ Code Mode Apache License, v2.0\par -All Code contributed to the WG by a WG Member or WG Party shall be licensed to OpenPOWER under Apache License, V2.0 -with the condition that the patent license granted in Section 3 of the License, as applied to the ``Work", hereby -includes implementations of the Work in physical form.\par - -Code contributed to the WG by a WG member or WG party may be licensed to OpenPOWER under a future open hardware license with -WG, TSC, and Board approval.\par +All Code contributed to the WG by a WG Member or WG Party shall be licensed to OpenPOWER under Apache License, V2.0.\par All contributions to the WG's git repository must include a developer certificate of originality. Non-Eligible person contributions to the git repository are bound to a Guest Participation Agreement. -The Guest Participation Agreement for this WG is agreement to the terms of the OS license as defined in the OS Licensing Mode and -documented in the license file within the WG's git repository.\par +The Guest Participation Agreement for this WG is agreement to the terms of the OS license as defined in the OS Licensing Mode and documented in the license file within the WG's git repository.\par The Guest Participation Agreement is agreed to automatically upon any contribution to the WG's git repository. Any contributions made outside the WG's git repository by a non-Eligible person must include a signed @@ -211,22 +189,11 @@ Alternatively this WG can provide a Guest Participation Agreement to be signed p The executed Contribution / Feedback License or Guest Participation Agreement must be sent to hub@openpower.foundation.\par -As a default position, all Code that is, or is made part of, an OpenPOWER Deliverable shall be licensed out by OpenPOWER under one of the following -licenses and shall at least be provided in source code form. -The selected license will include or be accompanied by a clarification that any necessary license rights for the POWER \acrshort{ISA} comes from -the POWER \acrshort{ISA} license and is not granted under the selected license for the OpenPOWER Deliverable. -\begin{itemize} -\item -Apache License, V2.0 with the condition that the patent license granted in Section 3 of the License, as applied to the ``Work", -hereby includes implementations of the Work in physical form. -\item -a future open hardware license with WG, TSC, and Board approval. -\end{itemize} +As a default position, all Code that is, or is made part of, an OpenPOWER Deliverable shall be licensed out by OpenPOWER under Apache License, V2.0.\par -\subsection{Open Source Communities} +\section{Open Source Communities} -This WG may accept Code from the following OS Communities under their respective licenses. +No known OS Communities to accept and/or contribute Code from/to at the time of chartering. This WG may accept and/or contribute Code from/to OS Communities with approval by the WG, TSC, and Board at any time and update the Charter accordingly. +Any code accepted from or contributed to approved OS Communities must be under a Permissive License such as Apache License, v2.0, 2 or 3 clause BSD, MIT, ISC, or other OS license approved by the WG, TSC, and Board.\par -This WG may accept or contribute Code from/to additional OS Communities with approval by the WG, TSC, and Board. -Any code accepted from or contributed to approved OS Communities must be under a Permissive License such as -Apache License, v2.0, 2 or 3 clause BSD, MIT, ISC, or other OS license approved by the WG, TSC, and Board. +This WG may accept OS Code under a Permissive License such as Apache License, v2.0, 2 or 3 clause BSD, MIT, ISC, or other OS license approved by the WG, TSC and Board. \ No newline at end of file diff --git a/glossaries.tex b/glossaries.tex index e3e748a..02ce045 100644 --- a/glossaries.tex +++ b/glossaries.tex @@ -4,9 +4,11 @@ %%% Common Acronyms \newacronym{IPR}{IPR}{Intellectual Property Rights} -\newacronym{SIG}{SIG}{Special Integration Work Group} +\newacronym{SIG}{SIG}{Special Integration Group} \newacronym{TWG}{TWG}{Technical Work Group} \newacronym{STIG}{STIG}{Special Technical Integration Group} \newacronym{ISA}{ISA}{Instruction Set Architecture} +\newacronym{WG}{WG}{Work Group} +\newacronym{OS}{OS}{Open Source} %%% Specific Acronyms