Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for Ownership (0.23 sec)

  1. .github/CODEOWNERS

    ##
    ## 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
    # All directories that are not explicitly listed below are considered
    # unassigned. This means that the ownership may be unknown, lost or
    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)
  2. .teamcity/mvnw.cmd

    @REM Licensed to the Apache Software Foundation (ASF) under one
    @REM or more contributor license agreements.  See the NOTICE file
    @REM distributed with this work for additional information
    @REM regarding copyright ownership.  The ASF licenses this file
    @REM to you under the Apache License, Version 2.0 (the
    @REM "License"); you may not use this file except in compliance
    @REM with the License.  You may obtain a copy of the License at
    @REM
    Batch File
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Feb 26 01:48:39 GMT 2020
    - 6.5K bytes
    - Viewed (0)
  3. architecture/standards/0005-introduce-core-ui-architecture-module.md

    This ADR does not specify the owner of this new architecture module. However, as a separate module, it can be assigned ownership independently of the other core services.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    - Introduce the module and move the services and their implementations.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Mon Mar 04 23:19:15 GMT 2024
    - 1.3K bytes
    - Viewed (0)
  4. architecture/standards/0004-use-a-platform-architecture.md

    ## Date
    
    2024-02-07
    
    ## Context
    
    The Gradle code base is essentially a large monolith, without strong internal boundaries.
    This has a number of negative effects on productivity, including:
    
    - Unclear ownership of code.
    - Difficult to focus on one particular area.
    - Unintended coupling between areas of the code, including tests.
    
    ## Decision
    
    Organize the Gradle code base into a set of coarse-grained "architecture modules".
    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)
  5. LICENSE

          "control" means (i) the power, direct or indirect, to cause the
          direction or management of such entity, whether by contract or
          otherwise, or (ii) ownership of fifty percent (50%) or more of the
          outstanding shares, or (iii) beneficial ownership of such entity.
    
          "You" (or "Your") shall mean an individual or Legal Entity
          exercising permissions granted by this License.
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Tue Jan 23 11:07:23 GMT 2024
    - 23.1K bytes
    - Viewed (0)
  6. .teamcity/mvnw

    # Licensed to the Apache Software Foundation (ASF) under one
    # or more contributor license agreements.  See the NOTICE file
    # distributed with this work for additional information
    # regarding copyright ownership.  The ASF licenses this file
    # to you under the Apache License, Version 2.0 (the
    # "License"); you may not use this file except in compliance
    # with the License.  You may obtain a copy of the License at
    #
    Shell Script
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Feb 26 01:48:39 GMT 2020
    - 9.8K bytes
    - Viewed (0)
Back to top