Skip to content

Commit

Permalink
new template proposal
Browse files Browse the repository at this point in the history
  • Loading branch information
mageddo committed Aug 27, 2024
1 parent c85cad3 commit f81e7f2
Showing 1 changed file with 38 additions and 7 deletions.
45 changes: 38 additions & 7 deletions .github/ISSUE_TEMPLATE/feature-request.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,47 @@ assignees: ''

---

## What is Happening
## Summary

What is the actual behavior and lacks which without that feature, and what's the fallback (if there is one)
while this feature is not implemented yet.
> A short description of what it is
## What is Expected
Example:

Please describe the wanted behavior with details of how it could work.
> Provide a solver which can solve from previously configured DNS records.
## Goals

## Changes (Optional)
> What is supposed to do in short.
Steps to implement the desired feature.
Example

> A simple, static DNS server
## Non-Goals

> What people would think it is supposed to do, but it is not?
Example
> * Not to implement a full and complex DNS server
## Motivation

> Why it's a feature to be considered?
Example:

> People can use DPS for static DNS entries instead of use /etc/hosts or something like.
## Description

> Explain the feature details and how it would work, usecases, examples, snippets of code, inputs and outputs, etc.
Example

> ### Storage
>
> DNS records will be stored at the existing DPS config file.
>
> ### DNS Records
> * It will have support to A, AAAA and CNAME entries.
> * Also, TTL by record will be supported

0 comments on commit f81e7f2

Please sign in to comment.