[
https://issues.apache.org/jira/browse/WHIMSY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717384#comment-14717384
]
Sam Ruby commented on WHIMSY-4:
-------------------------------
bq. I disagree - if the last checked date is available, then a script can
determine if the cron job has not run successfully recently (assuming that the
script has some idea of the cron frequency).
Whether this is necessary or not is another issue.
Just so we are absolutely clear: if the svn update job (which is a completely
separate cron job) fails for any reason, the public-committee-info job will
continue to "successfully" run without updating the output.
bq. I am planning to use some interface scripts to extract the data in the
formats currently expected by the existing reporter.a.o and people.a.o scripts.
If you are parsing the log files, expect your parsing to break as those files
may be updated, renamed, or removed at any time and without warning.
> 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)
