- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 138 for team (0.13 sec)
-
architecture/standards/0001-use-architectural-decision-records.md
ADRs can be written by any team. Like code, they should be reviewed by any other relevant teams. The goal is not to *own* a decision, but to *share* it with other teams, and improve the build tool together. ### Format The format for ADR should follow this template: ```markdown # ADR-000X - Title ## Date 20YY-MM-DD ## Context
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
SECURITY.md
for the past five days please contact the security team directly: - Primary security coordinator: ******@****.*** - Secondary coordinator: ******@****.*** - If you receive no response: ******@****.*** ### Disclosure Process MinIO uses the following disclosure process: 1. Once the security report is received one member of the security team tries to verify and reproduce
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 2.2K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/junit/junit/4.13.1/junit-4.13.1.pom
<scm> <connection>scm:git:git://github.com/junit-team/junit4.git</connection> <developerConnection>scm:git:******@****.***:junit-team/junit4.git</developerConnection> <url>https://github.com/junit-team/junit4</url> <tag>r4.13.1</tag> </scm> <issueManagement> <system>github</system> <url>https://github.com/junit-team/junit4/issues</url> </issueManagement> <ciManagement>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 24.5K bytes - Viewed (0) -
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).
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
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 08 11:36:15 GMT 2024 - Last Modified: Sun Feb 25 22:19:29 GMT 2024 - 4.5K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.ci-reporting.gradle.kts
* failing tasks only, to not use up unnecessary disk space on Team City. This also improves the performance of * artifact publishing by reducing the artifacts and packaging reports that consist of multiple files. * * Reducing the number of reports also makes it easier to find the important ones when analysing a failed build in * Team City. */
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Jul 11 06:57:51 GMT 2023 - 2K bytes - Viewed (0) -
architecture/README.md
This directory contains documentation that describes Gradle's architecture and how the various pieces fit together and work. ## Architecture decision records (ADRs) The Gradle team uses ADRs to record architectural decisions that the team has made. See [Architecture decisions records](standards) for the list of ADRs.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.4K bytes - Viewed (0) -
ci/devinfra/README.md
Maintainer: TensorFlow DevInfra Issue Reporting: File an issue against this repo and tag [@devinfra](https://github.com/orgs/tensorflow/teams/devinfra) ******************************************************************************** A directory for build and CI related scripts and jobs managed by the TensorFlow
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Tue Jun 06 21:00:01 GMT 2023 - 732 bytes - Viewed (0) -
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 May 07 11:14:38 GMT 2024 - Last Modified: Fri Apr 26 21:24:36 GMT 2024 - 1.9K bytes - Viewed (0) -
.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 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 15:52:09 GMT 2024 - 9.8K bytes - Viewed (0)