Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 33 for Team (0.16 sec)

  1. doc/README.md

    	[http.Request]                     # symbol documentation; auto-linked as in Go doc strings
    	[#12345](/issue/12345)             # GitHub issues
    	[CL 6789](/cl/6789)                # Gerrit changelists
    
    ## For the release team
    
    At the start of a release development cycle, the contents of `next` should be deleted
    and replaced with those of `initial`. From the repo root:
    
        > cd doc
        > rm -r next/*
        > cp -r initial/* next
    
    Plain Text
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Fri Apr 26 21:24:36 GMT 2024
    - 1.9K bytes
    - Viewed (0)
  2. architecture-standards/0004-use-a-platform-architecture.md

    An architecture module is responsible for providing some coherent set of features and:
    
    - Provides a set of APIs and services for use from outside the module.
    - Has a private implementation.
    - Is owned by a single team. A team may own multiple architecture modules.
    
    The modules are arranged into several different "Gradle platforms".
    A Gradle platform is a logical distribution that provides support for a specific kind of automation.
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:56:13 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  3. architecture-standards/0001-use-architectural-decision-records.md

    * Review in Google Doc is not as simple as a PR code review in GitHub
    
    ## Decision
    
    The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.
    
    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as *build tool* team) want to promote.
    * To avoid asking the same thing multiple times during code review.
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:43:19 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  4. architecture/standards/0001-use-architectural-decision-records.md

    * Review in Google Docs is not as simple as a PR code review in GitHub
    
    ## Decision
    
    The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow.
    
    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as the *build tool* team) want to promote.
    * To avoid asking the same thing multiple times during code review.
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  5. architecture/standards/0004-use-a-platform-architecture.md

    An architecture module is responsible for providing a coherent set of features and:
    
    - Provides a set of APIs and services for use from outside the module.
    - Has a private implementation.
    - Is owned by a single team. A team may own multiple architecture modules.
    
    The modules are arranged into several different "Gradle platforms".
    A Gradle platform is a logical distribution that provides support for a specific kind of automation.
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sun Feb 25 22:19:29 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  6. manifests/charts/README.md

    - Better security: separate Istio components reside in different namespaces, allowing different teams or
    roles to manage different parts of Istio. For example, a security team would maintain the
    root CA and policy, a telemetry team may only have access to Prometheus,
    and a different team may maintain the control plane components (which are highly security sensitive).
    
    The install is organized in 'environments' - each environment consists of a set of components
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Wed Feb 07 17:53:24 GMT 2024
    - 6.7K bytes
    - Viewed (0)
  7. maven-core/src/site/apt/configuration-management.apt

    ~~ KIND, either express or implied.  See the License for the
    ~~ specific language governing permissions and limitations
    ~~ under the License.
    
     -----
     Maven configuration management
     -----
     The Maven Team
     -----
    
    Configuration levels in maven
    
     In maven configuration control happens on four differ levels: the site level, the group level,
    Plain Text
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Mar 18 00:24:53 GMT 2024
    - 5.8K bytes
    - Viewed (0)
  8. CONTRIBUTING.md

    just getting started, GitHub has a
    [how-to](https://help.github.com/articles/using-pull-requests/).
    
    TensorFlow team members will be assigned to review your pull requests. Once the
    pull requests are approved and pass continuous integration checks, a TensorFlow
    team member will apply `ready to pull` label to your change. This means we are
    working on getting your pull request submitted to our internal repository. After
    Plain Text
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Thu Mar 21 11:45:51 GMT 2024
    - 15.6K bytes
    - Viewed (0)
  9. .github/CODEOWNERS

    ## GitHub docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
    ##
    ## CODEOWNERS style rules:
    ## 1. Prefer team ownership over individual user ownership.
    ## 2. GBT-related team should be listed first.
    ## 3. Try to keep paths alphabetically sorted within visual groups.
    ## 4. List individual owners last.
    ##
    
    # bt-unassigned-maintainers must be the first owner
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 15:52:09 GMT 2024
    - 9.8K bytes
    - Viewed (0)
  10. docs/de/docs/history-design-future.md

    Es wird gegenüber früheren Alternativen gewählt, da es für viele Anwendungsfälle besser geeignet ist.
    
    Viele Entwickler und Teams verlassen sich bei ihren Projekten bereits auf **FastAPI** (einschließlich mir und meinem Team).
    
    Dennoch stehen uns noch viele Verbesserungen und Funktionen bevor.
    
    **FastAPI** hat eine große Zukunft vor sich.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Sat Mar 30 18:10:48 GMT 2024
    - 4.8K bytes
    - Viewed (0)
Back to top