Mailing-List: contact commits-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Date: Sat, 11 Jul 2015 09:04:04 +0000 (UTC)
From: =?utf-8?Q?Herv=C3=A9_Boutemy_=28JIRA=29?= <jira@apache.org>
To: commits@community.apache.org
Message-ID: <JIRA.12843317.1436306127000.161762.1436605444763@Atlassian.JIRA>
In-Reply-To: <JIRA.12843317.1436306127000@Atlassian.JIRA>
References: <JIRA.12843317.1436306127000@Atlassian.JIRA>
 <JIRA.12843317.1436306127741@arcas>
Subject: [jira] [Commented] (COMDEV-144) Missing script to create
 reportingcycles.json file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COMDEV-144?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1462=
3321#comment-14623321 ]=20

Herv=C3=A9 Boutemy commented on COMDEV-144:
--------------------------------------

in april (or may, I don't precisely remember), I tried to start a discussio=
n on comdev mailing list about json formats, documentation, choice, to be a=
ble to work on canonical format for data (even perhaps sometime replace DOA=
P)

but there was not much interest, and absolute no work from anybody (and I d=
idn't have time relly learn json schema, which seems to be a good way to do=
cument json formats)

once we make formats more public, discussing about such choices will be eas=
ier

> Missing script to create reportingcycles.json file
> --------------------------------------------------
>
>                 Key: COMDEV-144
>                 URL: https://issues.apache.org/jira/browse/COMDEV-144
>             Project: Community Development
>          Issue Type: Bug
>          Components: Reporter Tool
>            Reporter: Sebb
>
> The file site/reportingcycles.json [1] gives details of the standard repo=
rting cycles, presumably extracted from committee-info.txt ("CI") [2].=20
> The CI file is not accessible by the reporter application currently, but =
I assume there must be a script somewhere that was used to create the origi=
nal file as the contents were a single line! It has now been indented and s=
orted it to make it easier to update, but it would be useful still to have =
a copy of whatever script was used.
> If the reporter tool gets access [3] to the CI file, then it would be wor=
th considering whether the data should include PMCs in the "Next month" sch=
edule as well as the regular quarterly entries.
> [1] https://svn.apache.org/repos/asf/comdev/reporter.apache.org/branches/=
deployed/site/reportingcycles.json
> [2] https://svn.apache.org/repos/private/committers/board/committee-info.=
txt
> [3] https://issues.apache.org/jira/browse/INFRA-9942


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