An API serving Buddhist texts and linked references.
| SUMMARY | |
|---|---|
| Version | 2.1 |
| Mission | To empower the global community with open access to the richness of Buddhist knowledge by building a comprehensive, text-backed graph database, fostering new insights and connections through our API, and enriching the world’s open data by contributing to Wikidata. |
| Chair(s): | @Tashi_Tsering |
| Communication: | - Discord Channel - GitHub Team - Google Calender |
| Documentation: | - PRD - Epics - Progress Board - Visual - Meeting Minutes |
Download & Documentation
Access the project’s resources:
- PRD:
- GitHub Repo:
- Documentation:
- Download Links:
Working Group Members & Contacts
| Name | Discord | GitHub | Role | |
|---|---|---|---|---|
| Gabor Detari | gabor@detari.dev | gdetari_81249 | gdetari | WG Lead |
| Tashi Tsering | tashitsering@dharmaduta.in | ta4_tsering | ta4tsering | Developer |
| Tenzin Tsering | tenzintsering@dharmaduta.in | tenzintsundue | tenzin3 | Developer |
| Elie Roux | roux.elie@gmail.com | elie8250 | eroux | BDRC |
| Tenzin Samten | samten@esukhia.org | iamsamten.56 | tenzinsamten | WeBuddhist |
| Tenzin Kunsang | tenkus@esukhia.org | kun_. | tenkus47 | Pecha AI Studio |
| Tenzin Tsewang | None | None | None | Pecha Data |
Team Members by Role
| Team Member | Role |
|---|---|
| Gabor | Backend Developer |
| Tashi Tsering | Backend Developer |
| Tenzin Tsering | Backend Developer |
ROLE DESCRIPTIONS
Backend Developer (Senior/Lead)
- Design and implement comprehensive database architecture for scalable data management
- Plan database schemas, relationships, and optimization strategies for current and future needs
- Maintain database performance, security, and backup/recovery systems
- Configure and manage DevOps infrastructure including CI/CD pipelines, deployment strategies, and environment management
- Develop robust RESTful/GraphQL API endpoints with comprehensive documentation
- Ensure API performance, security, rate limiting, and error handling for optimal user experience
- Monitor system performance, troubleshoot backend issues, and implement scalability solutions
- Collaborate with frontend teams to define API contracts and data requirements
- Implement authentication, authorization, and data validation layers
- Maintain development and production environments with proper monitoring and logging
Joining and Participating
To become a WG member, you must be registered on forum.openpecha.org. Members may be added or removed during regular WG meetings with quorum. Each membership change includes a reason, selected from the list below.
Reasons to Add a Member:
- Participation in WG meetings, events, or activities
- Contributions to WG-related projects
- Self-nomination during a WG meeting
Reasons to Remove a Member:
- No participation for over 3 months
- Violation of the OpenPecha Code of Conduct
- Personal request for removal
These are general guidelines; the WG may consider specific situations.
Communication Channels
- Discussion: OpenPecha Discord Server
- Documentation & Archives: OpenPecha Forum
- Meeting Schedules & Notifications: Sent via Google Calendar and Gmail mailing list
Meetings
Meeting invites are shared through Google Calendar. Please subscribe to the Gmail list to receive updates.