Searched full:guidelines (Results 1 – 25 of 745) sorted by relevance
12345678910>>...30
12 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…20 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…37 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…39 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…42 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…45 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…54 …ase style or not prefixed in a category, according to the Apple Coding Guidelines [objc-property-d…
9 * [Contributing Guidelines](#contributing-guidelines)10 * [General Pull Request Guidelines](#general-pull-request-guidelines)11 …* [Guidelines for Specific Contribution Categories](#guidelines-for-specific-contribution-categori…29 # Contributing Guidelines32 provide guidelines with the goal of enabling community contributions while still35 Please note that while these guidelines may seem onerous to some developers,38 Before we describe project-specific guidelines, we recommend that external47 [Tensorflow Contributing Guidelines](https://github.com/tensorflow/tensorflow/blob/master/CONTRIBUT…49 ## General Pull Request Guidelines66 contributor is the way to go, please follow these guidelines from[all …]
4 just a few small guidelines you need to follow.13 ## Community Guidelines16 Guidelines](https://opensource.google.com/conduct/).
7 compatibility guidelines. Code should not open ``namespace absl`` as that8 conflicts with Abseil's compatibility guidelines and may result in breakage.20 See `the full Abseil compatibility guidelines <https://
12 Extensive contribution guidelines are available in the repository at21 guidelines`_, do not report them in the public issue tracker.23 .. _`security reporting guidelines`: https://cryptography.io/en/latest/security/
4 just a few small guidelines you need to follow.24 ## Community Guidelines27 [Google's Open Source Community Guidelines](https://opensource.google.com/conduct/).
3 title: Bug disclosure guidelines6 permalink: /getting-started/bug-disclosure-guidelines/9 ## Bug Disclosure Guidelines
4 just a few small guidelines you need to follow.25 ## Community Guidelines28 [Google's Open Source Community Guidelines](https://opensource.google.com/conduct/).
4 just a few small guidelines you need to follow.25 ## Community Guidelines28 Guidelines](https://opensource.google/conduct/).
4 just a few small guidelines you need to follow.25 ## Community Guidelines28 Guidelines](https://opensource.google.com/conduct/).
1 # Contributing guidelines7 - Read [contributing guidelines](CONTRIBUTING.md).10 …s are consistent with the [guidelines](https://github.com/tensorflow/tensorflow/blob/master/CONTRI…56 ### Contribution guidelines and standards60 make sure your changes are consistent with the guidelines and follow the63 #### General guidelines and philosophy for contribution
4 just a few small guidelines you need to follow.30 ## Community Guidelines33 [Google's Open Source Community Guidelines](https://opensource.google/conduct/).
1 Code Review Guidelines43 Guidelines for patch contributors77 Guidelines for all reviewers90 Guidelines for code owners133 guidelines for them:151 Guidelines for maintainers
29 - Make commits of logical units. See these general `Git guidelines`_ for50 More details may be found in the `Gerrit Signed-off-by Lines guidelines`_.74 - Follow the :ref:`Coding Style` and :ref:`Coding Guidelines`.204 - All binary components must follow the contribution guidelines (in particular223 .. _Git guidelines: http://git-scm.com/book/ch5-2.html225 .. _Gerrit Signed-off-by Lines guidelines: https://review.trustedfirmware.org/Documentation/user-si…
12 coding-guidelines14 code-review-guidelines
1 # Guidelines for submitting bugs:6 via the guidelines here:23 * All commits should adhere to the git commit message guidelines described
6 1. [Guidelines](#guidelines)26 ## Guidelines section in README.md files
1 # iperf3 Contribution Guidelines5 This page contains some guidelines for filing issues, pull requests,7 guidelines and not hard rules, and it is intended that common sense
1 This document describes the coding guidelines for this project.6 demonstrates the bug, it makes sense to follow the coding guidelines
1537 info["guidelines"] = [dict(x="1")]1544 info["guidelines"] = [dict(y="1")]1551 info["guidelines"] = [dict(x=0, y=0, angle=-1)]1557 info["guidelines"] = [dict(x=0, y=0, angle=361)]1564 info["guidelines"] = [dict(x=0, name=1)]1571 info["guidelines"] = [dict(x=0, color=1)]1577 info["guidelines"] = [dict(x=0, color="1 0, 0, 0")]1582 info["guidelines"] = [dict(x=0, color="1 0 0, 0")]1587 info["guidelines"] = [dict(x=0, color="1 0 0 0")]1593 info["guidelines"] = [dict(x=0, color=", 0, 0, 0")][all …]
5 //! [portability guidelines] are followed, the behavior should be identical no8 //! [portability guidelines]: ../struct.Poll.html#portability