Skip to content

Commit 533ef42

Browse files
authored
second draft of project committee charter/process
Signed-off-by: musikc (Christina) <[email protected]>
1 parent 8ec35c8 commit 533ef42

File tree

1 file changed

+15
-10
lines changed

1 file changed

+15
-10
lines changed

PDR-0011-Project-Committee/readme.md

Lines changed: 15 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Created: 2025-10-18
2323
- Applicants should demonstrate relevant experience in open-source development, governance, community management, or blockchain-related technology.
2424
- Efforts should be made to ensure diversity in geography, professional background and ecosystem representation.
2525
2. **Number of Members**
26-
- The Committee shall consist of a minimum of **five (5)** and a maximum of **nine (9)** members, depending on workload and project volume.
26+
- The Committee shall consist of a minimum of **three (3)** and a maximum of **five (5)** members, depending on workload and project volume.
2727
3. **Application & Selection Process**
2828
- The AB shall issue a **public call for applications** at least 30 days prior to appointments, describing the role, expected workload and selection criteria.
2929
- Interested individuals submit an application outlining their background, qualifications and potential conflicts of interest.
@@ -60,22 +60,27 @@ The PC operates under delegation from the AB to manage the following responsibil
6060
### A. Evaluation & Selection
6161
- Review **Prospective Project** submissions (per PDR-0003) to ensure:
6262
- Alignment with PRAGMA’s goals and vision.
63-
- Open-source licensing with PRAGMA as owner.
63+
- Open-source licensing willing to donate to PRAGMA.
6464
- Legal and IP soundness.
65-
- Minimum contributor base (≥3 active contributors).
66-
- Three acceptable releases demonstrating sustainability.
67-
- Compliance with a DCO and contribution policies.
65+
- Has a clear roadmap alligned with its objectives
6866
- Conduct follow-up interviews or Q&A when necessary.
6967
- Provide written recommendations and scores to the AB for decision.
7068

7169
### B. Oversight of Incubating Projects
72-
- Assign a **Guide** or liaison for each incubating project.
70+
- Assign a **Guide** essentially a liaison for each incubating project.
7371
- Review and assess quarterly reports, ensuring timely submission and transparency.
7472
- Validate adherence to roadmap, governance model and PRAGMA’s ethical and legal standards.
7573
- Identify at-risk projects and recommend interventions or discontinuation.
7674

7775
### C. Transition to Maintainer Committee
78-
- After multiple successful quarters, prepare recommendations to the AB for **GA referral** to establish a Maintainer Committee (per Article 5(2) of the Statutes).
76+
- After multiple successful quarters, prepare recommendations to the AB for **GA referral** to establish a Maintainer Committee (per Article 5(2) of the Statutes). The decision to accept or reject the project is based on meeting the following requirements:
77+
- The project must have more than three active contributors.
78+
- The project must have demonstrated its ability to grow by offering a clear path to join its new contributors.
79+
- The project made at least three, acceptable releases.
80+
- The project provides timely quarterly reports.
81+
- The project's name is clear and free of trademark disputes, cultural appropriation, and other issues.
82+
- The source code was either only developed by project team members or accepted by using a DCO.
83+
- The source code is licensed under a PRAGMA-approved license with PRAGMA as the owner.
7984
- Ensure each new Maintainer Committee submits its organizational regulations for AB approval.
8085

8186
### D. Reporting & Documentation
@@ -94,10 +99,10 @@ The PC operates under delegation from the AB to manage the following responsibil
9499
## VII. Application Workflow
95100
1. **Call for Applications:** PC announces open calls for new projects at least **twice per year**.
96101
2. **Submission:** Applicants complete a standardized form (per PDR-0003) and submit required materials.
97-
3. **Review:** PC verifies completeness and evaluates proposals.
98-
4. **Recommendation:** Projects meeting criteria are forwarded to the AB for approval or rejection.
102+
3. **Review:** PC verifies completeness and evaluates proposals, selecting to make recommendations.
103+
4. **Recommendation:** Recommended projects forwarded to the AB for approval or rejection.
99104
5. **Incubation Phase:** Approved projects enter incubation under PC oversight.
100-
6. **Graduation:** After three releases, the PC may recommend project graduation to the AB for approval or rejection.
105+
6. **Graduation:** After three releases, the PC may recommend project graduation to the AB for approval or rejection if acceptance criteria has been met.
101106

102107
## VIII. Conflict of Interest
103108
- All members must disclose actual or potential conflicts, including employment or funding ties to projects under review.

0 commit comments

Comments
 (0)