Le dimanche 12 juillet 2015 14:14:49 sebb a écrit : > On 12 July 2015 at 13:58, <hbout...@apache.org> wrote: > > Author: hboutemy > > Date: Sun Jul 12 12:58:09 2015 > > New Revision: 1690454 > > > > URL: http://svn.apache.org/r1690454 > > Log: > > updated explanation on import scripts vs update scripts > > > > 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=1690454&r1=1690453&r2=1690454&view=diff > > ========================================================================= > > ===== --- comdev/projects.apache.org/scripts/README.txt (original) > > +++ comdev/projects.apache.org/scripts/README.txt Sun Jul 12 12:58:09 2015 > > > > @@ -43,3 +43,8 @@ various sources: > > in: data/projects.xml + projects' DOAP files > > out: site/json/projects/*.json + site/json/foundation/projects.json > > > > + site/doap/{committeeId}/{project}.rdf > > > > + > > +NOTICE: what prevents import scripts to be added to cron? > > +1. parse committees.py requires committee-info.txt, which is not > > available on project-vm (require authentication) > Agreed this means the script must be run by a process with suitable karma > > > +2. both scripts not only update files but sometimes need to add new files > > (new committees or new projects) or move + (projects going to Attic or > > retired committees) > > Why should it make a difference if files need to be added? > There is already a cronjob that detects new files and runs 'svn add' for > them the real problem is when moving a file is required: if we blindly add new files for files that should be moved, not only do we get too much files, but when removing the old file we loose history (that could have been useful)
Regards, Hervé
