/[dep]/web/deps/dep0.mdwn
ViewVC logotype

Diff of /web/deps/dep0.mdwn

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 77 by zack, Sun Jul 26 17:25:49 2009 UTC revision 81 by zack, Sun Jul 26 18:01:18 2009 UTC
# Line 37  easily assess whether they should use sa Line 37  easily assess whether they should use sa
37  because it's difficult to know whether it adjusts to the consensus  because it's difficult to know whether it adjusts to the consensus
38  reached during the discussion period.  reached during the discussion period.
39    
40  As our normative documents rely on wide adoption of a practice before  Our normative documents rely on wide adoption of a practice before
41  documenting it, and adopters can be reluctant to make use of it before a  documenting it, and adopters can be reluctant to make use of it before a
42  clear indication that a practice has some consensus behind it, this  clear indication that a practice has some consensus behind it. This
43  creates a hard to break loop that this process hopes to alleviate, by  creates a hard to break loop that this process hopes to alleviate, by
44  providing a mechanism to reflect the status of each proposal, including  providing a mechanism to reflect the status of each proposal, including
45  whether it has reached consensus or not.  whether it has reached consensus or not.
# Line 162  be met: Line 162  be met:
162    
163  Once accepted:  Once accepted:
164    
165  * the final version of the DEP text is archived in a central place  * the final version of the DEP text is archived on
166    (VCS on alioth, plus web page generated from that) for future    <http://dep.debian.net> for future reference
   reference  
167  * if applicable, the proposed DEP change is integrated into  * if applicable, the proposed DEP change is integrated into
168    authoritative texts such as policy, developer's reference, etc.    authoritative texts such as policy, developer's reference, etc.
169    
# Line 176  A DEP can become REJECTED in the followi Line 175  A DEP can become REJECTED in the followi
175    explicitly acknowledge so    explicitly acknowledge so
176  * there are no modifications to a DEP in DRAFT state for 6 months or  * there are no modifications to a DEP in DRAFT state for 6 months or
177    more    more
178  * there is no consensus that the implementation of a DEP in CANDIDATE  * there is no consensus either on the draft text or on the fact that
179    state is working satisfactorily    the implementation is working satisfactorily
180    
181  #### ACCEPTED -> OBSOLETE: no longer relevant  #### ACCEPTED -> OBSOLETE: no longer relevant
182    
# Line 191  A DEP can become OBSOLETE when it is no Line 190  A DEP can become OBSOLETE when it is no
190    
191  In one of these states, no further actions are needed.  In one of these states, no further actions are needed.
192    
193    It is recommended that DEPs in one of these states carry a reason
194    describing why they have moved to such a state.
195    
196    
197  What the drivers should do  What the drivers should do
198  --------------------------  --------------------------
199    
200  The additional, hopefully small, burden of the DEP process falls on the  The only additional burden of the DEP process falls on the shoulders of its
201  shoulders of its drivers. They have to take care of all the practical  drivers. They have to take care of all the practical work of writing
202  work of writing and maintaining the draft, so that everyone else can  and maintaining the text, so that everyone else can just continue
203  just continue discussing things over e-mail as before.  Driver's burden  discussing things as before.  Driver's burden can be summarized as:
 can be summarized as:  
204    
205  * Write the draft.  * Write the draft text and update it during discussion.
 * Update the draft during discussion.  
206  * Determine when (rough) consensus in discussion has been reached.  * Determine when (rough) consensus in discussion has been reached.
207  * Implement, or find volunteers to implement.  * Implement, or find volunteers to implement.
208  * Determine when consensus of implementation success has been reached,  * Determine when consensus of implementation success has been reached,
209    when the testing of the available implementation has been satisfactory.    when the testing of the available implementation has been satisfactory.
210  * Update the DEP with progress updates at suitable intervals, until the  * Update the DEP with progress updates at suitable intervals, until the
211    DEP has been accepted.    DEP has been accepted (or rejected).
212    
213  If the drivers go missing in action, other people may step in and  If the drivers go missing in action, other people may step in and
214  courteously take over the driving position.  courteously take over the driving position.
215    
216    **Note**: the drivers can of course participate in the discussion as
217    everybody else, but have no special authority to impose their ideas to
218    others. <q>DEP gives pencils, not hammers.</q>
219    
220    
221  Format and content  Format and content
222  ------------------  ------------------
# Line 232  start with a paragraph of the following Line 236  start with a paragraph of the following
236  * Abstract: a short paragraph (formatted as the long Description in  * Abstract: a short paragraph (formatted as the long Description in
237    debian/control)    debian/control)
238    
239    (Additionally, REJECTED DEPs can carry a "Reason:" field describing
240    why they were rejected.)
241    
242  The rest of the file is free form. If the DEP is kept in a wiki, using  The rest of the file is free form. If the DEP is kept in a wiki, using
243  its markup syntax is, of course, a good idea.  its markup syntax is, of course, a good idea.
244    
# Line 252  License Line 259  License
259    
260  The DEP must have a license that is DFSG free. You may choose the  The DEP must have a license that is DFSG free. You may choose the
261  license freely, but the "Expat" license is recommended. The  license freely, but the "Expat" license is recommended. The
262  official URL for it is http://www.jclark.com/xml/copying.txt and  official URL for it is <http://www.jclark.com/xml/copying.txt> and
263  the license text is:  the license text is:
264    
265      Copyright (c) <year>  <your names>      Copyright (c) <year>  <your names>
# Line 276  the license text is: Line 283  the license text is:
283      TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE      TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
284      SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.      SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
285    
286  The justification for this recommendation is that this license is the  The justification for this recommendation is that this license is one
287  most permissive of the well-known licenses. By using this license, it is  of the most permissive of the well-known licenses. By using this
288  easy to copy parts of the DEP to other places, such as documentation for  license, it is easy to copy parts of the DEP to other places, such as
289  Debian development or embedded in individual packages.  documentation for Debian development or embedded in individual
290    packages.
291    
292    
293    
# Line 321  License Line 329  License
329  The following copyright statement and license apply to DEP0 (this  The following copyright statement and license apply to DEP0 (this
330  document).  document).
331    
332  Copyright (c) 2008  Stefano Zacchiroli, Adeodato Simó, Lars Wirzenius  Copyright (c) 2008-2009  Stefano Zacchiroli, Adeodato Simó, Lars Wirzenius
333    
334  Permission is hereby granted, free of charge, to any person obtaining  Permission is hereby granted, free of charge, to any person obtaining
335  a copy of this software and associated documentation files (the  a copy of this software and associated documentation files (the
# Line 342  CLAIM, DAMAGES OR OTHER LIABILITY, WHETH Line 350  CLAIM, DAMAGES OR OTHER LIABILITY, WHETH
350  TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE  TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
351  SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.  SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
352    
   
   
   
 TODO  
 ----  
   
 * Figure out how to mark up a DEP file in wiki.debian.org's syntax  
   in such a way as to make the initial RFC822-style paragraph format  
   sensibly, but without making it require much or any wiki markup.  
 * Mention somewhere explicitly that the location of the index is  
   <http://dep.debian.net>.  
   
   
353  Changes  Changes
354  -------  -------
355    
356  * 2009-07-26:  * 2009-07-26:
357    [ Stefano Zacchiroli ]    [ Zack, Dato, Lars]
358    * Re-word state description: describe separately states and    * Re-word state description: describe separately states and
359      transitions.      transitions.
360    * Rename "DROPPED" status to "REJECTED"; inhibit "resurrection" of    * Rename "DROPPED" status to "REJECTED"; inhibit "resurrection" of
361      REJECTED DEPs.      REJECTED DEPs.
362      * mention that dep.debian.net is the central archival place
363      * stress that DEPs give no special powers to drivers, in the "driver
364        role" section
365    
366  * 2008-06-12:  * 2008-06-12:
367    [ Lars Wirzenius ]    [ Lars Wirzenius ]
Legend:
Removed from v.77  
changed lines
  Added in v.81
  ViewVC Help
Powered by ViewVC 1.1.5