Some checks failed
Go / build-and-release (push) Has been cancelled
- Add Gitea issue templates for bug reports and feature requests with structured YAML forms for version, database backend, and log level - Add GitHub Actions CI workflow for automated testing on push/PR - Add GitHub Actions release workflow for building multi-platform binaries on tag push with SHA256 checksums - Add CONTRIBUTING.md with development setup, PR guidelines, and commit message format documentation - Add DECENTRALIZE_NOSTR.md expansion plan outlining WireGuard tunnel, GUI installer, system tray, and proxy server architecture - Update allowed commands in Claude settings - Bump version to v0.35.5 Files modified: - .gitea/issue_template/: Bug report, feature request, and config YAML - .github/workflows/: CI and release automation workflows - CONTRIBUTING.md: New contributor guide - docs/plans/DECENTRALIZE_NOSTR.md: Expansion architecture plan - .claude/settings.local.json: Updated allowed commands - pkg/version/version: Version bump to v0.35.5 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
119 lines
3.6 KiB
YAML
119 lines
3.6 KiB
YAML
name: Feature Request
|
|
about: Suggest a new feature or enhancement for ORLY relay
|
|
title: "[FEATURE] "
|
|
labels:
|
|
- enhancement
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
## Feature Request Guidelines
|
|
|
|
Thank you for suggesting a feature. Please provide as much detail as possible to help us understand your proposal.
|
|
|
|
**Before submitting:**
|
|
- Search [existing issues](https://git.mleku.dev/mleku/next.orly.dev/issues) to avoid duplicates
|
|
- Check if this is covered by an existing [NIP](https://github.com/nostr-protocol/nips)
|
|
- Review the [documentation](https://git.mleku.dev/mleku/next.orly.dev) for current capabilities
|
|
|
|
- type: dropdown
|
|
id: category
|
|
attributes:
|
|
label: Feature Category
|
|
description: What area of ORLY does this feature relate to?
|
|
options:
|
|
- Protocol (NIP implementation)
|
|
- Database / Storage
|
|
- Performance / Optimization
|
|
- Policy / Access Control
|
|
- Web UI / Admin Interface
|
|
- Deployment / Operations
|
|
- API / Integration
|
|
- Documentation
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem Statement
|
|
description: |
|
|
What problem does this feature solve? Is this related to a frustration you have?
|
|
A clear problem statement helps us understand the motivation.
|
|
placeholder: "I'm always frustrated when..."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: solution
|
|
attributes:
|
|
label: Proposed Solution
|
|
description: |
|
|
Describe the solution you'd like. Be specific about expected behavior.
|
|
placeholder: "I would like ORLY to..."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives Considered
|
|
description: |
|
|
Describe any alternative solutions or workarounds you've considered.
|
|
placeholder: "I've tried X but it doesn't work because..."
|
|
|
|
- type: input
|
|
id: nip
|
|
attributes:
|
|
label: Related NIP
|
|
description: If this relates to a Nostr Implementation Possibility, provide the NIP number
|
|
placeholder: "NIP-XX"
|
|
|
|
- type: dropdown
|
|
id: impact
|
|
attributes:
|
|
label: Scope of Impact
|
|
description: How significant is this feature?
|
|
options:
|
|
- Minor enhancement (small quality-of-life improvement)
|
|
- Moderate feature (adds useful capability)
|
|
- Major feature (significant new functionality)
|
|
- Breaking change (requires migration or config changes)
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: contribution
|
|
attributes:
|
|
label: Willingness to Contribute
|
|
description: Would you be willing to help implement this feature?
|
|
options:
|
|
- "Yes, I can submit a PR"
|
|
- "Yes, I can help with testing"
|
|
- "No, but I can provide more details"
|
|
- "No"
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: additional
|
|
attributes:
|
|
label: Additional Context
|
|
description: |
|
|
Any other context, mockups, examples, or references that help explain the feature.
|
|
|
|
For protocol features, include example event structures or message flows if applicable.
|
|
|
|
- type: checkboxes
|
|
id: checklist
|
|
attributes:
|
|
label: Checklist
|
|
options:
|
|
- label: I have searched existing issues and this is not a duplicate
|
|
required: true
|
|
- label: I have described the problem this feature solves
|
|
required: true
|
|
- label: I have checked if this relates to an existing NIP
|
|
required: false
|