incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <>
Subject Re: [website] Do we still need the Clutch report?
Date Mon, 04 Mar 2019 19:21:56 GMT
Hi Bertrand,

> On Mar 4, 2019, at 8:20 AM, Bertrand Delacretaz <> wrote:
> Hi,
> I was looking at streamlining the incubator.a.o website generation,
> currently the build script at [1] calls "python3" to build
> the page.
> Is that information still useful considering how our workflows have
> evolved over time?

Let’s more fully investigate the clutch process … I think is using a database
created by clutch...

> Whimsy provides lots of useful information under
> which is generated
> automatically from LDAP AFAIK, so more reliable (hopefully not derived
> from clutch data, we should verify that) and maybe sufficient.

AFAIK there is some code in Whimsy to make sure that status in content/projects/*.xml is kept
in sync.

> I also think we should eliminate the XML files under
> if the relevant data is in LDAP, to eliminate data duplication, or at
> least drastically simplify them, but that's another story.

The files under content/projects in xml are the complete detailed status of every podling
that is or has been through the Incubator. Eliminating these files is therefore problematic.
There is useful information in there that goes away with a TLP LDAP or when LDAP goes away
with retirement. Also these xml files do define the podling status page.

Whimsy also uses yml files under content/podlings/ to document some of the same information
that is in the xml. I think that this better conforms with our current workflows. I think
that the data here should be made to override and replace the xml files somehow.

The migration of the Incubator website to jBake and Git is definitely incomplete.

Important pages still under the old style. <> <> <>

Missing pages “lost in migration": <> <>

I’ve evaluated ^/incubator/public/trunk/content
Moving onto ^/incubator/public/trunk and clutch


> -Bertrand
> [1]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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