subject:"Re\: PDFBox Website"

Re: PDFBox Website

2018-02-09 Thread Maruan Sahyoun


> Am 09.02.2018 um 19:28 schrieb Andreas Lehmkuehler :
> 
> Am 08.02.2018 um 10:52 schrieb Maruan Sahyoun:
>> I'm planning to do some adjustments for the PDFBox Website
>> # top level menu for the major sections
>> # a new blog menu entry with the news and the idea that we write short infos 
>> about upcoming changes e.g. 3.0
>> # a link on each page which takes you directly to GitHub to edit/patch
>> # a more prominent banner for PDFBox (kind of hero image) with a download 
>> button
>> A little more like the sorts of
>> https://struts.apache.org
>> http://cassandra.apache.org
>> http://amaterasu.incubator.apache.org (although the teaser is much too big)
>> http://skywalking.incubator.apache.org
>> http://iota.incubator.apache.org (not with the large picture)
>> https://grpc.io
>> https://atom.io
>> WDYT?
> Your changes were always better than those I could have done :-)

thanks

> 
>> Shall I do that on a branch or are you fine with doing the changes on 
>> master. Will be small steps anyway because of available time.
> IMHO, do want you need to do. If you need safety use a branch, if not, minor 
> steps in the master are as well good enough at least for me.
> In the end we are able to restore any version of the website we'd like.

OK - I'll do it on master. For major changes I'll do a feature branch.

Maruan

> 
> Andreas
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Re: PDFBox Website

2018-02-09 Thread Andreas Lehmkuehler


Am 08.02.2018 um 10:52 schrieb Maruan Sahyoun:

I'm planning to do some adjustments for the PDFBox Website

# top level menu for the major sections
# a new blog menu entry with the news and the idea that we write short infos 
about upcoming changes e.g. 3.0
# a link on each page which takes you directly to GitHub to edit/patch
# a more prominent banner for PDFBox (kind of hero image) with a download button

A little more like the sorts of

https://struts.apache.org
http://cassandra.apache.org
http://amaterasu.incubator.apache.org (although the teaser is much too big)
http://skywalking.incubator.apache.org
http://iota.incubator.apache.org (not with the large picture)


https://grpc.io
https://atom.io

WDYT?

Your changes were always better than those I could have done :-)


Shall I do that on a branch or are you fine with doing the changes on master. 
Will be small steps anyway because of available time.
IMHO, do want you need to do. If you need safety use a branch, if not, minor 
steps in the master are as well good enough at least for me.

In the end we are able to restore any version of the website we'd like.

Andreas




-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Re: PDFBox Website [PDFBOX-3040]

2015-10-30 Thread Maruan Sahyoun


> Am 30.10.2015 um 20:06 schrieb John Hewson :
> 
> 
>> On 30 Oct 2015, at 11:58, Maruan Sahyoun  wrote:
>> 
>> Hi,
>>> Am 30.10.2015 um 19:39 schrieb John Hewson :
>>> 
>>> 
 On 30 Oct 2015, at 03:33, Maruan Sahyoun  wrote:
 
> 
> Am 29.10.2015 um 20:27 schrieb Maruan Sahyoun :
> 
> 
>> Am 29.10.2015 um 20:20 schrieb John Hewson :
>> 
>> 
>>> On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
>>> 
 
 Am 29.10.2015 um 19:44 schrieb John Hewson >>> >:
 
 
> On 29 Oct 2015, at 02:47, Maruan Sahyoun  > 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/
>>>  
>>> 
>>> 
>>> into
>>> 
>>> 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
> Marua

Re: PDFBox Website [PDFBOX-3040]

2015-10-30 Thread John Hewson


> On 30 Oct 2015, at 11:58, Maruan Sahyoun  wrote:
> 
> Hi,
>> Am 30.10.2015 um 19:39 schrieb John Hewson :
>> 
>> 
>>> On 30 Oct 2015, at 03:33, Maruan Sahyoun  wrote:
>>> 
 
 Am 29.10.2015 um 20:27 schrieb Maruan Sahyoun :
 
 
> Am 29.10.2015 um 20:20 schrieb John Hewson :
> 
> 
>> On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
>> 
>>> 
>>> Am 29.10.2015 um 19:44 schrieb John Hewson >> >:
>>> 
>>> 
 On 29 Oct 2015, at 02:47, Maruan Sahyoun >>> > 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/
>>  
>> 
>> 
>> into
>> 
>> 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?

— 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: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
>>>

Re: PDFBox Website [PDFBOX-3040]

2015-10-30 Thread Maruan Sahyoun

Hi,
> Am 30.10.2015 um 19:39 schrieb John Hewson :
> 
> 
>> On 30 Oct 2015, at 03:33, Maruan Sahyoun  wrote:
>> 
>>> 
>>> Am 29.10.2015 um 20:27 schrieb Maruan Sahyoun :
>>> 
>>> 
 Am 29.10.2015 um 20:20 schrieb John Hewson :
 
 
> On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
> 
>> 
>> Am 29.10.2015 um 19:44 schrieb John Hewson > >:
>> 
>> 
>>> On 29 Oct 2015, at 02:47, Maruan Sahyoun >> > 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/
>  
> 
> 
> into
> 
> 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. 

"… 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: dev-unsubscr...@pdfbox.apache.org
>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
> 
> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
> 
>>> 
>>> 
>>> ---

Re: PDFBox Website [PDFBOX-3040]

2015-10-30 Thread John Hewson


> On 30 Oct 2015, at 03:33, Maruan Sahyoun  wrote:
> 
>> 
>> Am 29.10.2015 um 20:27 schrieb Maruan Sahyoun :
>> 
>> 
>>> Am 29.10.2015 um 20:20 schrieb John Hewson :
>>> 
>>> 
 On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
 
> 
> Am 29.10.2015 um 19:44 schrieb John Hewson  >:
> 
> 
>> On 29 Oct 2015, at 02:47, Maruan Sahyoun > > 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/ 
 
 
 into
 
 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.

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.

— 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: dev-unsubscr...@pdfbox.apache.org
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
> 
> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
> 
> 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
 
 For additional commands, e-mail: dev-h...@pdfbox.apache.org 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
> 
> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>

Re: PDFBox Website [PDFBOX-3040]

2015-10-30 Thread Maruan Sahyoun


> Am 29.10.2015 um 20:27 schrieb Maruan Sahyoun :
> 
> 
>> Am 29.10.2015 um 20:20 schrieb John Hewson :
>> 
>> 
>>> On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
>>> 
 
 Am 29.10.2015 um 19:44 schrieb John Hewson >>> >:
 
 
> On 29 Oct 2015, at 02:47, Maruan Sahyoun  > 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/ 
>>> 
>>> 
>>> into
>>> 
>>> 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.

> 
>> 
>>> 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: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
 
 For additional commands, e-mail: dev-h...@pdfbox.apache.org 
 
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
>>> 
>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Re: PDFBox Website [PDFBOX-3040]

2015-10-29 Thread Maruan Sahyoun


> Am 29.10.2015 um 20:20 schrieb John Hewson :
> 
> 
>> On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
>> 
>>> 
>>> Am 29.10.2015 um 19:44 schrieb John Hewson >> >:
>>> 
>>> 
 On 29 Oct 2015, at 02:47, Maruan Sahyoun >>> > 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/ 
>> 
>> 
>> into
>> 
>> 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.

> 
>> 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.

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: dev-unsubscr...@pdfbox.apache.org
 For additional commands, e-mail: dev-h...@pdfbox.apache.org
 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
>>> 
>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>>> 
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Re: PDFBox Website [PDFBOX-3040]

2015-10-29 Thread John Hewson


> On 29 Oct 2015, at 12:00, Maruan Sahyoun  wrote:
> 
>> 
>> Am 29.10.2015 um 19:44 schrieb John Hewson > >:
>> 
>> 
>>> On 29 Oct 2015, at 02:47, Maruan Sahyoun >> > 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/ 
> 
> 
> into
> 
> https://svn.apache.org/repos/asf/pdfbox/cmssite/trunk/ 
> 

Ok, great, that makes sense. Yes I’d like to see that get merged in.

> 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.

— 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: dev-unsubscr...@pdfbox.apache.org
>>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>> 
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org 
> 
> For additional commands, e-mail: dev-h...@pdfbox.apache.org 
>

Re: PDFBox Website [PDFBOX-3040]

2015-10-29 Thread Maruan Sahyoun


> Am 29.10.2015 um 19:44 schrieb John Hewson :
> 
> 
>> On 29 Oct 2015, at 02:47, Maruan Sahyoun  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/

into

https://svn.apache.org/repos/asf/pdfbox/cmssite/trunk/

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. 
> 
>> 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: dev-unsubscr...@pdfbox.apache.org
>> For additional commands, e-mail: dev-h...@pdfbox.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Re: PDFBox Website [PDFBOX-3040]

2015-10-29 Thread John Hewson


> On 29 Oct 2015, at 02:47, Maruan Sahyoun  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?

> 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. 

> 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: dev-unsubscr...@pdfbox.apache.org
> For additional commands, e-mail: dev-h...@pdfbox.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Re: PDFBox Website

2014-02-09 Thread Andreas Lehmkuehler


Hi,

Am 09.02.2014 14:21, schrieb Maruan Sahyoun:

Hi ..

I highlighted how to get help a little more on the home page as to direct 
people to use the mailing list and not Jira. Please take a look at 
http://pdfbox.staging.apache.org/index.html and let me know what you think.

Good idea, let's hope that people will read it before creating an Q&A JIRA


BR

Maruan Sahyoun


BR
Andreas Lehmkühler

Re: PDFBox Website

Re: PDFBox Website

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website [PDFBOX-3040]

Re: PDFBox Website

12 matches

Site Navigation

Mail list logo

Footer information