You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by sebb <se...@gmail.com> on 2012/06/08 11:12:49 UTC

Clutch data - could ReportingSchedule data be merged into podlings.xml ?

As the subject says: is there any need for a separate
ReportingSchedule page now that we have podlings.xml?

The CMS bookmark allows direct edit via the copy at
http://incubator.apache.org/podlings.xml

So is the Wiki page still necessary?

Thoughts?

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


Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ?

Posted by David Crossley <cr...@apache.org>.
Jukka Zitting wrote:
> sebb wrote:
> > As the subject says: is there any need for a separate
> > ReportingSchedule page now that we have podlings.xml?
> 
> Not really AFAICT.
> 
> +1 to merging them, though note that the reminder script needs to be
> updated too.

Great idea. I have been wondering that for ages.

Regarding the reminders, Clutch generates the lists of
podling dev mail lists due to report, and stored in our SVN.
An infra tool picks up those lists to send the reminders.
Clutch determines their mailing list name from various hints,
checks to see if it is established and archives are available.
If not, it uses the general@ list for that podling.

http://incubator.apache.org/clutch.html#data
report_due_[1-3].txt

e.g. for Group-3 June:
http://incubator.apache.org/report_due_3.txt

-David

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


Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ?

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Fri, Jun 8, 2012 at 12:12 PM, sebb <se...@gmail.com> wrote:
> As the subject says: is there any need for a separate
> ReportingSchedule page now that we have podlings.xml?

Not really AFAICT.

+1 to merging them, though note that the reminder script needs to be
updated too.

BR,

Jukka Zitting

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


Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ?

Posted by Upayavira <uv...@odoko.co.uk>.
tell me your username on the wiki and I'll add you...

On Tue, Jun 12, 2012, at 09:32 AM, sebb wrote:
> On 9 June 2012 02:46, sebb <se...@gmail.com> wrote:
> > On 9 June 2012 02:38, David Crossley <cr...@apache.org> wrote:
> >> sebb wrote:
> >>> As the subject says: is there any need for a separate
> >>> ReportingSchedule page now that we have podlings.xml?
> >>
> >> Some things to take care with, when we modify Clutch:
> >>
> >> Clutch based everything on the presence in ReportingSchedule
> >> and the name of the podling used there (lowercase, no spaces).
> >
> > Presence is roughly equal to status=current.
> >
> > Clutch currently uses the same transformation on the podling name atttribute.
> >
> > So this should not be much of a problem.
> >
> >> The main name in podlings.xml might be different,
> >> so some assumptions in clutch might need adjustment.
> >
> > If a name attribute in podlings.xml is wrong, then it needs fixing.
> > AFAIK, they all agree currently (IIRC clutch checks this).
> >
> >> Also the sequence of its data and hint-gathering process.
> >
> > Yes.
> >
> >> So a basic entry for a podling needs to be added to
> >> the podlings.xml file soon after acceptance.
> >
> > Yes.
> 
> Clutch now ignores the ReportingSchedule Wiki page and relies instead
> on the <reporting> tag in podlings.xml.
> 
> The documentation referring to ReportingSchedule has been updated, but
> the page itself now needs to be updated to redirect users to
> podlings.xml.
> 
> I don't have write karma for the Wiki so if someone else could update
> the page that would be great.
> 
> >> -David
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

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


Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ?

Posted by sebb <se...@gmail.com>.
On 9 June 2012 02:46, sebb <se...@gmail.com> wrote:
> On 9 June 2012 02:38, David Crossley <cr...@apache.org> wrote:
>> sebb wrote:
>>> As the subject says: is there any need for a separate
>>> ReportingSchedule page now that we have podlings.xml?
>>
>> Some things to take care with, when we modify Clutch:
>>
>> Clutch based everything on the presence in ReportingSchedule
>> and the name of the podling used there (lowercase, no spaces).
>
> Presence is roughly equal to status=current.
>
> Clutch currently uses the same transformation on the podling name atttribute.
>
> So this should not be much of a problem.
>
>> The main name in podlings.xml might be different,
>> so some assumptions in clutch might need adjustment.
>
> If a name attribute in podlings.xml is wrong, then it needs fixing.
> AFAIK, they all agree currently (IIRC clutch checks this).
>
>> Also the sequence of its data and hint-gathering process.
>
> Yes.
>
>> So a basic entry for a podling needs to be added to
>> the podlings.xml file soon after acceptance.
>
> Yes.

Clutch now ignores the ReportingSchedule Wiki page and relies instead
on the <reporting> tag in podlings.xml.

The documentation referring to ReportingSchedule has been updated, but
the page itself now needs to be updated to redirect users to
podlings.xml.

I don't have write karma for the Wiki so if someone else could update
the page that would be great.

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

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


Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ?

Posted by sebb <se...@gmail.com>.
On 9 June 2012 02:38, David Crossley <cr...@apache.org> wrote:
> sebb wrote:
>> As the subject says: is there any need for a separate
>> ReportingSchedule page now that we have podlings.xml?
>
> Some things to take care with, when we modify Clutch:
>
> Clutch based everything on the presence in ReportingSchedule
> and the name of the podling used there (lowercase, no spaces).

Presence is roughly equal to status=current.

Clutch currently uses the same transformation on the podling name atttribute.

So this should not be much of a problem.

> The main name in podlings.xml might be different,
> so some assumptions in clutch might need adjustment.

If a name attribute in podlings.xml is wrong, then it needs fixing.
AFAIK, they all agree currently (IIRC clutch checks this).

> Also the sequence of its data and hint-gathering process.

Yes.

> So a basic entry for a podling needs to be added to
> the podlings.xml file soon after acceptance.

Yes.

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

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


Re: Clutch data - could ReportingSchedule data be merged into podlings.xml ?

Posted by David Crossley <cr...@apache.org>.
sebb wrote:
> As the subject says: is there any need for a separate
> ReportingSchedule page now that we have podlings.xml?

Some things to take care with, when we modify Clutch:

Clutch based everything on the presence in ReportingSchedule
and the name of the podling used there (lowercase, no spaces).

The main name in podlings.xml might be different,
so some assumptions in clutch might need adjustment.
Also the sequence of its data and hint-gathering process.

So a basic entry for a podling needs to be added to
the podlings.xml file soon after acceptance.

-David

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