move to authoring section

Author: AlexisBRENON

airflow-core/docs/authoring-and-scheduling/index.rst

@@ -33,6 +33,7 @@ It's recommended that you first review the pages in :doc:`core concepts </core-c
     connections
     dynamic-task-mapping
     assets
+    ownership
 
 .. _scheduling-section:
 

airflow-core/docs/authoring-and-scheduling/ownership.rst

@@ -0,0 +1,38 @@
+ .. 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
+
+ ..   http://www.apache.org/licenses/LICENSE-2.0
+
+ .. Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+
+
+.. _ownership:
+
+Ownership
+=========
+
+When multiple users are authoring the DAGs of a single Airflow instance, it can be tedious to know who is responsible of what.
+One way to overcome this is to attach owners, allowing users to know who is in charge of a particular DAG or Task.
+
+This ownership is split in two parts:
+
+1. at the Task level, through the ``owner`` argument of the :class:`~airflow.models.baseoperator.BaseOperator`;
+2. at the DAG level, to customize the UI through the ``owner_links`` definition.
+
+In Airflow 2, the list of owners was displayed in the DAG list view, not taking into account the ``owner_links`` value.
+Starting with Airflow 3.1, the owners are displayed in the header of the DAG view.
+Hence, a clickable link (that may be a instant messaging handle or a mailto link) is displayed for any owner matching an item defined in the ``owner_links`` dictionary is converted to a clickable link.
+
+If you don't need the Task level granularity, and want to define a set of owners at the DAG level, you may leverage the :ref:` \`\`default_args\`\` argument <concepts-default-arguments>` to apply the same set of owners to every tasks in the DAG.
+
+

airflow-core/docs/core-concepts/dags.rst

@@ -686,23 +686,6 @@ This is especially useful if your tasks are built dynamically from configuration
     Here's a [url](www.airbnb.com)
     """
 
-.. _concepts:dags-ownership:
-
-Ownership
-~~~~~~~~~
-
-In addition to these documentation and notes, you are also able to link a DAG with a set of owners.
-This way the DAG users may be able to reach out the right set of people when needed.
-
-This ownership is split in two parts:
-
-1. at the :ref:`Task level <concepts:task-owner>` through the ``owner`` definition;
-2. at the DAG level to customize the UI through the ``owner_links`` definition.
-
-Each DAG collects the set of owners from its task set, and display it on the DAGs view UI.
-Any owner matching an item defined in the ``owner_links`` dictionary is converted to a clickable link (that may be a instant messaging handle or a mailto link).
-
-
 Packaging dags
 --------------
 

airflow-core/docs/core-concepts/tasks.rst

@@ -236,12 +236,3 @@ This is achieved via the ``executor_config`` argument to a Task or Operator. Her
 
 The settings you can pass into ``executor_config`` vary by executor, so read the :doc:`individual executor documentation <executor/index>` in order to see what you can set.
 
-
-.. _concepts:task-owner:
-
-Ownership
----------
-
-It is possible to set an owner to a Task through the ``owner`` argument of the :class:`~airflow.models.baseoperator.BaseOperator`.
-This may allow DAGs users to know who is in charge of the development of the different parts of a DAG.
-The owner definition also allows to customize the DAG rendering in the DAGs view UI, :ref:`creating links <concepts:dags-ownership>` to contact the owners through the ``owner_links`` of the :class:`~airflow.models.dag.DAG`.