ceph/src/arrow/docs/source/developers/experimental_repos.rst

   1 .. Licensed to the Apache Software Foundation (ASF) under one
   2 .. or more contributor license agreements.  See the NOTICE file
   3 .. distributed with this work for additional information
   4 .. regarding copyright ownership.  The ASF licenses this file
   5 .. to you under the Apache License, Version 2.0 (the
   6 .. "License"); you may not use this file except in compliance
   7 .. with the License.  You may obtain a copy of the License at
   8
   9 ..   http://www.apache.org/licenses/LICENSE-2.0
  10
  11 .. Unless required by applicable law or agreed to in writing,
  12 .. software distributed under the License is distributed on an
  13 .. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  14 .. KIND, either express or implied.  See the License for the
  15 .. specific language governing permissions and limitations
  16 .. under the License.
  17
  18 Experimental repositories
  19 =========================
  20
  21 Apache Arrow has an explicit policy over developing experimental repositories
  22 in the context of
  23 `rules for revolutionaries <https://grep.codeconsult.ch/2020/04/07/rules-for-revolutionaries-2000-edition/>`_.
  24
  25 The main motivation for this policy is to offer a lightweight mechanism to
  26 conduct experimental work, with the necessary creative freedom, within the ASF
  27 and the Apache Arrow governance model. This policy allows committers to work on
  28 new repositories, as they offer many important tools to manage it (e.g. github
  29 issues, “watch”, “github stars” to measure overall interest).
  30
  31 Process
  32 +++++++
  33
  34 * A committer *may* initiate experimental work by creating a separate git
  35   repository within the Apache Arrow (e.g. via `selfserve <https://selfserve.apache.org/>`_)
  36   and announcing it on the mailing list, together with its goals, and a link to the
  37   newly created repository.
  38 * The committer *must* initiate an email thread with the sole purpose of
  39   presenting updates to the community about the status of the repo.
  40 * There *must not* be official releases from the repository.
  41 * Any decision to make the experimental repo official in any way, whether by merging or migrating, *must* be discussed and voted on in the mailing list.
  42 * The committer is responsible for managing issues, documentation, CI of the repository,
  43   including licensing checks.
  44 * The committer decides when the repository is archived.
  45
  46 Repository management
  47 +++++++++++++++++++++
  48
  49 * The repository *must* be under ``apache/``
  50 * The repository’s name *must* be prefixed by ``arrow-experimental-``
  51 * The committer has full permissions over the repository (within possible in ASF)
  52 * Push / merge permissions *must only* be granted to Apache Arrow committers
  53
  54 Development process
  55 +++++++++++++++++++
  56
  57 * The repository must follow the ASF requirements about 3rd party code.
  58 * The committer decides how to manage issues, PRs, etc.
  59
  60 Divergences
  61 +++++++++++
  62
  63 * If any of the “must” above fails to materialize and no correction measure
  64   is taken by the committer upon request, the PMC *should* take ownership
  65   and decide what to do.