# 🕉️ Homepage

**URL:** <https://forum.webuddhist.com/t/homepage/348>\
**Category:** 👋 Growth WG\
**Created:** [July 11, 2025, 6:56am UTC](https://forum.webuddhist.com/t/homepage/348 "2025-07-11T06:56:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Evan](https://avatars.discourse-cdn.com/v4/letter/e/54ee81/32.png) [@Evan](https://forum.webuddhist.com/u/Evan)\
**Post date:** [July 11, 2025, 6:56am UTC](https://forum.webuddhist.com/t/homepage/348/1 "2025-07-11T06:56:02Z")

</div>

WeBuddhist and Sherab user community growth and partnerships.

| SUMMARY | |
| --- | --- |
| **Version** | 1.0 |
| **Mission** | Building a diverse and engaged community through clear communication, transparent governance, and by forging strategic partnerships that accelerate the project’s adoption and success. |
| **Chair(s):** | @nortse000 |
| **Communication:** | - [Discord Channel](https://discord.gg/R675TpZ97s) - [GitHub Team](https://github.com/orgs/OpenPecha/teams/community-and-outreach-wg) - Google Calendar |
| **Documentation:** | - PRD(Requirements) - [Github Project Board](https://github.com/orgs/OpenPecha/projects/122) - [Visuals](https://app.excalidraw.com/s/9MjBj0OINTj/6VL4auDChBC) - Meeting Minutes |

* * *

## Charter Details

### 1. Mission and Scope

- **Mission:** This Wroking Group’s mission is to build a diverse and engaged community through clear communication, transparent governance, and by forging strategic partnerships that accelerate the project’s adoption and success.
  - _Example: “To provide a reliable, scalable, and secure infrastructure for project development and deployment.”_

- **In Scope:** A bulleted list of what this WG is responsible for.
  - _Example: Managing the project’s CI/CD systems._
  - _Example: Owning and maintaining the `project/infra` code repository._
  - _Example: Defining and enforcing data backup and recovery policies._

- **Out of Scope:** A bulleted list of what this WG is explicitly _not_ responsible for, to prevent ambiguity.
  - _Example: Managing user-facing application features._
  - _Example: Setting the project’s overall strategic direction._

### 2. Responsibilities and Deliverables

- **Core Responsibilities:** A clear, bulleted list of the WG’s ongoing duties.
  - _Example: Triage and prioritize bugs and feature requests related to owned assets._
  - _Example: Review and merge pull requests against owned repositories._
  - _Example: Publish a quarterly status report to the community._

- **Key Deliverables:** Tangible services or products the WG provides.
  - _Example: A stable and documented build and test environment._
  - _Example: Public-facing dashboards for system health and performance._

### 3. Governance and Decision Making

- **Decision-Making Process:** How does the WG make decisions?
  - _Example: “Decisions are made by lazy consensus. Proposals are posted to the mailing list for 72 hours. If no objections are raised, the proposal is accepted. If there are objections, a formal vote is held during the next meeting, requiring a simple majority to pass.”_

- **Conflict Resolution:** How are disagreements handled?
  - _Example: “Disagreements are first discussed within the WG. If a consensus cannot be reached, the WG Chair makes the final call. Decisions can be appealed to the project’s Steering Committee.”_

### 4. Membership and Roles

- **Joining:** How does someone become a member?
  - _Example: “Membership is open to any contributor who has had at least 3 non-trivial pull requests merged within the WG’s owned repositories. Prospective members can be nominated by an existing member at a WG meeting.”_

- **Member Responsibilities:** What is expected of members?
  - _Example: Attend at least 50% of scheduled meetings per quarter._
  - _Example: Actively participate in discussions, code reviews, and bug triage._

- **Roles and Responsibilities:**
  - **Chair/Lead:** [Define how the Chair is selected, their term length, and their duties, e.g., running meetings, representing the WG].
  - **Tech Lead:** [Define how the Tech Lead is selected and their duties, e.g., setting technical direction, approving major architectural changes].

- **Stepping Down:** How does a member leave the WG?
  - _Example: “Members may step down at any time by notifying the WG Chair. Inactive members who do not meet participation requirements for two consecutive quarters will be moved to emeritus status.”_

- **Current Members:**
  - @nortse000, Role (e.g., Facilitator)
  - @Trinley, Member
  - @Evan, Member

## WG Meeting Calendar

- **Meetings:** [e.g., 2nd Tuesday of each month, 16:00 UTC]
- **Meeting Minutes:** [Link]

https://calendar.google.com/calendar/embed?src=buddhism_wiki_wg%40openpecha.org&ctz=Asia%2FKolkata
## Related WGs and Groups

- [[WG](https://..)

## Useful Links

- [Resource 1](https://xn--rvg)
- [Resource 2](https://xn--rvg)
- [Resource 3](https://xn--rvg)
