From b1346d21bb015cedcb71bcee4152851f79b86a58 Mon Sep 17 00:00:00 2001 From: Shivampal157 Date: Thu, 22 Jan 2026 03:03:09 +0530 Subject: [PATCH 1/3] Docs: add contributor details for Shivam Pal --- Community.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/Community.md b/Community.md index 147f4a6e..bafb1539 100644 --- a/Community.md +++ b/Community.md @@ -909,3 +909,21 @@ SRCC + + + + + + + + + + + + + + + + + +
NameShivam Pal
GitHubhttps://github.com/Shivampal157
LinkedInhttps://www.linkedin.com/in/shivam-pal-677777301
CollegeIIIT Agartala
\ No newline at end of file From c17c898bd4cdbf633e42d30279da3eda3fe651f1 Mon Sep 17 00:00:00 2001 From: Shivampal157 Date: Fri, 1 May 2026 02:04:45 +0530 Subject: [PATCH 2/3] Add DMP 2026 proposal pack and issue #776 implementation package Made-with: Cursor --- DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md | 102 +++++++++++++ DMP2026_PROPOSALS_SHIVAM.md | 151 ++++++++++++++++++++ 2 files changed, 253 insertions(+) create mode 100644 DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md create mode 100644 DMP2026_PROPOSALS_SHIVAM.md diff --git a/DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md b/DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md new file mode 100644 index 00000000..a2c8eb88 --- /dev/null +++ b/DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md @@ -0,0 +1,102 @@ +# DMP 2026 - Issue #776 Implementation Package + +Issue link: https://github.com/Code4GovTech/C4GT/issues/776 + +This document is a PR-ready implementation package for: + +`[MergeShip] MVP-1: GitHub OAuth onboarding + contributor profile bootstrap` + +## What is already implemented locally + +I completed the MVP-1 implementation in a local MergeShip branch: + +- branch: `feat/776-oauth-profile-bootstrap` +- commit: `2351a51` + +### Implemented scope + +1. Environment-based Appwrite setup for client and server. +2. Contributor profile bootstrap API. +3. Contributor profile fetch API. +4. Onboarding integration to bootstrap profile after GitHub identity resolution. +5. `.env.example` and setup documentation updates. + +## API design + +### `POST /api/profile/bootstrap` + +Creates or updates contributor profile after OAuth login. + +Request body: + +```json +{ + "userId": "appwrite_user_id", + "githubId": "github_provider_uid_or_handle", + "username": "github_login", + "avatarUrl": "optional", + "name": "optional", + "email": "optional" +} +``` + +Response: + +- `200`: `{ ok: true, profile, action: "created" | "updated" }` +- `400`: missing required fields +- `503`: missing server env config +- `500`: internal failure + +### `GET /api/profile/me?userId=` + +Fetches contributor profile by userId. + +Response: + +- `200`: `{ ok: true, profile }` +- `400`: missing userId +- `404`: profile not found +- `503`: missing server env config +- `500`: internal failure + +## Data model (MVP) + +Contributor document fields: + +- `userId` +- `githubId` +- `username` +- `avatarUrl` +- `name` +- `email` +- `level` (default `L1`) +- `joinedAt` +- `updatedAt` + +## Environment variables required + +```bash +NEXT_PUBLIC_APPWRITE_ENDPOINT= +NEXT_PUBLIC_APPWRITE_PROJECT_ID= +APPWRITE_ENDPOINT= +APPWRITE_PROJECT_ID= +APPWRITE_API_KEY= +APPWRITE_DATABASE_ID= +APPWRITE_CONTRIBUTOR_COLLECTION_ID= +``` + +## Planned PR title + +`feat(auth): github oauth onboarding and contributor profile bootstrap` + +## Planned PR summary + +- Add OAuth profile bootstrap and profile retrieval APIs. +- Integrate onboarding flow with bootstrap API call. +- Move Appwrite config to env-based setup. +- Add `.env.example` and setup docs updates. + +## Notes + +- This implementation is intentionally limited to MVP-1. +- Ranking, triage queue, and gamification are explicitly out of scope for this phase. diff --git a/DMP2026_PROPOSALS_SHIVAM.md b/DMP2026_PROPOSALS_SHIVAM.md new file mode 100644 index 00000000..f4b19369 --- /dev/null +++ b/DMP2026_PROPOSALS_SHIVAM.md @@ -0,0 +1,151 @@ +# DMP 2026 Proposal Pack (Shivam Pal) + +This document contains 3 proposal drafts optimized for: +- 2 hours/day availability +- full-stack + backend + devops + ML profile +- better selection probability (fit + execution realism) + +--- + +## Proposal 1 (Primary) - Issue #774 + +**Ticket:** [#774 - MergeShip](https://github.com/Code4GovTech/C4GT/issues/774) +**Title Suggestion:** MergeShip Contributor-Maintainer Orchestration Core (MVP) + +### Why this project (short note for application) +This project matches my strongest stack areas: backend APIs, full-stack workflow design, integration engineering, and practical DevOps. I plan to focus on an MVP that improves contributor onboarding and maintainers' triage workflow with measurable outcomes. + +### Goals +- [ ] Build GitHub OAuth based onboarding flow with contributor profile bootstrap. +- [ ] Implement L1-L3 ranking engine using deterministic scoring (initial rules + configurable weights). +- [ ] Build PR triage API with maintainers' priority stack and assignment recommendations. +- [ ] Implement basic quest/XP pipeline (first issue linked, first PR opened, first PR merged, first review). +- [ ] Deliver midpoint demo with contributor and maintainer dashboard views. + +### Expected Outcome +An MVP platform where: +- contributors can authenticate via GitHub, see rank and suggested next tasks, +- maintainers can view sorted PR/task queues and assign work faster, +- platform tracks progress through transparent XP and milestone events. + +### Acceptance Criteria +- User can sign in via GitHub OAuth and create a profile successfully. +- Rank engine produces stable L1-L3 output for sample contributor profiles. +- Maintainer queue API returns sortable, filterable PR/task recommendations. +- Quest/XP events are persisted and visible on contributor dashboard. +- Docker-based local setup and one-click run instructions are available. + +### Implementation Details +- **Backend:** Node.js + Express modular services (`auth`, `ranking`, `triage`, `quests`) +- **Frontend:** React/Next dashboard pages for contributor + maintainer views +- **Database:** MongoDB collections for user profile, rank snapshots, quest events +- **Integrations:** GitHub OAuth + GitHub API ingestion for contribution stats +- **DevOps:** Docker compose, env templates, CI lint/test checks +- **AI Scope (MVP-safe):** Start with template-based issue decomposition; optional LLM hook behind feature flag + +### 2-hour/day execution plan (realistic) +- **Week 1:** setup, auth, schema, basic profile flow +- **Week 2:** ranking engine + tests + initial dashboard cards +- **Week 3:** PR triage API + maintainer queue UI +- **Week 4:** quest/XP events + docs + polish + demo video + +### Risk & Mitigation +- **Risk:** Full custom LLM can exceed timeline + **Mitigation:** deliver deterministic decomposition templates first; keep LLM integration optional. +- **Risk:** GitHub API limits + **Mitigation:** cached snapshots and background sync. + +### Suggested issue comment (human tone) +I am interested in working on this with an MVP-first approach. I can contribute consistently (~2 hours/day) and focus on a production-friendly orchestration core: GitHub OAuth onboarding, deterministic L1-L3 ranking, PR triage APIs, and quest/XP tracking. +If this scope looks good, I can share a milestone-wise implementation plan and begin with auth + ranking engine foundation. + +--- + +## Proposal 2 (Backup A) - Issue #748 + +**Ticket:** [#748 - Finternet Verifiable Presentations + ZK Selective Disclosure](https://github.com/Code4GovTech/C4GT/issues/748) +**Title Suggestion:** UNITS Credential Verification Pipeline with Selective Disclosure MVP + +### Why this project +This aligns with my backend + security engineering interest. I can contribute by building a reliable verification service with clear API contracts and auditability. + +### Goals +- [ ] Build credential verification API for VP validation workflow. +- [ ] Implement selective disclosure proof handling path (MVP-focused). +- [ ] Add robust validation/error taxonomy for malformed credentials/proofs. +- [ ] Provide audit logs and verification traces for maintainers/debugging. +- [ ] Add integration tests with sample credential payloads. + +### Expected Outcome +A working backend verification module that accepts VP payloads, validates required claims selectively, and returns deterministic verification results with trace IDs. + +### Acceptance Criteria +- API handles valid/invalid VP payloads deterministically. +- Selective-disclosure validation path is implemented for target fields. +- Verification responses include trace metadata and machine-readable errors. +- Test suite covers positive, negative, and replay-like edge cases. + +### Implementation Details +- **Backend:** Python/FastAPI or Node/Express (as per project conventions) +- **Security:** strict schema + signature/proof validation pipeline +- **Observability:** structured logs + correlation IDs +- **DevOps:** reproducible local setup + CI validation tests + +### 2-hour/day plan +- **Week 1:** read existing flow, schema contracts, API skeleton +- **Week 2:** core VP validation + error taxonomy +- **Week 3:** selective disclosure + logging + integration tests +- **Week 4:** hardening, docs, and maintainers' review iteration + +--- + +## Proposal 3 (Backup B) - Issue #749 + +**Ticket:** [#749 - Finternet MCP Server for UNITS API](https://github.com/Code4GovTech/C4GT/issues/749) +**Title Suggestion:** MCP Adapter Layer for UNITS API with Reliability Guardrails + +### Why this project +Strong fit for backend/platform work: API adapter design, tool contracts, reliability, and maintainability. + +### Goals +- [ ] Build MCP server wrapper for prioritized UNITS API actions. +- [ ] Add typed tool contracts and schema-level validation. +- [ ] Implement retry/fallback for unstable upstream responses. +- [ ] Add response caching for repetitive reads where safe. +- [ ] Add telemetry for latency/error rate per tool endpoint. + +### Expected Outcome +An MCP server integration layer that agents/tools can use with stable contracts and improved operational reliability. + +### Acceptance Criteria +- Core MCP tools are discoverable and executable end-to-end. +- Validation rejects malformed tool calls with clear error structure. +- Retry and fallback logic handles transient failures correctly. +- Logs/metrics show per-tool performance and failure context. + +### Implementation Details +- **Backend:** adapter modules around UNITS APIs +- **Contracts:** JSON schema validation for tool input/output +- **Reliability:** timeout/retry circuit, defensive response parsing +- **DevOps:** dockerized local run + smoke tests in CI + +### 2-hour/day plan +- **Week 1:** contract design + baseline tools +- **Week 2:** robust error handling + retries + caching +- **Week 3:** telemetry + integration tests + docs +- **Week 4:** maintainers' feedback loop + refinement + +--- + +## Final Submission Strategy + +1. Submit **Proposal 1 (#774)** as primary. +2. Keep **#748** and **#749** as polished backups. +3. Before submitting, add one meaningful issue comment and one small starter contribution (docs/test/setup) for the primary ticket. +4. Keep scope realistic and milestone-bound; avoid overpromising custom-LLM-heavy first deliverable. + +--- + +## Quick Personal Pitch (can reuse in forms) + +I have been contributing consistently to open-source projects in backend, full-stack, and CI/dev workflows. I prefer shipping maintainable increments with clear test coverage and practical documentation. For DMP 2026, I am targeting a milestone-driven implementation with realistic scope and consistent execution. From 527c6bb8f91e539a0ceeaea6d74bd07d9002bfaf Mon Sep 17 00:00:00 2001 From: Shivampal157 Date: Fri, 1 May 2026 02:07:31 +0530 Subject: [PATCH 3/3] remove C4GT MergeShip proposal and implementation docs Made-with: Cursor --- DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md | 102 ------------- DMP2026_PROPOSALS_SHIVAM.md | 151 -------------------- 2 files changed, 253 deletions(-) delete mode 100644 DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md delete mode 100644 DMP2026_PROPOSALS_SHIVAM.md diff --git a/DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md b/DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md deleted file mode 100644 index a2c8eb88..00000000 --- a/DMP2026_ISSUE_776_IMPLEMENTATION_PACKAGE.md +++ /dev/null @@ -1,102 +0,0 @@ -# DMP 2026 - Issue #776 Implementation Package - -Issue link: https://github.com/Code4GovTech/C4GT/issues/776 - -This document is a PR-ready implementation package for: - -`[MergeShip] MVP-1: GitHub OAuth onboarding + contributor profile bootstrap` - -## What is already implemented locally - -I completed the MVP-1 implementation in a local MergeShip branch: - -- branch: `feat/776-oauth-profile-bootstrap` -- commit: `2351a51` - -### Implemented scope - -1. Environment-based Appwrite setup for client and server. -2. Contributor profile bootstrap API. -3. Contributor profile fetch API. -4. Onboarding integration to bootstrap profile after GitHub identity resolution. -5. `.env.example` and setup documentation updates. - -## API design - -### `POST /api/profile/bootstrap` - -Creates or updates contributor profile after OAuth login. - -Request body: - -```json -{ - "userId": "appwrite_user_id", - "githubId": "github_provider_uid_or_handle", - "username": "github_login", - "avatarUrl": "optional", - "name": "optional", - "email": "optional" -} -``` - -Response: - -- `200`: `{ ok: true, profile, action: "created" | "updated" }` -- `400`: missing required fields -- `503`: missing server env config -- `500`: internal failure - -### `GET /api/profile/me?userId=` - -Fetches contributor profile by userId. - -Response: - -- `200`: `{ ok: true, profile }` -- `400`: missing userId -- `404`: profile not found -- `503`: missing server env config -- `500`: internal failure - -## Data model (MVP) - -Contributor document fields: - -- `userId` -- `githubId` -- `username` -- `avatarUrl` -- `name` -- `email` -- `level` (default `L1`) -- `joinedAt` -- `updatedAt` - -## Environment variables required - -```bash -NEXT_PUBLIC_APPWRITE_ENDPOINT= -NEXT_PUBLIC_APPWRITE_PROJECT_ID= -APPWRITE_ENDPOINT= -APPWRITE_PROJECT_ID= -APPWRITE_API_KEY= -APPWRITE_DATABASE_ID= -APPWRITE_CONTRIBUTOR_COLLECTION_ID= -``` - -## Planned PR title - -`feat(auth): github oauth onboarding and contributor profile bootstrap` - -## Planned PR summary - -- Add OAuth profile bootstrap and profile retrieval APIs. -- Integrate onboarding flow with bootstrap API call. -- Move Appwrite config to env-based setup. -- Add `.env.example` and setup docs updates. - -## Notes - -- This implementation is intentionally limited to MVP-1. -- Ranking, triage queue, and gamification are explicitly out of scope for this phase. diff --git a/DMP2026_PROPOSALS_SHIVAM.md b/DMP2026_PROPOSALS_SHIVAM.md deleted file mode 100644 index f4b19369..00000000 --- a/DMP2026_PROPOSALS_SHIVAM.md +++ /dev/null @@ -1,151 +0,0 @@ -# DMP 2026 Proposal Pack (Shivam Pal) - -This document contains 3 proposal drafts optimized for: -- 2 hours/day availability -- full-stack + backend + devops + ML profile -- better selection probability (fit + execution realism) - ---- - -## Proposal 1 (Primary) - Issue #774 - -**Ticket:** [#774 - MergeShip](https://github.com/Code4GovTech/C4GT/issues/774) -**Title Suggestion:** MergeShip Contributor-Maintainer Orchestration Core (MVP) - -### Why this project (short note for application) -This project matches my strongest stack areas: backend APIs, full-stack workflow design, integration engineering, and practical DevOps. I plan to focus on an MVP that improves contributor onboarding and maintainers' triage workflow with measurable outcomes. - -### Goals -- [ ] Build GitHub OAuth based onboarding flow with contributor profile bootstrap. -- [ ] Implement L1-L3 ranking engine using deterministic scoring (initial rules + configurable weights). -- [ ] Build PR triage API with maintainers' priority stack and assignment recommendations. -- [ ] Implement basic quest/XP pipeline (first issue linked, first PR opened, first PR merged, first review). -- [ ] Deliver midpoint demo with contributor and maintainer dashboard views. - -### Expected Outcome -An MVP platform where: -- contributors can authenticate via GitHub, see rank and suggested next tasks, -- maintainers can view sorted PR/task queues and assign work faster, -- platform tracks progress through transparent XP and milestone events. - -### Acceptance Criteria -- User can sign in via GitHub OAuth and create a profile successfully. -- Rank engine produces stable L1-L3 output for sample contributor profiles. -- Maintainer queue API returns sortable, filterable PR/task recommendations. -- Quest/XP events are persisted and visible on contributor dashboard. -- Docker-based local setup and one-click run instructions are available. - -### Implementation Details -- **Backend:** Node.js + Express modular services (`auth`, `ranking`, `triage`, `quests`) -- **Frontend:** React/Next dashboard pages for contributor + maintainer views -- **Database:** MongoDB collections for user profile, rank snapshots, quest events -- **Integrations:** GitHub OAuth + GitHub API ingestion for contribution stats -- **DevOps:** Docker compose, env templates, CI lint/test checks -- **AI Scope (MVP-safe):** Start with template-based issue decomposition; optional LLM hook behind feature flag - -### 2-hour/day execution plan (realistic) -- **Week 1:** setup, auth, schema, basic profile flow -- **Week 2:** ranking engine + tests + initial dashboard cards -- **Week 3:** PR triage API + maintainer queue UI -- **Week 4:** quest/XP events + docs + polish + demo video - -### Risk & Mitigation -- **Risk:** Full custom LLM can exceed timeline - **Mitigation:** deliver deterministic decomposition templates first; keep LLM integration optional. -- **Risk:** GitHub API limits - **Mitigation:** cached snapshots and background sync. - -### Suggested issue comment (human tone) -I am interested in working on this with an MVP-first approach. I can contribute consistently (~2 hours/day) and focus on a production-friendly orchestration core: GitHub OAuth onboarding, deterministic L1-L3 ranking, PR triage APIs, and quest/XP tracking. -If this scope looks good, I can share a milestone-wise implementation plan and begin with auth + ranking engine foundation. - ---- - -## Proposal 2 (Backup A) - Issue #748 - -**Ticket:** [#748 - Finternet Verifiable Presentations + ZK Selective Disclosure](https://github.com/Code4GovTech/C4GT/issues/748) -**Title Suggestion:** UNITS Credential Verification Pipeline with Selective Disclosure MVP - -### Why this project -This aligns with my backend + security engineering interest. I can contribute by building a reliable verification service with clear API contracts and auditability. - -### Goals -- [ ] Build credential verification API for VP validation workflow. -- [ ] Implement selective disclosure proof handling path (MVP-focused). -- [ ] Add robust validation/error taxonomy for malformed credentials/proofs. -- [ ] Provide audit logs and verification traces for maintainers/debugging. -- [ ] Add integration tests with sample credential payloads. - -### Expected Outcome -A working backend verification module that accepts VP payloads, validates required claims selectively, and returns deterministic verification results with trace IDs. - -### Acceptance Criteria -- API handles valid/invalid VP payloads deterministically. -- Selective-disclosure validation path is implemented for target fields. -- Verification responses include trace metadata and machine-readable errors. -- Test suite covers positive, negative, and replay-like edge cases. - -### Implementation Details -- **Backend:** Python/FastAPI or Node/Express (as per project conventions) -- **Security:** strict schema + signature/proof validation pipeline -- **Observability:** structured logs + correlation IDs -- **DevOps:** reproducible local setup + CI validation tests - -### 2-hour/day plan -- **Week 1:** read existing flow, schema contracts, API skeleton -- **Week 2:** core VP validation + error taxonomy -- **Week 3:** selective disclosure + logging + integration tests -- **Week 4:** hardening, docs, and maintainers' review iteration - ---- - -## Proposal 3 (Backup B) - Issue #749 - -**Ticket:** [#749 - Finternet MCP Server for UNITS API](https://github.com/Code4GovTech/C4GT/issues/749) -**Title Suggestion:** MCP Adapter Layer for UNITS API with Reliability Guardrails - -### Why this project -Strong fit for backend/platform work: API adapter design, tool contracts, reliability, and maintainability. - -### Goals -- [ ] Build MCP server wrapper for prioritized UNITS API actions. -- [ ] Add typed tool contracts and schema-level validation. -- [ ] Implement retry/fallback for unstable upstream responses. -- [ ] Add response caching for repetitive reads where safe. -- [ ] Add telemetry for latency/error rate per tool endpoint. - -### Expected Outcome -An MCP server integration layer that agents/tools can use with stable contracts and improved operational reliability. - -### Acceptance Criteria -- Core MCP tools are discoverable and executable end-to-end. -- Validation rejects malformed tool calls with clear error structure. -- Retry and fallback logic handles transient failures correctly. -- Logs/metrics show per-tool performance and failure context. - -### Implementation Details -- **Backend:** adapter modules around UNITS APIs -- **Contracts:** JSON schema validation for tool input/output -- **Reliability:** timeout/retry circuit, defensive response parsing -- **DevOps:** dockerized local run + smoke tests in CI - -### 2-hour/day plan -- **Week 1:** contract design + baseline tools -- **Week 2:** robust error handling + retries + caching -- **Week 3:** telemetry + integration tests + docs -- **Week 4:** maintainers' feedback loop + refinement - ---- - -## Final Submission Strategy - -1. Submit **Proposal 1 (#774)** as primary. -2. Keep **#748** and **#749** as polished backups. -3. Before submitting, add one meaningful issue comment and one small starter contribution (docs/test/setup) for the primary ticket. -4. Keep scope realistic and milestone-bound; avoid overpromising custom-LLM-heavy first deliverable. - ---- - -## Quick Personal Pitch (can reuse in forms) - -I have been contributing consistently to open-source projects in backend, full-stack, and CI/dev workflows. I prefer shipping maintainable increments with clear test coverage and practical documentation. For DMP 2026, I am targeting a milestone-driven implementation with realistic scope and consistent execution.