Establish repository contribution and product foundations #3

Context

devNepal is at the documentation and planning stage. Contributors need a coherent repository entry point, contribution rules, governance, reporting policies, and implementation requirements before application development begins.

In scope

• Establish the Apache-2.0 licence, English and Nepali READMEs, contribution conventions, governance, maintainer information, and conduct/security policies.
• Add the English privacy draft, full product requirements, and v0.1 requirements with accurate traceability.
• Provide GitHub issue and PR templates and repository ignore rules.
• Track unfinished setup and launch work separately in docs/READINESS.md with completion criteria.

Out of scope

Application implementation, CI and bot installation, provisioning private contacts, public account launch, and a Nepali privacy translation. Future readiness tasks do not block this seed documentation change.

Acceptance criteria

• Repository guidance and templates are internally consistent and accurately describe how to contribute now.
• Both READMEs provide working documentation setup instructions and valid local links.
• PRDs describe the intended requirements without implementation-status annotations.
• Outstanding readiness work has stable IDs, responsible roles, milestones and completion criteria.
• All commits in the PR are signed off; no dependencies or application behaviour are introduced.

Where to look

Root Markdown policies and READMEs, docs/, .github/ISSUE_TEMPLATE/, .github/PULL_REQUEST_TEMPLATE.md, and .gitignore.

Tests expected

Check local Markdown links, requirement/readiness references, YAML parsing, ignore behaviour, whitespace and commit sign-offs. No application tests apply because the repository has no application code.

Size

M — 4 to 16 hours. The full reference PRD accounts for much of the document volume.

Mentor

@pramodkandel