TASK Proposal [Task ID]: [Short task name]

Proposal Type: Task

• ID: [Task ID]
• Project: [Project Name]
• SubProject: [SubProject Name]
• Task: [Task Name]
• Bounty: [Total Agreed Bounty]
• Developers: [ Who Develops the task]
• Authors: [Who Writes the Task Proposal]
• Reviewers: [Who Reviews the Task Proposal]
• Voting Starts: [When is the DAO Vote starting DATE FORMAT: YYYY-MM-DD]
• Voting Deadline: [When is the DAO Vote Ending DATE FORMAT: YYYY-MM-DD]
• Tasks Deadline: [When is the Tasks Deadline DATE FORMAT: YYYY-MM-DD]

Abstract

The Abstract is a multi-sentence (short paragraph) technical summary.

Specification

The Specification section should describe the syntax and semantics of any task.

Why

Justification of doing this task

What

What will be done.

How

How will it be done.

Rationale

The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made.

Proof of Work

How to prove the work performed, what will be the delivery to consider it done.

Bounty Proposal

Author Bounty

Developers Bounty

Reviewers Bounty

Tasks Dependency

Here you add ID Tasks and Forum Links of the tasks it depends on for being ready to execute .

References

Not personal opinions usually a little of research and background which can give a strong justification.