50 lines
1.2 KiB
Markdown
50 lines
1.2 KiB
Markdown
---
|
|
id: EP-DOMAIN-NNN
|
|
type: ep
|
|
ep_id: EP-DOMAIN-NNN
|
|
target_org: <github-org-or-owner>
|
|
target_repo: <repository-name>
|
|
title: "Short description of the extension point"
|
|
status: draft
|
|
domain: infotech # select an allowed sector domain; do not use a legacy project name
|
|
related_workstream: null
|
|
state_hub_contribution_id: null
|
|
created: "YYYY-MM-DD"
|
|
updated: "YYYY-MM-DD"
|
|
location: "src/file.ts:42"
|
|
upstream_issue_url: null
|
|
---
|
|
|
|
# Extension Point Proposal: EP-DOMAIN-NNN
|
|
|
|
## Summary
|
|
|
|
_One-paragraph description of the extension point: where in the upstream codebase
|
|
it would live, what it would enable, and who would benefit._
|
|
|
|
## Location
|
|
|
|
**File**: `<path/in/upstream/repo>`
|
|
**Line**: _approximate location where the hook/callback would be inserted_
|
|
|
|
## Proposed Interface
|
|
|
|
```typescript
|
|
// or Python, Rust, etc. — match the upstream project's language
|
|
interface ExtensionPoint {
|
|
// …
|
|
}
|
|
```
|
|
|
|
## Rationale
|
|
|
|
_Why this extension point is valuable. What use cases does it unlock?
|
|
Why should upstream accept it rather than keeping it local?_
|
|
|
|
## Implementation Sketch
|
|
|
|
_Brief notes on how upstream might implement this, if relevant._
|
|
|
|
## Notes
|
|
|
|
_References to related upstream issues, PRs, or discussions._
|