User Tools

Site Tools


This is an old revision of the document!

Application Process for creating a Sector Working Group in Hyperledger


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.


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.

Sector Working 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: Google Forms Link

Sector Working Group Title

Please provide a title, generally of the form “Something Something Working Group”.


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

Work Products

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.

Collaborators (other groups)

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

The following individuals have already expressed an interest in joining this working group, 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.

Proposed Chair

The following individual has volunteered to serve as the initial Chair for the working group:

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.

Process of the Group

Participation is open to everyone in the community. Meetings will be held weekly, bi-weekly, or monthly (as determined by the Chair) via teleconference. When needed a task force can be created and have separate working sessions to discuss specific work items. The Group is under the supervision of Hyperledger Ecosystem Team and gets an assigned staff member as a Point of Contact for all matters that require governance or approval.

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.


Meeting details, meeting notes, and documentation shall be made publicly available. The following proposed items will be created:


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


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.

Running the Working Group

Responsibilities of a Chair

The chair is responsible for the following items:

  • 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
  • Leading the meeting
  • Sending out cancellation notices prior to the meeting
  • Ensuring that 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.
  • Facilitating the group and helping ensure that the goals and objectives are set
  • Enforcing the Working Group’s adherence to the Hyperledger Code of Conduct


Minutes for each meeting should be noted and accessible from the working group's wiki page on Members of the working group will need to decide who will take notes.

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.


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.

Cancelling a Meeting

Meetings are placed on the Hyperledger Community calendar. To ensure that the meeting can be removed, please send an email in advance of the meeting to In addition, please notify the mailing list and Rocket.Chat.

After Approval of Working Group

When a new working group 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 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.
  • Set up real-time chat channel for the working group. Channel should be named #{working-group-name}-wg.
  • Set up the mailing lists for the working group. Use mailing list request form to create hyperledger-{working-group-name}-wg mailing list for this project.
  • Set up a wiki page for the working group. Create a page at https:%%//{working-group-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 Hyperledger Community folder to store meeting recordings and other documents. Give permissions to the working group 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 the quarterly working group reports for this working group. Add the working group to the quarterly working group schedule and working group updates page.
  • Work with the working group lead to ensure that the community calendar is updated (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.
groups/sig-application.1541165503.txt.gz · Last modified: 2018/11/02 13:31 by Marta Piekarska