OptimisticDev/rfcs
2
1
Fork 0
forked from kaboom-standards-organization/rfcs
Code Pull requests Activity

RFC 0000: Explain what soft/hard requirements are

Browse source
This commit is contained in:
OptimisticDev 2024-10-18 00:06:09 +00:00
parent d667ac0152
commit e510f5fba8
Signed by: OptimisticDev
SSH key fingerprint: SHA256:efAXeDMyuFt1iia2xaqlrcHPlsXcjQEWNA2tmvVTqK8
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
rfcs/0000-Genesis_RFC.md
View file

@ -73,8 +73,8 @@ You must only use proper grammar, proper casing, proper casing and proper punctu
You must not use expletives (swearing) in RFCs. You must not use expletives (swearing) in RFCs.
You must keep the use of informal language to a minimum. You must keep the use of informal language to a minimum.
Hard requirements must be explicitly stated with the use of "must" or "must not". Hard requirements (HAVE to be followed, no matter what) must be explicitly stated with the use of "must" or "must not".
Soft requirements must be explicitly stated with the use of "should" or "should not". Soft requirements (RECOMMENDED to follow, but not absolutely required) must be explicitly stated with the use of "should" or "should not".
Please try to keep the use of complex words to a minimum. Please try to keep the use of complex words to a minimum.
Try to only use simple language, as the Kaboom community has a large amount of non-native English speakers with varying levels of proficiency who may want to participate in this project too and must be denied from doing so by something like a language barrier. Try to only use simple language, as the Kaboom community has a large amount of non-native English speakers with varying levels of proficiency who may want to participate in this project too and must be denied from doing so by something like a language barrier.