Reusable Templates¶
This page contains copyable Markdown patterns for ESIIL Working Group documentation. Keep entries short and adapt them to the needs of the group.
Working Group Snapshot¶
Use this near the top of a project page or charter.
## Snapshot
| Field | Details |
| --- | --- |
| Working group | Name of the group |
| Leads | Names and affiliations |
| Status | Planning, active, releasing, archived |
| Primary output | Dataset, report, notebook, package, workshop, or other product |
| Repository | Link to source repository |
| Contact | Preferred contact path |
Team Role Roster¶
Use this during startup and revisit it when participation changes. See Working Group Team Roles for role descriptions.
## Team Roles
| Role | Name | Contact | Notes |
| --- | --- | --- | --- |
| Project Leader | | | |
| Co-Leader | | | |
| Tech Lead | | | Primary technical contact with ESIIL CI |
| Collaboration Lead | | | Works with ESIIL facilitators on team science and norms |
| Transition Lead | | | Coordinates IP, authorship, communication, and transition planning |
Kickoff Agenda¶
## Kickoff Agenda
1. Introductions and roles
2. Review of proposal goals and expected outputs
3. Confirmation of Tech Lead, Collaboration Lead, and Transition Lead
4. Discussion of timeline and milestones
5. Data, software, and infrastructure needs
6. Team norms, meeting cadence, and communication plan
7. Documentation, repository, and public website plan
8. Immediate action items
Team Norms Starter¶
## Team Norms
- **Meeting cadence:**
- **Decision-making process:**
- **Notes and action items:**
- **Authorship and attribution expectations:**
- **Communication channels:**
- **Participation expectations:**
- **How to raise blockers or conflict:**
- **How to orient new participants:**
Decision Note¶
Use this when a structural, data, publication, or process decision needs to be easy to recover later.
!!! note "Decision: short title"
**Date:** YYYY-MM-DD
**Decision:** State the decision in one sentence.
**Rationale:** Explain the context and tradeoffs briefly.
**Follow-up:** Link to related issues, pull requests, notes, or outputs.
Data Source Entry¶
## Data Source
- **Name:** Dataset or catalog name
- **Provider:** Organization or repository
- **Access:** URL, API, STAC catalog, cloud path, or request process
- **Format:** File type, service type, or storage layout
- **Coverage:** Spatial, temporal, taxonomic, or thematic scope
- **License:** License and reuse constraints
- **Citation:** Required or preferred citation
- **Notes:** Privacy, sovereignty, quality, or uncertainty considerations
Technical Support Request¶
Use this when the Tech Lead needs to summarize a technical question for ESIIL CI.
## Technical Support Request
- **Requested by:** Name and role
- **Working group:** Group name
- **Repository or workspace:** Link
- **Need:** Repository, container, workflow, software, cloud computing, reproducibility, or other support
- **Current status:** What exists now
- **Blocker:** What is preventing progress
- **Timeline:** When support is needed
- **Related materials:** Links to issues, notes, data sources, or code
Output Inventory¶
Use this during the active period and at closeout.
## Output Inventory
| Output | Location | Status | Citation or Attribution | Maintenance |
| --- | --- | --- | --- | --- |
| [Name] | [Link] | Draft, released, archived | [Citation] | Active, limited, archived |
Final Report Outline¶
## Final Report
1. Working group title and participants
2. Original goals and any major scope changes
3. Activities completed
4. Outputs produced
5. Data, software, or infrastructure used
6. Outcomes, impacts, or community benefits
7. Challenges and lessons learned
8. Future work or maintenance plan
9. Links to repositories, websites, releases, publications, or archives