[
https://issues.apache.org/jira/browse/WHIMSY-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715288#comment-14715288
]
Sebb commented on WHIMSY-4:
---------------------------
Sorry, I forgot to mention that the S1 cttes missing from S3 include
Fundraising and Marketing.
But I guess that it is not necessarily the case that the chair is a member of
the committee (e.g. when the board temporarily provides a chair).
Also if the roster is not listed in S3, then null is a better response than
providing just the chairs.
I wonder why the chairs attribute has an array of name/id attributes whereas
the roster is a hash with key: id and value: hash of name/date.
Would it not be better to use the same format for both sets of members?
I think(hope) it is true that each member id can only appear once in
chair/roster so a set is suitable.
Thanks for all the work on this; I hope to start work on merging the info into
projects.a.o etc soon
> 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)
