feature_request.yaml raw

   1  name: Feature Request
   2  about: Suggest a new feature or enhancement for ORLY relay
   3  title: "[FEATURE] "
   4  labels:
   5    - enhancement
   6  body:
   7    - type: markdown
   8      attributes:
   9        value: |
  10          ## Feature Request Guidelines
  11  
  12          Thank you for suggesting a feature. Please provide as much detail as possible to help us understand your proposal.
  13  
  14          **Before submitting:**
  15          - Search [existing issues](https://git.mleku.dev/mleku/next.orly.dev/issues) to avoid duplicates
  16          - Check if this is covered by an existing [NIP](https://github.com/nostr-protocol/nips)
  17          - Review the [documentation](https://git.mleku.dev/mleku/next.orly.dev) for current capabilities
  18  
  19    - type: dropdown
  20      id: category
  21      attributes:
  22        label: Feature Category
  23        description: What area of ORLY does this feature relate to?
  24        options:
  25          - Protocol (NIP implementation)
  26          - Database / Storage
  27          - Performance / Optimization
  28          - Policy / Access Control
  29          - Web UI / Admin Interface
  30          - Deployment / Operations
  31          - API / Integration
  32          - Documentation
  33          - Other
  34      validations:
  35        required: true
  36  
  37    - type: textarea
  38      id: problem
  39      attributes:
  40        label: Problem Statement
  41        description: |
  42          What problem does this feature solve? Is this related to a frustration you have?
  43          A clear problem statement helps us understand the motivation.
  44        placeholder: "I'm always frustrated when..."
  45      validations:
  46        required: true
  47  
  48    - type: textarea
  49      id: solution
  50      attributes:
  51        label: Proposed Solution
  52        description: |
  53          Describe the solution you'd like. Be specific about expected behavior.
  54        placeholder: "I would like ORLY to..."
  55      validations:
  56        required: true
  57  
  58    - type: textarea
  59      id: alternatives
  60      attributes:
  61        label: Alternatives Considered
  62        description: |
  63          Describe any alternative solutions or workarounds you've considered.
  64        placeholder: "I've tried X but it doesn't work because..."
  65  
  66    - type: input
  67      id: nip
  68      attributes:
  69        label: Related NIP
  70        description: If this relates to a Nostr Implementation Possibility, provide the NIP number
  71        placeholder: "NIP-XX"
  72  
  73    - type: dropdown
  74      id: impact
  75      attributes:
  76        label: Scope of Impact
  77        description: How significant is this feature?
  78        options:
  79          - Minor enhancement (small quality-of-life improvement)
  80          - Moderate feature (adds useful capability)
  81          - Major feature (significant new functionality)
  82          - Breaking change (requires migration or config changes)
  83      validations:
  84        required: true
  85  
  86    - type: dropdown
  87      id: contribution
  88      attributes:
  89        label: Willingness to Contribute
  90        description: Would you be willing to help implement this feature?
  91        options:
  92          - "Yes, I can submit a PR"
  93          - "Yes, I can help with testing"
  94          - "No, but I can provide more details"
  95          - "No"
  96      validations:
  97        required: true
  98  
  99    - type: textarea
 100      id: additional
 101      attributes:
 102        label: Additional Context
 103        description: |
 104          Any other context, mockups, examples, or references that help explain the feature.
 105  
 106          For protocol features, include example event structures or message flows if applicable.
 107  
 108    - type: checkboxes
 109      id: checklist
 110      attributes:
 111        label: Checklist
 112        options:
 113          - label: I have searched existing issues and this is not a duplicate
 114            required: true
 115          - label: I have described the problem this feature solves
 116            required: true
 117          - label: I have checked if this relates to an existing NIP
 118            required: false
 119