incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <>
Subject Re: Tooling friendly incubator report
Date Sun, 24 Aug 2014 20:54:44 GMT

On Aug 24, 2014, at 1:26 PM, jan i <> wrote:

> On 24 August 2014 22:00, Alan D. Cabrera <> wrote:
>> On Aug 24, 2014, at 12:54 PM, jan i <> wrote:
>>> On 24 August 2014 21:47, Alan D. Cabrera <> wrote:
>>>> Here's a first sketch of a YAML based incubator report
>>> looks good, but 2 questions arise after a brief look:
>>> you use the expression "shepherds", thats a new expression to me (I
>> thought
>>> we in TAC was the only the used it).
>> What's TAC?
> Travel Assistance, another internal project.
>> Shepherds are supposed to review the reports.
> Sometimes its good to be new in a project, and able to ask the "of course"
> questions.
> Does not have a thing called "shepherd". Seems like a good idea though.

This is a role that's been in place for a while now.  I, personally, am loath to document
it since I am adamantly against having this role in the first place.  (please, don't respond
to my opinion on this thread)

>>> I thought you would start with the single incubator project reports,
>>> because the board report can to a large extent be generated from those ?
>> There's shared collected data about the Incubator itself.  We could break
>> out the podlings' reports into separate files but that would lead to an
>> explosion of files in the report directory.
> Then let me see if I misunderstood the sequence. I thought every incubator
> project submit its own report internally to incubator, and that is then
> combined into the board report.

Currently, a single wiki page gets generated, emails get sent out notifying the podlings that
a report is due, and podlings fill in the wiki page.  Instead of scraping a wiki page I am
proposing a more structured YAML file to replace the wiki page.

> I would really prefer that every incubator project had its own file (or
> directory if you prefer), it has 2 advantages:
> 1) the file only contain information relevant for that project.
> 2) it is much easier for IPMC to determine, which mentors have acted on a
> specific project report.

These are tooling issues.  All things being equal, one file per month is better than N files
per month.

> the board report should then be assembled via a tool, and IPMC (the chair)
> can add the verbal missing parts.


> but its just my opinion, and if incubator is used to work differently, I
> will not be the one to propose big changes.

This is pretty much how it works now.  As I mentioned above, I am merely proposing that we
use a more structured YAML file instead of a wiki page.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message