[jira] [Comment Edited] (WHIMSY-4) Create public sanitised version of committee-info.txt

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WHIMSY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716255#comment-14716255 ] 

Sebb edited comment on WHIMSY-4 at 8/27/15 10:13 AM:
-----------------------------------------------------

Started looking at using the data in reporter.a.o.

The "report" attribute seems incomplete: if the cttee is on a monthly cycle, then the default cycle is not shown at all.
I think it would be better to show both sets of data.

Also, rather than a single string containing comma-space separated entries, it might be easier to use if the months were separate entries in an array. i.e. one entry for each month, plus one starting "Next month:" (if needed)


was (Author: sebb@apache.org):
Started looking at using the data in reporter.a.o.

The "report" attribute seems incomplete: if the cttee is on a monthly cycle, then the default cycle is not shown at all.
I think it would be better to show both sets of data.

> Create public sanitised version of committee-info.txt
> -----------------------------------------------------
>
>                 Key: WHIMSY-4
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-4
>             Project: Whimsy
>          Issue Type: New Feature
>            Reporter: Sebb
>
> The committee-info.txt (CI) file contains the canonical information for the composition of PMCs etc. This information is needed by various other scripts and is supposed to be synched to various web pages.
> It would be very useful to create a sanitised, structured version of the CI file for consumption by other apps, for example people.apache.org, projects.apache.org, reporter.apache.org.
> Whimsy already has access to the file, it would just need to reformat it and publish it on the public part of the site.
> The advantage of using Whimsy to create a sanitised version is that only one place would be responsible for the cleaning up process.
> Ideally the format would be readable by both humans and computers.
> So perhaps JSON would be suitable (Python supports this).
> Probably best to recreate the file on a timed basis rather than as an svnpubsub client. [In the case of svnpubsub it may not be easy to determine if the process has stopped working, or there have been no recent updates to the file]. In any case the file should contain a timestamp.
> The following data is needed as a minimum:
> PMC names (foundation date) and chairs (name and availid)
> PMC members (name and availid) and joining dates
> Similar info for the other Committees (Board, President's, W3C)
> Reporting schedules:
> - quarterly months with contents
> - next month list (not sure if comments are needed)
> There are some PMCs that were re-established after having been disbanded.
> In this case the dates should probably be taken from the most recent incarnation?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)