On 24 April 2018 at 11:21, Jan Iversen <jancasacon...@gmail.com> wrote: > > >> On 24 Apr 2018, at 12:16, sebb <seb...@gmail.com> wrote: >> >> On 24 April 2018 at 10:58, Jan Iversen <j...@apache.org >> <mailto:j...@apache.org>> wrote: >>> >>> >>> Sent from my iPad >>> >>>> On 24 Apr 2018, at 11:49, sebb <seb...@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", >
