ok, there is a misunderstanding: reverted as first step

then we need to discuss, since I don't see when it may be used given current 
logic where everything comes from committee-info.txt and rdf files: that's the 
way I added committees created during last monthes, ie simply running 
parsecommittees.py

adding committees as json when the committee does not exist in committee-
info.txt is a nonsense IMHO: once I added committe-info.txt parsing feature, 
after long thoughts on it, I really don't see any use for this addpmc.py 
script

(the discussion about RDF/DOAP is another independant topic, ie where to find 
information that is not in committee-info.txt)


do you really think addpmc.py is useful now?

Regards,

Hervé

Le dimanche 21 juin 2015 15:52:28 Daniel Gruno a écrit :
> Excuse me? That script WAS used for adding new committees to the site,
> simple and easy.
> Please revert, and don't just delete stuff because you personally don't
> use it.
> 
> WIth regards,
> Daniel.
> 
> On 2015-06-21 03:50, hbout...@apache.org wrote:
> > Author: hboutemy
> > Date: Sun Jun 21 01:50:14 2015
> > New Revision: 1686683
> > 
> > URL: http://svn.apache.org/r1686683
> > Log:
> > removed addpmc.py: not used
> > 
> > Removed:
> >      comdev/projects.apache.org/scripts/import/addpmc.py
> > 
> > Modified:
> >      comdev/projects.apache.org/scripts/README.txt
> > 
> > Modified: comdev/projects.apache.org/scripts/README.txt
> > URL:
> > http://svn.apache.org/viewvc/comdev/projects.apache.org/scripts/README.tx
> > t?rev=1686683&r1=1686682&r2=1686683&view=diff
> > =========================================================================
> > ===== --- comdev/projects.apache.org/scripts/README.txt (original)
> > +++ comdev/projects.apache.org/scripts/README.txt Sun Jun 21 01:50:14 2015
> > 
> > @@ -34,8 +34,7 @@ various sources:
> >     in: foundation/committees.json + foundation/committees-retired.json +
> >     committee-info.txt
> >     (https://svn.apache.org/repos/private/committers/board/committee-info
> >     .txt) out: foundation/committees.json +
> >     foundation/committees-retired.json> 
> > -- parsepmcs.py: imports PMC data (RDF) from the old project.apache.org
> > site. No need -  to run that more than once?
> > +- parsepmcs.py: imports PMC data (RDF) from the old project.apache.org
> > site.> 
> >     in:
> >     https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/proj
> >     ects/pmc_list.xml + PMC data .rdf files out: foundation/pmcs.json
> > 
> > @@ -43,8 +42,3 @@ various sources:
> >     turns them into JSON objects.
> >     in:
> >     https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/proj
> >     ects/files.xml + projects' DOAP files out: projects/*.json +
> >     foundation/projects.json
> > 
> > -
> > -- addpmc.py
> > -  in: foundation/pmcs.json + foundation/committees-evolution.json +
> > params
> > -  out: foundation/pmcs.json + foundation/committees-evolution.json
> > -  list of PMCs with site url (pmcs.json) and monthly list of new
> > committees (committees-evolution.json)

Reply via email to