From: Arran Cudbard-Bell Date: Thu, 3 Aug 2017 19:46:32 +0000 (-0400) Subject: Reflow to 100 columns X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f578ded0200693673edeb7f710959761b0946aba;p=thirdparty%2Ffreeradius-server.git Reflow to 100 columns --- diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index e10ec3f93cf..0da24d55edf 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -13,12 +13,10 @@ The GitHub issue tracker and mailing lists have a strict code of conduct. > will result in the individual being unsubscribed from the mailing lists and/or permanent > banishment from the GitHub repositories. -This code of conduct is simple to abide by, and is simple to -enforce. Unlike other codes of conduct, it does not require -participants to be explicitly "inclusive" or "accepting" of certain -topics. It requires participants to be *blind* to non-technical -subjects, as those subjects are explicitly off topic. The FreeRADIUS -community is inclusive by virtue of not being exclusionary. +This code of conduct is simple to abide by, and is simple to enforce. Unlike other codes of conduct, +it does not require participants to be explicitly "inclusive" or "accepting" of certain topics. It +requires participants to be *blind* to non-technical subjects, as those subjects are explicitly off +topic. The FreeRADIUS community is inclusive by virtue of not being exclusionary. ## 2. Expected Behaviour @@ -36,44 +34,36 @@ The following behaviours are expected and requested of all community members: ## 3. Our Limitations -We understand that when participants ask questions, their goal is to -obtain help from the community. Please be aware that the FreeRADIUS -community is not large. The project has three core members, none of -whom are dedicated 100% to FreeADIUS. The project has about seventy -modules, each of which has complex behavior. All of that code, test -cases, and documentation have to be updated with limited resources. - -FreeRADIUS is built mainly for Linux and BSD systems. It depends on -SQL (MySQL, Postgresl, Oracle, SQLite), LDAP, REST, Couchbase, -OpenDirectory, PAM, Redis, flat-text files, and SecurID. It has -plugins for Perl, Python, MRuby, and Lua. It supports multiple -authentication types, including PAP, CHAP, MS-CHAP, Digest, EAP-GTC, -EAP-MD5, EAP-MSCHAPv2, PEAP, TTLS, TLS, EAP-FAST, SIM, AKA, LEAP, PWD. -The TLS-based EAP methods work with TLSv1.0, TLSv1.1, and TLSv1.2. -The EAP methods interact with client EAP configurations on Linux, BSD, -MacOS, iOS, Android, and many other embedded systems. FreeRADIUS -supports NAS equipment from Cisco, HP, Juniper, Alcatel-Lucent, -Aerohive, Ruckus, Aruba, Mikrotik, and dozens of other vendors, across -thousands of individual products. - -Finally, the configuration files support a nearly infinite number of -ways to integrate and arrange the above technlogies. In short, we -cannot be experts in every part of the RADIUS ecosystem. - -We rely on well researched and technically sound contributions in -order to make the project a success. This means useful contributions -from you, the community. +We understand that when participants ask questions, their goal is to obtain help from the community. + Please be aware that the FreeRADIUS community is not large. The project has three core members, +none of whom are dedicated 100% to FreeADIUS. The project has about seventy modules, each of which +has complex behavior. All of that code, test cases, and documentation have to be updated with +limited resources. + +FreeRADIUS is built mainly for Linux and BSD systems. It depends on SQL (MySQL, Postgresl, Oracle, +SQLite), LDAP, REST, Couchbase, OpenDirectory, PAM, Redis, flat-text files, and SecurID. It has +plugins for Perl, Python, MRuby, and Lua. It supports multiple authentication types, including PAP, +CHAP, MS-CHAP, Digest, EAP-GTC, EAP-MD5, EAP-MSCHAPv2, PEAP, TTLS, TLS, EAP-FAST, SIM, AKA, LEAP, +PWD. The TLS-based EAP methods work with TLSv1.0, TLSv1.1, and TLSv1.2. The EAP methods interact +with client EAP configurations on Linux, BSD, MacOS, iOS, Android, and many other embedded systems. +FreeRADIUS supports NAS equipment from Cisco, HP, Juniper, Alcatel-Lucent, Aerohive, Ruckus, Aruba, +Mikrotik, and dozens of other vendors, across thousands of individual products. + +Finally, the configuration files support a nearly infinite number of ways to integrate and arrange +the above technlogies. In short, we cannot be experts in every part of the RADIUS ecosystem. + +We rely on well researched and technically sound contributions in order to make the project a +success. This means useful contributions from you, the community. ## 4. Unacceptable Behaviour -The main source of unacceptable behavior is community participants who -are unaware of the complexities outlined in the previous section. -They have questions, and they want answers. They believe that as the -experts, we can answer any and all questions about all possible -technologies which interact with FreeRADIUS. +The main source of unacceptable behavior is community participants who are unaware of the +complexities outlined in the previous section. They have questions, and they want answers. They +believe that as the experts, we can answer any and all questions about all possible technologies +which interact with FreeRADIUS. -That expectation is unreasonable. When that expectation turns to -entitlement and anger, it becomes unacceptable behaviour. +That expectation is unreasonable. When that expectation turns to entitlement and anger, it becomes +unacceptable behaviour. The following behaviours are unacceptable within our community: @@ -87,11 +77,10 @@ The following behaviours are unacceptable within our community: ## 5. Consequences of Unacceptable Behaviour -Where unacceptable behaviour is noted and the community participant -informed of behaviour and next steps, the community participant is -expected to comply immediately. Arguing with the warnings is deemed -"off topic" for the community (see section 1), and is seen as a -continuance of the unacceptable behavior. +Where unacceptable behaviour is noted and the community participant informed of behaviour and next +steps, the community participant is expected to comply immediately. Arguing with the warnings is +deemed "off topic" for the community (see section 1), and is seen as a continuance of the +unacceptable behavior. The community organizers will take any action they deem appropriate, which may include permanent expulsion from the community using appropriate mechanisms.