This repository is intended to help fdgt users and maintainers and discuss major changes to the fdgt service.
An RFC, or Request For Comment, is a document outlining some change or enhancement to a system. RFCs have a long history in the engineering industry, namely in the ISOC's[1] IETF[2] [3], the principal technical development and standards-setting bodies for the Internet.
fdgt uses the "Structured Request For Comment" process proposed by Phil Calçado. This allows us to propose large changes that may affect the community and our users without hearing from them first.
To create a new RFC for fdgt, just open an issue! There is a template in place to help you create a great RFC.
Things that should be an RFC: breaking changes and new features should always come in as RFCs. Some smaller new features may be added without an RFC (think quality of life features), but most should make their way into development via the RFC process.
Things that should not be an RFC: bugs, technical support questions, and requests for new code examples. Bugs and technical support questions should all be created as issues on the fdgt-apis/api repository. Requests for new code examples should be created as issues on the fdgt-apis/website repository.
[1] ISOC - Internet Society: https://en.wikipedia.org/wiki/Internet_Society [2] IETF - Internet Engineering Task Force on Wikipedia: https://en.wikipedia.org/wiki/Internet_Engineering_Task_Force [3] Request for Comments on Wikipedia: https://en.wikipedia.org/wiki/Request_for_Comments