COMMUNITY

3. Working Groups and Interest Groups

What Are Working Groups

Working Groups (WGs) are collaborative organizations within the iFay community, organized by sub-project or technical domain. Each working group focuses on a specific area of the iFay ecosystem, responsible for specification development, code maintenance, and technical evolution in that area.

Current Working Groups

WG-FayID

Responsible for the identity system, corresponding to the independent FayID project. Scope includes:

  • FayID generation, allocation, and management mechanisms
  • Identifier encoding schemes and capacity planning
  • Identity migration and lifecycle management

WG-Ego

Responsible for the personalization model, corresponding to the independent Ego project. Scope includes:

  • Ego model training, deployment, and switching mechanisms
  • Host personality trait collection and alignment
  • Multi-version Ego management and personality switching

WG-Protocols

Responsible for the design and evolution of the iFay protocol family. Covers the following protocols:

  • Faying Protocol (secure pairing)
  • Telepathy Protocol (semantic communication between Fays)
  • ICP Interactive Dialogue Protocol (human UI-friendly)
  • CAP Control Authority Protocol (terminal takeover)
  • DTP Data Tunnel Protocol (bidirectional data transfer)
  • SSP Skill Sharing Protocol (service exposure)

WG-FayGer

Responsible for the runtime environment. Scope includes:

  • FayGer container design and implementation
  • Cross-platform and cross-device runtime support
  • FayManifest declarative assembly mechanism

WG-iFACTS

Responsible for the compliance test suite. Scope includes:

  • Writing and maintaining iFACTS test cases
  • Managing the four test levels from L1 to L4
  • Developing and enforcing iFay Ready certification standards

WG-Documentation

Responsible for documentation and translation. Scope includes:

  • Writing and maintaining specification documents and blueprint documents
  • Developer guides and tutorials
  • Coordinating multilingual translations

WG-Community

Responsible for community operations and governance. Scope includes:

  • Organizing and promoting community events
  • Maintaining and improving governance processes
  • Onboarding and supporting new contributors

Working Group Responsibilities

Each working group should fulfill the following responsibilities:

  • Maintain the code and specifications in their respective domains
  • Review related Pull Requests
  • Participate in SEP discussions involving their domain
  • Report progress to Core Maintainers regularly
  • Coordinate cross-domain collaboration with other working groups

How to Join a Working Group

The process for joining a working group is straightforward:

  1. Post a self-introduction in the corresponding working group's GitHub Discussion
  2. Describe your technical background and areas of interest
  3. Start participating in discussions and contributing

Working groups are open to all contributors — no special approval is required. We welcome developers of all backgrounds to join — whether you are an open-source project developer, application developer, or service provider developer, you can find a way to participate that suits you.

Working Group Lifecycle

Working groups are not permanent. As the iFay project evolves:

  • New working groups can be created as needed (for example, when a new sub-project or technical domain requires a dedicated collaborative organization)
  • Working groups that have completed their mission or are no longer active can be dissolved
  • The creation and dissolution of working groups is decided by Core Maintainers