Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5D587200BC0 for ; Tue, 15 Nov 2016 23:52:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5BD83160B03; Tue, 15 Nov 2016 22:52:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A6592160AF2 for ; Tue, 15 Nov 2016 23:52:47 +0100 (CET) Received: (qmail 2475 invoked by uid 500); 15 Nov 2016 22:52:46 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 2456 invoked by uid 99); 15 Nov 2016 22:52:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2016 22:52:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0345D1A93BB for ; Tue, 15 Nov 2016 22:52:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.479 X-Spam-Level: * X-Spam-Status: No, score=1.479 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id uQHDXCdxOPlO for ; Tue, 15 Nov 2016 22:52:45 +0000 (UTC) Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id D09AF5F4E7 for ; Tue, 15 Nov 2016 22:52:44 +0000 (UTC) Received: from Air-McShane.local ([62.100.100.218]) by mrelay.perfora.net (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LzZYq-1csa0d1f9e-014nXy for ; Tue, 15 Nov 2016 23:52:38 +0100 To: Apache ComDev From: Shane Curcuru Subject: Documented Process for archiving project/module? Message-ID: Date: Tue, 15 Nov 2016 23:52:34 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:MYxKwbZzv31iwES80/YpZeT2Lre3f8c4+8LtP9WsRVxNp60yasS jjXFrdURgAi80/vpYoBZ+kkGh6aBCJXW/MI4vq6ttNtIrGXIqjkgQOiCRPw98nw2zjWBNec RYTYzCu+NcC3jWnn4EnEys0Au2fxIXEr4ba9u61VoL3M5gAWu9OFOt39IxUPK+/rDNJRVuj q/QbgFJ5hTx1MyP95OPqg== X-UI-Out-Filterresults: notjunk:1;V01:K0:bj3YoQoqHRI=:uBAIi3FxqfI4N9+RzS4tFJ Tu9GkEeeoS5NWTNuhtDz9XL9/zndiDxL0fJYl3hqtLvEJQrS9k93O+Ihd6MD7aqYZaiXnNEd7 ylIvipRsy9Ude4vh6C+I7JOHqWt4IzWV6aBewyDfe5Zx0LFXLRt3722viv69qrtIhIcjtaFdY Tq46N93O7SHiBEJezTnICEfSQ6JJk7V7E1V1uqipglYaER9oqAMdHrJrqQ1klnVF5h2V1AV/g kepmG9S4i+T2/vZuxqimgJyUn1z/S/jlqU/7Kfpb2sMwVgjnB8WFgo7keHUT59hap+J4NBuS8 Y/VjhIVI5aw525X+JdVXhqeGTK6nYF5ND0jfknxpPWPwVCf7YPtztqzcki4vvS3oYCUgGqTLw UbFyzXp/b8MYFB8Tdp12xrXnDsPxfcPfpNAdF2A8hFcvm6COxMv5ppqp9dFPK0EHQTNrUhcrc DiDyA52LW/4fnt6OEc6Qk9ALaEg0zTA2cY0OZICZ85aSE7tYx2E7XyN5CUe921R2kWKmGtRaj iKyhEUAg6gbNikEVuynJhpj1Pi4IQTGvWWOx/ZxoxCWK2za6e3PMPgcW2v6i20qxIatqBBVW7 d7/hmekJtG9x5VmcA4csKTYA7HHihrCLVV6w5jCwKgSvOsZHgZDOMSo92hpYmpw7eisdXshvt oJWvqy1cYVNtRz05e5dBEKNBQ1/qt27nx2jEYiOQ/WK9nzg6hDcKjLoxnnYT6n/pBPiKCzkXY 2L2IcXhbLPQW8jpIW9+AI/t0ULqw+J0aFSbRuA== archived-at: Tue, 15 Nov 2016 22:52:48 -0000 Do we have an overview of the whole decision/action process around retiring each of a podling, a TLP, and a module/subproject within a TLP? I know the Attic has technical process documentation - but do we have a guide for the whole process, starting with either a community member (or the board!) noticing a project is mostly inactive, to actually deciding it's not active enough to be maintained, etc.? The board regularly sees or hears about projects or modules that aren't active, and want to retire. But we aren't consistent across the ASF at communicating that status to the larger *public* community - sometimes it's just the PMC list that decides and moves to the board. Just an idea... - Shane --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@community.apache.org For additional commands, e-mail: dev-help@community.apache.org