User Tools

Site Tools


groups:sig-application

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
groups:sig-application [2018/11/19 20:35]
Tracy Kuhrt SIGs
groups:sig-application [2018/11/19 21:09] (current)
Tracy Kuhrt [After Approval of SIG]
Line 3: Line 3:
 ====== Preface ====== ====== Preface ======
  
-Sector Working Group gathers ​the community that works on a domain specific problem and aims to create an environment for open discussion, document co-creation and solution proposals. ​Technical Working Groups focus on technical aspects of blockchain and Hyperledger. TWG gathers community of various environments to work on global, technical solutions. SWG cuts through a vertical trying to address problems specific to that particular community. ​While Technical Working ​Groups are under the supervision of Technical Steering Committee, Sector Working Group is overlooked by Hyperledger Staff and the Governing Board. Anyone in the community should feel empowered to propose a new Sector Working ​Group as long as they can find at least 15 Interested initial contributors.+Special Interest Groups (SIGs) gather ​the community that works on a domain specific problem and aims to create an environment for open discussion, document co-creation and solution proposals. ​SIGs cuts through a vertical trying to address problems specific to that particular community. ​Special Interest ​Groups are overlooked by Hyperledger Staff and the Governing Board. Anyone in the community should feel empowered to propose a new Special Interest ​Group as long as they can find at least 15 Interested initial contributors.
  
 ====== Introduction ====== ====== Introduction ======
  
-This document outlines the process for establishing and running Hyperledger ​sector specific working ​groups. We begin with an application form for a new working group, to be reviewed by Hyperledger staff and distributed to the Hyperledger Governing Board for information. Then we define the standard process that all working groups ​are expected to follow. It ends with the steps necessary after a working group is approved.+This document outlines the process for establishing and running Hyperledger ​special interest ​groups. We begin with an application form for a new SIG, to be reviewed by Hyperledger staff and distributed to the Hyperledger Governing Board for information. Then we define the standard process that all SIGs are expected to follow. It ends with the steps necessary after a SIG is approved.
  
-====== ​Sector Working ​Group Application ======+====== ​Special Interest ​Group Application ======
  
-The working ​group will create a charter utilizing the following application. Items that are //​italicized//​ should be added by the person proposing the new working ​group. You can find an online version of this form at: +The special interest ​group will create a charter utilizing the following application. Items that are //​italicized//​ should be added by the person proposing the new special interest ​group. You can find an online version of this form at: 
 [[https://​goo.gl/​forms/​S1AqiGjCRXnT3SIw2| Google Forms Link]] [[https://​goo.gl/​forms/​S1AqiGjCRXnT3SIw2| Google Forms Link]]
  
-=== Sector Working ​Group Title ===+=== Special Interest ​Group Title ===
  
-//Please provide a title, generally of the form “Something Something ​Working Group”.//+//Please provide a title, generally of the form “Something Something ​SIG”.//
  
 === Introduction === === Introduction ===
  
-> //Please provide an introduction that addresses why the working group is required and what are the main goals and objectives of the group. //+> //Please provide an introduction that addresses why the SIG is required and what are the main goals and objectives of the group. //
  
 === Scope === === Scope ===
  
-> //Please provide the scope and audience of the working group. Also, include items that are not within scope of this working group. It’s ​as important to define the boundaries, to ensure a well-focused ​working group.//+> //Please provide the scope and audience of the SIG. Also, include items that are not within ​the scope of this SIG. It’s important to define the boundaries, to ensure a well-focused ​SIG.//
  
 === Work Products === === Work Products ===
Line 30: Line 30:
 > The anticipated initial work products will include (but is not limited to): > The anticipated initial work products will include (but is not limited to):
  
-> //Please list the work products that the group expects to initially focus on, such as white papers, use cases, case studies, or a face to face event. Ideally these are measurable work products that help the TSC assess whether the working group is making progress.//+> //Please list the work products that the group expects to initially focus on, such as white papers, use cases, case studies, or a face to face event. Ideallythese are measurable work products that help the Hyperledger Staff and Governing Board assess whether the SIG is making progress.//
  
 === Collaborators (other groups) === === Collaborators (other groups) ===
- +> //Please provide any specific groups or projects that this SIG will immediately collaborate with.//
-> This Sector Working Group will collaborate with other Hyperledger working groups, the TSC, Linux Foundation staff, and the project maintainers. +
->  +
-> //Please provide any specific ​working ​groups or projects that this working group will immediately collaborate with.//+
  
 === Interested Parties === === Interested Parties ===
  
-> The following individuals have already expressed an interest in joining this working group, and we hope they will become contributors over the first year:+> The following individuals have already expressed an interest in joining this SIG, and we hope they will become contributors over the first year:
  
 > //List of interested parties listed with their consent, including name, association,​ and optionally email addresses.//​ > //List of interested parties listed with their consent, including name, association,​ and optionally email addresses.//​
Line 46: Line 43:
 === Proposed Chair === === Proposed Chair ===
  
-> The following individual has volunteered to serve as the initial Chair for the working group:+> The following individual has volunteered to serve as the initial Chair of the SIG:
  
-> //Usually this is the person who has been most active in encouraging the development of the working group. The Chair will kick off the discussions and work products, as well as, manage the tone and cadence of conversations. Hyperledger Staff will appoint a chair along with the approval of the working group.//+> //Usually this is the person who has been most active in encouraging the development of the SIG. The Chair will kick off the discussions and work products, as well as, manage the tone and cadence of conversations. Hyperledger Staff will appoint a chair along with the approval of the SIG.//
  
 ====== Process of the Group ====== ====== Process of the Group ======
Line 56: Line 53:
 ===== Chair Term ===== ===== Chair Term =====
  
-The Chair of the working group will serve for as long as they still want to lead the working group. At which point, they will inform Hyperledger Point of Contactof ​their desire to step down from the position. ​Hypereldger ​Point of Contact will then appoint another chair with input from the community and existing chair.+The Chair of the SIG will serve for as long as they still want to lead the SIG. At which point, they will inform Hyperledger Point of Contact of their desire to step down from the position. ​Hyperledger ​Point of Contact will then appoint another chair with input from the community and existing chair.  NOTE: in most cases, we strongly suggest only a single chair. Hyperledger does not encourage co-chairing.
  
 ===== Transparency ===== ===== Transparency =====
Line 64: Line 61:
   * Wiki   * Wiki
   * Mailing List   * Mailing List
-  * Rocket ​Chat +  * Chat channel on [[https://​chat.hyperledger.org|Hyperledger'​s Chat]]
-  * Optional Github Repository+
   * Meeting Recordings will be stored in the [[https://​drive.google.com/​open?​id=0B_NJV6eJXAA1WFZDZXNHYjMyV1U|Hyperledger Community Google Drive]]   * Meeting Recordings will be stored in the [[https://​drive.google.com/​open?​id=0B_NJV6eJXAA1WFZDZXNHYjMyV1U|Hyperledger Community Google Drive]]
  
 ===== Amendments ===== ===== Amendments =====
  
-Changes to the charter may be proposed by active group members and, if it obtains rough consensus as determined by the Chair, can be brought forward to Hyperledger Point of Contact+Changes to the charter may be proposed by active group members and, if it obtains ​rough consensus as determined by the Chair, can be brought forward to Hyperledger Point of Contact
  
 +===== Quarterly Reports =====
 +The requirement to report on a quarterly basis to the Hyperledger POC is described [[groups:​SIGs:​sig-updates|here]]. Every quarter, SIGs must submit a report to Hyperledger Point of Contact assigned to them. The report must be submitted according to the schedule outlined for the SIG. The report of SIG must contain information about what was accomplished in the previous quarter and the plans for the next quarter. After posting the report on the SIG's wiki, the chair schedules a call with POC to do a readout. The Chair is responsible for sending out an email to TSC informing the TSC where the update can be found. Governing Board will be updated by Hyperledger Point of Contact on the state of health of all SIGs.
 ===== Disbanding ===== ===== Disbanding =====
  
-Should the scope reach completion or conversely the traffic on the various conversation forums and the teleconference activity wither to very low levels, then the Chair of the WG may ask the Hyperledger Staff to disband the WG.+Should the scope reach completion or conversely the traffic on the various conversation forums and the teleconference activity wither to very low levels, then the Chair of the SIG may ask the Hyperledger Staff to disband the SIG.
  
 ====== Running the Working Group ====== ====== Running the Working Group ======
Line 83: Line 81:
  
   * Sending agendas for meetings to make meetings more productive   * Sending agendas for meetings to make meetings more productive
-  * Ensuring that minutes are taken, including capturing list of participants. This does not mean that they will be responsible for taking the minutes, but rather that someone is taking the minutes+  * Ensuring that minutes are taken, including capturing ​the list of participants. This does not mean that they will be responsible for taking the minutes, but rather that someone is taking the minutes
   * Leading the meeting   * Leading the meeting
   * Sending out cancellation notices prior to the meeting   * Sending out cancellation notices prior to the meeting
-  * Ensuring that [[https://​wiki.hyperledger.org/​groups/​tsc/​wg-updates|working group updates]] are uploaded to the groups ​wiki and sent on quarterly basis to Hyperledger Point of Contact, followed by a call to discuss the progress. ​A summary ​is sent out to the TSC.+  * Ensuring that SIG updates are uploaded to the SIG'​s ​wiki and sent on quarterly basis to Hyperledger Point of Contact, followed by a call to discuss the progress. ​An email to the update ​is sent out to the TSC mailing list.
   * Facilitating the group and helping ensure that the goals and objectives are set   * Facilitating the group and helping ensure that the goals and objectives are set
-  * Enforcing the Working Group’s adherence to the [[https://​wiki.hyperledger.org/​community/​hyperledger-project-code-of-conduct|Hyperledger Code of Conduct]]+  * Enforcing the SIG's adherence to the [[https://​wiki.hyperledger.org/​community/​hyperledger-project-code-of-conduct|Hyperledger Code of Conduct]]
  
 ===== Minutes ===== ===== Minutes =====
  
-Minutes for each meeting should be noted and accessible from the working group's wiki page on wiki.hyperledger.org. Members of the working group will need to decide who will take notes.+Minutes for each meeting should be noted and accessible from the SIG's wiki page on wiki.hyperledger.org. Members of the SIG will need to decide who will take notes.
  
 ===== Meeting Cadence ===== ===== Meeting Cadence =====
  
-Working groups ​typically meet on a bi-weekly basis. However, each working group chair should determine whether they will meet on a weekly, bi-weekly, or monthly basis.+SIGs typically meet on a bi-weekly basis. However, each SIG'​s ​chair should determine whether they will meet on a weekly, bi-weekly, or monthly basis.
  
 ===== Agendas ===== ===== Agendas =====
  
-In advance of every meeting, the Chair should send out an agenda to both the Rocket.Chat and Mailing List to ensure that attendees know what will be discussed.+In advance of every meeting, the Chair should send out an agenda to both the SIG'​s ​Chat Channel ​and Mailing List to ensure that attendees know what will be discussed.
  
 ===== Cancelling a Meeting ===== ===== Cancelling a Meeting =====
  
-Meetings are placed on the [[https://​calendar.google.com/​calendar/​embed?​src=linuxfoundation.org_nf9u64g9k9rvd9f8vp4vur23b0%40group.calendar.google.com&​ctz=UTC|Hyperledger Community calendar]]. To ensure that the meeting can be removed, please send an email in advance of the meeting to [[mailto:​zoom@hyperledger.org|zoom@hyperledger.org]]. In addition, please notify the mailing list and Rocket.Chat.+Meetings are placed on the [[https://​calendar.google.com/​calendar/​embed?​src=linuxfoundation.org_nf9u64g9k9rvd9f8vp4vur23b0%40group.calendar.google.com&​ctz=UTC|Hyperledger Community calendar]]. To ensure that the meeting can be removed, please send an email in advance of the meeting to [[mailto:​zoom@hyperledger.org|zoom@hyperledger.org]]. In addition, please notify the SIG'​s ​mailing list and chat channel.
  
-====== After Approval of Working Group ======+====== After Approval of SIG ======
  
-When a new working group gets approved, Hyperledger staff will ensure the following checklist is completed:+When a new SIG gets approved, Hyperledger staff will ensure the following checklist is completed:
  
-  * A staff member is identified as the Point of Contact for Sector Working Group. This staff lead will be the main point of contact for the WG chair and oversee the specific ​Working Group+  * A staff member is identified as the Point of Contact for SIG. This staff lead will be the main point of contact for the SIG'​s ​chair and will oversee the specific ​SIG
-  * A Working Group Charter is created on the Hyperledger wiki based on the application,​ adding two lines ”Approved by the Hyperledger Governing Board on <​date>​” and “Implementing the standard ​working group process defined <​here>​”,​ linking to the right page on the wiki. +  * A SIG Charter is created on the Hyperledger wiki based on the application,​ adding two lines ”Approved by the Hyperledger Governing Board on <​date>​” and “Implementing the standard ​SIG process defined <​here>​”,​ linking to the right page on the wiki. 
-  * Set up **real-time chat** channel for the working group. Channel should be named [[https://​chat.hyperledger.org/​channel/​%7Bworking-group-name%7D-wg|#{working-group-name}-wg]]+  * Set up **real-time chat** channel for the SIG. Channel should be named ''​#{SIG-name}-wg''​
-  * Set up the **mailing lists** for the working group. Use [[https://​docs.google.com/​forms/​d/​e/​1FAIpQLSfd-MN4H6tQK_3cNWLh6Y5WUO4Pl_uU6lmXyuMF89AGrcyp6w/​viewform|mailing list request form]] to create hyperledger-{working-group-name}-wg mailing list for this project+  * Set up the **mailing lists** for the SIG
-  * Set up a **wiki** page for the working group. Create a page at [[https://wiki.hyperledger.org/​groups/​%7Bworking-group-name%7D|https:​%%//​%%wiki.hyperledger.org/​groups/​{working-group-name}]]. The initial sections on the Wiki should include: Charter, Antitrust Policy Notification,​ Meeting Details, Communication Channels, Community Folder. +  * Set up a **wiki** page for the SIG. Create a page at ''​https://​wiki.hyperledger.org/​groups/​{SIG-name}''​. The initial sections on the Wiki should include: Charter, Antitrust Policy Notification,​ Meeting Details, Communication Channels, Community Folder. 
-  * Set up a **community folder** within the [[https://​drive.google.com/​open?​id=0B_NJV6eJXAA1WFZDZXNHYjMyV1U|Hyperledger Community]] folder to store meeting recordings and other documents. Give permissions to the working group chair to edit. +  * Set up a **community folder** within the [[https://​drive.google.com/​open?​id=0B_NJV6eJXAA1WFZDZXNHYjMyV1U|Hyperledger Community]] folder to store meeting recordings and other documents. Give permissions to the SIG'​s ​chair to edit. 
-  * Set up a **Zoom meeting id** for hosting ​the working group meetings. This meeting ​should ​ensure that all meetings will be recorded to the cloud. +  * Set up a schedule ​for the SIG's quarterly updates. This should be captured on the calendar ​for the SIG at https://lists.hyperledger.org. 
-  * Set up the **quarterly working group reports** ​for this working group. Add the working group to the quarterly working group [[https://wiki.hyperledger.org/​groups/​tsc/​wg-update-schedule|schedule]] and [[https://​wiki.hyperledger.org/​groups/​tsc/​wg-updates|working group updates]] page+  * Send [[https://​docs.google.com/​document/​d/​1HNGgxAagqjC_aa2f9c1jjgjlaDh1A-KSXNCZVYoKf1k/​edit|Welcome Email Template]] 
-  * Send [[https://​docs.google.com/​document/​d/​1fHg4_mE15NXFtk2KFpWaWoMbQ5t64CsWfbju233mR94/​edit|Welcome Email Template]] +  * Work with the SIG's chair to ensure that the **community calendar** is updated ([[https://​calendar.google.com/​calendar/​embed?​src=linuxfoundation.org_nf9u64g9k9rvd9f8vp4vur23b0%40group.calendar.google.com&​ctz=UTC|Hyperledger Community calendar]]) to include the date/time of the meeting. IMPORTANT: Since a single Zoom account allows only one meeting can occur at the same time, ensure that the meeting day/time does not conflict with an existing community meeting. 
-  * Work with the working group lead to ensure that the **community calendar** is updated ([[https://​calendar.google.com/​calendar/​embed?​src=linuxfoundation.org_nf9u64g9k9rvd9f8vp4vur23b0%40group.calendar.google.com&​ctz=UTC|Hyperledger Community calendar]]) to include the date/time of the meeting. IMPORTANT: Since a single Zoom account allows ​multiple IDs, but only one meeting can occur at the same time, ensure that the meeting day/time does not conflict with an existing community meeting. +  * Send out calendar invite to the mailing list.
-  * Send out calendar invite to the mailing list.+
groups/sig-application.1542659751.txt.gz · Last modified: 2018/11/19 20:35 by Tracy Kuhrt