Martin Sebor wrote:
> robert burrell donkin wrote:
> >Martin Sebor wrote:
> >>Rodent of Unusual Size wrote:
> >>
> >>>APACHE INCUBATOR PROJECT STATUS: -*-indented-text-*-
> >>>Last modified at [$Date: 2005-01-20 01:12:13 -0500 (Thu, 20 Jan
> >
> >2005) $]
> >
> >>It has been pointed out a couple of times in the past (see the posts
> >>below) that this status report is out of date. In an effort to prevent
> >>this from causing confusion in the future I would like to propose that
> >>the incubator status file not be posted here unless it is up to date
> >>and unless it has changed since the last time it was posted.
> >
> >i wonder whether one of ken's reasons for automating this posting was to
> >encourage folks to keep the status up-to-date.
> 
> I suspect you are right. The problem is that it is not being kept up
> to date and that people such as myself who are new to this community
> and trying to learn have been confused by it.
> 
> >
> >IMO it's better to fix the source of the confusion than to shoot the
> >messenger.
> 
> That certainly wasn't my goal :)
> 
> >if you've found some errors in the status page then these
> >need to
> >be fixed. if you don't have the required karma then i'd recommend
> >submitting
> >a patch in JIRA.
> 
> I will be happy to put together a patch but being new here I'm afraid
> I'm not sure that my proposed fix is correct. Let me post it here for
> review before I put it in Jira. Comments are welcome!

Thanks Martin. It is unfortunate that people have not
kept the website documents up-to-date and that this
top-level "STATUS" document suffers from the same issue.

The only way that things will get fixed is for people
continue to raise such issues and attempt to fix it.
Thanks.

The note that you have patched below is something
that is listed under the "Resolved Issues" section.
In my opinion that stuff should have been long ago
moved to another file because it is old resolved issues.
Those notes are not completely relevant now.

Lets backup a bit.

You have raised two completely separate issues in the
one email ...

1) The STATUS file for the Incubator project as a whole
is way out-of-date and is confusing.

2) The requirements for each incubating project to
declare their status, are misleading and confusing.

These should be treated as two separate email topics.

-David

> Index: /build/sebor/incubator/STATUS
> ===================================================================
> --- /build/sebor/incubator/STATUS     (revision 345672)
> +++ /build/sebor/incubator/STATUS     (working copy)
> @@ -43,11 +43,11 @@
>      o Coming up with a set of bylaws for the project
>        (http://mail-archives.apache.org/eyebrowse/[EMAIL 
> PROTECTED]&by=thread&from=517190)
>  
> -    o All projects under incubation must use a STATUS file (or a
> -      status.xml file if the project prefers XML) that contains
> -      information the PMC needs about the project. This file must
> -      live at the root of the project cvs module
> -      (http://mail-archives.apache.org/eyebrowse/[EMAIL 
> PROTECTED]&by=thread&from=504543)
> +    o All projects under incubation must maintain a status Web page that
> +      contains information the PMC needs about the project. The page is
> +      generated from a .html or .cwiki source file which resides in the
> +      following Subversion subdirectory
> +      
> http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/
>  
>      o Projects under incubation should display appropriate "disclaimers"
>        so that it is clear that they are, indeed, under incubation
> @@ -80,10 +80,8 @@
>  
>    -- Who has been identified as the mentor for the incubation?
>  
> -  -- Are they tracking progress in the file
> +  -- Are they tracking progress on the status Web page?
>  
> -      incubator/projects/{project_name}/STATUS
> -
>  Copyright:
>  
>    -- Have the papers that transfer rights to the ASF been received?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to