Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Tue, 29 Jan 2013 16:12:34 +1100
From: David Crossley <crossley@apache.org>
To: general@incubator.apache.org
Subject: Re: Incubator voting status page
Message-ID: <20130129051234.GC3028@igg.local>
References: <20130125172612.GR3241@lp-shahaf.local>
 <5102C382.5080709@apache.org> <20130125231623.GA3081@lp-shahaf.local>
 <51035FBC.9060901@apache.org>
 <CALhtWkeHv8sc8_J_cUJ1e8CSEZTVgmn9PeFsWLeeR+JCfn2scg@mail.gmail.com>
 <5103E86C.7080300@e-reka.si> <20130127151736.GO3192@lp-shahaf.local>
 <51062742.1010209@apache.org> <20130128075800.GA2963@lp-shahaf.local>
 <51063D5F.3050504@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <51063D5F.3050504@apache.org>
User-Agent: Mutt/1.4.2.3i

Branko Čibej wrote:
> On 28.01.2013 08:58, Daniel Shahaf wrote:
> > Branko Čibej wrote on Mon, Jan 28, 2013 at 08:22:42 +0100:
> >> On 27.01.2013 16:17, Daniel Shahaf wrote:
> >>> Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100:
> >>>> On 26.01.2013 14:27, Benson Margulies wrote:
> >>>>>
> >>>>> Brane, are you currently using the pickled clutch metadata? If we just
> >>>>> need to add a field to it we can.
> >>>>
> >>>> Nope, I'm currently walking the incubator archive tree. The clutch
> >>>> metadata is in general good enough, since if clutch can generate
> >>>> target/current.ent, I can certainly get the information I need from
> >>>> that. ...

Clutch does not generate that file. It is handled by the Incubator
Ant build.xml 

> >>>> ... The only question is the conversion from
> >>>> list@podling.incubator.apache.org (which clutch knows about) to
> >>>> archive/podling.apache.org/list (which is where the podling mail
> >>>> archives will be in future) is consistent.
> >>>>
> >>> Yes, it is, for all *@p.i.a.o lists.
> >>
> >> Well, I've found an inconsistency while changing the scripts to parse
> >> the content/podlings.xml and content/projects/<podling-name>.xml.
> >> Onami's dev list is the old-style:
> >>
> >>     onami-dev@incubator.apache.org
> >>
> >> but its archive is new-style:
> >>
> >>     onami.incubator.apache.org/dev
> >>
> >> I don't want to special-case the script for this; can we make the
> >> archive consistent with the mailing list address?
> >>
> > They seem consistent with the other "new-style" podlings:
> >
> > minotaur,9:~apmail/public-arch% find . -maxdepth 2 -name \*onami\* 
> > ./onami.apache.org
> > minotaur,9:~apmail/public-arch% grep -h List-Id onami.apache.org/*/* | uniq
> > List-Id: <commits.onami.incubator.apache.org>
> > List-Id: <dev.onami.incubator.apache.org>
> > List-Id: <user.onami.incubator.apache.org>
> 
> Ah, could it be then that content/projects/onami.xml is just wrong and
> needs to be updated? It says:
> 
> <td id="mail-dev"><code>onami-dev</code><code>@</code><code>incubator.apache.org</code></td>

You are striking the same type of problems that Clutch has
needed to deal with over the years. In general, the state of
podling metadata is not reliable. That is something that we
need to get podling developers interested with.

So Clutch makes educated guesses about the podling mail lists.
When it sees that its mbox files are flowing (they could be
not yet established or held up waiting for initial moderation)
then it writes their dev list address into the report_due_[1-3].txt
files for 'marvin' to utilise
(see http://incubator.apache.org/clutch.html#data)
and puts "hasMailListDev" into clutch.pkl for the mod_mbox URL.
With the latter, if the name starts with "incubator-"
then that is an "old-style" list.

-David

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org