Re: svn commit: r1830185 - /attic/site-lua/docs/OUT

2018-04-27 Thread sebb
On 27 April 2018 at 15:47, sebb <seb...@gmail.com> wrote:
> On 27 April 2018 at 15:41, Henk P. Penning <penn...@uu.nl> wrote:
>> On Thu, 26 Apr 2018, sebb wrote:
>>
>>> Date: Thu, 26 Apr 2018 15:13:08 +0200
>>> From: sebb <seb...@gmail.com>
>>> To: general@attic.apache.org
>>> Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
>>
>>
>>>>   I think postlude should be just a text blob :
>>>>
>>>> postlude: |-
>>>>   just a blob
>>>>
>>>>   Adding structuring is artificial, and a source of errors.
>>>
>>>
>>> It makes checking the generated HTML harder.
>>
>>
>>   how so ? the generate HTML is exactly the same as the blob ;
>>
>>   See the source of the hardest case :
>>
>> http://mirror-vm80.apache.org/projects/jakarta-taglibs.html
>>
>>   compare with :
>>
>> https://svn.apache.org/repos/asf/attic/site-lua/docs/data/attic.yaml
>
> I stand corrected; I had assumed the blob was flattened into a single line.

However the YAML version has lost the original indentation.
Many of the line breaks in the YAML version as also different, but I
assume that was caused by some unnecessary line-wrapping

These make it harder to test for significant changes.

>>   Groeten,
>>
>>   HPP
>>
>>
>>>>>>   can you please fix the projects.json ?
>>>>>>   Avoid the booleans by changing the values of
>>>>>>   'nodist' and 'keys' to 1 (instead of 'true').
>>>>
>>>>
>>>>
>>>>> Why avoid booleans?
>>>>
>>>>
>>>>
>>>>   It is a perl thingy ; a JSON-read accepts true and false,
>>>>   but the resulting data-structure has typed values
>>>>   JSON::XS::Boolean (or some such) that YAML doesn't grok.
>>>>   Using just 0 and 1 makes it a little easier (without
>>>>   loss). Please fix.
>>>
>>>
>>> The Jekyll PoC does not use Perl.
>>>
>>> It's also ambiguous to use 0 and 1 because their truth values depends
>>> on the language.
>>>
>>>>   Groeten,
>>>>
>>>>   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 \_/
>>>
>>>
>>
>>    _
>> 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: r1830185 - /attic/site-lua/docs/OUT

2018-04-27 Thread sebb
On 27 April 2018 at 15:41, Henk P. Penning <penn...@uu.nl> wrote:
> On Thu, 26 Apr 2018, sebb wrote:
>
>> Date: Thu, 26 Apr 2018 15:13:08 +0200
>> From: sebb <seb...@gmail.com>
>> To: general@attic.apache.org
>> Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
>
>
>>>   I think postlude should be just a text blob :
>>>
>>> postlude: |-
>>>   just a blob
>>>
>>>   Adding structuring is artificial, and a source of errors.
>>
>>
>> It makes checking the generated HTML harder.
>
>
>   how so ? the generate HTML is exactly the same as the blob ;
>
>   See the source of the hardest case :
>
> http://mirror-vm80.apache.org/projects/jakarta-taglibs.html
>
>   compare with :
>
> https://svn.apache.org/repos/asf/attic/site-lua/docs/data/attic.yaml

I stand corrected; I had assumed the blob was flattened into a single line.

>   Groeten,
>
>   HPP
>
>
>>>>>   can you please fix the projects.json ?
>>>>>   Avoid the booleans by changing the values of
>>>>>   'nodist' and 'keys' to 1 (instead of 'true').
>>>
>>>
>>>
>>>> Why avoid booleans?
>>>
>>>
>>>
>>>   It is a perl thingy ; a JSON-read accepts true and false,
>>>   but the resulting data-structure has typed values
>>>   JSON::XS::Boolean (or some such) that YAML doesn't grok.
>>>   Using just 0 and 1 makes it a little easier (without
>>>   loss). Please fix.
>>
>>
>> The Jekyll PoC does not use Perl.
>>
>> It's also ambiguous to use 0 and 1 because their truth values depends
>> on the language.
>>
>>>   Groeten,
>>>
>>>   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 \_/
>>
>>
>
>    _
> 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: r1830185 - /attic/site-lua/docs/OUT

2018-04-27 Thread Henk P. Penning

On Thu, 26 Apr 2018, sebb wrote:


Date: Thu, 26 Apr 2018 15:13:08 +0200
From: sebb <seb...@gmail.com>
To: general@attic.apache.org
Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT



  I think postlude should be just a text blob :

postlude: |-
  just a blob

  Adding structuring is artificial, and a source of errors.


It makes checking the generated HTML harder.


  how so ? the generate HTML is exactly the same as the blob ;

  See the source of the hardest case :

http://mirror-vm80.apache.org/projects/jakarta-taglibs.html

  compare with :

https://svn.apache.org/repos/asf/attic/site-lua/docs/data/attic.yaml

  Groeten,

  HPP


  can you please fix the projects.json ?
  Avoid the booleans by changing the values of
  'nodist' and 'keys' to 1 (instead of 'true').




Why avoid booleans?



  It is a perl thingy ; a JSON-read accepts true and false,
  but the resulting data-structure has typed values
  JSON::XS::Boolean (or some such) that YAML doesn't grok.
  Using just 0 and 1 makes it a little easier (without
  loss). Please fix.


The Jekyll PoC does not use Perl.

It's also ambiguous to use 0 and 1 because their truth values depends
on the language.


  Groeten,

  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 \_/




   _
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: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread sebb
On 26 April 2018 at 14:04, Henk P. Penning <penn...@uu.nl> wrote:
> On Thu, 26 Apr 2018, sebb wrote:
>
>> Date: Thu, 26 Apr 2018 13:25:49 +0200
>> From: sebb <seb...@gmail.com>
>> To: general@attic.apache.org
>> Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
>
>
>> I have recently tried using an array for postlude.
>> That has the advantage that the output is still folded.
>> I would like to keep that feature if possible.
>> I will try converting the copy under site-jekyll to YAML and see if
>> there are any issues
>
>
>   I think postlude should be just a text blob :
>
> postlude: |-
>   just a blob
>
>   Adding structuring is artificial, and a source of errors.

It makes checking the generated HTML harder.

And I don't agree it causes errors.

>
>>>   can you please fix the projects.json ?
>>>   Avoid the booleans by changing the values of
>>>   'nodist' and 'keys' to 1 (instead of 'true').
>
>
>> Why avoid booleans?
>
>
>   It is a perl thingy ; a JSON-read accepts true and false,
>   but the resulting data-structure has typed values
>   JSON::XS::Boolean (or some such) that YAML doesn't grok.
>   Using just 0 and 1 makes it a little easier (without
>   loss). Please fix.

The Jekyll PoC does not use Perl.

It's also ambiguous to use 0 and 1 because their truth values depends
on the language.

>   Groeten,
>
>   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: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread Henk P. Penning

On Thu, 26 Apr 2018, sebb wrote:


Date: Thu, 26 Apr 2018 13:25:49 +0200
From: sebb <seb...@gmail.com>
To: general@attic.apache.org
Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT



I have recently tried using an array for postlude.
That has the advantage that the output is still folded.
I would like to keep that feature if possible.
I will try converting the copy under site-jekyll to YAML and see if
there are any issues


  I think postlude should be just a text blob :

postlude: |-
  just a blob

  Adding structuring is artificial, and a source of errors.


  can you please fix the projects.json ?
  Avoid the booleans by changing the values of
  'nodist' and 'keys' to 1 (instead of 'true').



Why avoid booleans?


  It is a perl thingy ; a JSON-read accepts true and false,
  but the resulting data-structure has typed values
  JSON::XS::Boolean (or some such) that YAML doesn't grok.
  Using just 0 and 1 makes it a little easier (without
  loss). Please fix.

  Groeten,

  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: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread Jan Iversen
and I forgot I still need to find a good yaml validator online, so I do not 
commit obvious mistakes.

rgds
jan i

Sent from my iPad

> On 26 Apr 2018, at 14:52, Henk P. Penning <penn...@uu.nl> wrote:
> 
>> On Thu, 26 Apr 2018, Jan Iversen wrote:
>> 
>> Date: Thu, 26 Apr 2018 13:32:31 +0200
>> From: Jan Iversen <j...@apache.org>
>> To: general@attic.apache.org
>> Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
> 
>> Why is that? Apart from a couple of old sites data are simple one liners.
> 
>  For example ACE ; I think this :
> 
>---
>name: ACE
>project: ace
>retired: December 2017
>mailnames:
>  - dev
>  - commits
>  - users
>jira: ACE
>scm: svn
>wiki: https://cwiki.apache.org/confluence/display/ace/
>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.
>---
> 
>  ... is better than :
> 
>{
>  "name":"ACE",
>  "project": "ace",
>  "retired": "December 2017",
>  "scm": "svn",
>  "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. "
>},
> 
>  I hate lines much longer than 80 chars.
> 
>> Jan I
> 
>  Groeten,
> 
>  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: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread Jan Iversen


Sent from my iPad

> On 26 Apr 2018, at 14:52, Henk P. Penning <penn...@uu.nl> wrote:
> 
>> On Thu, 26 Apr 2018, Jan Iversen wrote:
>> 
>> Date: Thu, 26 Apr 2018 13:32:31 +0200
>> From: Jan Iversen <j...@apache.org>
>> To: general@attic.apache.org
>> Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT
> 
>> Why is that? Apart from a couple of old sites data are simple one liners.
> 
>  For example ACE ; I think this :
> 
>---
>name: ACE
>project: ace
>retired: December 2017
>mailnames:
>  - dev
>  - commits
>  - users
>jira: ACE
>scm: svn
>wiki: https://cwiki.apache.org/confluence/display/ace/
>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.
>---
> 
>  ... is better than :
> 
>{
>  "name":"ACE",
>  "project": "ace",
>  "retired": "December 2017",
>  "scm": "svn",
>  "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. "
>},
> 
>  I hate lines much longer than 80 chars.
and that is exactly one of the old sites we do not touch anymore.

look at the never sites.

rgds
jan i
> 
>> Jan I
> 
>  Groeten,
> 
>  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: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread Henk P. Penning

On Thu, 26 Apr 2018, Jan Iversen wrote:


Date: Thu, 26 Apr 2018 13:32:31 +0200
From: Jan Iversen <j...@apache.org>
To: general@attic.apache.org
Subject: Re: svn commit: r1830185 - /attic/site-lua/docs/OUT



Why is that? Apart from a couple of old sites data are simple one liners.


  For example ACE ; I think this :

---
name: ACE
project: ace
retired: December 2017
mailnames:
  - dev
  - commits
  - users
jira: ACE
scm: svn
wiki: https://cwiki.apache.org/confluence/display/ace/
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.
---

  ... is better than :

{
  "name":"ACE",
  "project": "ace",
  "retired": "December 2017",
  "scm": "svn",
  "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. "
},

  I hate lines much longer than 80 chars.


Jan I


  Groeten,

  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: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread Jan Iversen


Sent from my iPhone

> On 26 Apr 2018, at 13:25, sebb <seb...@gmail.com> wrote:
> 
>> On 26 April 2018 at 12:01, Henk P. Penning <penn...@uu.nl> wrote:
>>> On Thu, 26 Apr 2018, he...@apache.org wrote:
>>> 
>>> Date: Thu, 26 Apr 2018 12:37:14 +0200
>>> From: he...@apache.org
>>> To: general@attic.apache.org
>>> Subject: svn commit: r1830185 - /attic/site-lua/docs/OUT
>> 
>> 
>>  I looked a YAML ... ; perhaps it is a better format ...
> 
> IMO it is easier to read and maintain so I am fine with that.

Why is that? Apart from a couple of old sites data are simple one liners.

My preference continues to be json.

Reds
Jan I
> 
>>  Fixed :
>> 
>>  -- fields in a prefered order
>>  -- 'description' and 'postlude' folden
> 
> I have recently tried using an array for postlude.
> That has the advantage that the output is still folded.
> I would like to keep that feature if possible.
> I will try converting the copy under site-jekyll to YAML and see if
> there are any issues
> 
>>  What do you think ?
>> 
>> Sebb,
>> 
>>  can you please fix the projects.json ?
>>  Avoid the booleans by changing the values of
>>  'nodist' and 'keys' to 1 (instead of 'true').
>> 
>> 
> 
> Why avoid booleans?


Re: svn commit: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread sebb
On 26 April 2018 at 12:01, Henk P. Penning <penn...@uu.nl> wrote:
> On Thu, 26 Apr 2018, he...@apache.org wrote:
>
>> Date: Thu, 26 Apr 2018 12:37:14 +0200
>> From: he...@apache.org
>> To: general@attic.apache.org
>> Subject: svn commit: r1830185 - /attic/site-lua/docs/OUT
>
>
>   I looked a YAML ... ; perhaps it is a better format ...

IMO it is easier to read and maintain so I am fine with that.

>   Fixed :
>
>   -- fields in a prefered order
>   -- 'description' and 'postlude' folden

I have recently tried using an array for postlude.
That has the advantage that the output is still folded.
I would like to keep that feature if possible.
I will try converting the copy under site-jekyll to YAML and see if
there are any issues

>   What do you think ?
>
> Sebb,
>
>   can you please fix the projects.json ?
>   Avoid the booleans by changing the values of
>   'nodist' and 'keys' to 1 (instead of 'true').
>
>

Why avoid booleans?


Re: svn commit: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread Henk P. Penning

On Thu, 26 Apr 2018, he...@apache.org wrote:


Date: Thu, 26 Apr 2018 12:37:14 +0200
From: he...@apache.org
To: general@attic.apache.org
Subject: svn commit: r1830185 - /attic/site-lua/docs/OUT


  I looked a YAML ... ; perhaps it is a better format ...

  Fixed :

  -- fields in a prefered order
  -- 'description' and 'postlude' folden

  What do you think ?

Sebb,

  can you please fix the projects.json ?
  Avoid the booleans by changing the values of
  'nodist' and 'keys' to 1 (instead of 'true').


Author: henkp
Date: Thu Apr 26 10:37:14 2018
New Revision: 1830185

URL: http://svn.apache.org/viewvc?rev=1830185=rev
Log:
test YAML

Added:
   attic/site-lua/docs/OUT

Added: attic/site-lua/docs/OUT
URL: http://svn.apache.org/viewvc/attic/site-lua/docs/OUT?rev=1830185=auto
==
--- attic/site-lua/docs/OUT (added)
+++ attic/site-lua/docs/OUT Thu Apr 26 10:37:14 2018
@@ -0,0 +1,889 @@
+---
+name: Abdera
+project: abdera
+retired: March 2017
+mailnames:
+  - dev
+  - commits
+  - user
+jira: ABDERA
+scm: svn
+wiki: https://cwiki.apache.org/confluence/display/abdera/
+description: |-
+  Apache Abdera was a project to build a functionally-complete,
+  high-performance implementation of the IETF Atom Syndication Format
+  (RFC 4287) and Atom Publishing Protocol (RFC 5023) specifications.
+postlude: |-
+  Some related projects to Abdera are: 
+  
+  http://openddr.mobi/;>OpenDDR - this is a new version
+  of OpenDDR, parts of which were migrated to Apache Devicemap, and now
+  have been merged back to OpenDDR. 
+  https://github.com/nielsbasjes/yauaa;>YAUAA: Yet Another
+  UserAgent Analyzer is an Apache licensed alternative to DeviceMap.
+  Rather than employing a fixed collection of User-Agent (UA) strings as
+  in DeviceMap, YAUAA performs a semantic analysis to determine certain
+  attributes of the UA. 
+  http://devicedetector.net/;>DeviceDetector is an LGPL
+  3.0 licensed PHP project that parses YAML based device data in a
+  similar way as DeviceMap/OpenDDR do with W3C compatible data. 
+  http://mobiledetect.net/;>mobiledetect is an MIT
+  licensed PHP project for detecting mobile devices. 
+  
+---
+name: ACE
+project: ace
+retired: December 2017
+mailnames:
+  - dev
+  - commits
+  - users
+jira: ACE
+scm: svn
+wiki: https://cwiki.apache.org/confluence/display/ace/
+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
+project: avalon
+retired: June 2004
+mailnames:
+  - dev
+jira: AVALON
+scm: svn
+wiki: http://wiki.apache.org/avalon/
+description: |-
+  Apache Avalon was closed long before the creation of the Apache Attic.
+  It's mentioned here for completeness.
+---
+name: AxKit
+retired: August 2009
+mailnames:
+website: http://axkit.org
+description: |-
+  Apache AxKit was an XML Application Server for Apache. It provided
+  on-the-fly conversion from XML to any format, such as HTML, WAP or
+  text using either W3C standard techniques, or flexible custom code.
+---
+name: Axis Sandesha2/C
+project: axis
+subproject: axis2/c/sandesha
+stem: axis-sandesha-c
+retired: September 2014
+mailnames:
+jira: SANDESHA2C
+scm: svn
+description: |-
+  Sandesha2/C was a C implementation of the WS-ReliableMessaging
+  specification. Sandesha2/C was built on top of Apache Axis2/C Web
+  services engine, as a module. Therefore by using Sandesha2/C you could
+  add reliable messaging capability to Web services hosted using
+  Axis2/C. Sandesha2/C could also be used with Axis2/C client to
+  interact with an already hosted Web services in a reliable manner.
+---
+name: Axis Savan/C
+project: axis
+subproject: axis2/c/savan
+retired: September 2014
+mailnames:
+jira: AXIS2C
+scm: svn
+description: |-
+  Savan/C was a C implementation of WS-Eventing specification. Savan/C
+  was built on top of Axis2/C. Therefore by using Savan/C you could add
+  WS-Eventing capability to Web services hosted using Axis2/C. Savan/C
+  was designed as a general publisher/subscriber tool. The arcitecture
+  was designed to abstract the general publisher/subscriber features so
+  that people could support more than one publisher/subscriber
+  mechanisms within the same infrastructure.
+---
+name: Axis Savan/Java
+project: axis
+subproject: axis2/java/savan
+retired: September 2014
+mailnames:
+jira: SAVAN
+description: |-
+  Savan/Java was a Java implementation of WS-Eventing specification.
+  Savan/Java was built on top of Axis2/Java. Therefore by using
+  Savan/Java you could add WS-Eventing capability to Web services hosted
+  using Axis2/Java. Savan/Java was designed as a general
+  publisher/subscriber tool. The arcitecture was designed

svn commit: r1830185 - /attic/site-lua/docs/OUT

2018-04-26 Thread henkp
Author: henkp
Date: Thu Apr 26 10:37:14 2018
New Revision: 1830185

URL: http://svn.apache.org/viewvc?rev=1830185=rev
Log:
test YAML

Added:
attic/site-lua/docs/OUT

Added: attic/site-lua/docs/OUT
URL: http://svn.apache.org/viewvc/attic/site-lua/docs/OUT?rev=1830185=auto
==
--- attic/site-lua/docs/OUT (added)
+++ attic/site-lua/docs/OUT Thu Apr 26 10:37:14 2018
@@ -0,0 +1,889 @@
+---
+name: Abdera
+project: abdera
+retired: March 2017
+mailnames:
+  - dev
+  - commits
+  - user
+jira: ABDERA
+scm: svn
+wiki: https://cwiki.apache.org/confluence/display/abdera/
+description: |-
+  Apache Abdera was a project to build a functionally-complete,
+  high-performance implementation of the IETF Atom Syndication Format
+  (RFC 4287) and Atom Publishing Protocol (RFC 5023) specifications.
+postlude: |-
+  Some related projects to Abdera are: 
+  
+  http://openddr.mobi/;>OpenDDR - this is a new version
+  of OpenDDR, parts of which were migrated to Apache Devicemap, and now
+  have been merged back to OpenDDR. 
+  https://github.com/nielsbasjes/yauaa;>YAUAA: Yet Another
+  UserAgent Analyzer is an Apache licensed alternative to DeviceMap.
+  Rather than employing a fixed collection of User-Agent (UA) strings as
+  in DeviceMap, YAUAA performs a semantic analysis to determine certain
+  attributes of the UA. 
+  http://devicedetector.net/;>DeviceDetector is an LGPL
+  3.0 licensed PHP project that parses YAML based device data in a
+  similar way as DeviceMap/OpenDDR do with W3C compatible data. 
+  http://mobiledetect.net/;>mobiledetect is an MIT
+  licensed PHP project for detecting mobile devices. 
+  
+---
+name: ACE
+project: ace
+retired: December 2017
+mailnames:
+  - dev
+  - commits
+  - users
+jira: ACE
+scm: svn
+wiki: https://cwiki.apache.org/confluence/display/ace/
+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
+project: avalon
+retired: June 2004
+mailnames:
+  - dev
+jira: AVALON
+scm: svn
+wiki: http://wiki.apache.org/avalon/
+description: |-
+  Apache Avalon was closed long before the creation of the Apache Attic.
+  It's mentioned here for completeness.
+---
+name: AxKit
+retired: August 2009
+mailnames:
+website: http://axkit.org
+description: |-
+  Apache AxKit was an XML Application Server for Apache. It provided
+  on-the-fly conversion from XML to any format, such as HTML, WAP or
+  text using either W3C standard techniques, or flexible custom code.
+---
+name: Axis Sandesha2/C
+project: axis
+subproject: axis2/c/sandesha
+stem: axis-sandesha-c
+retired: September 2014
+mailnames:
+jira: SANDESHA2C
+scm: svn
+description: |-
+  Sandesha2/C was a C implementation of the WS-ReliableMessaging
+  specification. Sandesha2/C was built on top of Apache Axis2/C Web
+  services engine, as a module. Therefore by using Sandesha2/C you could
+  add reliable messaging capability to Web services hosted using
+  Axis2/C. Sandesha2/C could also be used with Axis2/C client to
+  interact with an already hosted Web services in a reliable manner.
+---
+name: Axis Savan/C
+project: axis
+subproject: axis2/c/savan
+retired: September 2014
+mailnames:
+jira: AXIS2C
+scm: svn
+description: |-
+  Savan/C was a C implementation of WS-Eventing specification. Savan/C
+  was built on top of Axis2/C. Therefore by using Savan/C you could add
+  WS-Eventing capability to Web services hosted using Axis2/C. Savan/C
+  was designed as a general publisher/subscriber tool. The arcitecture
+  was designed to abstract the general publisher/subscriber features so
+  that people could support more than one publisher/subscriber
+  mechanisms within the same infrastructure.
+---
+name: Axis Savan/Java
+project: axis
+subproject: axis2/java/savan
+retired: September 2014
+mailnames:
+jira: SAVAN
+description: |-
+  Savan/Java was a Java implementation of WS-Eventing specification.
+  Savan/Java was built on top of Axis2/Java. Therefore by using
+  Savan/Java you could add WS-Eventing capability to Web services hosted
+  using Axis2/Java. Savan/Java was designed as a general
+  publisher/subscriber tool. The arcitecture was designed to abstract
+  the general publisher/subscriber features so that people could support
+  more than one publisher/subscriber mechanisms within the same
+  infrastructure.
+---
+name: Beehive
+project: beehive
+retired: January 2010
+mailnames:
+  - dev
+  - commits
+  - user
+jira: BEEHIVE
+scm: svn
+wiki: https://wiki.apache.org/beehive
+description: |-
+  Apache Beehive was a simple object model built on J2EE and Struts that
+  used annotations to reduce the amount of required code.
+postlude: |-
+  If you are