cqfn / degit Goto Github PK

I think this project needs a PRD (Project Requirement Description or Product for commercial project) Document.
Project Requirement Description (PRD) is a high-level description document to clearly outline or specify the requirements of an open source project, including the vision, problem statement, features, functionality, capability, as well the assumption, dependency and constrains by technology, resource, or unknown, if there is any. Project Requirement Description (PRD) as a project blueprint serves as the guide for the ecosystem dev and technical teams to help build, release, the project, and evangelist for project adoption in the community.

Degit Project is suggested to adopt the BDD (Behavior driven development) test mythology. BDD is the next evolution of a TDD test methodology to produce the high quality code with agility and consistency. BDD is one of agile development technologies. It is an extension of TDD. the software test is driven by software behavior is defined and is described by a simple text language (English, or any nature languages) , Test Automation is golang-native and the test cases directly derived from the description. It provides clear communication mechanism among developers, tester, business, and users.
Golang testing framework is built to help you efficiently write expressive and comprehensive tests using Behavior-Driven Development (“BDD”) style. There are many Golang BDD test frameworks available in the open source community: Goconvey, Goblin, Cukumber Ginkgo andGomega, One of the widely adopted Golang Test Framework Gingo (https://github.com/onsi/ginkgo) is known used in many Go centric popular open source projects.

It would be great if decentralized ownership could be added to this concept.
Approving merges to master using consensus instead of a single man's opinion.
Incentives and rough concept are described in my short paper: Trust Issues In Open Source and NPM

From the product perspective, the project needs to define some kinds of performance benchmark metrics requirement for the High Availability Capability of this project. HA (High Availability) , Per Wikipedia, High is a characteristic of a system which aims to ensure an agreed level of operational performance. it can be defined by a simple term: Availability = (minutes in a month - minutes of downtime) * 100/minutes in a month. (a better precise term will be availability % = AST - downtime/ AST %100. where AST is defined Agreed Service Time).
HA definition provide a clear guidelines to the system architect for the design goals and the system architecture in design.