You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@attic.apache.org by he...@apache.org on 2018/04/24 04:52:50 UTC
svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Author: henkp
Date: Tue Apr 24 04:52:50 2018
New Revision: 1829959
URL: http://svn.apache.org/viewvc?rev=1829959&view=rev
Log:
rm tab (illegal)
Modified:
attic/site-jekyll/src/_data/projects.json
Modified: attic/site-jekyll/src/_data/projects.json
URL: http://svn.apache.org/viewvc/attic/site-jekyll/src/_data/projects.json?rev=1829959&r1=1829958&r2=1829959&view=diff
==============================================================================
--- attic/site-jekyll/src/_data/projects.json (original)
+++ attic/site-jekyll/src/_data/projects.json Tue Apr 24 04:52:50 2018
@@ -18,7 +18,7 @@
"jira": "ACE",
"wiki": "https://cwiki.apache.org/confluence/display/ace/",
"mailnames": ["dev", "commits", "users"],
- "description": " Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
+ "description": "Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
},
{
"name": "Avalon",
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Posted by sebb <se...@gmail.com>.
On 24 April 2018 at 11:21, Jan Iversen <ja...@gmail.com> wrote:
>
>
>> On 24 Apr 2018, at 12:16, sebb <se...@gmail.com> wrote:
>>
>> On 24 April 2018 at 10:58, Jan Iversen <jani@apache.org <ma...@apache.org>> wrote:
>>>
>>>
>>> Sent from my iPad
>>>
>>>> On 24 Apr 2018, at 11:49, sebb <se...@gmail.com> wrote:
>>>>
>>>>> On 24 April 2018 at 05:52, <he...@apache.org> wrote:
>>>>> Author: henkp
>>>>> Date: Tue Apr 24 04:52:50 2018
>>>>> New Revision: 1829959
>>>>>
>>>>> URL: http://svn.apache.org/viewvc?rev=1829959&view=rev
>>>>> Log:
>>>>> rm tab (illegal)
>>>>
>>>> The text was updated to make sure it agreed with the existing Attic site.
>>> why are you aiming at 100% match with the existing site ? it hardly makes sense, especially in cases where the exiting site have errors.
>>
>> I already explained that this makes it easier to check that the
>> existing data has been correctly included.
>>
>> If I have found errors in the existing site then I have fixed them.
>>
>> I don't know of a better way.
>>
>>> Could we please take a break in the stream of commits, and instead use the time to decide, what we as a community wants. Making site-jekyll 100% like the existing site (just new maintenance), does not really help the decision of what we want.
>>>
>>
>> Am I only allowed to commit the finished PoC?
> Of course not, you are a committer you commit when you want.
>>
>>> I still argue, we just need something simple, a build script and a couple of templates (which are easy to read).
>>
>> That is my aim too, but I am doing it in stages.
>>
>> So please don't judge the PoC until it is complete.
> I believe you have made a proof of concept, enough to make a decision, but if you want to complete it, knowing the risk it will not go into production, it is totally your choice.
>
> I am not against you working on site-jekyll, I am just trying to help optimise our normally very scarce resources and as I wrote in my preliminary review I see problems with the site-jekyll solution.
Many of the problems you mentioned are no longer present, or are in
process of being addressed.
So I think it's too early to say that the solution will not work.
Or that it does not meet whatever the requirements are.
> rgds
> Jan I.
>
>
>>
>>> rgds
>>> jan i
>>>>
>>>>> Modified:
>>>>> attic/site-jekyll/src/_data/projects.json
>>>>>
>>>>> Modified: attic/site-jekyll/src/_data/projects.json
>>>>> URL: http://svn.apache.org/viewvc/attic/site-jekyll/src/_data/projects.json?rev=1829959&r1=1829958&r2=1829959&view=diff
>>>>> ==============================================================================
>>>>> --- attic/site-jekyll/src/_data/projects.json (original)
>>>>> +++ attic/site-jekyll/src/_data/projects.json Tue Apr 24 04:52:50 2018
>>>>> @@ -18,7 +18,7 @@
>>>>> "jira": "ACE",
>>>>> "wiki": "https://cwiki.apache.org/confluence/display/ace/",
>>>>> "mailnames": ["dev", "commits", "users"],
>>>>> - "description": " Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>>>>> + "description": "Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>>>>> },
>>>>> {
>>>>> "name": "Avalon",
>
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Posted by Jan Iversen <ja...@gmail.com>.
> On 24 Apr 2018, at 12:16, sebb <se...@gmail.com> wrote:
>
> On 24 April 2018 at 10:58, Jan Iversen <jani@apache.org <ma...@apache.org>> wrote:
>>
>>
>> Sent from my iPad
>>
>>> On 24 Apr 2018, at 11:49, sebb <se...@gmail.com> wrote:
>>>
>>>> On 24 April 2018 at 05:52, <he...@apache.org> wrote:
>>>> Author: henkp
>>>> Date: Tue Apr 24 04:52:50 2018
>>>> New Revision: 1829959
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=1829959&view=rev
>>>> Log:
>>>> rm tab (illegal)
>>>
>>> The text was updated to make sure it agreed with the existing Attic site.
>> why are you aiming at 100% match with the existing site ? it hardly makes sense, especially in cases where the exiting site have errors.
>
> I already explained that this makes it easier to check that the
> existing data has been correctly included.
>
> If I have found errors in the existing site then I have fixed them.
>
> I don't know of a better way.
>
>> Could we please take a break in the stream of commits, and instead use the time to decide, what we as a community wants. Making site-jekyll 100% like the existing site (just new maintenance), does not really help the decision of what we want.
>>
>
> Am I only allowed to commit the finished PoC?
Of course not, you are a committer you commit when you want.
>
>> I still argue, we just need something simple, a build script and a couple of templates (which are easy to read).
>
> That is my aim too, but I am doing it in stages.
>
> So please don't judge the PoC until it is complete.
I believe you have made a proof of concept, enough to make a decision, but if you want to complete it, knowing the risk it will not go into production, it is totally your choice.
I am not against you working on site-jekyll, I am just trying to help optimise our normally very scarce resources and as I wrote in my preliminary review I see problems with the site-jekyll solution.
rgds
Jan I.
>
>> rgds
>> jan i
>>>
>>>> Modified:
>>>> attic/site-jekyll/src/_data/projects.json
>>>>
>>>> Modified: attic/site-jekyll/src/_data/projects.json
>>>> URL: http://svn.apache.org/viewvc/attic/site-jekyll/src/_data/projects.json?rev=1829959&r1=1829958&r2=1829959&view=diff
>>>> ==============================================================================
>>>> --- attic/site-jekyll/src/_data/projects.json (original)
>>>> +++ attic/site-jekyll/src/_data/projects.json Tue Apr 24 04:52:50 2018
>>>> @@ -18,7 +18,7 @@
>>>> "jira": "ACE",
>>>> "wiki": "https://cwiki.apache.org/confluence/display/ace/",
>>>> "mailnames": ["dev", "commits", "users"],
>>>> - "description": " Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>>>> + "description": "Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>>>> },
>>>> {
>>>> "name": "Avalon",
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Posted by sebb <se...@gmail.com>.
On 24 April 2018 at 10:58, Jan Iversen <ja...@apache.org> wrote:
>
>
> Sent from my iPad
>
>> On 24 Apr 2018, at 11:49, sebb <se...@gmail.com> wrote:
>>
>>> On 24 April 2018 at 05:52, <he...@apache.org> wrote:
>>> Author: henkp
>>> Date: Tue Apr 24 04:52:50 2018
>>> New Revision: 1829959
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1829959&view=rev
>>> Log:
>>> rm tab (illegal)
>>
>> The text was updated to make sure it agreed with the existing Attic site.
> why are you aiming at 100% match with the existing site ? it hardly makes sense, especially in cases where the exiting site have errors.
I already explained that this makes it easier to check that the
existing data has been correctly included.
If I have found errors in the existing site then I have fixed them.
I don't know of a better way.
> Could we please take a break in the stream of commits, and instead use the time to decide, what we as a community wants. Making site-jekyll 100% like the existing site (just new maintenance), does not really help the decision of what we want.
>
Am I only allowed to commit the finished PoC?
> I still argue, we just need something simple, a build script and a couple of templates (which are easy to read).
That is my aim too, but I am doing it in stages.
So please don't judge the PoC until it is complete.
> rgds
> jan i
>>
>>> Modified:
>>> attic/site-jekyll/src/_data/projects.json
>>>
>>> Modified: attic/site-jekyll/src/_data/projects.json
>>> URL: http://svn.apache.org/viewvc/attic/site-jekyll/src/_data/projects.json?rev=1829959&r1=1829958&r2=1829959&view=diff
>>> ==============================================================================
>>> --- attic/site-jekyll/src/_data/projects.json (original)
>>> +++ attic/site-jekyll/src/_data/projects.json Tue Apr 24 04:52:50 2018
>>> @@ -18,7 +18,7 @@
>>> "jira": "ACE",
>>> "wiki": "https://cwiki.apache.org/confluence/display/ace/",
>>> "mailnames": ["dev", "commits", "users"],
>>> - "description": " Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>>> + "description": "Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>>> },
>>> {
>>> "name": "Avalon",
>>>
>>>
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Posted by Jan Iversen <ja...@gmail.com>.
> On 24 Apr 2018, at 15:38, Henk P. Penning <pe...@uu.nl> wrote:
>
> On Tue, 24 Apr 2018, Jan Iversen wrote:
>
>> Date: Tue, 24 Apr 2018 11:58:10 +0200
>> From: Jan Iversen <ja...@apache.org>
>> To: general@attic.apache.org
>> Subject: Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
>
>> I still argue, we just need something simple, a build script and a
>> couple of templates (which are easy to read).
>
> I just committed 'mk-stuff' ; 200 lines of perl-code ;
> for now, the texts for {index,resolution,process}.html
> are in mk-stuff too ; I couldn't decide where to put them.
>
> Prog 'mk-stuff' generates {index,resolution,process}.html
> and projects/*.
>
> At work : http://mirror-vm80.apache.org/index.html
>
> Not all (per project) attributes are shown correctly,
> but you get the idea.
And I like the idea !
A few comments:
- How about doing “mv _data/* .” And “mv _layout/* .”, that makes things even simpler
- Can project.html not be without the strange loops etc ?
Btw seems you are not using that.
- We should also remove some of the fields in projects.json
- You have the templates directly in mk_stuff, it would be more readable if stored as a file, and e.g. replacing ATTIC_X
Have a nice afternoon.
rgds
Jan I.
>
>> jan i
>
> Regards,
>
> HPP
>
> ------------------------------------------------------------ _
> Henk P. Penning, ICT-beta R Uithof MG-403 _/ \_
> Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penning@uu.nl \_/
Re: svn commit: r1829959 -
/attic/site-jekyll/src/_data/projects.json
Posted by "Henk P. Penning" <pe...@uu.nl>.
On Tue, 24 Apr 2018, Jan Iversen wrote:
> Date: Tue, 24 Apr 2018 11:58:10 +0200
> From: Jan Iversen <ja...@apache.org>
> To: general@attic.apache.org
> Subject: Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
> I still argue, we just need something simple, a build script and a
> couple of templates (which are easy to read).
I just committed 'mk-stuff' ; 200 lines of perl-code ;
for now, the texts for {index,resolution,process}.html
are in mk-stuff too ; I couldn't decide where to put them.
Prog 'mk-stuff' generates {index,resolution,process}.html
and projects/*.
At work : http://mirror-vm80.apache.org/index.html
Not all (per project) attributes are shown correctly,
but you get the idea.
> jan i
Regards,
HPP
------------------------------------------------------------ _
Henk P. Penning, ICT-beta R Uithof MG-403 _/ \_
Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penning@uu.nl \_/
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Posted by Jan Iversen <ja...@apache.org>.
Sent from my iPad
> On 24 Apr 2018, at 11:49, sebb <se...@gmail.com> wrote:
>
>> On 24 April 2018 at 05:52, <he...@apache.org> wrote:
>> Author: henkp
>> Date: Tue Apr 24 04:52:50 2018
>> New Revision: 1829959
>>
>> URL: http://svn.apache.org/viewvc?rev=1829959&view=rev
>> Log:
>> rm tab (illegal)
>
> The text was updated to make sure it agreed with the existing Attic site.
why are you aiming at 100% match with the existing site ? it hardly makes sense, especially in cases where the exiting site have errors.
Could we please take a break in the stream of commits, and instead use the time to decide, what we as a community wants. Making site-jekyll 100% like the existing site (just new maintenance), does not really help the decision of what we want.
I still argue, we just need something simple, a build script and a couple of templates (which are easy to read).
rgds
jan i
>
>> Modified:
>> attic/site-jekyll/src/_data/projects.json
>>
>> Modified: attic/site-jekyll/src/_data/projects.json
>> URL: http://svn.apache.org/viewvc/attic/site-jekyll/src/_data/projects.json?rev=1829959&r1=1829958&r2=1829959&view=diff
>> ==============================================================================
>> --- attic/site-jekyll/src/_data/projects.json (original)
>> +++ attic/site-jekyll/src/_data/projects.json Tue Apr 24 04:52:50 2018
>> @@ -18,7 +18,7 @@
>> "jira": "ACE",
>> "wiki": "https://cwiki.apache.org/confluence/display/ace/",
>> "mailnames": ["dev", "commits", "users"],
>> - "description": " Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>> + "description": "Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
>> },
>> {
>> "name": "Avalon",
>>
>>
Re: svn commit: r1829959 - /attic/site-jekyll/src/_data/projects.json
Posted by sebb <se...@gmail.com>.
On 24 April 2018 at 05:52, <he...@apache.org> wrote:
> Author: henkp
> Date: Tue Apr 24 04:52:50 2018
> New Revision: 1829959
>
> URL: http://svn.apache.org/viewvc?rev=1829959&view=rev
> Log:
> rm tab (illegal)
The text was updated to make sure it agreed with the existing Attic site.
> Modified:
> attic/site-jekyll/src/_data/projects.json
>
> Modified: attic/site-jekyll/src/_data/projects.json
> URL: http://svn.apache.org/viewvc/attic/site-jekyll/src/_data/projects.json?rev=1829959&r1=1829958&r2=1829959&view=diff
> ==============================================================================
> --- attic/site-jekyll/src/_data/projects.json (original)
> +++ attic/site-jekyll/src/_data/projects.json Tue Apr 24 04:52:50 2018
> @@ -18,7 +18,7 @@
> "jira": "ACE",
> "wiki": "https://cwiki.apache.org/confluence/display/ace/",
> "mailnames": ["dev", "commits", "users"],
> - "description": " Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
> + "description": "Apache ACE was a software distribution framework that allows you to centrally manage and distribute software components, configuration data and other artifacts to target systems. It is built using OSGi and can be deployed in different topologies. The target systems are usually also OSGi based, but don't have to be. "
> },
> {
> "name": "Avalon",
>
>