Return-Path: X-Original-To: apmail-community-commits-archive@minotaur.apache.org Delivered-To: apmail-community-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C6DF218DA7 for ; Fri, 10 Jul 2015 06:24:04 +0000 (UTC) Received: (qmail 58677 invoked by uid 500); 10 Jul 2015 06:24:04 -0000 Delivered-To: apmail-community-commits-archive@community.apache.org Received: (qmail 58653 invoked by uid 500); 10 Jul 2015 06:24:04 -0000 Mailing-List: contact commits-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list commits@community.apache.org Received: (qmail 58644 invoked by uid 99); 10 Jul 2015 06:24:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jul 2015 06:24:04 +0000 Date: Fri, 10 Jul 2015 06:24:04 +0000 (UTC) From: =?utf-8?Q?Herv=C3=A9_Boutemy_=28JIRA=29?= To: commits@community.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COMDEV-144?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1462= 1814#comment-14621814 ]=20 Herv=C3=A9 Boutemy commented on COMDEV-144: -------------------------------------- yes, formats are not the same: projects new in the past had the same handwr= itten format, and I changed to an automatically parsed content, one effect = being changing the format I know I'll have the same work to do in reporter to integrate these changes= , if we agree on the way to use projects json files from reporter > 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)