> Am 30.10.2015 um 20:06 schrieb John Hewson <[email protected]>: > > >> On 30 Oct 2015, at 11:58, Maruan Sahyoun <[email protected]> wrote: >> >> Hi, >>> Am 30.10.2015 um 19:39 schrieb John Hewson <[email protected]>: >>> >>> >>>> On 30 Oct 2015, at 03:33, Maruan Sahyoun <[email protected]> wrote: >>>> >>>>> >>>>> Am 29.10.2015 um 20:27 schrieb Maruan Sahyoun <[email protected]>: >>>>> >>>>> >>>>>> Am 29.10.2015 um 20:20 schrieb John Hewson <[email protected]>: >>>>>> >>>>>> >>>>>>> On 29 Oct 2015, at 12:00, Maruan Sahyoun <[email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> Am 29.10.2015 um 19:44 schrieb John Hewson <[email protected] >>>>>>>> <mailto:[email protected]>>: >>>>>>>> >>>>>>>> >>>>>>>>> On 29 Oct 2015, at 02:47, Maruan Sahyoun <[email protected] >>>>>>>>> <mailto:[email protected]>> wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I've done all the changes to be able to build locally using jekyll. >>>>>>>>> Shall we merge the branch jekyll-migration back to trunk or what are >>>>>>>>> the proposed next steps? >>>>>>>> >>>>>>>> I’m confused, why would we want jekyll-migration to be in trunk? >>>>>>>> That’s where our source code lives, not our website. Did you mean >>>>>>>> something else, e.g. merging back into the cmssite branch? >>>>>>> >>>>>>> for clarity >>>>>>> >>>>>>> merge >>>>>>> >>>>>>> https://svn.apache.org/repos/asf/pdfbox/cmssite/branches/jekyll-migration/ >>>>>>> >>>>>>> <https://svn.apache.org/repos/asf/pdfbox/cmssite/branches/jekyll-migration/> >>>>>>> >>>>>>> into >>>>>>> >>>>>>> https://svn.apache.org/repos/asf/pdfbox/cmssite/trunk/ >>>>>>> <https://svn.apache.org/repos/asf/pdfbox/cmssite/trunk/> >>>>>> >>>>>> Ok, great, that makes sense. Yes I’d like to see that get merged in. >>>>> >>>>> We'd need to first remove the Apache CMS build from the …/cmssite/trunk/ >>>>> as a merge would trigger a rebuild which is not compliant. >>>> >>>> given that we agreed to use pdfbox-docs in the past and a merge will >>>> interfere with the Apache CMS I'll be updating pdfbox-docs with the >>>> current jekyll-migration content so we can start building from there. >>>> The ../cmssite/trunk content can remain as a backup for the moment until >>>> the change has been done and the build process is documented. >>> >>> The time for doing this has long since passed. The RC phase is not the time >>> to try changing version control systems. The current situation is not good >>> - we need people beyond yourself to be able to use and contribute to the >>> docs in the manner which they expect. >> >> it has been possible in the past to contribute (before the Apache CMS, with >> the Apache CMS) and still is with the new system. There never was a >> dependency on a single person. Assuming with "they" you are including >> yourself what exactly doesn't meet your requirements? >> >>> >>> If you have no way of moving to jekyll without also abandoning SVN then >>> IMHO we should not be going down that road. Especially not now. >>> >> >> moving from the Apache CMS to jekyll IMHO is a more breaking change than >> moving from SVN to git (assuming that most people should know the basic >> commands for both of have a decent GUI anyway). Again if there are specific >> concerns you have maybe these can be addressed. > > My concern is that there is no technical reason to move away from SVN. > Literally having to reply to another email on this topic is why it’s such a > waste of time… can we just stick with what works and not have everyone > re-learning what used to work fine yesterday? An can we stop wasting time > discussing it?
we had the plan to move the docs to git a while ago which didn't work out as the Apache CMS limited us from pulling the content. With the local build this limitation is gone. No need to revisit that discussion. Agreed. Maruan > > — John > >> "… not now …" Why not? Everything is still available and it's not that a lot >> of people have contributed content over content to the website lately. >> >> BR >> Maruan >> >> >>> — John >>> >>>>> >>>>>> >>>>>>> BR >>>>>>> Maruan >>>>>>> >>>>>>>> >>>>>>>>> We could also use the jekyll-migration branch as a base for >>>>>>>>> pdfbox-docs (git), build from there and after that remove the cmssite >>>>>>>>> svn repo completely. Would be my preference. >>>>>>>> >>>>>>>> That depends on what you mean above… I’ll wait for the explanation. >>>>>>>> Also cmssite is a branch, not a repo. >>>>>> >>>>>> Building from SVN is far simpler. But I’d be interested in removing >>>>>> ApacheCMS from the equation. >>>> >>>> the Apache CMS is already no longer used with the current jekyll local >>>> build. Instead the content is pushed directly into the production site >>>> (same as we do for the javadoc). >>>> >>>> BR >>>> Maruan >>>> >>>>> >>>>> Building from SVN is far simpler because … ? >>>>> >>>>> BR >>>>> Maruan >>>>> >>>>> >>>>>> >>>>>> — John >>>>>> >>>>>>>>> After having done that I'll do some more changes to the website but >>>>>>>>> wanted to complete the infrastructure related topics first. >>>>>>>>> >>>>>>>>> BR >>>>>>>>> Maruan >>>>>>>>> --------------------------------------------------------------------- >>>>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>>>> For additional commands, e-mail: [email protected] >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>>> <mailto:[email protected]> >>>>>>>> For additional commands, e-mail: [email protected] >>>>>>>> <mailto:[email protected]> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> <mailto:[email protected]> >>>>>>> For additional commands, e-mail: [email protected] >>>>>>> <mailto:[email protected]> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> <mailto:[email protected]> >>>> <mailto:[email protected] >>>> <mailto:[email protected]>> >>>> For additional commands, e-mail: [email protected] >>>> <mailto:[email protected]> <mailto:[email protected] >>>> <mailto:[email protected]>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> <mailto:[email protected]> >> For additional commands, e-mail: [email protected] >> <mailto:[email protected]> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
