en/glep/glep-0028.txt

GLEP: 28
Title: "Expiration" of inactive GLEPs
Version: $Revision: 1.3 $
Last-Modified: $Date: 2004/10/20 20:40:10 $
Author: Grant Goodyear <g2boojum@gentoo.org>
Status: Informational
Type: Standards Track
Content-Type: text/x-rst
Created: 2-Jun-2004
Post-History: 2-Jun-2004, 20-Jul-2004


Status
======

This GLEP was approved on 14-Jun-2004.

Abstract
========

To keep inactive GLEPs from lingering in a limbo state, Draft GLEPs that have
been inactive for more than 60 days and Accepted GLEPs that have been
inactive for over six months should be marked "deferred" due to inactivity
(and, presumably, lack of interest).


Motivation
==========

Right now a number of GLEPs have been in "Draft" status for as much as 11
months, with no obvious activity occurring to either submit the GLEP for
approval or to withdraw it as a bad idea.  Similarly, although it has not yet
really been a problem, Accepted GLEPs also have the potential to linger
without any indication that they are moving forward toward being finalized.
Having a "timeout" period for GLEPs should spur GLEP authors to remain active
in either getting support for or finalizing  GLEPs.

Specification
=============


If a Draft GLEP is inactive for more than 60 days or an Accepted GLEP is
inactive for more than six months, then it would be marked as "deferred" on
the main `GLEP page`_.  Inactivity is defined simply as the GLEP author has
not contacted the GLEP editors with either an update or a request to submit
the GLEP for approval (in the case of a Draft GLEP) or a request that the GLEP
be marked final (in the case of an Accepted GLEP).

.. _GLEP page: http://glep.gentoo.org 

A GLEP that has been marked "deferred" may be reopened by request of the GLEP
author or a Gentoo manager, as long as that request also includes either an
update or a note submitting the GLEP for approval or finalization.

Rationale
=========

The GLEP editors have better things to do than chase after GLEP authors to
find out how their GLEPs are progressing.  This GLEP should help.


Backwards Compatibility
=======================

Not really an issue here.


Copyright
=========

This document has been placed in the public domain.
1	GLEP: 28
2	Title: "Expiration" of inactive GLEPs
3	Version: $Revision: 1.3 $
4	Last-Modified: $Date: 2004/10/20 20:40:10 $
5	Author: Grant Goodyear <g2boojum@gentoo.org>
6	Status: Informational
7	Type: Standards Track
8	Content-Type: text/x-rst
9	Created: 2-Jun-2004
10	Post-History: 2-Jun-2004, 20-Jul-2004
11
12
13	Status
14	======
15
16	This GLEP was approved on 14-Jun-2004.
17
18	Abstract
19	========
20
21	To keep inactive GLEPs from lingering in a limbo state, Draft GLEPs that have
22	been inactive for more than 60 days and Accepted GLEPs that have been
23	inactive for over six months should be marked "deferred" due to inactivity
24	(and, presumably, lack of interest).
25
26
27	Motivation
28	==========
29
30	Right now a number of GLEPs have been in "Draft" status for as much as 11
31	months, with no obvious activity occurring to either submit the GLEP for
32	approval or to withdraw it as a bad idea. Similarly, although it has not yet
33	really been a problem, Accepted GLEPs also have the potential to linger
34	without any indication that they are moving forward toward being finalized.
35	Having a "timeout" period for GLEPs should spur GLEP authors to remain active
36	in either getting support for or finalizing GLEPs.
37
38	Specification
39	=============
40
41
42	If a Draft GLEP is inactive for more than 60 days or an Accepted GLEP is
43	inactive for more than six months, then it would be marked as "deferred" on
44	the main `GLEP page`_. Inactivity is defined simply as the GLEP author has
45	not contacted the GLEP editors with either an update or a request to submit
46	the GLEP for approval (in the case of a Draft GLEP) or a request that the GLEP
47	be marked final (in the case of an Accepted GLEP).
48
49	.. _GLEP page: http://glep.gentoo.org
50
51	A GLEP that has been marked "deferred" may be reopened by request of the GLEP
52	author or a Gentoo manager, as long as that request also includes either an
53	update or a note submitting the GLEP for approval or finalization.
54
55	Rationale
56	=========
57
58	The GLEP editors have better things to do than chase after GLEP authors to
59	find out how their GLEPs are progressing. This GLEP should help.
60
61
62	Backwards Compatibility
63	=======================
64
65	Not really an issue here.
66
67
68	Copyright
69	=========
70
71	This document has been placed in the public domain.