\section{\acrfull{WG} name}

HUB \acrfull{SIG}

\section{Definitions}

Reference the OpenPOWER Foundation \acrfull{IPR} Policy and OpenPOWER Work Group Process for additional term definitions.

\begin{enumerate}
\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{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{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 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{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{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{SIG} will work with Providers to make available resources, such as but not limited to:
\begin{itemize}
\item
Cloud Server Hardware
\item
FPGA based Hardware
\item
GPU based Hardware
\item
Specialized hardware
\item
Software distributions
\end{itemize}
\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 Work Group : defines Acceleration requirements for POWER
\item
Memory Work Group : defines Memory requirements for POWER
\item
HW Architecture Work Group : maintains the hardware architecture specifications that may be needed for new development on POWER
\item
System Software Work Group : owns definition, documentation, and maintenance of the firmware, Linux and other software on POWER
\item
\end{itemize}

\section{Users}

Any open source project that plans to run on POWER.

\section{Work Product}

\begin{itemize}
\item
Documentation for development on, adoption of, porting to, converting to POWER
\item
Code, such as patches for POWER, to be pushed to upstream project(s)
\item
Ensure testing and/or maintaining of open source on POWER
\end{itemize}

\section{Projects}

\begin{itemize}
\item
Build documentation on development on, adoption of, porting to, converting to POWER
\item
Assist in code patching of open source to POWER
\item
Assist in testing and/or maintenance of open source on POWER
\item
Provide machine resources for open source development on POWER
\end{itemize}

\section{Participation}

Public\par

Participation and voting right requirements are as outlined per the OpenPOWER Work Group Process.\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}

Lance Albertson (OSU) - Toshaan Bharvani (VanTosh)

\section{Meeting Plan}

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 \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}

\begin{itemize}
\item
Oregon State University
	\begin{itemize}
	\item
	Lance Albertson (lance@osuosl.org)
	\end{itemize}
\item
VanTosh
	\begin{itemize}
	\item
	Toshaan Bharvani (toshaan@vantosh.com)
	\end{itemize}
\item
Raptor Computing Systems
	\begin{itemize}
	\item
	Timothy Pearson (tpearson@raptorengineering.com)
	\end{itemize}
\item
IBM
	\begin{itemize}
	\item
	Bob Szabo (rszabo@us.ibm.com)
	\end{itemize}
\item
Yadro
	\begin{itemize}
	\item
	Alexey Stepanov (a.stepanov@yadro.com)
	\end{itemize}
\end{itemize}

\section{Balloting Approval Requirements}

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.
A Provider can be removed from their position as Provider by Full Majority Vote as well.
\item
The initial Providers will be voted in the first meeting.
\end{itemize}

\section{Member Organization Support}

Member organization support will be confirmed as part of the approval process.

\section{Anticipated Contributions}

None

\section{IPR, Confidentiality \& Licensing}

The following sections may not be modified after chartering. Changes require closing and submitting a new charter.

\subsection{Confidentiality Mode}

Non-confidential

\subsection{IPR Policy}

Code Mode

\subsection{Open Source Licensing 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.\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 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
Contribution / Feedback License as defined in Section 7.1 and Appendix A of the OpenPOWER IPR Policy.
Alternatively this WG can provide a Guest Participation Agreement to be signed per Section 7.2.\par

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 Apache License, V2.0.\par

\section{Open Source Communities}

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 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.