Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-30 Thread Henk P. Penning 

On Sun, 29 Apr 2018, Jan Iversen wrote:


Date: Sun, 29 Apr 2018 19:31:48 +0200
From: Jan Iversen <j...@apache.org>
To: general@attic.apache.org
Subject: Re: svn commit: r1830424 - /attic/site/xdocs/process.xml



On 29 Apr 2018, at 08:23, Henk P. Penning <penn...@uu.nl> wrote:


Hi,


Hi Jan,

 May I ask you (as chair) to set an agenda?
 to focus everybody's enthousiasm :-)


Wearing my chair hat, I need to give a polite note. A chair is just a
member of the community like any other PMC, with no special powers
(something I highly second). So everybody can start the agenda [...]


  Sorry about that.
  Attic is the first 'project' I'm involved in.
  Re: etiquette, I'm a newbie :-)

  Regards,

  HPP

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-29 Thread Jan Iversen 


> On 29 Apr 2018, at 08:23, Henk P. Penning <penn...@uu.nl> wrote:
> 
>> On Sat, 28 Apr 2018, Jan Iversen wrote:
>> 
>> Date: Sat, 28 Apr 2018 19:44:45 +0200
>> From: Jan Iversen <j...@apache.org>
>> To: general@attic.apache.org
>> Subject: Re: svn commit: r1830424 - /attic/site/xdocs/process.xml
> 
>> I want to have a clear process, as it works today. In general I am not
>> in favor of just changing the process documentation, without having a
>> community consensus.
>> 
>> The process doc is on the live site, and should therefore be correct,
>> and things that may come in the future belong in either of the 2
>> solutions.
> 
> Hi Jan,
> 
>  May I ask you (as chair) to set an agenda?
>  to focus everybody's enthousiasm :-)

Wearing my chair hat, I need to give a polite note. A chair is just a member of 
the community like any other PMC, with no special powers (something I highly 
second). So everybody can start the agenda you suggest, however since I made 
the ball run, I will initiate a couple of mails.
> 
>  Perhaps something like this :
> 
>1. pick a winner
I have tried several times to start a discussion/vote, but until now I have 
been told to wait, because things are not complete. I will try one last time.

>2. format : is there consensus for yaml now ?
>   Is so, switch ; otherwise maybe later.
It seems I am the only one against, and I will not block something you and Sebb 
agree on.

>3. cleanup ; todo by all ; any order
>   -- fix the (proces) doc, other details, beautify
to me it is important we agree to these changes before they are made (as just 
happened)
>   -- fix the httpd rules [flagged/ -> flags/]
Seem like something for you and/or Sebb to do.
>   -- do the build stuff
Same.
>4. switch to git
This is just self service (have not tried yet).

As both you and Sebb have promised to maintain the site, future maintenance 
seems secured securing I am mostly of the hook (apart from the board report).

rgds
jan I
> 
>> jan i
> 
>  Regards,
> 
>  HPP
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Hervé BOUTEMY 
Le samedi 28 avril 2018, 19:44:45 CEST Jan Iversen a écrit :
> Sent from my iPad
> 
> > On 28 Apr 2018, at 18:10, Hervé BOUTEMY  wrote:
> > 
> > Le samedi 28 avril 2018, 15:07:34 CEST Jan Iversen a écrit :
> >> Sent from my iPad
> >> 
>  On 28 Apr 2018, at 14:56, sebb  wrote:
>  On 28 April 2018 at 13:45, Jan Iversen  wrote:
>  
>  
>  Sent from my iPad
>  
> >> On 28 Apr 2018, at 14:28, sebb  wrote:
> >> 
> >> On 28 April 2018 at 13:06, Jan Iversen  wrote:
> >> 
> >> 
> >> Sent from my iPad
> >> 
> >>> On 28 Apr 2018, at 13:07, Hervé BOUTEMY 
> >>> wrote:
> >>> 
> >>> oh, I was just trying to document, not change anything:
> >>> - the svnwcsub part is what works for years but was not well known
> >>> outside
> >>> infra team
> >>> - the buildbot job *for the current build.sh*
> >>> (in/repos/asf/attic/site/) which is just a way to not require to do
> >>> the build locally
> >>> 
> >>> this does not include anything regarding future changes that are in
> >>> discussion/tests:
> >>> - Git migration
> >>> - build switch from Ant/Anakia to 3 other solutions
> >>> 
> >>> do you see something that is not simple documentation in my commit?
> >>> (I don't want to add more diversity in ideas for future changes,
> >>> just
> >>> document)
> >> 
> >> will the buildbot is new, and adding it to our current process is a
> >> bit
> >> premature, especially since we might end up not needing it.
> >> 
> >> No need to reverse the commit, I simply wanted to point out facts,
> >> because during the last period things seem to have their own life,
> >> and
> >> are then seen as facts. If I were to retire a project tomorrow, I
> >> would use the old method, without a buildbot.>>>
> > 
> > No, you cannot ignore the buildbot because it happens when you commit.
> > 
> > However provided that you commit all the changes at once, you should
> > not notice a difference.
>  
>  then let me just say, the process (online right now) says:
>  
>  in xdocs/projects/ copy one of the files to the new project name (eg.
>  devicemap.xml) Add the new file as a link in the
>  xdocs/stylesheets/project.xml navigation Run 'ant' from the root (ie:
>  the attic/site/ directory you checked out) Review the generated files
>  in
>  docs/** in your browser
>  SVN commit all changes. Remember to add both the new xdocs/ project
>  file
>  and the new generated docs/ project file N.B. the buildbot will detect
>  any changes to the source and build/commit the outout. So it's
>  important
>  to checkin all the changes at once. Or just checkin the source changes
>  and let buildbot do the rest. The new pages should go live quickly
>  so according to that I have to run ant (old process) and commit both
>  xdocs and docs, and then buildbot will do something.this is not
>  really understandable as it in reality describes 2 competing
>  procedures.>
> >>> 
> >>> There are two alternative procedures:
> >>> - build everything locally and check it all in in one commit
> >>> - check in the xdocs changes and let buildbot do the work
> >>> 
> >>> I can disable the automatic buildbot if you insist.
> >>> But I thought we had already agreed to use it.
> >> 
> >> I just want the procedure to be very clear.
> >> the “run ant” step is not optional as an example.
> > 
> > I don't understand this sentence: is it a question or an assertion (which
> > is wrong IMHO)?
> 
> it is a statement, looking at process.html as it is right now is at very
> least confusing, because it describes 2 methods, but does not clearly state
> which steps are mandatory and which steps are optional (choose method)
there are 2 options: light remote or full local
- light remote process, without local build to check before commit: build is 
done by buildbot
- full local process with local build to check before commit
It's really usual with sites built from markup as seen in many other Apache 
projects, whatever the build tool and the CI server are (which differ from 
project to project to adapt local technical knowledge)

> > The "ant run" is optional once we have buildbot, it's only useful if you
> > want to build locally to check locally something. But you can commit the
> > source without having run locally the build: buildbot will do the job for
> > you.
> yes but we are not there today, and the document should describe things as
> they are, and not as they possibly will be.
> > And when you tell that in the future you'll edit the source at GitHub
> > (which is IMHO a very good target), you'll be exactly on the case where
> > you commit the source without having locally tested it
> > 
> >> The build job is there,

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Hervé BOUTEMY 
Le samedi 28 avril 2018, 15:07:34 CEST Jan Iversen a écrit :
> Sent from my iPad
> 
> > On 28 Apr 2018, at 14:56, sebb  wrote:
> >> On 28 April 2018 at 13:45, Jan Iversen  wrote:
> >> 
> >> 
> >> Sent from my iPad
> >> 
>  On 28 Apr 2018, at 14:28, sebb  wrote:
>  
>  On 28 April 2018 at 13:06, Jan Iversen  wrote:
>  
>  
>  Sent from my iPad
>  
> > On 28 Apr 2018, at 13:07, Hervé BOUTEMY  wrote:
> > 
> > oh, I was just trying to document, not change anything:
> > - the svnwcsub part is what works for years but was not well known
> > outside
> > infra team
> > - the buildbot job *for the current build.sh*
> > (in/repos/asf/attic/site/) which is just a way to not require to do
> > the build locally
> > 
> > this does not include anything regarding future changes that are in
> > discussion/tests:
> > - Git migration
> > - build switch from Ant/Anakia to 3 other solutions
> > 
> > do you see something that is not simple documentation in my commit?
> > (I don't want to add more diversity in ideas for future changes, just
> > document)
>  
>  will the buildbot is new, and adding it to our current process is a bit
>  premature, especially since we might end up not needing it.
>  
>  No need to reverse the commit, I simply wanted to point out facts,
>  because during the last period things seem to have their own life, and
>  are then seen as facts. If I were to retire a project tomorrow, I
>  would use the old method, without a buildbot.>>> 
> >>> No, you cannot ignore the buildbot because it happens when you commit.
> >>> 
> >>> However provided that you commit all the changes at once, you should
> >>> not notice a difference.
> >> 
> >> then let me just say, the process (online right now) says:
> >> 
> >> in xdocs/projects/ copy one of the files to the new project name (eg.
> >> devicemap.xml) Add the new file as a link in the
> >> xdocs/stylesheets/project.xml navigation Run 'ant' from the root (ie:
> >> the attic/site/ directory you checked out) Review the generated files in
> >> docs/** in your browser
> >> SVN commit all changes. Remember to add both the new xdocs/ project file
> >> and the new generated docs/ project file N.B. the buildbot will detect
> >> any changes to the source and build/commit the outout. So it's important
> >> to checkin all the changes at once. Or just checkin the source changes
> >> and let buildbot do the rest. The new pages should go live quickly
> >> so according to that I have to run ant (old process) and commit both
> >> xdocs and docs, and then buildbot will do something.this is not
> >> really understandable as it in reality describes 2 competing procedures.> 
> > There are two alternative procedures:
> > - build everything locally and check it all in in one commit
> > - check in the xdocs changes and let buildbot do the work
> > 
> > I can disable the automatic buildbot if you insist.
> > But I thought we had already agreed to use it.
> 
> I just want the procedure to be very clear.
> the “run ant” step is not optional as an example.
I don't understand this sentence: is it a question or an assertion (which is 
wrong IMHO)?

The "ant run" is optional once we have buildbot, it's only useful if you want 
to build locally to check locally something. But you can commit the source 
without having run locally the build: buildbot will do the job for you.

And when you tell that in the future you'll edit the source at GitHub (which 
is IMHO a very good target), you'll be exactly on the case where you commit 
the source without having locally tested it

> The build job is there, so I assume it can be used.
yes, it can be used. It can also be ignored = what happens when you run the 
build.sh script locally and commit xdocs+docs simultaneously.

But with your sentence "the “run ant” step is not optional as an example", I 
don't get where you want to go: build and commit xdocs+docs locally (then 
ignore buildbot)? or commit just source in xdocs and let buildbot do the build 
and commut docs?

Regards,

Hervé

> 
> rgds
> jan i
> 
> >> rgds
> >> jan i
> >> 
>  rgds
>  jan i
>  
> > Regards,
> > 
> > Hervé
> > 
> > [1] http://svn.apache.org/viewvc/attic/site/
> > 
> > Le samedi 28 avril 2018, 12:54:40 CEST Jan Iversen a écrit :
> >> Isn’t it a bit premature to change the process ? Seen from pow we are
> >> experimenting with at least 3 proposals of which 1 does not need a
> >> buildbot.
> >> 
> >> This is of course just my opinion.
> >> 
> >> rgds
> >> jan I
> >> 
> >> Sent from my iPad
> >> 
> >>> On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:
> >>> 
> >>> Author: hboutemy
> >>> Date: Sat Apr 28 10:33:07 2018
> >>> New Revision: 1830424
> >>> 
>

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Jan Iversen 


Sent from my iPad

> On 28 Apr 2018, at 14:56, sebb  wrote:
> 
>> On 28 April 2018 at 13:45, Jan Iversen  wrote:
>> 
>> 
>> Sent from my iPad
>> 
 On 28 Apr 2018, at 14:28, sebb  wrote:
 
 On 28 April 2018 at 13:06, Jan Iversen  wrote:
 
 
 Sent from my iPad
 
> On 28 Apr 2018, at 13:07, Hervé BOUTEMY  wrote:
> 
> oh, I was just trying to document, not change anything:
> - the svnwcsub part is what works for years but was not well known outside
> infra team
> - the buildbot job *for the current build.sh* (in/repos/asf/attic/site/) 
> which
> is just a way to not require to do the build locally
> 
> this does not include anything regarding future changes that are in
> discussion/tests:
> - Git migration
> - build switch from Ant/Anakia to 3 other solutions
> 
> do you see something that is not simple documentation in my commit?
> (I don't want to add more diversity in ideas for future changes, just
> document)
 will the buildbot is new, and adding it to our current process is a bit 
 premature, especially since we might end up not needing it.
 
 No need to reverse the commit, I simply wanted to point out facts, because 
 during the last period things seem to have their own life, and are then 
 seen as facts. If I were to retire a project tomorrow, I would use the old 
 method, without a buildbot.
>>> 
>>> No, you cannot ignore the buildbot because it happens when you commit.
>>> 
>>> However provided that you commit all the changes at once, you should
>>> not notice a difference.
>> 
>> then let me just say, the process (online right now) says:
>> 
>> in xdocs/projects/ copy one of the files to the new project name (eg. 
>> devicemap.xml)
>> Add the new file as a link in the xdocs/stylesheets/project.xml navigation
>> Run 'ant' from the root (ie: the attic/site/ directory you checked out)
>> Review the generated files in docs/** in your browser
>> SVN commit all changes. Remember to add both the new xdocs/ project file and 
>> the new generated docs/ project file N.B. the buildbot will detect any 
>> changes to the source and build/commit the outout. So it's important to 
>> checkin all the changes at once. Or just checkin the source changes and let 
>> buildbot do the rest.
>> The new pages should go live quickly
>> so according to that I have to run ant (old process) and commit both xdocs 
>> and docs, and then buildbot will do something.this is not really 
>> understandable as it in reality describes 2 competing procedures.
> 
> There are two alternative procedures:
> - build everything locally and check it all in in one commit
> - check in the xdocs changes and let buildbot do the work
> 
> I can disable the automatic buildbot if you insist.
> But I thought we had already agreed to use it.

I just want the procedure to be very clear. the “run ant” step is not optional 
as an example. The build job is there, so I assume it can be used.

rgds
jan i
> 
>> rgds
>> jan i
>>> 
 rgds
 jan i
> 
> Regards,
> 
> Hervé
> 
> [1] http://svn.apache.org/viewvc/attic/site/
> 
> Le samedi 28 avril 2018, 12:54:40 CEST Jan Iversen a écrit :
>> Isn’t it a bit premature to change the process ? Seen from pow we are
>> experimenting with at least 3 proposals of which 1 does not need a
>> buildbot.
>> 
>> This is of course just my opinion.
>> 
>> rgds
>> jan I
>> 
>> Sent from my iPad
>> 
>>> On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:
>>> 
>>> Author: hboutemy
>>> Date: Sat Apr 28 10:33:07 2018
>>> New Revision: 1830424
>>> 
>>> URL: http://svn.apache.org/viewvc?rev=1830424=rev
>>> Log:
>>> added links to Buildbot job and svnwcsub configuration
>>> 
>>> Modified:
>>> attic/site/xdocs/process.xml
>>> 
>>> Modified: attic/site/xdocs/process.xml
>>> URL:
>>> http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=
>>> 1830423=1830424=diff
>>> =
>>> = --- attic/site/xdocs/process.xml (original)
>>> +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
>>> @@ -76,8 +76,9 @@
>>> 
>>> The following are usefull svn/https locations:
>>>  
>>> 
>>> - svn site >> href="http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/
>>> asf/attic + svn site >> href="http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf
>>> /attic: sources in xdocs, generated html in
>>> docs>
>>>   site >>   href="http://attic.apache.org;>http://attic.apache.org
>>> 
>>> + internals: >> href="https://ci.apache.org/builders/attic-site;>Buildbot job to
>>> build from source and

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread sebb 
On 28 April 2018 at 13:45, Jan Iversen  wrote:
>
>
> Sent from my iPad
>
>> On 28 Apr 2018, at 14:28, sebb  wrote:
>>
>>> On 28 April 2018 at 13:06, Jan Iversen  wrote:
>>>
>>>
>>> Sent from my iPad
>>>
 On 28 Apr 2018, at 13:07, Hervé BOUTEMY  wrote:

 oh, I was just trying to document, not change anything:
 - the svnwcsub part is what works for years but was not well known outside
 infra team
 - the buildbot job *for the current build.sh* (in/repos/asf/attic/site/) 
 which
 is just a way to not require to do the build locally

 this does not include anything regarding future changes that are in
 discussion/tests:
 - Git migration
 - build switch from Ant/Anakia to 3 other solutions

 do you see something that is not simple documentation in my commit?
 (I don't want to add more diversity in ideas for future changes, just
 document)
>>> will the buildbot is new, and adding it to our current process is a bit 
>>> premature, especially since we might end up not needing it.
>>>
>>> No need to reverse the commit, I simply wanted to point out facts, because 
>>> during the last period things seem to have their own life, and are then 
>>> seen as facts. If I were to retire a project tomorrow, I would use the old 
>>> method, without a buildbot.
>>
>> No, you cannot ignore the buildbot because it happens when you commit.
>>
>> However provided that you commit all the changes at once, you should
>> not notice a difference.
>
> then let me just say, the process (online right now) says:
>
> in xdocs/projects/ copy one of the files to the new project name (eg. 
> devicemap.xml)
> Add the new file as a link in the xdocs/stylesheets/project.xml navigation
> Run 'ant' from the root (ie: the attic/site/ directory you checked out)
> Review the generated files in docs/** in your browser
> SVN commit all changes. Remember to add both the new xdocs/ project file and 
> the new generated docs/ project file N.B. the buildbot will detect any 
> changes to the source and build/commit the outout. So it's important to 
> checkin all the changes at once. Or just checkin the source changes and let 
> buildbot do the rest.
> The new pages should go live quickly
> so according to that I have to run ant (old process) and commit both xdocs 
> and docs, and then buildbot will do something.this is not really 
> understandable as it in reality describes 2 competing procedures.

There are two alternative procedures:
- build everything locally and check it all in in one commit
- check in the xdocs changes and let buildbot do the work

I can disable the automatic buildbot if you insist.
But I thought we had already agreed to use it.

> rgds
> jan i
>>
>>> rgds
>>> jan i

 Regards,

 Hervé

 [1] http://svn.apache.org/viewvc/attic/site/

 Le samedi 28 avril 2018, 12:54:40 CEST Jan Iversen a écrit :
> Isn’t it a bit premature to change the process ? Seen from pow we are
> experimenting with at least 3 proposals of which 1 does not need a
> buildbot.
>
> This is of course just my opinion.
>
> rgds
> jan I
>
> Sent from my iPad
>
>> On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:
>>
>> Author: hboutemy
>> Date: Sat Apr 28 10:33:07 2018
>> New Revision: 1830424
>>
>> URL: http://svn.apache.org/viewvc?rev=1830424=rev
>> Log:
>> added links to Buildbot job and svnwcsub configuration
>>
>> Modified:
>>  attic/site/xdocs/process.xml
>>
>> Modified: attic/site/xdocs/process.xml
>> URL:
>> http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=
>> 1830423=1830424=diff
>> =
>> = --- attic/site/xdocs/process.xml (original)
>> +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
>> @@ -76,8 +76,9 @@
>>
>> The following are usefull svn/https locations:
>>   
>>
>> - svn site > href="http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/
>> asf/attic + svn site > href="http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf
>> /attic: sources in xdocs, generated html in
>> docs>
>>site >href="http://attic.apache.org;>http://attic.apache.org
>>
>> + internals: > href="https://ci.apache.org/builders/attic-site;>Buildbot job to
>> build from source and commit generated html, > href="https://github.com/apache/infrastructure-puppet/blob/deployment/mod
>> ules/svnwcsub/files/svnwcsub.conf#L36">svnwcsub configuration to
>> update generated html from svn to webserver>
>>jira >href="https://issues.apache.org/jira/browse/ATTIC;>https://issues.ap
>>ache.org/jira/browse/ATTIC committees.xml >

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Jan Iversen 


Sent from my iPad

> On 28 Apr 2018, at 14:28, sebb  wrote:
> 
>> On 28 April 2018 at 13:06, Jan Iversen  wrote:
>> 
>> 
>> Sent from my iPad
>> 
>>> On 28 Apr 2018, at 13:07, Hervé BOUTEMY  wrote:
>>> 
>>> oh, I was just trying to document, not change anything:
>>> - the svnwcsub part is what works for years but was not well known outside
>>> infra team
>>> - the buildbot job *for the current build.sh* (in/repos/asf/attic/site/) 
>>> which
>>> is just a way to not require to do the build locally
>>> 
>>> this does not include anything regarding future changes that are in
>>> discussion/tests:
>>> - Git migration
>>> - build switch from Ant/Anakia to 3 other solutions
>>> 
>>> do you see something that is not simple documentation in my commit?
>>> (I don't want to add more diversity in ideas for future changes, just
>>> document)
>> will the buildbot is new, and adding it to our current process is a bit 
>> premature, especially since we might end up not needing it.
>> 
>> No need to reverse the commit, I simply wanted to point out facts, because 
>> during the last period things seem to have their own life, and are then seen 
>> as facts. If I were to retire a project tomorrow, I would use the old 
>> method, without a buildbot.
> 
> No, you cannot ignore the buildbot because it happens when you commit.
> 
> However provided that you commit all the changes at once, you should
> not notice a difference.

then let me just say, the process (online right now) says:

in xdocs/projects/ copy one of the files to the new project name (eg. 
devicemap.xml)
Add the new file as a link in the xdocs/stylesheets/project.xml navigation
Run 'ant' from the root (ie: the attic/site/ directory you checked out)
Review the generated files in docs/** in your browser
SVN commit all changes. Remember to add both the new xdocs/ project file and 
the new generated docs/ project file N.B. the buildbot will detect any changes 
to the source and build/commit the outout. So it's important to checkin all the 
changes at once. Or just checkin the source changes and let buildbot do the 
rest.
The new pages should go live quickly
so according to that I have to run ant (old process) and commit both xdocs and 
docs, and then buildbot will do something.this is not really understandable 
as it in reality describes 2 competing procedures. This is a good example of 
why I prefer not to change the procedure until we have decided on a new one 
(incl. the text in process.html)

rgds
jan i
> 
>> rgds
>> jan i
>>> 
>>> Regards,
>>> 
>>> Hervé
>>> 
>>> [1] http://svn.apache.org/viewvc/attic/site/
>>> 
>>> Le samedi 28 avril 2018, 12:54:40 CEST Jan Iversen a écrit :
 Isn’t it a bit premature to change the process ? Seen from pow we are
 experimenting with at least 3 proposals of which 1 does not need a
 buildbot.
 
 This is of course just my opinion.
 
 rgds
 jan I
 
 Sent from my iPad
 
> On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:
> 
> Author: hboutemy
> Date: Sat Apr 28 10:33:07 2018
> New Revision: 1830424
> 
> URL: http://svn.apache.org/viewvc?rev=1830424=rev
> Log:
> added links to Buildbot job and svnwcsub configuration
> 
> Modified:
>  attic/site/xdocs/process.xml
> 
> Modified: attic/site/xdocs/process.xml
> URL:
> http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=
> 1830423=1830424=diff
> =
> = --- attic/site/xdocs/process.xml (original)
> +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
> @@ -76,8 +76,9 @@
> 
> The following are usefull svn/https locations:
>   
> 
> - svn site  href="http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/
> asf/attic + svn site  href="http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf
> /attic: sources in xdocs, generated html in
> docs>
>site href="http://attic.apache.org;>http://attic.apache.org
> 
> + internals:  href="https://ci.apache.org/builders/attic-site;>Buildbot job to
> build from source and commit generated html,  href="https://github.com/apache/infrastructure-puppet/blob/deployment/mod
> ules/svnwcsub/files/svnwcsub.conf#L36">svnwcsub configuration to
> update generated html from svn to webserver>
>jira href="https://issues.apache.org/jira/browse/ATTIC;>https://issues.ap
>ache.org/jira/browse/ATTIC committees.xml href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/da
>ta/committees.xml">https://svn.apache.org/repos/asf/comdev/projects.a
>pache.org/data/committees.xml>
>   
>>> 
>>>

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread sebb 
On 28 April 2018 at 13:06, Jan Iversen  wrote:
>
>
> Sent from my iPad
>
>> On 28 Apr 2018, at 13:07, Hervé BOUTEMY  wrote:
>>
>> oh, I was just trying to document, not change anything:
>> - the svnwcsub part is what works for years but was not well known outside
>> infra team
>> - the buildbot job *for the current build.sh* (in/repos/asf/attic/site/) 
>> which
>> is just a way to not require to do the build locally
>>
>> this does not include anything regarding future changes that are in
>> discussion/tests:
>> - Git migration
>> - build switch from Ant/Anakia to 3 other solutions
>>
>> do you see something that is not simple documentation in my commit?
>> (I don't want to add more diversity in ideas for future changes, just
>> document)
> will the buildbot is new, and adding it to our current process is a bit 
> premature, especially since we might end up not needing it.
>
> No need to reverse the commit, I simply wanted to point out facts, because 
> during the last period things seem to have their own life, and are then seen 
> as facts. If I were to retire a project tomorrow, I would use the old method, 
> without a buildbot.

No, you cannot ignore the buildbot because it happens when you commit.

However provided that you commit all the changes at once, you should
not notice a difference.

> rgds
> jan i
>>
>> Regards,
>>
>> Hervé
>>
>> [1] http://svn.apache.org/viewvc/attic/site/
>>
>> Le samedi 28 avril 2018, 12:54:40 CEST Jan Iversen a écrit :
>>> Isn’t it a bit premature to change the process ? Seen from pow we are
>>> experimenting with at least 3 proposals of which 1 does not need a
>>> buildbot.
>>>
>>> This is of course just my opinion.
>>>
>>> rgds
>>> jan I
>>>
>>> Sent from my iPad
>>>
 On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:

 Author: hboutemy
 Date: Sat Apr 28 10:33:07 2018
 New Revision: 1830424

 URL: http://svn.apache.org/viewvc?rev=1830424=rev
 Log:
 added links to Buildbot job and svnwcsub configuration

 Modified:
   attic/site/xdocs/process.xml

 Modified: attic/site/xdocs/process.xml
 URL:
 http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=
 1830423=1830424=diff
 =
 = --- attic/site/xdocs/process.xml (original)
 +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
 @@ -76,8 +76,9 @@

  The following are usefull svn/https locations:


 - svn site >>> href="http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/
 asf/attic + svn site >>> href="http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf
 /attic: sources in xdocs, generated html in
 docs>
 site >>> href="http://attic.apache.org;>http://attic.apache.org

 + internals: >>> href="https://ci.apache.org/builders/attic-site;>Buildbot job to
 build from source and commit generated html, >>> href="https://github.com/apache/infrastructure-puppet/blob/deployment/mod
 ules/svnwcsub/files/svnwcsub.conf#L36">svnwcsub configuration to
 update generated html from svn to webserver>
 jira >>> href="https://issues.apache.org/jira/browse/ATTIC;>https://issues.ap
 ache.org/jira/browse/ATTIC committees.xml >>> href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/da
 ta/committees.xml">https://svn.apache.org/repos/asf/comdev/projects.a
 pache.org/data/committees.xml>

>>
>>

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Hervé BOUTEMY 
oh, I was just trying to document, not change anything:
- the svnwcsub part is what works for years but was not well known outside 
infra team
- the buildbot job *for the current build.sh* (in/repos/asf/attic/site/) which 
is just a way to not require to do the build locally

this does not include anything regarding future changes that are in 
discussion/tests:
- Git migration
- build switch from Ant/Anakia to 3 other solutions

do you see something that is not simple documentation in my commit?
(I don't want to add more diversity in ideas for future changes, just 
document)

Regards,

Hervé

[1] http://svn.apache.org/viewvc/attic/site/

Le samedi 28 avril 2018, 12:54:40 CEST Jan Iversen a écrit :
> Isn’t it a bit premature to change the process ? Seen from pow we are
> experimenting with at least 3 proposals of which 1 does not need a
> buildbot.
> 
> This is of course just my opinion.
> 
> rgds
> jan I
> 
> Sent from my iPad
> 
> > On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:
> > 
> > Author: hboutemy
> > Date: Sat Apr 28 10:33:07 2018
> > New Revision: 1830424
> > 
> > URL: http://svn.apache.org/viewvc?rev=1830424=rev
> > Log:
> > added links to Buildbot job and svnwcsub configuration
> > 
> > Modified:
> >attic/site/xdocs/process.xml
> > 
> > Modified: attic/site/xdocs/process.xml
> > URL:
> > http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=
> > 1830423=1830424=diff
> > =
> > = --- attic/site/xdocs/process.xml (original)
> > +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
> > @@ -76,8 +76,9 @@
> > 
> >   The following are usefull svn/https locations:
> > 
> > 
> > - svn site  > href="http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/
> > asf/attic + svn site  > href="http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf
> > /attic: sources in xdocs, generated html in
> > docs> 
> >  site  >  href="http://attic.apache.org;>http://attic.apache.org
> > 
> > + internals:  > href="https://ci.apache.org/builders/attic-site;>Buildbot job to
> > build from source and commit generated html,  > href="https://github.com/apache/infrastructure-puppet/blob/deployment/mod
> > ules/svnwcsub/files/svnwcsub.conf#L36">svnwcsub configuration to
> > update generated html from svn to webserver> 
> >  jira  >  href="https://issues.apache.org/jira/browse/ATTIC;>https://issues.ap
> >  ache.org/jira/browse/ATTIC committees.xml  >  href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/da
> >  ta/committees.xml">https://svn.apache.org/repos/asf/comdev/projects.a
> >  pache.org/data/committees.xml> 
> >

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Henk P. Penning 

On Sat, 28 Apr 2018, Jan Iversen wrote:


Date: Sat, 28 Apr 2018 12:54:40 +0200
From: Jan Iversen <j...@apache.org>
To: general@attic.apache.org
Subject: Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

Isn’t it a bit premature to change the process ? Seen from pow we are
experimenting with at least 3 proposals of which 1 does not need a
buildbot.


  I agree ; site maintainance (with svn) can be as simple as

  -- svn up
  -- edit data/attic.yaml
  -- make
  -- commit

  I assume the same works after a switch to git.

  Regards,

  Henk Penning


rgds
jan I

Sent from my iPad


On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:

Author: hboutemy
Date: Sat Apr 28 10:33:07 2018
New Revision: 1830424

URL: http://svn.apache.org/viewvc?rev=1830424=rev
Log:
added links to Buildbot job and svnwcsub configuration

Modified:
   attic/site/xdocs/process.xml

Modified: attic/site/xdocs/process.xml
URL: 
http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=1830423=1830424=diff
==
--- attic/site/xdocs/process.xml (original)
+++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
@@ -76,8 +76,9 @@

  The following are usefull svn/https locations:

- svn site http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/asf/attic
+ svn site http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf/attic: 
sources in xdocs, generated html in docs
 site http://attic.apache.org;>http://attic.apache.org
+ internals: https://ci.apache.org/builders/attic-site;>Buildbot job to build from 
source and commit generated html, https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnwcsub/files/svnwcsub.conf#L36;>svnwcsub 
configuration to update generated html from svn to webserver
 jira https://issues.apache.org/jira/browse/ATTIC;>https://issues.apache.org/jira/browse/ATTIC
 committees.xml https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml;>https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml







   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

Re: svn commit: r1830424 - /attic/site/xdocs/process.xml

2018-04-28 Thread Jan Iversen 
Isn’t it a bit premature to change the process ? Seen from pow we are 
experimenting with at least 3 proposals of which 1 does not need a buildbot.

This is of course just my opinion.

rgds
jan I

Sent from my iPad

> On 28 Apr 2018, at 12:33, hbout...@apache.org wrote:
> 
> Author: hboutemy
> Date: Sat Apr 28 10:33:07 2018
> New Revision: 1830424
> 
> URL: http://svn.apache.org/viewvc?rev=1830424=rev
> Log:
> added links to Buildbot job and svnwcsub configuration
> 
> Modified:
>attic/site/xdocs/process.xml
> 
> Modified: attic/site/xdocs/process.xml
> URL: 
> http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1830424=1830423=1830424=diff
> ==
> --- attic/site/xdocs/process.xml (original)
> +++ attic/site/xdocs/process.xml Sat Apr 28 10:33:07 2018
> @@ -76,8 +76,9 @@
> 
>   The following are usefull svn/https locations:
> 
> - svn site  href="http://svn.apache.org/repos/asf/attic;>http://svn.apache.org/repos/asf/attic
> + svn site  href="http://svn.apache.org/viewvc/attic;>http://svn.apache.org/repos/asf/attic:
>  sources in xdocs, generated html in docs
>  site  href="http://attic.apache.org;>http://attic.apache.org
> + internals:  href="https://ci.apache.org/builders/attic-site;>Buildbot job to build 
> from source and commit generated html,  href="https://github.com/apache/infrastructure-puppet/blob/deployment/modules/svnwcsub/files/svnwcsub.conf#L36;>svnwcsub
>  configuration to update generated html from svn to webserver
>  jira  href="https://issues.apache.org/jira/browse/ATTIC;>https://issues.apache.org/jira/browse/ATTIC
>  committees.xml  href="https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml;>https://svn.apache.org/repos/asf/comdev/projects.apache.org/data/committees.xml
> 
> 
>