You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by sebb <se...@gmail.com> on 2015/07/12 15:14:49 UTC
Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
On 12 July 2015 at 13:58, <hb...@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.txt?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
>
Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
Posted by sebb <se...@gmail.com>.
On 12 July 2015 at 19:49, Hervé BOUTEMY <he...@free.fr> wrote:
> Le dimanche 12 juillet 2015 15:41:13 sebb a écrit :
>> On 12 July 2015 at 14:56, Hervé BOUTEMY <he...@free.fr> wrote:
>> > Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
>> >> On 12 July 2015 at 13:58, <hb...@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)
>> In which case, why not run 'svn add' and 'svn mv' as part of the
>> script where necessary?
> we need to detect when a project moves to Attic
That must already be known to the script else how does the person
running the script know what to do?
> then integrate svn commands to the python script
That should be fairly easyl.
> feasible, but adds complexity...
>
>>
>> This would be safer than the cronjob which assumes that all new files
>> are to be added to SVN.
>
Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
Posted by zinhtut aung <zi...@gmail.com>.
https://docs.google.com/document/d/1-8FzDaDG1u71IOo4Kx_mg-xWHa3Gv4L8zcBdBGMn98U/edit?usp=docslist_api
On 13 Jul 2015 02:50, "Hervé BOUTEMY" <he...@free.fr> wrote:
> Le dimanche 12 juillet 2015 15:41:13 sebb a écrit :
> > On 12 July 2015 at 14:56, Hervé BOUTEMY <he...@free.fr> wrote:
> > > Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
> > >> On 12 July 2015 at 13:58, <hb...@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)
> > In which case, why not run 'svn add' and 'svn mv' as part of the
> > script where necessary?
> we need to detect when a project moves to Attic
> then integrate svn commands to the python script
>
> feasible, but adds complexity...
>
> >
> > This would be safer than the cronjob which assumes that all new files
> > are to be added to SVN.
>
>
Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
Posted by Hervé BOUTEMY <he...@free.fr>.
Le dimanche 12 juillet 2015 15:41:13 sebb a écrit :
> On 12 July 2015 at 14:56, Hervé BOUTEMY <he...@free.fr> wrote:
> > Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
> >> On 12 July 2015 at 13:58, <hb...@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)
> In which case, why not run 'svn add' and 'svn mv' as part of the
> script where necessary?
we need to detect when a project moves to Attic
then integrate svn commands to the python script
feasible, but adds complexity...
>
> This would be safer than the cronjob which assumes that all new files
> are to be added to SVN.
Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
Posted by sebb <se...@gmail.com>.
On 12 July 2015 at 14:56, Hervé BOUTEMY <he...@free.fr> wrote:
> Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
>> On 12 July 2015 at 13:58, <hb...@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)
In which case, why not run 'svn add' and 'svn mv' as part of the
script where necessary?
This would be safer than the cronjob which assumes that all new files
are to be added to SVN.
Re: svn commit: r1690454 - /comdev/projects.apache.org/scripts/README.txt
Posted by Hervé BOUTEMY <he...@free.fr>.
Le dimanche 12 juillet 2015 14:14:49 sebb a écrit :
> On 12 July 2015 at 13:58, <hb...@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é