incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Fisher (JIRA)" <>
Subject [jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website
Date Fri, 08 Mar 2019 15:40:00 GMT


David Fisher commented on INCUBATOR-231:

We could, but it will need to be more than the pickle that needs checking.

 {{clutch.pkl}} is input to the reporter functions.

In {{content/clutch/}} these html website sections are also generated: {{clutchm.ent, clutchmy.ent,
clutcho1.ent, clutcho2.ent, clutchr1.ent, clutchr2.ent, clutcht.ent}}. Plus these text files:
{{clutch.txt, report_due_1.txt, report_due_2.txt, report_due_3.txt}}

Whimsy and Gitbox provide good LDAP and Git repository information.
 {{PROJECT_LDAP = ""}}
 {{GITBOX_DIR = ""}}

I see that real improvements in workflow and reporting based on finding out what is actually

The clutch can do more to help identify the real status of all of the podlings. I've added
the following key to each podling's dictionary in the pickle:

 {{'fixMeList': ['INFO: training: Does not yet have a website','INFO: training: Does not yet
have a distribution area']}}

 I'm working on the language. I feel that we can generate a strong self documenting status
page that can both generate each podling's report to be enhanced by the podling and help podling's
self serve.

> Cleanup Git-generated Incubator website
> ---------------------------------------
>                 Key: INCUBATOR-231
>                 URL:
>             Project: Incubator
>          Issue Type: Task
>            Reporter: Bertrand Delacretaz
>            Priority: Major
>         Attachments: clutch2data.txt,, gitbox.svn.diff.txt
> [] is generated from []
but a few things (clutch, project pages) are still maintained under []
> We should cleanup and unify for consistency, and there's a number of folders in svn that
are not used anymore. Everything should move to Git to avoid confusion.
> Also, a lot of the projects information in the XML files found under []
is duplicated in other places, LDAP, podlings websites etc - it would be good to clean that
up and simplify those pages to adapt to our current workflows, while preserving history where
it makes sense.
> There are also YAML files with yet more duplicated information at []
, not sure if that's used or useful.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message