[
https://issues.apache.org/jira/browse/WHIMSY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717304#comment-14717304
]
Sam Ruby commented on WHIMSY-4:
-------------------------------
I've now pushed out the change and added a cron job. Be on the lookout for
breakage to other tools that may depend on data derived from committee info.
bq. The intention is to allow the reader to determine if the extracted data is
up to date. That's not possible without knowing when the data was last
checked. Since the source file in SVN is not public, it's not possible for
every person/script that has access to the JSON to determine its validity.
As described before, that information is not sufficient to determine if there
is a problem, nor helpful in identifying the problem. And saying that some
unnamed users who aren't in a position to do anything about the problem need to
know this information isn't a use case.
That being said, I don't have a problem making the necessary information public:
https://whimsy.apache.org/logs/
There you can see when public-committee-info was last run, and if all goes
well, the size of the log will be zero. But the information you really need to
know is contained in update-svn which shows the results of the last attempt to
update the local copy of the committers repository.
Please do NOT treat these URLs, or the format of the data contained therein, as
stable.
bq. 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.
I'll keep this issue open until I resolve this - after that point, new
bugs/feature requests can be opened as separate issues.
> 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)
